“Authorization Concept” Contents Index The Authors · LOAs EKORG (Purchasing Organization ) is the field in which you define the pur-chasing organizations these authorizations

Reading SampleThis chapter introduces you to role-based access control. This serves as a basis for showing you how a purpose-based separation can be made within the authorization concept by using line organizational attributes and process organizational attributes. Finally, it describes how to make risk definitions and introduce a new risk assessment.

Volker Lehnert, Iwona Luther, Björn Christoph, Carsten Pluder Nicole Fernandes

GDPR and SAP: Data Privacy with SAP Business Suite and SAP S/4HANA430 Pages, 2014, $109.95 ISBN 978-1-4932-1712-0

www.sap-press.com/4652

First-hand knowledge.

“Authorization Concept”

Contents

Index

The Authors

https://www.sap-press.com/gdpr-and-sap_4652/?utm_source=AWS&utm_medium=readingsample&utm_campaign=Browse%20the%20Book&utm_content=1712

239

7

Chapter 7

Authorization Concept

For a long time, authorizations were the only thing many customers

thought about when it came to data protection. Of course, a well-defined

authorization concept will continue to play an extremely important role in

data protection in the future. However, a large number of adjustments to

the concepts may be necessary.

This chapter will provide you with a brief introduction to the role-based

access control concept (RBAC). This serves as a basis for showing you how a

purpose-based separation can be made within the authorization concept

by using line organizational attributes (LOAs) and process organizational

attributes (POAs). Finally, we’ll describe abstractly how to make risk defini-

tions and introduce a new risk assessment.

7.1 Users and Authorizations: An Introduction

To display how the principle of minimization and purpose limitation can

be realized in authorizations, you’ll need at least an overview of users and

authorizations. The following explanations are based on the book Authori-

zations in SAP Software by Lehnert and Stelzner (SAP PRESS, 2010, www.sap-

press.com/2316).

7.1.1 Users

Different types

of users

For a (natural) person to be able to perform actions in the SAP system, he

needs a user to whom authorizations are assigned (see Figure 7.1). Each per-

son 1 has 2 a user 3; one (or more) roles 4 are assigned to the user. A role

5 has a menu 6 that contains applications 7. In relation to these applica-

tions, authorizations 8 are included in the role. The individual authoriza-

tions are of an authorization object 9.

240

7 Authorization Concept

Figure 7.1 Person, User, and Role in Authorizations

All of the actions in the SAP system are performed by users. There are differ-

ent user types for different types of actions, as follows:

� Dialog user

Dialog users are personalized for natural persons who use the graphical

user interface, SAP GUI, to log on to the SAP system. The dialog user is

the main user type and therefore the focus of this book.

� Service user

Service users are used, for example, for the anonymous access of several

users in web services. For this reason, the authorizations for this user

type should be restricted considerably. A user logs on using the SAP GUI;

it’s possible that the user will log on more than once. The status of the

password of a service user is always productive, which also means that

only a user administrator can change the password.

� Communication user

Communication users are person-related users who log on, not using the

SAP GUI, but rather by means of a remote function call (RFC). The user

can change the password. The system checks whether the password has

expired or is new. Depending on whether the user has logged on interac-

tively or not, the password may have to be changed.

� System user

System users are needed in technical processes, such as batch runs. The

ME22N

ME25

…

Au

tho

riza

tio

nsRole

menu

TCD: ME22N, ME25 …

S_TCODE

ACTVT: 02, 03 …BSART: NB

M_BEST_BSA

…

……

6

241


7

user doesn’t log on using the SAP GUI. Multiple logons are possible when

working with system users. Passwords don’t have to be changed.

� Reference user

The reference user is a means of simplifying authorization administra-

tion. It’s not possible to log on to the SAP system with this user. The ref-

erence user is used to pass on authorizations.

The business authorization concept also has to contain information about

the users displayed. For reasons of rule conformity, you can only grant

technical users the authorizations that are required, which makes it all the

more important that this principle applies to all users that allow people to

access the system.

7.1.2 Authorizations

Authorizations are necessary to start SAP ERP system applications and exe-

cute their functions. The following sections explain the structural proper-

ties and the use of authorizations in ABAP programs.

ABAP programs include authorization checks to protect the execution of a

business function from unauthorized persons. When the programs are exe-

cuted, the system determines whether the user is allowed to process the

application-specific data as required.

Authorization fieldTo map a business process from the perspective of authorization, you first

have to define a parameter for each characteristic value involved in the pro-

cess. This parameter is called an authorization field. Because several param-

eters are normally involved in a business transaction, you’ll need to have

the right combinations of authorization fields.

Authorization

object

These combinations are called authorization objects. An authorization

object consists of a maximum of 10 authorization fields and is assigned to

an authorization object class. After you assign values to the fields contained

in an authorization object, an authorization is created. In the following sec-

tions, we’ll look at two examples of authorization objects.

Example: Authorization Object M_BEST_EKO

Figure 7.2 shows a simple example of an authorization object M_BEST_EKO

(Purchasing Organization in the Purchase Order).

242


Figure 7.2 Example of an Authorization Object

The object contains the authorization fields ACTVT (Activity) and EKORG

(Purchasing Organization). You can use the authorizations for this object to

specify which types of processing (e.g., creating purchase orders) members

of a particular purchasing organization can perform within a given applica-

tion (e.g., purchase order).

ACTVT is one of the most frequently used authorization fields, and appears

in objects in very different application areas.

LOAs EKORG (Purchasing Organization) is the field in which you define the pur-

chasing organizations these authorizations should apply to. Chapter 5,

Section 5.2.1, already covered the purchasing organization as a line organi-

zational attribute (LOA). At this point, you can also maintain this exact char-

acteristic (and the other LOAs mentioned in Chapter 5) in the authoriza-

tions.

Example: Authorization Object M_BEST_BSA

POAs The situation is similar for authorization objects such as M_BEST_BSA (Docu-

ment Type in Purchase Order), which are suitable for including process

organizational attributes (POAs), as previously described in Chapter 5, Sec-

tion 5.3.

$EKORGPurchasingorganization

EKORG

ActivityACTVT

M_BEST_EKO

Enter76

Remove75

Display prices09

Display change documents08

Delete06

Print, edit messages04

Display03

Change02

Create or generate01

243


7

The authorization objects consist of two fields. If you choose to display this

authorization object in Transaction SU21 (Maintain Authorization Objects),

you’ll see a screen similar to Figure 7.3.

Figure 7.3 Authorization Object M_BEST_BSA

Authorization check

during program

execution

If the authorization objects have been specified, corresponding authoriza-

tions will be generated that will always be based on the role in this model.

Both authorization objects are used to control which activity is possible, in

which purchasing organization, and in which document type. Depending

on the complexity of the program, several authorizations will be checked

step by step, starting with a start authorization check. The checking

sequence of the technical process in Transaction ME21N (Create Purchase

Order) is simplified and schematized in Figure 7.4.

244


Figure 7.4 Authorization Checks in the Program Sequence

The first check shown in the graphic for S_TCODE (Transaction Code Check at

Transaction Start) is also possible for other start authorization objects; the

object S_SERVICE (Check at Startup of External Services) is particularly

important for SAP S/4HANA because this is required for SAP Fiori apps.

