Enterprise Resource Planning Blogs by SAP
Get insights and updates about cloud ERP and RISE with SAP, SAP S/4HANA and SAP S/4HANA Cloud, and more enterprise management capabilities with SAP blog posts.
Showing results for 
Search instead for 
Did you mean: 
Product and Topic Expert
Product and Topic Expert
With 1911 release of SAP Business ByDesign Cloud ERP we introduce a new dimension to manage data privacy with the new information lifecycle management work center.

So with 1911 we recommend to use only the new information lifecycle management work center and it's configuration and to retire the old data protection and privacy work center.

To move to the new information lifecycle based data privacy management you need to do the following:

  1. Business Configuration: Activate scoping element “Information Lifecycle Management”

  2. Business Configuration: Double check that you have activated the scoping question “Read Access Logging” under Security/System Management (this is unchanged but has been moved to the ILM work center)

  3. Business Configuration: Configure the new retention periods for business documents

  4. Assign information lifecycle management work center to the administrator or data privacy officer

  5. Double check that you have activated the read access log field groups (this is unchanged but has been moved to the ILM work center)

  6. Activate the document lifecycle KPIs for the data privacy officer or other users

Here you can find more details regarding configuration.

Please be aware that the information provided in this blog is describes the old functionality to have a reference. The new functionality can be found in this blog.

Here is quick overview on what ByDesign has offered until 1908 to support data privacy. Please do not use it in parallel with the new information lifecycle management work center introduced in 1911:

  1. Data Protection & Privacy Work Center for Data Privacy Officers: Allows to disclose and delete personal data across business scenarios including custom add-ons by partners (PDI). Support for all natural persons like private accounts, contacts, internal and external employees and for leads without reference to account master data.

  2. Data Retention Periods: Configure minimal retention periods for key business documents in order to control deletion.

  3. Block usage of data: Manually or automatically block usage of data for new business processes.

  4. Logging: Change logs and read access logs for special categories of personal data like religion, bank etc.

  5. Marketing permissions: Manage the natural persons consent for marketing communication.

  6. Authorization: Grant and revoke access to data only to users which need the data.

  7. More information: Most important links on GDPR, Business ByDesign, SAP and it's data centers, certifications, security measures and privacy by design.

The demo video below gives you an impression on how this works in detail:

1. Central Data Protection & Privacy Work Center

As you have seen in the demo the data privacy expert can use the data privacy work center to easily find employees, service agents (i.e. external employees) or private accounts (1) and block data for usage or trigger the deletion (3). Additionally he can generate a synopsis for master and transaction data which is stored for a natural person in the system (2) as you can see in the screenshots below.

Data disclosure and deletion of personal data coming from custom add-ons is also supported by using the cloud application development studio (PDI). Since 1711 customers and partners are enabled to identify all the personal data stored in add-on BO’s using ABSL coding and to include it for disclosure, anonymization or deletion. Here you find a good tutorial on how this works.

2. Configuration of data retention periods

Furthermore you can define in the business configuration the data retention periods for multiple business areas and countries which control that data cannot be deleted within the minimal retention period.

3. Block usage of data for new business

Besides disclosing and deleting natural persons data it is also possible to manually or automatically block it for usage in new business processes:

  1. Blocked persons will not appear in master data work centers, value helps & webservices and cannot be used for new business processes anymore.

  2. Only the data privacy team will be able to see all master data and also be able to unblock.

  3. Existing business documents will remain visible and will still be possible to process.

  4. PDI add-ons which use standard business partner queries need to add parameter “ExludeBusinessPurposeCompleted” to hide blocked persons

The screenshots above show you how reports will look like if they contain blocked persons:

  1. Blocked persons data will not appear in reports and data sources

  2. Reports it will not allow to filter for blocked persons

  3. Existing business documents will remain visible without persons data and key figures remain stable

  4. Navigation to the natural person will not be possible anymore

  5. Blocked data will not be transmitted to via interfaces to BW (so you might think about doing assuming a full upload from time to time).

With our 1902 release we have added capabilities to automatically block business partners for normal business users. So besides the well known capabilities it is now also possible to automatically block data for usage by using a scheduled run.

In the blocking run you can define the recurrence (e.g. daily) and an offset for how long a business partner needs to be in “obsolete” status before getting blocked by the run (e.g. 30 days).

Additionally data privacy experts are able to disallow the deletion of natural persons data e.g. due to a legal hold or other reasons.

4. Read access logging of sensitive data and change logs

Data privacy experts can configure which predefined business partner attributes are to be treated as special category of data and activate read access logging for sensitive data of natural persons.

  1. Activate or deactivate predefined field groups for read access logging including change log.

  2. Extension fields can be marked as special category either by key user or PDI. Field group configuration can be extended by PDI.

  3. PDI allows to mark partner created BO fields as special.

  4. Download daily read access logs by webservice or UI within 14 days. Log is provided as XML files to be archived with external applications.

  5. Here you can find more details on read access logging and how to automatically download logs by webs...

Administrators, sales and marketing employees can according to their authorization access change logs:

  1. See changes per date and user

  2. See changed attribute with old / new value and modification type

  3. Export changes

5. Marketing permissions

Sales and marketing employees can mark contacts and private accounts to be excluded, included or checked before executing outbound marketing campaigns:

  1. Mark contacts to be included, excluded from marketing campaigns per channel including ability to retrieve and change consent by webservice.

  2. Channel independent marketing permissions which can be used to indicate that overall recheck might be needed.

  3. Ability to add more marketing channel by configuration e.g. social media, e-mail-newsletter…

  4. Ability to extend channels by PDI

6. User Authorization also for external applications

Finally ByDesign does not only control what happens inside the system but also how data is being consumed in external applications with the standard web-services and interfaces.

  1. Communication scenarios and arrangements allow to control external access (via the Application and User Management work center).

  2. Valid certificates are required to allow access ByDesign Web services.

  3. Communication Monitoring for e.g. failed web service calls. Customers still need to assess which integration scenarios are exposed to whom.

7. More information on GDPR and links to documentation

Here you get general overview material on GDPR, the SAP GDPR policies and especially the SAP data center data privacy measures and it's certifications which are continuously being audited:

  • General information on GDPR and SAP


The information provided in this blog should not be considered as legal advice or replace legal counsel for your specific needs. Readers are cautioned not to place undue reliance on these statements and they should not be relied upon in making purchasing decisions or for achieving compliancy to legal regulations.