UI Data Protection – How to mask a field in Module Pool Programs in case Technical Information using F1 key is not available

Introduction

In this blog post, we will learn how to mask a field in Module Pool Programs when Technical Information on press of “F1” key is not available.

In transaction ME22N, Item Details List is one of the fields where you cannot get Technical Information by pressing “F1” key on the field.

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

UI Data Protection Masking for SAP S/4HANA is a solution that allows you to protect restricted and sensitive data values at field level by masking, clearing, or disabling fields for those users who are not authorized to view or edit this data.

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

Item Details List

Maintain Technical Address

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

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

There are some instances where “F1” is not working for some fields. In our scenario, “F1” is not working for “Item Details List” field on “ME22N” transaction screen. In such cases, please follow the given steps to derive the technical address for the fields –

Item Details List

Place the cursor on “Item Details List” field, navigate to menu “System” and click on menu option “Status”.

On “System: Status” screen, Double-Click on “Screen Number” field.

On “Screen Painter” screen, click on “Layout” button.

Double-Click on “Item” list-box.

On “Screen Attributes” screen, you’ll get the field name in “Name” field.

Follow the given path:

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

Follow below mentioned steps:

Under “GUI Dynpro Technical Address”, maintain technical address for the following field.

Item Details List

• Enter “Program Name” as “SAPLMEGUI”
• Enter “Screen Number” as “6000”
• Enter “Field Name” as “DYN_6000-LIST“
• Enter “Logical Attribute” as “LA_ITEM_DETAILS_LIST”
• Click on “Save” button

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_ITEM_DETAILS_LIST” 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 “/UISM/PFCG_ROLE“. In this example, we have used a blank role “/UISM/PFCG_ROLE”. Customers can use any role as per their requirement.
• Enter “Field Level Action” as “MASK_FULL”
• Click on “Save” button
• Click on “Generate Programs” button in order to activate the Module Pool Program

Conclusion

In this blog post, we have learnt how Role-based masking is achieved for a field in Module Pool Program in case Technical Information using F1 key was not available.