nerdexam
SAP

C_TB1200_10 · Question #77

While browsing through sales orders, a user sees gaps in the document records. What might have caused this? There are 2 correct answers to this question.

The correct answer is B. The user does not have data ownership permission to the documents. C. Header owner is selected for data ownership and the user only has a relationship with the row. Gaps in document records occur when data ownership settings restrict a user's visibility to only documents they "own" or have a relationship with. Option B is correct because if the user lacks the necessary data ownership permission for specific documents, those records are…

Implementation and Setup

Question

While browsing through sales orders, a user sees gaps in the document records. What might have caused this? There are 2 correct answers to this question.

Options

  • AHeader and row owner is selected for data ownership and the user only has a relationship with the
  • BThe user does not have data ownership permission to the documents.
  • CHeader owner is selected for data ownership and the user only has a relationship with the row
  • DThe documents were flagged in data ownership as No Restriction.

How the community answered

(40 responses)
  • A
    18% (7)
  • B
    73% (29)
  • D
    10% (4)

Explanation

Gaps in document records occur when data ownership settings restrict a user's visibility to only documents they "own" or have a relationship with. Option B is correct because if the user lacks the necessary data ownership permission for specific documents, those records are simply hidden from their view, creating numbered gaps in the sequence. Option C is correct because when only the Header Owner is set as the ownership criterion, a user who is linked only to the row-level owner - not the header owner - fails to meet that criterion and cannot see the document.

Option A is incorrect because when both Header and Row Owner are configured, the system typically applies OR logic, meaning a relationship with either the header or row owner grants visibility - so a user with at least one relationship would still see the document. Option D is incorrect because "No Restriction" is the opposite of the problem: it removes ownership filtering entirely, making documents visible to all users, which would eliminate gaps rather than cause them.

Memory tip: Think of it as a keyhole - the data ownership setting defines which keyhole exists (header, row, or both), and the user's relationship is the key. If the keyhole requires a header key but you only have a row key (Option C), or you have no key at all (Option B), the document stays locked and invisible, creating a gap.

Topics

#data ownership#document visibility#user permissions#authorization

Community Discussion

No community discussion yet for this question.

Full C_TB1200_10 Practice