UI Data Protection – Role based masking scenario in PA30

Introduction

In this blog post, we will learn how to mask “Social Security Number” and “Date of Birth” of Employees in Info type 2 (Personal Data) in transactions PA20, PA30, SE16 and SE16N.

A PFCG Role will be used for the authorization check which will allow users with the specified role to view the field value. If a user does not have this role, it means the user is not authorized and data will be protected either through masking, clearing, or disabling the field.

The end result for unauthorized users will look like below:

Prerequisite

Product “UI data protection masking for SAP S/4HANA” is used in this scenario to protect sensitive data at field level and must be installed in the S/4HANA system.

The product is a cross-application product which can be used to mask/protect any field in SAP GUI, SAPUI5/SAP Fiori, CRM Web Client UI, and Web Dynpro ABAP.

Let’s begin

Configuration to achieve masking

Logical Attribute is a functional modelling of how any attribute such as Social Security Number, Bank Account Number, Amounts, Pricing information, Quantity etc. should behave with masking.

Configure Logical Attribute – Follow the given path:

SPRO -> SAP NetWeaver -> UI Data Protection Masking for SAP S/4HANA -> Maintain Metadata Configuration -> Maintain Logical Attributes

Social Security Number

Birth Date

Maintain Field Level Security and Masking Configuration

Here, we will define how masking will behave with the logical attribute that we created in above step.

Follow the given path:

SPRO -> SAP NetWeaver -> UI Data Protection Masking for SAP S/4HANA -> Data Protection Configuration -> Maintain Field Level Security and Masking Configuration

Follow below mentioned steps:

• Click on “New Entries” button
• Enter “Sensitive Entity” as “LA_SOCSECNO” and press “Enter” key. “Description” and “Application Module” will get populated in corresponding fields
• Check “Enable Configuration” check-box
• Select “Role Based Authorization” option
• Enter “PFCG Role” as “ZTEST“. In this example, we have used a blank role “ZTEST”. Customers can use any role as per their requirement.
• Enter “Field Level Action” as “SSN_PATTERN”
• Click on “Save” button

• Click on “New Entries” button
• Enter “Sensitive Entity” as “LA_BIRTHDATE” and press “Enter” key. “Description” and “Application Module” will get populated in corresponding fields
• Check “Enable Configuration” check-box
• Select “Role Based Authorization” option
• Enter “PFCG Role” as “ZTEST“. In this example, we have used a blank role “ZTEST”. Customers can use any role as per their requirement.
• Enter “Field Level Action” as “MASK_FIELD”
• Click on “Save” button

Maintain Technical Address

In this step, we will associate the Technical Address of the fields to be masked with the Logical Attributes.

You can get the Technical Address of a GUI field by pressing “F1” on the field.

Follow the given path:

SPRO -> SAP NetWeaver -> UI Data Protection Masking for SAP S/4HANA -> Maintain Metadata Configuration -> Maintain Technical Address

Follow below mentioned steps:

Under “GUI Table Field Mapping”, maintain technical address for following fields.

• Click on “New Entries” button
• Enter “Table Name” as “P0002”
• Enter “Field Number” as “PERID”
• Enter “Logical Attribute” as “LA_SOCSECNO”
• Enter “Description” as “Social Security Number”
• Click on “Save” button
• Click on “Mass Configuration” button which is required to generate technical addresses for Module Pool Programs

• Click on “New Entries” button
• Enter “Table Name” as “P0002”
• Enter “Field Number” as “GBDAT”
• Enter “Logical Attribute” as “LA_BIRTHDATE”
• Enter “Description” as “Date of Birth”
• Click on “Save” button
• Click on “Mass Configuration” button which is required to generate technical addresses for Module Pool Programs

Conclusion

In this blog post, we have learnt how Role-based masking is achieved for “Social Security Number” and “Date of Birth” fields.

Note:

For information on masking in UIM, please refer blog post Field Masking – Role based masking scenario in PA30.