Access Restriction via LOAs and POAs

A user is assigned to a person, and roles are assigned to this user. The roles

contain authorization objects that—as soon as the role has been gener-

ated—constitute the authorizations of the user concerned. A sequence of

authorization checks takes place in a number of programs, for example, in

business applications. It’s therefore possible to sufficiently restrict the

user’s access using LOAs and POAs by differentiating the access in a rele-

vant way.

7.2 Rethinking Organizational Levels

To complete the picture, a few more details about the organizational levels

are necessary. For roles, the organizational levels are strong organizational

differentiators that are validated in numerous authorizations. In many

System actionUser action

Enter values/save

TransactionME21N

Check for values, authorization object:M_BEST_WRK

Check for values, authorization object:M_BEST_EKO

Check for values, authorization object:M_BEST_BSA

Start check on M_BEST_EKO

Check for S_TCODE ME21N

245

7.2 Rethinking Organizational Levels

7

cases, the organizational levels correspond to the characteristics described

in Chapter 5, Section 5.2.1, such as company code or purchasing organiza-

tion.

Existing organiza-

tional levels

The organizational levels available in the system are shown in table USORG

(Organizational Levels for the Profile Generator), as shown in Figure 7.5. In

principle, authorization fields for organizational levels can also be “raised.”

Organizational levels are initially also authorization fields in an authoriza-

tion object. Their special feature is their status and the possibilities that

arise from it. Organizational levels are required for the derivation concept.

As you go through the defined organizational levels, you’ll find that not all

organizational levels are LOAs as defined in this book.

Figure 7.5 Organizational Levels in Table USORG (Organizational Levels

for the Profile Generator)

246


Derivation concept The derivation concept is the central technical vehicle of the authorization

concept. The system also recognizes the need to differentiate roles along

clear organizational boundaries. As shown in Figure 7.6, roles can be

derived from a central reference role that has its own specific organiza-

tional level characteristics and LOAs. Assuming there are three legally inde-

pendent units, these can each be mapped with one set of LOAs; when

deriving the roles, these values are entered in the derived role.

Figure 7.6 Derivation Concept and LOAs

As described in Chapter 5, as a general rule, we assume that the purpose of

processing personal data is to be considered specifically for a legally inde-

pendent entity. Accordingly, it’s also important that the organizational

model is reflected in the use of the organizational levels. Chapter 12 deals

with the control measures that are necessary to achieve this. An essential

question in this context is how the organizational levels were defined in

the roles.

Procedural model

as a basis

If you’ve been following our procedural model (see Chapter 3), you’ve seen

a comprehensive overview of the line organization differentiation require-

ments simply because you also need these attributes for blocking and

deleting and when providing information. If you also use the business

retention Data Controller Rule Framework, you’ll have a representation

there that can be used accordingly with the authorization concept.

LOA 1

LOA 2

LOA 3

Derived roleLOA 1

Derived roleLOA 2

Derived roleLOA 3

Reference role

247

7.3 Defining Process Attributes

7

Alternative

approach

If, however, you want to start with authorizations as your first step of

implementation, you have no other option than to determine the relation-

ships outlined in Chapter 5, Section 5.2.1. This section will also show you

where you can evaluate the assignments in the enterprise structure. You’ll

have to determine which assignments are maintained and evaluate

whether the relationships refer uniquely to a controller (usually the legal

person). The controller is usually represented by the company code.

After you’ve traced this assignment, check table USORG (Organizational Lev-

els for the Profile Generator) to see which organizational levels are available

for authorizations in your system. The next step requires an actual analy-

sis; you’ll have to examine the actual assignments to the authorizations in

table AGR_1252 (Organizational Levels). You should also consider the manual

values of these fields in table AGR_1251 (Authorization Data for Activity

Group). Together, these two specifications provide information on which

line-organizational differentiations currently exist for you in the roles.

Entries made to these fields in table AGR_1251 (Authorization Data for Activ-

ity group) are also proof that your authorization concept doesn’t comply

with the standard.

No Generic Maintenance

Generic maintenance with “*” or comprehensive intervals “0001–9999”

aren’t generally useful as a means of differentiation.

Is the Data Processed Separately for Each Purpose?

Our regular discussions with SAP Consulting often deal with the question

of whether or not data can actually be processed separately. In such cases,

our standard response is that a brief look at the organizational differentia-

tion of roles will provide a rapidly identified and weighty indicator.


POAs were already addressed in Chapter 5, Section 5.3. In doing so, we also

clarified our assumptions in the process and gradually presented the ele-

ments of an exemplary process: customer, order, delivery, and billing

248


document. These business objects are regularly protected by relevant

authorization objects that allow you to differentiate according to POAs. As

an example, refer to authorization object V_VBAK_AAT (Sales Document:

Authorization for Sales Document Types) (see Figure 7.7).

Figure 7.7 Authorization Object V_VBAK_AAT (Sales Document: Authorization

for Sales Document Types)

Authorizations for handling a sales order are also assigned in SAP ERP Con-

trolling (CO) (e.g., product cost estimate). From a data protection perspec-

tive, an application-related solution should be sought; this is achieved

using the two authorization objects in Figure 7.8.

Authorization object V_VBAK_AAT allows you to differentiate between differ-

ent sales document types. A detailed description of such attributes can be

249


7

found in Authorizations in SAP Software by Lehnert and Stelzner (SAP

PRESS, 2010, www.sap-press.com/2316).

Procedural model

as a basis

With regard to POAs, it’s also important that you’ve already identified the

most important POAs in our procedure model because you’ll also need

these attributes for blocking and deleting. Likewise, when using the Data

Controller Rule Framework, the model should have already been mapped

in its essential parts.

Figure 7.8 LOAs and POAs in the Authorization Objects for the Sales Order

Alternative

approach

An alternative procedure in this case is much more complex, as there are

far more possible fields and approaches. However, experience with the cus-

tomer has shown that a differentiation has usually already been made for

purely business-related and internal organizational reasons; this differenti-

ation must be examined and, where necessary, modified.

One possible starting point is again the characteristic value of the roles,

which can be analyzed using table AGR_1251 (Authorization Data for the

Activity Group). This time, however, it’s not just the small number of orga-

nizational levels that need to be considered but rather other numerous

Sales Order

V_VBAK_AAT - Sales Document:Authorization for Sales Document Types

AUART Sales Document Type

ACTVT Activity

V_VBAK_VKO - Sales Document:Authorization for Sales Areas

VKORG Sales Organization

VTWEG Distribution Channel

SPART Division

ACTVT Activity

Purpose

ILM objectLOA POA

250


fields. You can further facilitate your work by describing the respective

activities in the fields. For example, you may add the term “Exclude activ-

ity” to the field ACTVT.

7.4 Authorization Risks

As previously explained in Chapter 1, Section 1.2.4, authorizations must fol-

low the strict principle of data minimization. All access beyond the purpose

of processing is a violation of the minimization principle.

Data protection

perspective

Risks in the authorization system are usually defined and evaluated. The

classic approach is ultimately a principle of prohibition, which is simply

based on the following principle: a user should not be able to execute cer-

tain actions or certain combinations of actions.

The principle of minimization is, however, a principle of requirement. A

