In SAP Leanix, how does the quality seal's renewal interval contribute to data quality assurance?

Question

Options

• AIt triggers automatic approval of fact sheets.
• BIt triggers the quality seal to break and thus switches the state to "check needed
• CIt triggers automatic rejection of fact sheets.
• DIt triggers the quality seal to break and thus switches the state to "draft".

• A
  3% (1)
• B
  89% (33)
• C
  5% (2)
• D
  3% (1)

Explanation

In SAP LeanIX, the quality seal has a configurable renewal interval that acts as a time-based expiry mechanism - when the interval elapses without re-approval, the seal automatically "breaks," moving the fact sheet's state to "check needed" so that data owners are prompted to review and re-validate the information, ensuring ongoing data accuracy. Option B is correct because this is precisely how LeanIX enforces continuous data quality: the seal doesn't persist indefinitely, it expires and flags the record for human review.

Why the distractors are wrong:

• A & C are wrong because the system never auto-approves or auto-rejects fact sheets - human review is required; automation only flags the need for action.
• D is wrong because the state transitions to "check needed", not "draft" - "draft" indicates an unpublished/incomplete fact sheet, which is a different lifecycle stage entirely.

Memory tip: Think of the quality seal like a food expiry date - when it expires, the item isn't thrown away (rejected/drafted), it's just flagged for someone to check whether it's still good. "Renewal interval → check needed" is the key chain to remember.

No community discussion yet for this question.