4.5.1 Deletion of Personal Data in Quality Management
This feature enables you to block and delete personal data in a simplified way by using SAP Information Lifecycle Management (ILM).
Personal data collected in business partner master data can be blocked as soon as business activities that use this data are completed and the residence time for the data has elapsed; after this time, only users with additional authorizations can access this data.
When the retention period for data expires, personal data can be destroyed completely so that it can no longer be retrieved. Retention periods must be defined in the customer system.
Technical Details
Table 202:
Product Feature is New
Country Dependency Valid for all countries
Application Component QM
Availability SAP S/4HANA 1709
Additional Details
Based on the retention period defined for data in the customer system, an end of purpose (EoP) check determines whether this data is still relevant for business activities. The retention period is part of the overall lifecycle of personal data, which consists of the following phases:
● Business activity: The relevant data is used in ongoing business, for example, contract creation, delivery, payment.
What's New in SAP S/4HANA 1709
Manufacturing P U B L I C 189
● Residence period: The data remains in the database and can be used in case of subsequent processes related to the original purpose, for example, reporting obligations.
● Blocking period: The relevant data needs to be retained for legal reasons. During the blocking period, business users of SAP applications are prevented from displaying and using this data; it can only be processed in case of mandatory legal provisions.
● Deletion: The data is deleted and no longer exists on the database.
Blocking of data can impact system behavior in the following ways:
● Display: The system does not display blocked data.
● Change: It is not possible to change a business object that contains blocked data.
● Create: It is not possible to create a business object that contains blocked data.
● Copy/Follow-Up: It is not possible to copy a business object or perform follow-up activities for a business object that contains blocked data.
Only users with special authorization can display blocked data; they are not authorized, however, to create, change, or copy business objects with blocked data, or perform follow-up activities with these business objects.
Effects on Customizing
To use SAP Information Lifecycle Management (ILM) to simplify the deletion of application-specific personal data:
● Activate the business function Information Lifecycle Management (ILM).
● Make the necessary Customizing settings related to SAP Information Lifecycle Management (ILM) in Customizing for SAP NetWeaver Application Server Basis Services Information Lifecycle Management .
● Run transaction ILMARA and maintain and activate the required audit areas for the ILM objects of the application.
● Run transaction IRMPOL and maintain the required retention policies for the ILM objects of the application.
To use the new functions to simplify the blocking and deletion of business partner master data:
● Activate the business function ILM-Based Deletion of Business Partner Data (BUPA_ILM_BF).
● Make the necessary customizing settings related to the blocking and deletion of business partner master data in Customizing for Cross-Application Components Data Protection .
To use the new functions to simplify the blocking and deletion of customer and supplier master data:
● Activate the following business functions:
● ILM-Based Deletion of Business Partner Data (BUPA_ILM_BF)
● ILM-Based Deletion of Customer and Supplier Master Data (ERP_CVP_ILM_1)
● Make the necessary customizing settings related to the blocking and deletion of customer and supplier master data in Customizing for Logistics - General Business Partner Deletion of Customer and Supplier Master Data
190 P U B L I C
What's New in SAP S/4HANA 1709 Manufacturing
See Also
For more information about the deletion of personal data in Quality Management see help.sap.com S/
4HANA 1709 :
● Product Assistance SAP S/4HANA Cross Components :
○ SAP Information Lifecycle Management
○ Data Protection Deletion of Business Partner, Customer and Supplier Master Data
○ Data Protection Configuring Data Protection Features Activating Business Functions
● Security Guide
○ Data Protection
○ SAP S/4HANA Enterprise Management Manufacturing Quality Management Data Protection .
● SAP Notes:
○ 1825544
○ 2007926
4.5.2 Authorization Objects in Quality Management
This feature enables you to define authorizations in Quality Management in a more consistent way. To make this possible, new authorization objects have been introduced that contain authorization fields for activities (create, edit, and so on).
Some existing authorization objects did not contain any activities. Authorization was checked using the
authorization object Q_TCODE (transaction code) instead, which also needed to be maintained. Since transaction codes are no longer relevant for Fiori apps, the old authorization objects are gradually being replaced by new authorization objects with activities.
The new authorization objects will replace the old authorization objects in the medium term. The old authorization objects will be deleted in the release after the next one. Until then, they remain valid. That means the new
What's New in SAP S/4HANA 1709
Manufacturing P U B L I C 191
authorization objects are checked in addition to the old authorization objects. The new objects were also assigned to the authorization profile SAP_NEW.
If you maintained the old authorization objects in a previous release, you do not need to maintain the new authorization objects immediately for existing functions as well, but only for new functions. However, we recommend that you change your authorizations over to the new authorization objects as soon as possible.
The following table shows which new authorization object replaces which old authorization objects.
Table 204:
New Authorization Object Replaces Following Old Authorization Objects
Comment
Q_CGRP_ACT Q_CAT_GRP and Q_TCODE Authorization for editing code groups
and codes
Q_CSSET_ACT Q_CAT_SSET and Q_TCODE Authorization for editing selection sets
Q_MINSPCHR Q_MASTERD, Q_STA_QPMK and Q_TCODE Authorization for editing master inspec
tion characteristics
Q_INSPMETH Q_MASTERD, Q_STA_QPTB and Q_TCODE Authorization for editing inspection methods
Q_SMPLPROC Q_TCODE Authorization for editing sampling pro
cedures
Q_DYNMODRL Q_TCODE Authorization for editing dynamic modi
fication rules
Q_QIRECPRC Q_MATERIAL und Q_TCODE Authorization for editing quality info re
cords for procurement
Q_SMPLSCHM Q_TCODE Authorization for editing sampling
schemes
Q_QLEVEL Q_MATERIAL and Q_TCODE Authorization for editing quality levels
Q_INSPPNT Q_TCODE Authorization for editing inspection
points
Effects on System Administration
1. Assign the authorization profile SAP_NEW to your roles.
192 P U B L I C
What's New in SAP S/4HANA 1709 Manufacturing
2. Enter the new authorization objects in your roles and maintain the authorizations for the new authorization objects. Note that the old objects will initially still be checked as well.
3. Then remove the authorization profile SAP_NEW again so the newly maintained authorizations become effective.