user should only be allowed to perform actions that correspond to the pur-

pose of processing.

To highlight this (in a simplified way) with quantity structures, consider

that of the approximately 60,000 business transactions, several thousand

transactions (approximately 2,500 in the SAP Access Control rules) are

listed in the classical risk definition logic and are regarded as risky. How-

ever, in terms of the minimization principle of data protection, any transac-

tion that is suitable for exposing personal data is a risk if this isn’t needed

for the specific purpose. Realistically, this is 20 times the amount.

All too risky? This, however, not only leads to considerable challenges in terms of the

amount of risk definitions but also in terms of the number of hits (again

simplified). After all, every one of the users in the system deals with per-

sonal data in one way or another, and this is precisely what the number of

hits would cover. It’s therefore almost worthless to say that almost every

user deals with personal data. The question is therefore, what do we have to

prove? We have to prove which users have access for which processing pur-

poses.

Activity-related

risks

From a user authorization perspective, activity-related risks can be divided

into three different types of critical access into the system:

251


7

� Segregation of duties (SoD) conflicts

SoD conflicts are the result of a combination of two activities. For exam-

ple, the combination of supplier maintenance and order processing is

critical. However, depending on rules, procedures, and Customizing set-

tings, an SoD conflict can also be displayed within a transaction if the set

of rules stipulates an SoD between entering and releasing a posting. The

technical control of these various activities allows for an operation-ori-

ented SoD; that is, a separation of the entry and release processes can be

configured.

� Critical actions

Critical actions affect a single activity (execution) leading to a risk. Main-

taining metadata preferences, for example, is a critical action because it

can result in the production system being opened for unauthorized

modifications. A critical action is defined as the connection of an appli-

cation, for example, of a transaction with an authorization object.

� Critical authorizations

Critical authorizations are critical in themselves, without the type of

access to this authorization needing to be defined already (technical

definition: authorization object without connection to a specific trans-

action). One example is debugging in change mode.

This is what the “classic” risk perspective has to offer! What about the risks

based purely on data protection law?

SoD in data

protection

In data protection, the SoD is particularly important for system-related

activities, such as the segregation of user administrator and authorization

administrator, or the SoD in transportation management.

Transportation Management

By transportation management, we mean the management of transport

requests between development and production systems.

SoD requirements explicitly linked to business management should be

borne in mind, for example, when customers or suppliers are unblocked.

The allocation of a special bonus and the initiation of payment are still a

risk of SoD in terms of business management; this risk doesn’t have to be

subject to any data protection considerations. The risks involved in the

252


SoD, therefore, play a rather marginal role in data protection in terms of

volume.

Critical actions in

data protection

Critical actions also exist in data protection. Naturally, technical actions are

more serious. The previously mentioned general maintenance of metadata

preferences is also an explicit data protection risk. Specifically, with regard

to data protection, it should also be noted that unlimited access to tables

generally constitutes a massive violation of the minimization principle and

the principle of purpose separation.

Critical authoriza-

tions in data protec-

tion

The definition of critical authorizations in data protection is much more

important than in classic risk assessment. For example, access to internal

vendors (e.g., travel expenses) is a risk for all users, regardless of the type of

access, who aren’t explicitly authorized for the purposes relating to internal

accounts payable.

Purpose risk The requirement to only provide authorizations if the access is covered

from the purpose of the processing leads to a new category. The latter must

be in a position to provide information as to whether the separation of pur-

poses in the user’s authorizations has been carried out in such a way that

the user only has authorizations resulting from the purposes for which he

has to be authorized. The term purpose risk has been introduced to describe

this risk.

Purpose Risk

A purpose risk is a general, purpose-oriented risk definition using the

authorization objects assigned to individual artifacts within a purpose, as

well as the LOAs and POAs of a purpose. The purpose risk is therefore made

up of a set of all critical authorizations as defined by data protection law in

relation to all artifacts of a processing purpose.

Let’s begin by taking a look at the graphic in Figure 7.9. In this context, the

sales order is protected by two essential authorization objects: V_VBAK_

AAT (Sales Document: Authorization for Sales Document Types) and V_

VBAK_VKO (Sales Document: Authorization for Sales Areas). The division,

distribution channel, or sales organization may be used as LOAs. The POA is

the order type. The activity is negligible for this assessment.

253


7

Figure 7.9 Relationships among Purpose, Artifact, and Authorization Object in

the Risk Definition

Given that sales organization n:1 is linked to the company code, a potential

risk definition is as shown in Table 7.1.

This artifact-related observation must now be repeated for each artifact in

the purpose until all risks have been defined.

Field Name Field Description Value

V_VBAK_AAT (Sales Document: Authorization for Sales Document Types)

AUART Sales document type Each within the scope of

the purpose

ACTVT Activity

V_VBAK_VKO (Sales Document: Authorization for Sales Organization)

VKORG Sales organization Controller

ACTVT Activity

Table 7.1 Risk Definition (Combination of “Critical” Authorizations)

Sales Order

V_VBAK_AAT - Sales Document:Authorization for Sales Document Types

AUART Sales Document Type

ACTVT Activity

V_VBAK_VKO - Sales Document:Authorization for Sales Areas

VKORG Sales Organization

VTWEG Distribution Channel

SPART Division

ACTVT Activity

Purpose

254


The cumulative total of all risk definitions (which are in fact definitions of

critical authorizations) represents the entire purpose risk. Thus, two levels

can be represented: one general level that provides information about the

purpose, and a concrete level that also identifies the artifacts in relation to

the purpose (see Table 7.2).

Procedural model

as a basis

Again, if you’ve been following our proposed procedure model, where sig-

nificant values have already been determined, they must also be applied

accordingly. To do this, you’ll have to prepare the artifacts for their SAP ILM

objects, for which you’ve already created rules. If you’ve already set up the

Data Controller Rule Framework, you’ll find yourself in the comfortable

position of having POAs, LOAs, and SAP ILM objects already assigned to the

purpose.

7.5 Summary

The topic of authorizations is technical and not necessarily trivial. It’s also

important for a more system-remote data protector to know that authori-

zations are generally checked at several levels, that the line organization

and the process organization must be observed, and that there is a close

relationship between the rules for deletion and the authorizations. It’s

unlikely that a data protector of this kind will make technical risk defini-

tions independently. They might also be able to consult those responsible

in IT as to which risks are defined and how POAs and LOAs are to be taken

into account.

In this chapter, we’ve shown the authorization-affine IT specialists that

they can ultimately—albeit in the guise of data protection—expect a famil-

iar field of activity with a generally substantial need for action.

User Purpose (General Level) Artifact (Specific Level)

Miller Sale of cough syrup Customer master, sales

order, billing document

Miller Sale of peppermint tea Customer master

Table 7.2 Two Levels of Purpose Risk

7

Contents

Foreword .......................................................................................................................... 15

Preface ............................................................................................................................... 17

1 Introduction to General Data Protection Regulation 25

1.1 What Does the GDPR Mean for you? .................................................... 25

1.1.1 Conceptual and Factual Principles ............................................ 26

1.1.2 An Essential Legal Consideration .............................................. 30

1.1.3 Principles of Processing ................................................................ 31

1.1.4 Special Categories of Personal Data ......................................... 33

