orkungedik/SAP-basis-dataset huggingface dataset:
## 13.7.8  SAP Field Service Management Integration
SAP S/4HANA Service supports the integration with SAP Field Service Management.
SAP Field Service Management is integrated with SAP S/4HANA Service using SAP Cloud Integration and SAP Cloud Connector. The following diagram provides an overview of the integration.
## Overview of SAP Field Service Management Integration with SAP S/4HANA
<!-- image -->
For details on the installation and configuration steps, and security information required for the integration of SAP Field Service Management, see the product assistance for SAP S/4HANA on the SAP Help Portal at http:/ /help.sap.com/s4hana. Search for Integration with SAP Field Service Management .
For more information about security and data protection in SAP Field Service Management, see the documentation for SAP Field Service Management on the SAP Help Portal at http:/ /help.sap.com/viewer/ product/SAP\_FIELD\_SERVICE\_MANAGEMENT. Search for Security and Data Protection .
For additional information about security, see the following:
- In the Service Guide for SAP BTP Connectivity on SAP Help Portal at http:/ /help.sap.com/viewer/product/ CP\_CONNECTIVITY Search for security .
- In the Product Overview for SAP Cloud Integration on SAP Help Portal at http:/ /help.sap.com/viewer/ product/CLOUD\_INTEGRATION:
- Security, Cloud Foundry Environment
- Security, Neo Environment
- In the ABAP Platform Security Guide on SAP Help Portal at http:/ /help.sap.com
## 13.7.9  In-House Repair
## Role Administration
The following business roles are used for the SAP Fiori apps in In-House Repair:
| Business Role             | System             | Purpose                                                   |
|---------------------------|--------------------|-----------------------------------------------------------|
| SAP_BR_CUST_SRVC_REP_REPA | SAP Fiori frontend | Customer Service Representative - Manage In-House Repairs |
| SAP_BR_CUST_SRVC_MGR_REPA | SAP Fiori frontend | Customer Service Manager - Plan In- House Repairs         |
| SAP_BR_CUST_SRVC_TEC_REPA | SAP Fiori frontend | Service Technician - Perform In-House Repairs             |
For information on creating back-end users for In-House Repair, go to https:/ /help.sap.com/s4hana\_op\_2021 and search for Creating Authorization Roles for Catalogs .
## Network and Communication Security
## Communication Channel Security
The table below shows the communication channels used by In-House Repair, the protocol used for the connection, and the type of data transferred.
| Communication Path                                              | Protocol Used   | Type of Data Transferred   | Data Requiring Special Pro- tection                                                              |
|-----------------------------------------------------------------|-----------------|----------------------------|--------------------------------------------------------------------------------------------------|
| frontend client using SAP GUI for Windows to SAP Fiori frontend | HTTP/HTTPS      | URLs                       | Passwords, all sensitive data such as credit card informa- tion, customer data, and con- ditions |
| frontend client using a web browser                             | HTTP/HTTPS      | All application data       | Passwords, all sensitive data such as credit card informa- tion, customer data, and con- ditions |
## Data Storage Security
Data is stored in database tables of SAP NetWeaver AS. Depending on the user, no special data storage security measures are required. In-House Repair is a dependent application, so the leading application storage security applies to survey read or edit rights.
## ICF and Session Security
For more information on the services required to use the apps in In-House Repair, see Internet Communication Framework Security (ICF) in Service [page 609].
## Deletion of Personal Data
For more information about the available deletion functionality, see Deletion of Personal Data in Service [page 611].
## 13.7.13  Warranty Management
## Authorizations
Warranty (LO-WTY) uses the authorization concept provided by the AS ABAP. Therefore, the recommendations and guidelines for authorizations as described in the SAP NetWeaver AS Security Guide ABAP also apply.
The ABAP platform authorization concept is based on assigning authorizations to users based on roles. For role maintenance, use the profile generator (transaction PFCG ) on the AS ABAP.
##  Note
For more information about how to create roles, see the ABAP Platform Security Guide under User Administration and Authentication .
## Standard Authorization Objects
The table below shows the security-relevant authorization objects that are used.
| Authorization Object   | Description                                   |
|------------------------|-----------------------------------------------|
| C_WTY_ACT              | Warranty: Actions Authorization Object        |
| C_WTY_OBJ              | Warranty: Process Object Authorization Object |
| C_WTY_STAT             | Warranty: Status Authorization Object         |
## Deletion of Personal Data
Warranty (LO-WTY) might process data, such as personal data, that is subject to the data protection laws applicable in specific countries/regions. You can use SAP Information Lifecycle Management (ILM) to control the blocking and deletion of personal data. For more information, see the product assistance for SAP S/4HANA on SAP Help Portal at https:/ /help.sap.com/s4hana\_op\_2021 under Cross Components Data Protection .
<!-- image -->
## Relevant Application Objects and Available Deletion Functionality
| Application       | Provided Deletion Functionality                     |
|-------------------|-----------------------------------------------------|
| Warranty (LO-WTY) | Archiving Object : WTY_CLAIM ILM Object : WTY_CLAIM |
## Relevant Application Objects and Available EoP/WUC Functionality
| Application       | Implemented Solution (EoP or WUC)   | Further Information   |
|-------------------|-------------------------------------|-----------------------|
| Warranty (LO-WTY) | EoP check                           | Checks tables:        |
|                   |                                     | PNWTYH,PNWTYV         |
## Configuration: Simplified Blocking and Deletion
You configure the settings related to the blocking and deletion of business partner master data in Customizing for Cross-Application Components → Data Protection .
## 13.8 Sourcing and Procurement
## 13.8.6  Ariba Network Integration
If you want to use integration scenarios with the Ariba Network, see chapter 'Business Network Integration' at the end of this guide.
## 13.8.7  Supplier Management
## 13.8.7.2  Internet Communication Framework Security (ICF)
You should only activate those services that are needed for the applications running in your system. For Supplier Information and Master Data, the following services are needed:
- /sap/bc/ui5\_ui5/sap/slc\_qnr\_resps1
- /sap/bc/ui5\_ui5/sap/slc\_eval\_resps1
- /sap/bc/ui5\_ui5/sap/slc\_sup\_evals1
- /sap/bc/webdynpro/srmsmc/WDA\_I\_BP\_SUPPLIER
- /sap/bc/webdynpro/srmsmc/WDA\_I\_QNR\_OVP
- /sap/bc/webdynpro/srmsmc/WDA\_I\_SEP\_OVP
- /sap/bc/webdynpro/srmsmc/WDA\_I\_SES
- /sap/bc/webdynpro/srmsmc/WDA\_I\_SEV\_OVP
- /sap/opu/odata/sap/slc\_questionnaire\_response\_srv
- /sap/opu/odata/sap/C\_SUPLREVALRSPEVALUATEST\_CDS
- /sap/opu/odata/sap/C\_SUPLREVALRESPST\_CDS
- /sap/bc/webdynpro/srmsmc/wda\_puc
- /sap/bc/webdynpro/srmsmc/wda\_puc\_t
- /sap/bc/webdynpro/srmsmc/WDA\_QLB\_OVP\_MAIN
- /sap/bc/webdynpro/srmsmc/WDA\_QLB\_OVP\_TRNS
- /sap/bc/webdynpro/srmsmc/WDA\_QNR\_OVP\_TRNS
- /sap/bc/webdynpro/srmsmc/wda\_sep\_ovp\_trns
- /sap/bc/webdynpro/srmsmc/wda\_act
- /sap/bc/webdynpro/srmsmc/wda\_tsk
Use the transaction SICF to activate these services.
For more information about ICF security, see the respective chapter in the ABAP Platform Security Guide.
## 13.8.7.3  Data Storage Security
## Cookies
Supplier Information and Master Data uses a Web Dynpro user interfaces. The SAP Web AS must issue cookies and accept them.
## Attachments
You restrict the allowed MIME types and the file size of attachments. You do this in Customizing for Materials Management under Purchasing Supplier and Category Management for all business processes you want to use. You can do this in the following Customizing activities:
- Define MIME Types for Attachments
- Define Maximum Size for Attachments
The above listed activities are available under each of the business processes nodes in Customizing.
For information about virus scanning for attachments, see Virus Scanning [page 24] and Application-Specific Virus Scan Profile (ABAP) [page 674].
## Security-Relevant Logging and Tracing
Supplier Management uses change documents to track changes made to supplier evaluation responses, supplier evaluation scorecards, supplier's control data and supplier's sustainability data. You can display change documents as follows:
- Open transaction RSSCD100 .
- In the Object Class field enter the value from the table that is relevant for the business object you are looking for:
Object Classes per Business Object
| Object Class   | Business Object                |
|----------------|--------------------------------|
| /SRMSMC/S_SUST | Supplier's Sustainability Data |
| /SRMSMC/S_CTRL | Supplier's Control Data        |
| /SRMSMC/SES    | Supplier Evaluation Scorecard  |
| /SRMSMC/SRS    | Supplier Evaluation Response   |
## Registering the Change Document Object for Application Business Object
1. In the SAP development system, enter the transaction SPRO .
2. Choose SAP Reference IMG .
3. Navigate to SAP Customizing Implementation Guide Cross-Application Components Processes and Tools for Enterprise Applications Reusable Objects and Functions for BOPF Environment Maintain BOSpecific Change Document Objects .
4. Choose IMG Activity button.
5. Choose Continue in the dialog box.
6. Choose New Entries in the Change Documents Adaptor: BO Specific Settings overview window.
7. Enter the business object.
8. Enter the change document.
9. Enter the change document call back class.
10. Save your entries.
## Related Information
- Go to https:/ /help.sap.com/s4hana\_op\_2021, enter Services for Application Developers into the search bar, press Enter , open the search result with that title, and navigate to Change Documents .
- Go to https:/ /help.sap.com/s4hana\_op\_2021, enter Security Aspects for Lifecycle Management into the search bar, press Enter , open the search result with that title, and navigate to Auditing and Logging .
## 13.8.7.4  Application-Specific Virus Scan Profile (ABAP)
SAP provides an interface for virus scanners to prevent manipulated or malicious files from damaging the system. To manage the interface and what file types are checked or blocked, there are virus scan profiles. Different applications rely on default profiles or application-specific profiles.
The Web Dynpro user interfaces of Supplier Information and Master Data require that you activate the virus scan profile /SIHTTP/HTTP\_UPLOAD .
You must make the settings for the virus scan profile in Customizing for Materials Management under Purchasing Supplier and Category Management Virus Scan Interface
For more information about virus scanning, see Virus Scanning [page 24].
## 13.8.7.5  Deletion of Personal Data
## Use
Supplier and Category Management might process data (personal data) that is subject to the data protection laws applicable in specific countries. You can use SAP Information Lifecycle Management (ILM) to control the blocking and deletion of personal data. For more information, see the product assistance for SAP S/4HANA on the SAP Help Portal at http:/ /help.sap.com/s4hana &lt;choose your current on-premise release&gt; Product Assistance Cross Components Data Protection .
## Relevant Application Objects and Available EoP/WUC functionality
Supplier and Category Management uses the standard archiving and deletion functions that are available for the business partner functionality. Therefore, there is no dedicated end of purpose check (EoP) nor a where-used check (WUC) for Supplier and Category Management.
Supplier and Category Management in SAP S/4HANA doesn't maintain an own data model in the IRF. An exit was implemented and registered at the table cluster CA\_APMDBP\_DETAILS instead. This way, any object in Supplier and Category Management that contains personal data of a given subject will be listed in a normal run of the tool.
| Application                      | Provided Deletion Functionality                 |
|----------------------------------|-------------------------------------------------|
| Supplier and Category Management | Transaction used for deletion: SARA             |
|                                  | Archiving object relevant for deletion: CA_BUPA |
For more information, see the product assistance for SAP S/4HANA on the SAP Help Portal at http:/ /help.sap.com/s4hana &lt;choose your current on-premise release&gt; Product Assistance Cross Components Data Protection Archiving .
## Configuration: Simplified Blocking and Deletion
You configure the settings related to the blocking and deletion of customer and supplier master data in Customizing under Logistics General Business Partner Deletion of Customer and Supplier Master Data .
## Display of Blocked Suppliers
If suppliers have been blocked, they can no longer be used in any Supplier and Category Management WebDynpro applications. The supplier data is not deleted, but it is no longer visible. Any supplier-related
entries are displayed as Blocked Supplier and all supplier-related links are disabled. Evaluation scorecards for the blocked suppliers are not displayed in the scorecards list in the Display Scorecards app.
This change is relevant for the following apps:
- Manage Activities
- Monitor Tasks
- Manage Templates
Supplier blocking via CDS view functions in the following apps:
- Manage Purchasing Categories
- Display Scorecards
- Quick Create for Procurement-Related Activities
- Open Activities card on the Procurement Overview Page
- Monitor Responses
- Evaluate Suppliers
- Monitor Responses
## 13.8.8  Integration
## 13.8.8.1  SAP S/4HANA Procurement Hub Integration
SAP S/4HANA currently supports integration with the SAP ERP back-end systems.
## 13.8.8.1.1  Direct Connectivity
The SAP S/4HANA hub system communicates with the connected SAP ERP back-end systems through XML messages using peer-to-peer connectivity options in an asynchronous mode.
## 13.8.8.1.2  Mediated Connectivity
For mediated connectivity, the SAP S/4HANA hub system is connected through SAP Process Integration. The communication with the connected SAP ERP back-end systems is performed through XML messages in asynchronous mode.
## 13.8.8.1.4  Roles and Authorizations in the SAP ERP Back-end System
You can activate Forward Error Handling (FEH) to monitor and process purchase requisitions that fail to be copied to the SAP ERP back-end system.
Users that process entries in FEH need specific authorizations assigned to their users , as well as the following authorization objects:
| Authorization Object   | Description                              |
|------------------------|------------------------------------------|
| S_FEH_INTF             | Interface-specific authorization for FEH |
| /SAPPO/FLT             | Postprocessing Order Filter              |
| /SAPPO/ORD             | Postprocessing Order (DISPLAY and EDIT)  |
| /SAPPO/WLA             | Assignment of Worklist                   |
## 13.9 Supply Chain
## 13.9.1  Inventory
## 13.9.1.1  Inventory Management
## 13.9.1.2  Direct Store Delivery
## 13.9.1.2.1  Deletion of Personal Data
## Use
The Direct Store Delivery application might process data (personal data) that is subject to the data protection laws applicable in specific countries. You can use SAP Information Lifecycle Management (ILM) to control the blocking and deletion of personal data. For more information, see the product assistance for SAP S/4HANA on the SAP Help Portal at https:/ /help.sap.com/s4hana\_op\_2021 Product Assistance Cross Components Data Protection .
<!-- image -->
Relevant Application Objects and Available Deletion Functionality
| Application Object   | Detailed Description                           | Provided Deletion Functionality                 |
|----------------------|------------------------------------------------|-------------------------------------------------|
| Visit List           | Archiving Visit Lists (LE-DSD)                 | Archiving object /DSD/VL                        |
| Settlement Documents | Archiving Settlement Documents (LE- DSD)       | Archiving object /DSD/SL                        |
| DEX                  | Archiving DEX Streams (LE-DSD)                 | Archiving object /DSD/DEX                       |
| Route Settlement     | Data destruction in Route Settlements (LE-DSD) | Destruction object /DSD/ HH_RAHD_DESTRUCTION    |
| DSDConnector         | Data destruction in DSDConnector (LE-DSD)      | Destruction object /DSD/ ME_TOUR_HD_DESTRUCTION |
| DSDLoading           | Data destruction in DSDLoading (LE- DSD)       | Destruction object /DSD/ SV_LC_HD_DESTRUCTION   |
| Visit Plan           | Data destruction in Visit Plants (LE- DSD)     | Destruction object /DSD/ VC_VPH_DESTRUCTION     |
| Deal Conditions      | Data destruction in Deal Conditions (LE-DSD)   | Destruction object /DSD/ PR_HEAD_DESTRUCTION    |
## Relevant Application Objects and Available EoP Functionality
| Application              | Implemented Solution (EoP or WUC)   | Further Information                                                                    |
|--------------------------|-------------------------------------|----------------------------------------------------------------------------------------|
| Logistics Execution (LE) | EoP check                           | This includes the business in the areas of: • Direct Store Delivery (Backend) (LE-DSD) |
## Configuration: Simplified Blocking and Deletion
You configure the settings related to the blocking and deletion of business partner master data in Customizing for Cross-Application Components under Data Protection .
- Define the settings for authorization management in Customizing for Cross-Application Components under Data Protection Authorization Management . For more information, see the Customizing documentation.
- Define the settings for blocking in Customizing for Cross-Application Components under Data Protection Blocking and Unblocking Business Partner .
## 13.9.1.3  Internet Communication Framework Security (ICF)
You should only activate those services that are needed for the applications running in your system. For Logistics Execution, the following services are needed:
- LECI
- VL31W
- VL32W
- VLPODW1
- VLPODW2
Use the transaction SICF to activate these services.
If your firewall(s) use URL filtering, also note the URLs used for the services and adjust your firewall settings accordingly.
For more information about ICF security, see the respective chapter in the ABAP Platform Security Guide.
## 13.9.1.4  Deletion of Personal Data in Batch Management
## Use
The Batch Management application might process data (personal data) that is subject to the data protection laws applicable in specific countries. You can use SAP Information Lifecycle Management (ILM) to control the blocking and deletion of personal data. For more information, see the product assistance for SAP S/4HANA on the SAP Help Portal at https:/ /help.sap.com/s4hana\_op\_2021 Product Assistance Cross Components Data Protection .
## Relevant Application Objects and Available Deletion Functionality
| Application      | Detailed Description                           | Provided Deletion Functionality   |
|------------------|------------------------------------------------|-----------------------------------|
| Batch Master     | Archiving Batch Master Records (LO- BM)        | Archiving object LO_BATCH         |
| Batch Where-Used | Archiving Batch Where-Used Records (LO-BM-WUL) | Archiving object LO_CHVW          |
## Relevant Application Objects and Available End of Purpose (EoP) functionality
| Application              | Implemented Solution       | Further Information                                                                                                                                                                                                                                                                                                                                                        |
|--------------------------|----------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| Batch Management (LO-BM) | End of purpose check (EoP) | For more information about the end of purpose check, see the product assis- tance for SAP S/4HANA on the SAP Help Portal at https:/ /help.sap.com/ s4hana_op_2021 under Product Assistance Enterprise Technology Data Archiving (CA-ARC) Logistics General (LO) Data Archiving in Batch Management (LO-BM) Business Partner End of Purpose (EoP) Check in Batch Management |
## Configuration: Simplified Blocking and Deletion
You configure the settings related to the blocking and deletion of business partner master data in Customizing for Cross-Application Components under Data Protection .
- Define the settings for authorization management in Customizing for Cross-Application Components under Data Protection Authorization Management . For more information, see the Customizing documentation.
- Define the settings for blocking in Customizing for Cross-Application Components under Data Protection Blocking and Unblocking Business Partner .
## 13.9.1.5  Returnable Packaging and Empties Management
## 13.9.1.5.1  Deletion of Personal Data (Returnable Packaging Logistics)
## Use
Returnable Packaging Logistics might process data (personal data) that is subject to the data protection laws applicable in specific countries. You can use SAP Information Lifecycle Management (ILM) to control the blocking and deletion of personal data. For more information, see the product assistance for SAP S/4HANA on the SAP Help Portal at https:/ /help.sap.com/s4hana\_op\_2021 Product Assistance Cross Components Data Protection .
## Relevant Application Objects and Available Deletion Functionality
| Application                              | Provided Deletion Functionality   |
|------------------------------------------|-----------------------------------|
| Returnable Packaging Logistics (IS-A-RL) | Archiving Object                  |
|                                          | VHURL_AC                          |
|                                          | VHURL_CP                          |
|                                          | VHURL_PO                          |
|                                          | VHURL_ST                          |
|                                          | VHURL_TR                          |
|                                          | Destruction Objects               |
|                                          | VHURL_CP_DESTRUCTION              |
|                                          | VHURL_RR_DESTRUCTION              |
|                                          | ILM Objects                       |
|                                          | VHURL_AC                          |
|                                          | VHURL_PO                          |
|                                          | VHURL_ST                          |
|                                          | VHURL_TR                          |
|                                          | VHURL_CP_DEST                     |
|                                          | VHURL_RR_DEST                     |
## Relevant Application Objects and Available EoP/WUC functionality
| Application                           | Implemented Solution (EoP or WUC)   | Further Information     |
|---------------------------------------|-------------------------------------|-------------------------|
| Returnable Packaging Logistics (IS-A- | EoP check                           | Checks tables:          |
| RL)                                   |                                     | RLACCT, RLPSHPA, RLPSHP |
## Configuration: Simplified Blocking and Deletion
You configure the settings related to the blocking and deletion of business partner master data in Customizing for Cross-Application Components → Data Protection → Blocking and Unblocking of Data → Customer Master/ Supplier Master Deletion .
## 13.9.1.5.2  Recycling Administration
## 13.9.1.5.2.2  Data Protection and Privacy
Data protection is associated with numerous legal requirements and privacy concerns. In addition to compliance with general data privacy acts, it is necessary to consider compliance with industry-specific legislation in different countries. This section describes the specific features and functions that Recycling Administration provides to support compliance with the relevant legal requirements and data privacy.
##  Note
Recycling Administration (IS-REA) is integrated in the central ILM check processes. If you use REA, the central ILM check processes also take the REA specific privacy related data (supplier, customer) into account. Only when REA reports back that this data is no longer used within this component, the system can block the corresponding REA data.
This section and any other sections in this Security Guide do not give any advice on whether these features and functions are the best method to support company, industry, regional or country-specific requirements. Furthermore, this guide does not give any advice or recommendations with regard to additional features that would be required in a particular environment; decisions related to data protection must be made on a case-bycase basis and under consideration of the given system landscape and the applicable legal requirements.
##  Note
In the majority of cases, compliance with data privacy laws is not a product feature. SAP software supports data privacy by providing security features and specific data-protection-relevant functions such as functions for the simplified blocking and deletion of personal data. SAP does not provide legal advice in any form. The definitions and other terms used in this guide are not taken from any given legal source.
## 13.9.2  Delivery and Transportation
## 13.9.2.2  Transportation Management
This section of the guide for SAP S/4HANA, on-premise edition contains information on tasks specific to Transportation Management.
## 13.9.2.2.5  Depersonalization of Data
Transportation Management (TM) may process data (personal data) that is subject to the data protection laws applicable in specific countries.
When you use the scenario builder from your productive system, the scenario builder may process your personal data. Hence you must use the BAdI /SCMTMS/SB\_ADD\_TEMPLATE\_DATA to depersonalize data before using it in the scenario builder.
This BAdI contains the method CHECK\_AND\_ADJUST\_DATA . This method processes the data that you have selected to use in the scenario builder.
For more information on example implementation of how you can access the data in the BAdI, see /SCMTMS/ SB\_ADD\_TEMPL\_DATA\_SMPL .
## 13.9.3  Warehousing
## 13.9.3.1  Extended Warehouse Management
## 13.9.3.1.2  Internet Communication Framework Security (ICF)
You should only activate those services that are needed for the applications running in your system. For this area the following services are needed:
- /sap/bc/gui/sap/its/scwm/rfui This service can be used, for example, to allow warehouse workers to use transaction from
- . In SAP Library choose SAP S/4HANA Enterprise Business Applications Supply Chain Extended Warehouse Management Radio Frequency Framework Work Processing Using Radio Frequency Resource Management Using Radio Frequency .
/SCWM/RFUI mobile applications. The service can be accessed from the SAP console or by using ITS mobile. For more information, see SAP Library for SAP S/4HANA at https:/ /help.sap.com/s4hana
- /sap/bc/webdynpro/scwm/ In this path various Web Dynpro user interfaces (UIs) for Extended Warehouse Management as well as for SAP Dock Appointment Scheduling are contained.
- /sap/bc/srt/xip/scwm Contains services which are used for SAP Process Integration communication.
- /sap/bc/srt/rfc/scwm Contains services which are used for remote function call (RFC) communication. For example, RFID\_AII\_EWM which is used to exchange radio frequency identification information with SAP Auto-ID
Infrastructure (SAP AII).
Use the transaction SICF to activate these services.
If your firewall(s) use URL filtering, also note the URLs used for the services and adjust your firewall settings accordingly.
For more information about ICF security, see the respective chapter in the ABAP Platform Security Guide.
## 13.9.3.1.5  Enterprise Services Security
For general information, see the chapters on Web Services Security in the ABAP Platform Security Guide and in the SAP Process Integration Security Guide.
## 13.9.3.2  Deletion of Personal Data
## Use
Location master data may contain personal data that is subject to the data protection laws applicable in specific countries. You can use SAP Information Lifecycle Management (ILM) to control the blocking and deletion of personal data. For more information, see the product Assistance for SAP S/4HANA on the SAP
Help Portal at https:/ /help.sap.com/s4hana\_op\_2021 Product Assistance Enterprise Business Applications Manufacturing Production Planning and Detailed Scheduling Master Data Location Data Protection
## Relevant Application Objects and Available Deletion Functionality
| Application             | Detailed Description                                                         | Provided Deletion Functionality                                                                                                                                                                                                     |
|-------------------------|------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| SCMLocation             | Without ILM                                                                  | You can run the report /SAPAPO/ DELETE_LOCATIONS from the SAP Easy Access menu, under SAP Menu Logistics SCMExtended Warehouse Management SCMBasis Master Data Location ; select the loca- tion, then choose Extras Delete Location |
| ILM-enabled SCMLocation | Refer to What's New for ILM-re- lated Information for SCMLocation (SCMB_LOC) | Destruction object /SCMB/LOC ILM object SCMB_LOC                                                                                                                                                                                    |
## Relevant Application Objects and Available EoP/WUC functionality
| Application   | Implemented Solution (EoP or WUC)   | Further Information   |
|---------------|-------------------------------------|-----------------------|
| SCMLocation   | End of Purpose (EoP) check          |                       |
## Configuration: Simplified Blocking and Deletion
You configure the settings related to the blocking and deletion of location master data in Customizing for SCM Extended Warehouse Management under SCM Basis Master Data Location Location Master Data Deletion .
## 13.9.4  Advanced Order Promising
## 13.9.4.1  Deletion of Personal Data in advanced Available-toPromise (aATP)
## Use
The applications in advanced Available-to-Promise (aATP) may process data (personal data) that is subject to the data protection laws applicable in specific countries. You can use SAP Information Lifecycle Management (ILM) to control the blocking and deletion of personal data. For more information, see the product assistance for SAP S/4HANA on the SAP Help Portal at https:/ /help.sap.com/s4hana\_op\_2021 under Product Assistance Cross Components Data Management .
## Relevant Application Objects and Available Deletion Functionality
| Component   | Application                          | Deletion Functionality          | Deletes/Destroys                                                                | Program                 |
|-------------|--------------------------------------|---------------------------------|---------------------------------------------------------------------------------|-------------------------|
| CA-ATP-BOP  | ATP: Backorder Proc- essing          | ATP_BOP_CSS_DESTR UCTION        | Custom sort sequen- ces                                                         | ATP_BOP_CSS_DES         |
| CA-ATP-BOP  | ATP: Backorder Proc- essing          | ATP_BOP_SEG_DESTR UCTION        | Segments                                                                        | ATP_BOP_SEG_DES         |
| CA-ATP-CTL  | ATP: Controller &Cen- tral Functions | AATP_CHARC_CTLG_D ESTRUCTION    | Blocked parent path values of value groups, blocked authorization values groups | AATP_CHARC_CATALO G_DES |
| CA-ATP-CTL  | ATP: Controller &Cen- tral Functions | ATP_CHECK_LOG_DES TRUCTION      | ATP check logs                                                                  | ATP_CHECK_LOG_DES       |
| CA-ATP-OVD  | ATP: Object and Value Determination  | ATP_OVD_ALTVCTRL_ DESTRUCTION   | Alternative controls                                                            | ATP_OVD_ALTVCTRL_ DES   |
| CA-ATP-OVD  | ATP: Object and Value Determination  | ATP_OVD_SUBSTNCTR L_DESTRUCTION | Substitution controls                                                           | ATP_OVD_SUBSTNCTR L_DES |
| CA-ATP-PAL  | ATP: Product Alloca- tion            | AATP_PROD_ALLOC_D ESTRUCTION    | Product allocation data                                                         | AATP_PROD_ALLOC_D ES    |
| CA-ATP-SUP  | SUP: Supply Protec- tion             | ATP_SUP_DESTRUCTI ON            | Supply protection ob- jects, supply protec- tion groups                         | ATP_SUP_DES             |
## Configuration: Simplified Blocking and Deletion
You configure the required Customizing settings for the blocking and unblocking of business partner master data in SAP Reference IMG Cross-Application Components Data Protection Blocking and Unblocking of Data Business Partner Master Data .
For the deletion of business partner master data, you configure the settings in SAP Reference IMG CrossApplication Components Data Protection Deletion of Data Deletion of Business Partner Data .
## 13.10  Cross-Line-of-Business
## 13.10.1  Commodity Management
## 13.10.1.1  Commodity Procurement
## 13.10.1.2  Commodity Risk Management
## 13.10.1.2.1  Deletion of Personal Data
## Use
Commodity Risk Management might process data (personal data) that is subject to the data protection laws applicable in specific countries. You can use SAP Information Lifecycle Management (ILM) to control the blocking and deletion of personal data. For more information, see the product assistance for SAP S/4HANA on the SAP Help Portal at https:/ /help.sap.com/s4hana\_op\_2021 Product Assistance Cross Components Data Protection .
See also the documentation under SAP S/4HANA on the SAP Help Portal at https:/ /
help.sap.com/s4hana\_op\_2021 Product Assistance Enterprise Business Applications Cross-Line-ofBusiness Commodity Management Commodity Risk Management Data Management in Commodity Risk Management .
## Relevant Application Objects and Available Deletion Functionality
| Application          | Detailed Description                             | Provided Deletion Functionality                               |
|----------------------|--------------------------------------------------|---------------------------------------------------------------|
| Order Request        | Archiving Order Requests (FSCM-FIN- CDOTE)       | Archiving object CMMFODOF_OF                                  |
| Order Fill           | Archiving Order Fills (FSCM-FIN- CDOTE)          | Archiving object CMM_FSA_SA , ILM ob- ject CMMFDOF_OF         |
| Commodity Subaccount | Archiving Commodity Subaccounts (FSCM-FIN-CDOTE) | Archiving object CMMFSA_SA , ILM ob- ject CMMFDOF_SUB_ACCOUNT |
Archiving and deletion of data is performed as follows:
1. Archiving objects are created with transaction AOBJ .
2. For each archiving object, the ILM object is defined with transaction IRM\_CUST .
3. Start transaction SARA and proceed as follows:
- Perform action Preproc . The data relevant for archiving is identified and marked for archiving.
- Perform action Write . The data marked for archiving is written to an archive file.
- Perform action Read . The archived data is displayed.
- Perform action Delete . The archived data is removed from the archive as well as from the database. This data is not available for any post processing anymore.
## 13.10.1.2.2  Change Logging
Personal data is subject to frequent changes. Therefore, for revision purposes or as a result of legal regulations, it may be necessary to track the changes that have been made to this data.
A change log is provided for the following fields of Commodity Derivative Order and Trade Execution (FSCM-FINCDOTE):
- Reference Account (Broker)
- Broker
- Creation Time
- Creation Date
- Changed By
- Decided By
- Decided On
To get change information for the following documents, run transaction SE38 , and perform the program RSSCD200 :
| Change Document Object   | Description                                     |
|--------------------------|-------------------------------------------------|
| CMM_AD_BO                | Commodity Management: Accrual Document          |
| CMMFDOF_CD_FILL          | Commodity Order Fill Change Document            |
| CMMFDOF_FL_PKT           | Change Document for Commodity Order Fill Packet |
| CMMFDOR_OR_DOC           | Commodity Derivative Order Assigned Documents   |
| CMMFDOR_OR_LEG           | Commodity Derivative Order Assigned Legs        |
| CMMFDOR_OR_REQ           | Commodity Derivative Order Request              |
| CMMFSA_CDO_SA            | Commodity Subaccount Change Structure           |
## 13.10.1.3  Commodity Sales
## 13.11  Analytics Technology
## 13.11.1  Process Performance Monitoring
## 13.11.1.1  Process Observer
## 13.11.1.1.2  Data Protection and Privacy in Process Observer
##  Caution
If you configure Process Observer in a way that it stores personal data, you are responsible for ensuring that you are compliant with the data protection laws applicable in the relevant countries.
For more information about configuring Process Observer, see the product assistance for SAP S/4HANA on the SAP Help Portal at https:/ /help.sap.com/s4hana\_op\_2021 Product Assistance Cross Components Process Observer (CA-EPT-POC) Process Monitoring and Analytics Process Monitoring Setup .
## 13.11.1.1.3  Deletion of Personal Data in Process Observer
Depending on your configuration, Process Observer might process data (personal data) that is subject to the data protection laws applicable in specific countries. You can use the following transactions to delete process log data:
- POC\_DELETE\_LOG
- POC\_MASS\_DELETE
For more information about the deletion and mass deletion of process log data, see the product assistance for SAP S/4HANA on the SAP Help Portal at https:/ /help.sap.com/s4hana\_op\_2021 Product Assistance Cross Components Process Observer (CA-EPT-POC) Operations Reports Reports Used in Operations for Process Monitoring .
## 13.12  Enterprise Technology
## 13.12.1  Master Data Maintenance
## 13.12.2  Enterprise Contract Management
## 13.12.2.3  Version Management of Legal Documents Sent for e-Signature
For e-Signature of legal documents, Enterprise Contract Management provides integration with DocuSign. However, you can use different service providers other than DocuSign.
##  Note
It is very important to note that SAP does not validate the content of the document sent for e-Signature to any providers including DocuSign. SAP is not responsible for content modifications in the version of the document sent by the e-Signature provider/signor.
## 13.12.3  Geographical Enablement Framework
## 13.12.3.1  Authorizations
The framework uses the authorization concept provided by the Application Server ABAP and SAP HANA Platform. Therefore, the recommendations and guidelines for authorizations as described in the SAP Netweaver Application Server, ABAP Security Guide and HANA platform also apply to SAP Geographical Enablement Framework. The SAP authorization concept is based on assigning authorizations to users based on roles. For role maintenance in application server ABAP (AS ABAP), use the profile generator transaction PFCG in the backend system.
## Standard Roles
The table below provides the standard roles that are used by the framework.
| Roles                   | Description                                                                                                                                                                                                                                      |
|-------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| sap.gef.data::gef_user  | Delivered in SAP HANADUfor the SAP Geographical Enable- ment Framework; it provides basic authorization to access the framework schema in SAP HANA(SAP_GEF). You can assign this role to SAP_GEF_USER or other reference users that are created. |
| sap.gef.data::gef_admin | In addition to all the authorizations provided in the gef_user role, this admin role provides advanced authori- zations for administrative tasks.                                                                                                |
For AS ABAP, the PFCG role template, SAP\_GEF\_USR is delivered. This template provides basic authorizations for the framework. Other authorization roles, if needed for accessing application data, need to be added to create PFCG roles for consuming the framework services.
## Standard Authorization Objects
The table below shows the security-relevant authorization objects that are used.
| Authorization   | Object     | Field Value         |
|-----------------|------------|---------------------|
| G_GEF_GEOM      | GEF_BO_ID  | Business Object ID  |
|                 | GEF_CONTXT | Geometry Context ID |
|                 | ACTVT      | Activity            |
## 13.12.3.2  Internet Communication Framework Security (ICF)
You should only activate the services that are needed for the applications running in your system. For this area the following services are needed:
- /default\_host/sap/ca/GEF/arcgis/rest/services In this path, the framework can provide services that conform to the specifications of different GIS service providers, if a custom GIS plug-in is developed and customized. For more information, see the Application Implementation section in the Geographical Enablement Framework documentation.
- /default\_host/sap/ca/GEF/rest/config In this path, the framework provides configuration information. This service is independent from any GIS service providers.
- /default\_host/sap/bc/ui5\_ui5/sap/gef\_ui The UI (Geometry Explorer and Geometry Editor) has been delivered to work with our framework. The UI starts from this path.
Use transaction SICF to activate these services.
If your firewall(s) uses URL filtering, also note the URLs used for the services and adjust your firewall settings accordingly.
For more information about ICF security, see the respective chapter in the ABAP Platform Security Guide.
## 13.12.3.3  Data Protection and Privacy
The SAP Geographical Enablement Framework does not collect, store, or process users' personal data. However, applications built on it may. Therefore, SAP recommends activating secure session management. We also recommend that you use SSL to protect the network communications where these security-relevant cookies are transferred.
Read access logging (RAL) monitors and logs read access to sensitive data, if any. It is required for applications to comply with legal regulations or public standards such as data privacy. In most cases, applications rely on the underlying business suite to save sensitive data. Therefore, it is also recommended to refer to the documents of the underlying platforms and activate the RAL based on the needs.
## 13.12.3.4  Enterprise Services Security
A technical limitation (tracked in security message 1670119508) has been identified; not all the user controlled inputs are sufficiently validated or encoded. This may cause security issues like Cross-Site Scripting (XSS).
This issue has been investigated and a solution is being implemented at this time. Contact SAP for the availability of this solution.
## 13.12.4  Master Data Governance
## 13.12.5  Agent Framework
## 13.12.5.1  Deletion of Personal Data in Agent Framework
The Agent Framework might process data (personal data) that is subject to the data protection laws applicable in specific countries as described in SAP Note 1825544 .
The Agent Framework works in conjunction with the Change Notification Service (CA-GTF-TS-CNS). The Change Notification Service represents an Agent Framework Event (such as a limit change to an account) in the form of a change pointer. Each change pointer is based on an export object.
In addition to the change pointers generated for an export object, the CNS can be configured to also provide images of the export object events. Depending on the export object type, these images might contain personal data. For data protection reasons, you must delete the image data at regular intervals. You should therefore schedule a regular job to call one of the two deletion reports CNS\_CP\_DELETE or CNS\_DP\_DELETE\_MULT . For this, you can use the simplified, integrated job control in the Agent Framework available in Customizing for Cross-Application Components General Application Functions Agent Framework .
## More Information
For more information, see the product assistance for SAP S/4HANA on the SAP Help Portal at https:/ / help.sap.com/s4hana\_op\_2021 and go to
- Cross Components Data Protection .
## 13.13  SAP S/4HANA Industries
## 13.13.1  Consumer
## 13.13.1.1  Agriculture
## 13.13.1.1.1  Agricultural Contract Management