UI Data Protection – Mask Net Price and Effective Price information in SE16 and ME13 transaction

Introduction

In this blog post, we will learn how to mask “Net Price” and “Effective Price” fields in EINE table in transactions SE16 and ME13.

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 for selective masking of sensitive data on SAP S/4HANA user interfaces – SAP GUI, SAPUI5/SAP Fiori, Web Dynpro for ABAP, and Web Client UI. Data can be protected at field level, either by masking the content (replacing original characters with generic characters, such as asterisks) or by clearing or disabling the field.

The solution uses both role-based and attribute-based authorizations, affording customers a high degree of control.

Requirement

Role-based masking is required for SE16 and ME13 transactions. “Net Price” and “Effective Price” fields need to be masked on these transactions. 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.

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

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.

Mass Configuration

For all the above entries, “Mass Configuration” report should be executed which is required to generate technical addresses.

Follow below mentioned steps:

• Select the entry in GUI Table Field Mapping
• Click on “Mass Configuration” button
• Click on “Select All” button
• Click on “Generate Customizing” button
• Save the information

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:

Effective Price

• Click on “New Entries” button
• Enter “Sensitive Entity” as “LA_EFFPRICE” 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_FIELD”
• Click on “Save” button

Net Price

• Click on “New Entries” button
• Enter “Sensitive Entity” as “LA_NETPRICE” 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_FIELD”
• Click on “Save” button

Conclusion

In this blog post, we have learnt how Role-based masking is achieved in transactions SE16 and ME13 for masking “Net Price” and “Effective Price” fields.