Name: Quality Seal
Uploaded: 2025-3-24
Duration: 200 s
Description: Quality Seal

<p>about your learning experience to help us improve.</p>

You've completed

cleanFiles/bookmap_SAP_LeanIX_Course_en-US_learning-sap-com_lsc-prod.zip (MMCP-DROPZONE) - 2025-04-07T11:52:30.000Z

Understanding Quality Seals

SAP LeanIX

Quality Seal

Second, we want to recap on the functionality of Quality Seal within SAP LeanIX. The tab next to fields is Quality Seal. Quality Seals serve as a configurable mechanism designed to conduct regular data checks, thereby enhancing the reliability of data in SAP LeanIX. The actual usage is performed by the responsible person per fact sheet, guiding them through a pre-defined data quality assurance routine. Quality Seals combine collaborative editing with clear responsibility, and a rigorous governance process. The main concept is simple. It assigns accountability to the responsible or accountable user, subscription role, to approve the quality of a fact sheet whenever other users make a change to it. Moreover, you can define a specific time frame for when the Quality Seal should break and automatically transition to the check-needed state. The following states are available, check-needed, approved, draft, and rejected. In the tool configuration, you can define a time cadence for when this Quality Seal should trigger regularly. When the seal breaks, the fact sheet owner is responsible for reviewing the data, making updates if necessary, and changing the state from check needed to approved. Let us now have a look on how to set this up. Open the Quality Seals configuration. In the quality states, set a renewal interval that suits your needs. We recommend require requesting approval every six months and enabling the draft mode underneath. Consequently, the Quality Seal automatically breaks every six months, and the state switches to check needed, notifying the responsible person for each fact sheet that a data check is required. After checking the data, the responsible fact sheet subscriber set it to approved manually. If someone makes changes to the fact sheet within the six months, the quality state is automatically set to check needed. If you want to allow applications in the draft state to be rejected, also enable the rejected checkbox in the configuration. Under mandatory fields, you can define certain attributes as mandatory. With that, you can specify which tags, fields, subscriptions, or attributes must be filled in in order to change the quality state to approved. If no information is stored within the attributes defined as mandatory, the state cannot be set to approved. Unused or red-only fields shouldn't be defined as mandatory. This configuration tab will only be active when the draft state is enabled, as we did earlier within the quality state section. Within the box, you will see all the active and possible attributes that can be set as mandatory, and you can define multiple attributes as such. As a best practice, we suggest setting business criticality, life cycle, functional, and technical fit as mandatory fields for applications. The number of mandatory attributes should be chosen wisely to avoid unnecessary overwhelm for the responsible person.