1.1.5 Justifiable Facts for Processing .................................................. 35

1.1.6 Requirement of Transparency .................................................... 37

1.1.7 Accuracy of Data ............................................................................. 42

1.1.8 Right to Be Forgotten .................................................................... 42

1.1.9 Data Portability ............................................................................... 45

1.1.10 Objection, Automated Individual Decision-Making,

and Profiling ..................................................................................... 46

1.1.11 Appropriateness of Measures, Documentation,

and Proof ........................................................................................... 46

1.1.12 Security of Processing ................................................................... 47

1.1.13 Privacy Impact Assessment ......................................................... 51

1.1.14 Records of processing activities ................................................. 52

1.2 Which Requirements Require Technical Support? ......................... 53

1.2.1 Purpose Limitation of Processing .............................................. 54

1.2.2 Data Accuracy: Rectification ....................................................... 55

1.2.3 Data Deletion and Data Blocking .............................................. 56

1.2.4 Technical and Organizational Measures ................................ 60

1.2.5 Accountability and Auditability ................................................. 66

1.2.6 Right of Access ................................................................................. 69

1.3 Which Requirements Can Be Technically Supported? .................. 72

1.3.1 Consent .............................................................................................. 72

8

Contents

1.3.2 Data Minimization ......................................................................... 72

1.3.3 Data Accuracy: Data Management .......................................... 74

1.3.4 Advance Information .................................................................... 74

1.3.5 Records of Processing Activities ................................................ 75

1.3.6 Accountability: Compliance Management ............................ 76

1.4 Summary ........................................................................................................... 79

2 Personal Data in SAP Business Suite and SAP S/4HANA 81

2.1 SAP Business Suite and SAP S/4HANA Data ...................................... 81

2.2 Personal Data in SAP ERP ........................................................................... 84

2.2.1 Business Partner ............................................................................. 84

2.2.2 Direct Personal Data Records in SAP ERP Financials ........... 85

2.2.3 Further Personal Data Records in SAP ERP Financials ........ 91

2.2.4 Employee Data in SAP ERP Financials ...................................... 92

2.2.5 User Data ........................................................................................... 92

2.2.6 Direct Personal Data Records in SAP ERP Controlling ........ 93

2.2.7 Indirect Personal Data Records in SAP ERP Controlling ..... 94

2.2.8 Reporting Tools in SAP ERP Controlling and Customer-

Specific Reporting ........................................................................... 97

2.2.9 Direct Personal Data in SAP ERP Sales and Distribution ... 97

2.3 Personal Data in SAP ERP HCM ................................................................ 99

2.3.1 Types of Personal Data ................................................................. 99

2.3.2 Info Subtypes ................................................................................... 102

2.4 Personal Data in SAP CRM ......................................................................... 103

2.4.1 Business Partners as Master Data ............................................ 104

2.4.2 Transactional Data of Business Partners ................................ 106

2.4.3 Data Exchange with Other SAP Systems ................................ 107

2.4.4 Report Options for Business Partners in Marketing ........... 107

2.5 SAP Business Suite Technical Integration Example ....................... 108

2.6 Summary ........................................................................................................... 109

9

Contents

3 Implementation Approach 111

3.1 Project Implementation Steps ................................................................. 111

3.1.1 What Is the Inductive Approach? .............................................. 114

3.1.2 Blocking and Deleting Personal Data as

Your Starting Point ......................................................................... 115

3.1.3 Separation Based on Purpose ..................................................... 118

3.1.4 Separating the Purpose and Authorizations ......................... 120

3.1.5 Informing the Data Subject ........................................................ 121

3.1.6 Logging ............................................................................................... 122

3.1.7 Data Transmission Security ........................................................ 123

3.1.8 Technical Security ........................................................................... 124

3.1.9 Data Portability ............................................................................... 125

3.1.10 Audit, Verification, and Documentation ................................ 125

3.2 Record of Processing Activities Approaches ...................................... 130

3.2.1 Inductive versus Deductive Approach ..................................... 130

3.2.2 Where the Two Approaches Meet ............................................ 132

3.3 Summary ........................................................................................................... 132

4 Blocking and Deletion with SAP Information Lifecycle Management 133

4.1 Introduction to SAP ILM .............................................................................. 133

4.1.1 Fundamentals of SAP Information Lifecycle

Management ................................................................................... 134

4.1.2 Lifecycle Management .................................................................. 136

4.1.3 Overview of Solutions ................................................................... 140

4.2 Preparatory Steps .......................................................................................... 143

4.2.1 Blocking Master Data in Transaction SPRO ........................... 143

4.2.2 Blocking Transactional Data in Transaction SPRO .............. 149

4.2.3 Blocking Master Data in SAP Information Lifecycle

Management ................................................................................... 149

4.2.4 Archiving Master and Transactional Data ............................. 156

4.2.5 Destruction of Master and Transactional Data .................... 157

10

Contents

4.2.6 Blocking and Deleting Master Data: Application

Rule Variants .................................................................................... 160

4.3 Blocking from a Business Perspective .................................................. 168

4.3.1 Blocking Master Data in the Business Process ..................... 168

4.3.2 Display of Blocked Master Data in the Business

Process ............................................................................................... 172

4.3.3 Unblocking Master Data in the Business Process ............... 178

4.3.4 Blocking Transactional Data in the Business Process ........ 181

4.3.5 Display of Blocked Transactional Data in the Business

Process ............................................................................................... 182

4.4 Deletion from a Business Perspective .................................................. 185

4.4.1 Data Destruction from the Database ...................................... 185

4.4.2 Destruction of Archived Data ..................................................... 188

4.5 Legal Case Management ............................................................................ 191

4.6 Time-Based Blocking of Personal Data in Personnel

Management ................................................................................................... 193

4.7 Summary ........................................................................................................... 195

5 Purpose-Based Processing 197

5.1 Controller and Purpose ............................................................................... 197

5.2 Organizational Structures (Line Organization) ................................ 200

5.2.1 Key Organizational Structures ................................................... 201

5.2.2 Alternate Structure Arrangements .......................................... 205

5.3 Process Organizational Structures ......................................................... 206

5.3.1 Account Groups ............................................................................... 207

5.3.2 Business Objects in SAP ERP Sales and Distribution ........... 210

5.3.3 Purpose Attributes in Sales Order Processing ....................... 213

5.4 How Organizational Structures Define Purpose ............................. 214

5.5 Summary ........................................................................................................... 215

11

Contents

6 Data Controller Rule Framework 217

6.1 Data Controller Rule Framework ............................................................ 221

6.1.1 Configuration of the Data Controller Rule Framework ..... 223

6.1.2 Rule Maintenance in the Data Controller Rule

Framework ........................................................................................ 230

6.2 Summary ........................................................................................................... 237

7 Authorization Concept 239

7.1 Users and Authorizations: An Introduction ....................................... 239

7.1.1 Users ................................................................................................... 239

7.1.2 Authorizations ................................................................................. 241

7.2 Rethinking Organizational Levels .......................................................... 244

7.3 Defining Process Attributes ...................................................................... 247

7.4 Authorization Risks ....................................................................................... 250

7.5 Summary ........................................................................................................... 254

8 Information Retrieval Framework 255

