Sap Se

Sap Ag

Carsten Pluder

Matthias Vogel

Benny Rolle

Ufuoma Ighoroje

Volker Lehnert

Bjoern Christoph

Thomas Schneider

Andreas Huber-Buschbeck

Marco Valentin

Stefan Hesse

Jerome Poulin

Devasena Rajamohan

Abhinava Pratap Singh

Johannes Gilbert

Susanne Doenig

Juergen Hollberg

Joerg Wiederspohn

Christof Rausse

Iwona Luther

Kerstin Hambrecht

Thiemo Lindemann

Klaus Zumbach

Andreas Seibel

Andreas Esau

Christian Hissler

Ralf Wagenknecht

Corinne Reisert

Gerd Egen

Dinesh Ravindran

Antsa Andriamboavonjy

Uwe Oehler

Rolf Waltemathe

Harsh Panwar

Eberhard Schick

Peter Wadewitz

Shankar V

Carlo Fuerst

Diane Schmidt

Karl Tillmann Rendel

Geetha Gopalakrishnan

Dharshan A

Tobias Schmidt

Heiko Theissen

Alain Bacchi

Astrid Doppenschmidt

Bleickard Langendoerfer

Chandramohan Reddy Yengoti

Cornel Leinenkugel

Gerold Wellenhofer

Gregor Arlt

Hans-Peter Thienel

Udo Herbst

Jens-Martin Wolle

Madhavi Koujalagi

Moghaddam Masoumeh

Oliver Vonderheid

Siarhei Ulasenka

Stefan Christian Boehm

Svetlana Rebholz

The present disclosure involves systems, software, and computer implemented methods for automating handling of data subject requests for data privacy integration protocols. One example method includes receiving a ticket for performing a data privacy integration protocol for a data subject. A work package that includes a work package parameter that is based on a ticket parameter is provided to responder applications. Processing of the work package by responder applications includes determining, for at least one object associated with the data subject, purposes associated with the object. The responder application determines, for each purpose, a purpose setting that corresponds to the work package parameter. The responder application processes the work package based on the work package parameter and the purpose settings and provides feedback to a data privacy integration service, which processes the feedback, to continue the data privacy integration protocol for the ticket.

Automating handling of data subject requests for data privacy integration protocols

Computer-readable media, methods, and systems are disclosed for providing purpose-based processing of data. A purpose agent assigns one or more purposes to a set of data such that access to the set of data may be restricted to a select few specifically authorized entities based on an assigned purpose. A retention period for storing the data is determined based on the assigned purpose. When the retention period expires the data is deleted from a data store.

Managing purpose-based processing of data using a purpose agent

The present disclosure involves systems, software, and computer implemented methods for integrated data privacy services. An example method includes receiving, from a requesting application in a landscape that includes a set of multiple applications, a data subject information request for a data subject. A set of target applications is determined from the set of multiple applications. The data subject information request is provided to each target application in the set of target applications. A data subject information response is received from each of the target applications. Each data subject information response includes application data for the data subject that was retrieved by a respective target application in response to the data subject information request. The received data subject information responses are aggregated to generate an aggregated data subject information response. The aggregated data subject information response is provided to the requesting application in response to the data subject information request.

Integrated personal data retrieval across multiple applications

The present disclosure involves systems, software, and computer implemented methods for integrated data privacy services. An example method includes sending a block command for an object to each application in a multiple-application landscape that includes a master data distribution application. A blocking status is received from each application that indicates whether the application successfully blocked the object in response to the block command. An overall blocking status is determined based on the received blocking statuses. In response to determining that at least one application failed to block the object, an unblock command is sent to each application. An unblocking status is received from each application and an overall unblocking status is determined. In response to determining that at least one application failed to unblock the object, a redistribution request is sent to the master data distribution application to redistribute the object to applications that failed to unblock the object.

Redistributing an object in an integrated end-of-purpose protocol

The present disclosure involves systems, software, and computer implemented methods for integrated data privacy services. An example method includes determining to initiate an integrated end of purpose protocol for an object. An end-of-purpose query is provided to multiple applications that requests each application to determine whether the application is able to block the object. End-of-purpose statuses are received, in response to the end-of-purpose query, that each indicate whether a respective application is able to block the object. The end-of-purpose statuses are evaluated to determine whether an aligned end of purpose has been reached for the object. In response to determining that the aligned end of purpose has been reached for the object, a block command is provided to each application that instructs the application to locally block the object in the application.

Integrated end-of-purpose protocol for multiple applications

The present disclosure involves systems, software, and computer implemented methods for aligned purpose disassociation in a multi-system landscape. One example method includes receiving, from multiple systems, a can-disassociate status for a purpose for an object instance. The status from a respective system can be an affirmative status that indicates that the system can disassociate the purpose from the instance or a negative status that indicates that the system cannot disassociate the purpose from the instance. The received statuses are evaluated to determine a central disassociate purpose decision for the purpose for the instance. The central disassociate purpose decision can be to disassociate the purpose from the instance when no system has the negative status and to not disassociate the purpose from the instance when at least one system has the negative status. The central disassociate purpose decision is provided to at least some of the multiple systems.

Aligned purpose disassociation in a multi-system landscape

A consent management system (CMS) manages a number of individual consent data records of data subjects. The CMS stores predefined consent templates to be instantiated when an individual consent data record is created. The CMS represents a centralized system for management of individual consent data records that are created, stored, and maintained in relation to provided consent by data subjects for purposes of operations related to stored personal data records by associated application systems. The CMS may run on an on-premise, cloud, or personal device computing platform.

Centralized consent management

A data information framework collects related data sharing characteristics (e.g., personal information, others) revealed by associated purpose information, and reports on that data. The location of the data is not restricted, and can be collected from various locations (e.g. different databases on different computer systems). An engine implements data creation defining links between different stored data structures (e.g., tables) using specific fields. A plurality of tables may be grouped into a smaller number of table clusters to facilitate constructing the data model. The model may be evaluated, enhanced, and/or corrected (e.g., by a user). The model may include fields reflecting the purpose information for the stored data, said fields accessible by the engine during data handling processes. The data model may include descriptions providing data storage location. Purpose information may be mapped to table fields. Field descriptions may be based upon purpose information, with some field values having intelligible text.

Data information framework

Various embodiments of systems and methods to determine data retention rules for data entities are described herein. In one aspect, the data entities are obtained. Usage statuses of the data entities are determined. One or more purpose of data corresponding to the one or more data entities is received. Further, legal entities corresponding to the one or more data entities are identified based on line organization attributes and the usage statuses. Process object attributes associated with the one or more data entities are identified based on the legal entities. Retention rules for the one or more data entities are determined based on the one or more purpose of data, the legal entities and the process object attributes.

Data retention rule generator

Embodiments described herein relate to an improved technique for blocking access to data records associated with an entity in a network comprising a plurality of systems. The operations include accessing and analyzing determination criteria associated with the entity to determine in which systems the data should be blocked. An end-of-purpose determination can be performed in one or more of the systems based on whether the current system is a master system, a dependent system of the master system, or a standalone system of the plurality of systems. Access to the entity data records can then be blocked from the appropriate systems when an end of purpose for the data has been reached for any processes running on the system.

Leading system determination

A business object model, which reflects data that is used during a given business transaction, is utilized to generate interfaces. This business object model facilitates commercial transactions by providing consistent interfaces that are suitable for use across industries, across businesses, and across different departments within a business during a business transaction.

Consistent set of interfaces derived from a business object model

Growing community of inventors

Spiesen-Elversberg, Germany

Carsten Pluder