Field Masking – 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 transaction PA30.

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

“Field Masking for SAP GUI” is a solution to protect sensitive data on SAP GUI screens at field level.Product “Field Masking for SAP GUI” is delivered to customer as add-on (UIM 100). To achieve Role based masking, Add-on UIM 100 must be installed in customer system.

Requirement

Role based masking is required for transaction PA30, “Social Security Number” and “Date of Birth” of Employees in Info type 2 (Personal Data) need to be masked.

Maintain Masking configuration

Configure Technical Information (Table Name-Field Name) of field in masking configuration.

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

Follow the given path:

SPRO -> SAP NetWeaver -> Field Masking for SAP GUI -> Masking Configuration->Maintain Masking Configuration

Social Security Number

Date of Birth

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 UI Data Protection, please refer blog post UI Data Protection – Role based masking scenario in PA30.