8.1 Transparency: Access to Data and Information ............................... 256

8.2 Setup of the Information Retrieval Framework .............................. 257

8.2.1 Activating the Business Function .............................................. 257

8.2.2 Determining the System Status ................................................ 258

8.2.3 Assignment of Authorizations ................................................... 259

8.3 SAP ILM Objects in the Information Retrieval Framework ......... 260

8.4 Creating an Information Retrieval Framework Data Model ...... 264

8.4.1 Display Information Retrieval Framework Data Model ..... 264

8.4.2 Selecting a Data Record for the Provision of

Information ...................................................................................... 266

8.4.3 Assigning an SAP ILM Object to a Purpose ............................. 268

12

Contents

8.4.4 Search for a Flight Customer ...................................................... 269

8.4.5 Making Corrections to the Information Retrieval

Framework Data Model ................................................................ 272

8.4.6 Checking the Changes Made to the Information

Retrieval Framework Data Model ............................................. 276

8.4.7 Final Search Results ....................................................................... 278

8.5 Handling a Data Subject Request ........................................................... 279

8.6 Central Instance ............................................................................................. 282

8.7 Further Technical Information ................................................................. 283

8.8 Summary ........................................................................................................... 284

9 Read Access Logging 285

9.1 Scope of Read Access Logging .................................................................. 285

9.2 Setup and Maintenance ............................................................................. 287

9.2.1 Operation .......................................................................................... 288

9.2.2 Authorizations ................................................................................. 288

9.2.3 Activation .......................................................................................... 289

9.3 Logging Purpose and Domains ................................................................ 290

9.3.1 Logging Purpose .............................................................................. 290

9.3.2 Log Domains ..................................................................................... 291

9.4 Recordings for User Interface Channels .............................................. 292

9.5 Configuration .................................................................................................. 297

9.6 Evaluation of Logs ......................................................................................... 301

9.6.1 Manual Evaluation ......................................................................... 302

9.6.2 Automated Search in Read Access Logging Logs ................. 304

9.7 Configurations for Remote API Channels ........................................... 305

9.8 Conditions ......................................................................................................... 307

9.9 Transport, Import, and Export ................................................................. 312

9.10 Summary ........................................................................................................... 312

13

Contents

10 SAP Master Data Governance 315

10.1 Master Data Maintenance Scenarios .................................................... 316

10.1.1 SAP Master Data Governance Central Governance ............ 317

10.1.2 SAP Master Data Governance Consolidation ........................ 319

10.1.3 Combining Scenarios ..................................................................... 322

10.2 Maintaining Sensitive Data ...................................................................... 322

10.3 Organizational Separation ........................................................................ 324

10.4 Data Quality Assurance Using Services ............................................... 326

10.4.1 Key Services ...................................................................................... 326

10.4.2 Proxy Provider .................................................................................. 328

10.5 Summary ........................................................................................................... 329

11 SAP Test Data Migration Server 331

11.1 Use Cases ........................................................................................................... 332

11.1.1 Setting Up Test Clients ................................................................. 332

11.1.2 Setting Up Clients for Training .................................................. 333

11.1.3 Setting Up Clients for Development ........................................ 333

11.1.4 Alternating Test Clients ................................................................ 333

11.1.5 Transfer of Selected Test Cases ................................................. 334

11.1.6 Conversion and System Scrambling ......................................... 334

11.1.7 Standard Range of Functionalities ........................................... 335

11.2 Structure and Functionality ...................................................................... 335

11.2.1 User Interface .................................................................................. 336

11.2.2 Process Control ................................................................................ 337

11.2.3 Migration Workbench for Data Records ................................. 338

11.2.4 Migration Workbench for Objects ............................................ 341

11.2.5 Conversion Workbench ................................................................ 343

11.2.6 Scrambling Control ........................................................................ 344

11.3 Integration of the System Landscape in SAP TDMS ....................... 346

11.4 Data Protection with SAP TDMS ............................................................. 347

11.4.1 SAP TDMS Usage Variants ........................................................... 348

14

Contents

11.4.2 Setting Up Scrambling .................................................................. 348

11.4.3 Scrambling Across Systems ......................................................... 350

11.5 Summary ........................................................................................................... 351

12 Accountability: Protection, Audits, Controls, and Documentation 353

12.1 Control Frame and Principles of Processing ...................................... 354

12.2 Lawfulness, Fairness, and Transparency ............................................. 355

12.3 Purpose Limitation ........................................................................................ 357

12.4 Data Minimization ........................................................................................ 360

12.5 Accuracy ............................................................................................................. 364

12.6 Storage Limitation ........................................................................................ 366

12.7 Integrity and Confidentiality ................................................................... 369

12.8 Accountability ................................................................................................. 377

12.9 Abstract Technical Controls ...................................................................... 378

12.10 Technical Control Actions: Examples .................................................... 381

12.11 Summary ........................................................................................................... 413

Appendices 415

A Relevant Transactions, Reports, and SAP Notes .............................. 415

B The Authors ...................................................................................................... 419

Index .................................................................................................................................. 423

423

Index

A

ABAP programs ......................................... 241

Access ............................................................ 325

Access checks .............................................. 374

Access control ............................................ 389

Access restriction ...................................... 244

Account groups ................................ 207, 208

Accountability ............................................ 377

Accounting documents .......................... 220

Accounts ....................................................... 104

Accuracy .................................. 32, 42, 74, 126

Activity types .......................................... 95, 96

Address validation ................................... 326

Addresses ..................................................... 105

Advance information ....................... 74, 256

Amount values .......................................... 349

Anonymization .................................. 47, 332

API channels ............................................... 297

configuration ......................................... 305

Application areas ...................................... 156

Application Link Enabling (ALE) ... 148, 389

Application names ................................... 148

Application rule variants ............. 152, 160,

161, 163

Archivability checks ................................ 141

Archive Development Kit (ADK) ... 136, 398

Archive files ................................................ 193

Archived data .................................... 156, 158

destruction .............................................. 188

Archiving objects ................... 156, 218, 261

Argument fields ................................ 343, 349

Assignment tables .................................... 344

Attribute maintenance ........................... 318

Attribution .................................................. 383

Audit activities ........................................... 129

Audit area ............................................ 150, 234

Auditing ........................................................... 66

Authorization check ............. 193, 243, 394

Authorization concept .................. 239, 387

Authorization control ............................. 325

Authorization field ................................... 241

Authorization groups ............. 89, 146, 157,

230, 395

Authorization objects .................... 159, 241,

248, 252

example .................................................... 243

Authorization risks .......................... 126, 412

Authorizations ............. 114, 120, 158, 239,

241, 247, 288

assignment ............................................. 259

critical ....................................................... 251

deactivating ........................................... 325

example .................................................... 242

Automated decision-making ........... 46, 70

Availability ............................................ 50, 375

B

Backup and disaster recovery .............. 412

Backward RFC .............................................. 283

BDLS run ....................................................... 334

Billing document ....................................... 212

type ............................................................ 213

Billing documents ..................................... 220

Binding data ................................................... 83

Blocked data ................................................ 160

Blocking ....................... 45, 56, 115, 138, 168

Blocking indicators ................................... 397

Business Add-Ins (BAdIs) .............. 261, 288

Business Address Services (BAS) ......... 399

Business Continuity Management

(BCM) ......................................................... 375

Business functions ................................... 144

Business Information Provider

(BIP) ............................................................ 399

Business Object Repository (BOR) ...... 192

Business objects ......................................... 210

Business partner management ........... 203

Business partner model ............................ 84

Business partners ............ 84, 143, 294, 309

blocking .................................................... 148

relationships ........................................... 104

roles ..................................................... 84, 104

424

Index

Business partners (Cont.)

types ........................................................... 104

Business Planning and Simulation

(BPS) ........................................................... 107

Business Process Library (BPL) ............. 334

Business Process Library Modeler

(BPL Modeler) ......................................... 342

Business processes ......................... 206, 221

blocking master data .......................... 168

unblocking .............................................. 178

Business rules ............................................. 232

Business Rules Framework (BRF) ........ 326

C

Central data maintenance ..................... 317

Central instance (CI) ................................. 282

Change logging .......................................... 122

Check authorization ................................. 173

Check date period ...................................... 144

Check tables ................................................. 263

Classification ............................................... 105

Client copies ...................................... 335, 337

Client separation ....................................... 198

Clients ............................................................ 201

Code review ................................................. 401

Code scans .................................................... 370

Communication user .............................. 240

Companies ................................................... 202

Company codes ................................ 201, 225

Compliance management ....................... 76

Condition fields ............................... 232, 236

Conditions .................................................... 310

Confidentiality ........................................... 377

Configuration validation ....................... 402

Consent ........................................... 36, 37, 356

Consistency ................................................. 338

Contact persons ........................ 97, 104, 209

Control frame ............................................. 354

Control keys .................................................. 82

Controller ........................... 29, 118, 197, 221

joint responsibility ............................... 198

mandatory assignment ..................... 198

Controlling area ......................................... 202

Controlling report ....................................... 94

Controls ............................................... 356, 359

Conversion Workbench (CWB) .... 343, 350

Conversions ................................................. 334

standard ................................................... 346

Cost Center Accounting .......................... 202

Cost center hierarchy ............................... 202

Cost centers ............................................ 94, 96

Cross-business process search ............. 282

Cross-company code postings ............. 215

Cross-site scripting ................................... 371

Customer data ............................................ 324

Customers ...................................................... 89

blocking .......................................... 153, 172

no blocking .............................................. 171

D

Data access control ..................................... 62

Data accuracy .............................................. 364

Data archiving ............................................. 230

Data blocking .............................................. 392

Data controller ............................................ 225

Data Controller Rule Framework ....... 120,

122, 126, 128, 217, 221, 246, 249,

279, 382

configuration ......................................... 223

rule maintenance .................................. 230

Data deletion ............................................... 397

Data dependency ....................................... 116

Data destruction .............................. 135, 157

Data enrichment ........................................ 328

Data exchange ............................................ 107

Data inventory ............................................ 115

Data media control ..................................... 61

Data minimization ................... 72, 360, 362

Data model errors ..................................... 276

Data portability ................ 45, 125, 127, 257

Data processing ......................... 28, 142, 200

for employment purposes ................. 359

Data protection ................................... 25, 137

Data protection impact assessment

(DPIA) ......................................................... 112

Data protection officer .............................. 38

Data protector ............................................. 403

Data quality assurance ............................ 326

Data records ................................................. 266

selection .................................................... 339

425

Index

Data records (Cont.)

transfer ..................................................... 340

writing ...................................................... 340

Data Retention Rule Framework ........ 120

Data subject requests .............................. 279

Data subjects ........................................ 25, 121

Data traces ................................................... 349

Data transfer ............................................... 114

Data transmission security ................... 123

Debtors ............................................................. 89

Decentralized data maintenance ....... 316

Deductive approach ................................. 112

Default audit area ..................................... 229

Deletion .............................. 56, 115, 138, 185

Deletion process ........................................ 219

Deliveries ............................................ 211, 220

Depersonalization ............. 43, 49, 363, 391

Derivation concept .................................. 246

Destruction worklist ................................ 189

Development client ................................. 333

Dialog user ................................................... 240

Differential privacy ........................... 48, 348

Distribution channel ............................... 202

Division ......................................................... 202

Document Relationship Browser

(DRB) ......................................................... 192

Double maintenance ............................... 163

Dual control principle ............................. 191

Dun & Bradstreet ...................................... 328

Duplicate check ......................................... 398

Duplicate detection ................................. 327

E

Employee data ........................................... 323

Employees ................................................... 104

Encryption ............................................ 49, 391

EoP check .................................. 142, 150, 167

Event logging .............................................. 374

External services ....................................... 329

F

Forward RFC ................................................ 283

Frequency of use ....................................... 362

G

General Ledger (G/L) ................................ 315

Generic Smart Search (GSS) ......... 255, 283

Greenfield implementation .................. 112

H

Health data ..................................................... 34

I

IBAN ....................................................... 295, 361

Identifiable data ............................................ 26

Implementation approach .................... 111

Inductive approach ......................... 112, 114

Industry solutions ........................... 144, 340

Info subtypes .............................................. 102

Information ................................................. 114

Information Retention Manager

(IRM) .......................................................... 133

Information retrieval framework ......... 71,

255, 381

confirming changes ............................. 276

correcting data model ........................ 272

create data model ................................ 264

data model ..................................... 272, 274

define system status ............................ 258

display data model .............................. 264

set up ......................................................... 257

tables ......................................................... 263

Information sheet ..................................... 106

Infotype namespaces .............................. 100

Infotypes ....................................... 99, 100, 194

country-specific ..................................... 100

Input mask ...................................................... 86

Integrity ........................................................... 49

Integrity and confidentiality ................ 369

Interface control ........................................ 383

Interface verification ............................... 127

Intermediate Document (IDoc) .............. 64

Internal control system .......................... 353

Internal orders .............................................. 94

International Financial Reporting

Standards (IFRS) .................................... 138

IRM rules .............................................. 136, 161

426

Index

L

Lawfulness, fairness, and

transparency .......................................... 355

Legal Case Management .............. 134, 191,

192, 398

Lifecycle management .................. 134, 136

Line organizational attributes

(LOAs) ....... 119, 121, 197, 205, 218, 239,

242, 246, 358

Log domains ...................................... 291, 308

assignment .............................................. 300

Log group

conditions ................................................ 311

create ......................................................... 298

Logging ... 67, 122, 286, 290, 372, 403, 404

behavior ................................................... 406

behavioral monitoring ....................... 304

conditions ................................................ 307

entries ........................................................ 312

evalutation .............................................. 301

events ........................................................ 407

fields ........................................................... 300

log domains ............................................ 291

purpose ..................................................... 290

restrcting .................................................. 288

type ............................................................. 301

M

Manage ILM Business Rules app ......... 230

Manual replication ................................... 319

Marketing attributes ...................... 105, 107

Master data ................................. 82, 108, 315

blocked ............................................ 146, 172

blocking .................................................... 143

blocking and deletion ......................... 160

business partners .................................. 104

maintenance .......................................... 316

management .......................................... 399

purchase order ......................................... 83

record ........................................................ 152

retention period .................................... 163

Master system ............................................ 147

Matching ....................................................... 321

Material documents ................................. 219

Material requirements planning

(MRP) ......................................................... 318

Material type ................................................. 82

Memory control ........................................... 62

Migration ...................................................... 339

Migration Workbench (MWB) .... 338, 339

objects ....................................................... 341

Minimal principle ...................................... 387

Minority indicator ...................................... 89

N

Natural person ............................................ 239

Notification obligations ............................ 38

O

Obligation to delete .................................. 139

Obligation to provide proof .................. 125

OData services ..................................... 64, 259

OneKey IQVIA ............................................. 328

Organization entities ............................... 223

Organization units ................ 224–226, 233

Organizational levels ..................... 244, 247

Organizational measures ............. 112, 400

Organizational separation ..................... 324

Organizational structures ... 118, 200, 204

defining purpose ................................... 214

key structures ......................................... 201

processes .................................................. 206

P

Password rules .................................. 374, 410

Patch Management ................................... 400

Patches ........................................................... 371

Payer ............................................................... 213

Payment behavior ....................................... 91

Personal data .... 66, 81, 130, 138, 211, 365

definition .................................................... 26

direct ............................................................ 85

lifecycle ....................................................... 28

processing ................................................ 207

SAP ERP HCM ........................................... 99

special categories .................................... 33

Personnel Administration (PA) ... 143, 193

427

Index

Plan variant ................................................. 102

Planning statuses ...................................... 102

Plant ............................................................... 202

Pocedural model ....................................... 257

Principle of minimization ..................... 250

Principle of proportionality ................. 361

Principles of processing ......................... 354

Privacy impact assessment (PIA) .......... 51,

127, 128, 378

Procedural model ........ 124, 129, 220, 246,

254, 287

Process Control Layer (PCL) .................. 337

Process organizational attributes

(POAs) ....... 119, 121, 197, 218, 227, 233,

239, 242, 247, 358

Processing .................................................... 113

justifications ............................................. 35

list of activities ......................................... 75

principles .................................................... 31

Processing entities ...................................... 25

Processor ......................................................... 29

Profile administrator .............................. 374

Profitability Analysis (CO-PA) .............. 205

Project approach comparison ............. 130

Project implementation ......................... 111

Proxy provider ........................................... 328

Pseudonymization ...................................... 47

Pupose rules ................................................ 231

Purchasing organization ....................... 202

Purpose ...................... 54, 139, 227, 290, 358

limitation ................................................ 357

Purpose attributes .................................... 213

Purpose of processing ................................ 29

Purpose risk ................................................ 252

Purpose-based processing ..................... 197

R

Read Access Logging (RAL) .... 63, 122, 285

activation ................................................ 289

automated search ................................ 304

channels ................................................... 287

configuration ......................................... 297

ID number ............................................... 304

logs ............................................................. 288

recording ................................................. 308

Read Access Logging (RAL) (Cont.)

scope .......................................................... 285

setup and maintenance ..................... 287

transport, import, and export ......... 312

Read logging ............................. 123, 127, 373

Recipient .......................................................... 29

Record of processing ................................... 52

Record of processing activities

(RoPA) .................................... 114, 128, 130

Recordings ................................ 293, 295, 297

Rectification ................................................... 55

Redundancy ................................................ 320

Reference data ............................................... 82

Reference user ............................................ 241

Religious beliefs ............................................ 34

Remote function call (RFC) ............ 64, 123,

199, 259, 339

connections ............................................ 282

Report Painter ............................................... 97

Report RPDINF01 ...................................... 102

Report Writer ................................................. 97

Residence periods ........ 140, 154, 165, 170

expired ...................................................... 171

Residence rules .... 134, 139, 151, 156, 162

Retention Management (RM) ............. 135,

217, 228

Retention periods .......... 70, 117, 139, 141,

160, 218, 229, 231, 232

Retention rules .................................. 134, 230

Retention Warehouse (RW) ................... 136

RFC client ...................................................... 306

RFC interfaces ............................................. 340

RFC server ..................................................... 306

Right of access .............................. 41, 69, 256

Right to be forgotten .................................. 42

Right to rectification ................................ 365

Risk definition ................................... 253, 254

Role-based access control concept

(RBAC) ....................................................... 239

Roles ............................................................... 249

Root organizational unit ........................ 203

Rules ............................................................... 153

activation ................................................ 233

generation ............................................... 235

group status ........................................... 236

428

Index

Rules (Cont.)

groups ....................................................... 235

Runtime ........................................................ 341

S

Salaries ............................................................. 96

Sales documents .............................. 220, 228

Sales order .................................................... 210

Sales organization ..................................... 202

SAP Access Control ......................... 121, 126

SAP Business Suite .......................... 117, 219

data .............................................................. 81

technical integration .......................... 108

SAP Business Warehouse

(SAP BW) ................................ 107, 203, 359

SAP Claims Management ....................... 116

SAP Collections and Disbursements

for Insurance .......................................... 116

SAP Customer Relationship

Management (SAP CRM) ............ 82, 292

middleware ............................................. 108

personal data ......................................... 103

Web Client ............................................... 107

SAP Enterprise Services ............................ 64

SAP Enterprise Threat Detection ........ 123

SAP Environment, Health, and

Safety (EHS) Management .................. 34

SAP ERP ..................... 81, 107, 282, 319, 348

personal data ........................................... 84

SAP ERP Controlling ................... 93, 94, 248

SAP ERP Financials ............ 85, 91, 116, 175

employee data ......................................... 92

SAP ERP HCM ............................. 99, 203, 335

master data ............................................ 100

SAP ERP HCM Organizational

Management ................................ 102, 203

SAP ERP Sales and Distribution ............. 97

SAP Fiori apps ............................................. 244

SAP for Insurance ........................................ 82

SAP Gateway ................................................ 259

SAP Governance, Risk, and Compliance

(SAP GRC) ....................................... 129, 358

SAP Information Lifecycle Management

(SAP ILM) ............. 92, 120, 122, 126, 133,

210, 217, 254, 255, 393

action ......................................................... 186

assign object purpose .......................... 268

blocking master data .......................... 149

objects ................ 150, 221, 232, 260, 273

overview ................................................... 134

rules .................................................. 227, 228

search ........................................................ 269

SAP Landscape Transformation

Replication Server .................................. 64

SAP Master Data Governance

(SAP MDG) ..................... 73, 119, 315, 399

central governance .............................. 317

consolidation .......................................... 319

decentralized maintenance .............. 322

SAP NetWeaver ........................................... 191

SAP Patient Management for

hospitals ..................................................... 82

SAP Policy Management

(FS-PM) ............................................... 82, 116

SAP Process Control ................................. 123

SAP S/4HANA ........................... 219, 244, 331

data .............................................................. 81

SAP Solution Manager ............................. 402

SAP Supplier Relationship

Management (SAP SRM) .................... 282

SAP Supply Chain Management

(SAP SCM) ................................................... 82

SAP Test Data Migration Server

(SAP TDMS) .................................... 331, 333

components ............................................ 335

data protection ...................................... 347

functionality overview ....................... 335

parallel processes .................................. 341

process control ....................................... 337

system landscape integration ......... 346

usage .......................................................... 348

use cases ................................................... 332

user interface .......................................... 336

Scope of processing .................................. 401

Scoring values ............................................. 399

Scrambling ................................ 332, 334, 344

cross-system ............................................ 350

set up .......................................................... 348

429

Index

Scrambling (Cont.)

types .......................................................... 345

Screening ...................................................... 328

Secure data storage .................................. 135

Security .................................................. 47, 114

Security patches ........................................... 50

Segregation of duties (SoD) ......... 251, 320

Sensitive data ............................................. 322

Sensitive information ................................ 88

Separation of clients ................................ 205

Sequence of deletion ............................... 218

Service user ................................................. 240

Shipping costs ............................................ 219

Simulation ................................................... 233

Single Sign-On (SSO) ................................ 374

SOX compliance ........................................ 121

Special categories ...................................... 286

Standard users ........................................... 411

Starting field ............................................... 267

Statistical key figures ................................. 95

Storage control .......................................... 389

Storage limitations ............................ 32, 366

blocking and deleting ......................... 368

Subtypes ....................................................... 194

System architecture ................................. 339

System keys ................................................. 350

System separation ........................... 198, 199

System states .............................................. 259

System user ................................................. 240

T

Table clusters ..................................... 265, 277

Table hierarchy ................................. 263, 270

Table logging ..................................... 122, 372

Target client ................................................ 339

Target groups ............................................. 108

Technical and organizational

measures (TOMs) .......................... 60, 360

Technical controls .................................... 378

examples ................................................. 381

Technical measures ........................ 112, 127

Technical security .................. 112, 124, 125

Test clients .......................................... 332, 333

Third-party ..................................................... 29

Time constraint ......................................... 101

Time limits ................................................... 113

Time offsets ........................................ 228, 229

Time reference ........................................... 228

Time-based blocking ................................ 193

Trade union membership ......................... 34

Training clients .......................................... 333

Transaction .................................................. 299

AOBJ .................................................. 260, 261

BP ................................... 293, 302, 308, 311

BUP_REQ_UNBLK ....................... 178, 180

CVP_DISPLAY_LOG ............................. 395

CVP_PRE_EOP .................... 169, 171, 172

CVP_UNBLOCK_MD ............................ 179

DB15 ................................................... 220, 261

DTINF_ADJUST_MODEL .......... 261, 264,

268, 278, 283

DTINF_MODELING .............................. 264

DTINF_PROC_COLL ............................. 280

DTINF_START_COLL ........................... 279

DTINF_TEST_MODEL ................ 269, 276,

279, 281

FB01 ............................................................ 171

FB03 .................................................. 175, 184

FBL5N ......................................................... 177

FK01 .............................................................. 85

ILM_DESTRUCTION .......... 185, 236, 398

ILM_LHM ................................................. 191

ILMARA .................................. 150, 229, 234

IRM_CUST_CSS ............................. 162, 235

IRMPOL .... 149, 151, 158, 160, 163, 166,

235, 237, 394

IRMRULE ............................... 230, 231, 237

IRMRULE_ACTIVATE ........................... 233

ME21N ....................................................... 243

MK01 ............................................................. 85

OBR8 .......................................................... 220

OMB9 ......................................................... 219

PA30 ........................................................... 100

PFCG ................................................. 191, 398

RMPOL ...................................................... 168

RSUSR200 ................................................ 406

RZ11 ............................................................. 403

S_ALR_87012177 ....................................... 92

S_ALR_87013611 ....................................... 94

SA38 ........................................................... 266

SARA ....................................... 185, 218, 236

430

Index

Transaction (Cont.)

SARI .................................................. 386, 393

SCASE ......................................................... 192

SE06 ........................................................... 402

SE11 ............................................................. 266

SE16 ......................................... 267, 386, 396

SE18 ............................................................. 284

SLG1 ............................................................ 395

SM37 ........................................................... 395

SPAM ......................................................... 401

SPRO ............................. 143, 149, 162, 257

SRALMANAGER ....... 289, 290, 292, 293,

295, 297

SRALMANANGER .................................. 302

SU21 ......................................... 243, 259, 288

TDMS ......................................................... 336

VA03 .......................................................... 211

VF03 ........................................................... 213

VL03N .............................................. 182, 212

VORA ............................................... 220, 230

VORI ........................................................... 219

VORL .......................................................... 220

XD01 ........................................................... 168

XD02 .......................................................... 173

XD03 .......................................................... 173

XK01 ............................................................. 85

Transactional data .......... 83, 106, 140, 340

blocking .......................................... 149, 181

Transmission control .............................. 389

Transparency ................... 37, 116, 126, 256,

321, 356

Transport ...................................................... 400

Transport control ...................................... 390

Transport Management System

(TMS) ................................................ 371, 403

Transport requests .................................... 251

U

UI channels .................................................. 292

Unblocking ................................................... 179

request ....................................................... 178

Unified Connectivity solution

(UCON) ...................................................... 124

User activity ................................................. 303

User administration ................................. 412

User concept ................................................ 409

User control ................................................... 62

User data ......................................................... 92

Users ............................................................... 239

V

Validation mechanisms .......................... 319

Vendors ........................................................... 85

master tables ............................................ 87

Vulnerabilities ............................................ 370

W

Web Dynpro .............................. 288, 291, 296

Where-used list ........................................... 384

First-hand knowledge.

Volker Lehnert, Iwona Luther, Björn Christoph, Carsten Pluder, Nicole Fernandes

GDPR and SAP: Data Privacy with SAP Business Suite and SAP S/4HANA430 Pages, 2014, $109.95 ISBN 978-1-4932-1712-0

www.sap-press.com/4652

We hope you have enjoyed this reading sample. You may recommend or pass it on to others, but only in its entirety, including all pages. This reading sample and all its parts are protected by copyright law. All usage and exploitation rights are reserved by the author and the publisher.

Volker Lehnert has held various positions in compliance and security at SAP since 2000. Since 2012, he has worked in SAP Application Innovation Services (AIS) as the product owner of data protection solutions, defining the data protection func-tions of the SAP Business Suite and SAP S/4HANA.

Carsten Pluder has been working for SAP in support and development since 1999. He currently works for SAP Appli-cation Innovation Services (AIS) as lead architect for data protection for the SAP Business Suite and SAP S/4HANA. He focuses on supporting SAP customers in the archiving of their

data and using SAP ILM.

Iwona Luther has been working for SAP for 20 years in the field of data archiving, which has evolved over the years to SAP Information Lifecycle Management. She is the product owner of SAP ILM. She is responsible for data archiving cour-ses through SAP Education.

Nicole Fernandes has worked as a translator for English, French, and German since 2005. Her fields of expertise are software/information technology and medical research/genetics. Her projects have included the translation of specia-lized ERP systems and industry-specific software solutions for

the temporary employment sector.

Björn Christoph has been working for SAP as a software architect since 2002. He has been focusing for several years on topics such as data protection and software security in the SAP software.

https://www.sap-press.com/gdpr-and-sap_4652/?utm_source=AWS&utm_medium=readingsample&utm_campaign=Browse%20the%20Book&utm_content=1712

“Authorization Concept” Contents Index The Authors · LOAs EKORG (Purchasing Organization ) is the field in which you define the pur-chasing organizations these authorizations

Documents