Skip to Content
Product Information

Attribute Based Access Control (ABAC) – Field Masking with Reveal on Demand and Data Block scenario in SE16 (ALV Grid Display, ALV List, and SE16 Standard List)

Introduction

In this blog post, we will learn how to configure masking and data block for “Unrestricted Stock”, “Stock in Transfer”, “In Quality Inspection”, “Restricted Stock”, “Blocked Stock”, and “Returns” fields of MARD table in transaction SE16 based on Plant and Storage Location information.

Attribute based authorizations are dynamic determination mechanism which determines whether a user is authorized to access specific data sets which can be based on the context attributes of the user and data (for example, price of certain sensitive materials are masked).

The end result will appear as:

ALV Grid Display

ALV List

Standard SE16 List

Reveal on Demand

Reveal on Demand provides additional data protection by masking the field value by default, even if the user is authorized to view the data. The authorized user then explicitly chooses the option to reveal the field value on the user interface.

When the authorized user reveals the data, a dialog box (which can be configured to display a confirmation message, reason code, and free text) is displayed. The user then has to specify, for example, a reason for revealing the data. The revealed data is masked again once the timeout takes effect or when the user switches off the reveal option.

  • To unmask the “Unrestricted Stock”, “Stock in Transfer”, “In Quality Inspection”, “Restricted Stock”, “Blocked Stock”, and “Returns” fields information using Reveal On Demand feature, Follow the given Path –

In SE16 transaction screen, Click on “Help” -> “Reveal On <–> Off” option

  • On Reveal On Demand pop-up, select “Reason” as “DVA Data Verification”, enter “Comments for Reveal” as “Unmask to view values”, and click on “OK” button

  • Field value will get unmasked for “Unrestricted Stock”, “Stock in Transfer”, “In Quality Inspection”, “Restricted Stock”, “Blocked Stock”, and “Returns” fields

  • To Again, mask the Field values, Follow the given path –

In SE16 transaction screen, Click on “Help” -> “Reveal On <–> Off” option

  • On Reveal On Demand pop-up, click on “OK” button

  • Unrestricted Stock”, “Stock in Transfer”, “In Quality Inspection”, “Restricted Stock”, “Blocked Stock”, and “Returns” fields will again appear as masked

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 GUISAPUI5/SAP FioriCRM 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 NumberBank Account NumberAmountsPricing informationQuantity 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

Configure Value Range

Value Ranges are a set of pre-populated values which can be used to derive the context under which an action should be executed.

Follow the given path:

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

Enter entries in “VR_SENSITIVE_PLANTS” Value Range

Enter entries in “VR_SENSITIVE_STORAGE_LOCATION” Value Range

Enter entries in “VR_BLOCKED_PLANTS” Value Range

Enter entries in “VR_BLOCKED_STORAGE_LOCATION” Value Range

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.

Policy Configuration

Policy is a combination of rules and actions which are defined in one or more blocks. The actions are executed on a sensitive entity (field to be protected) which has to be assigned to a Policy. The conditions are based on contextual attributes which help derive the context.

Context Attributes are logical attributes which are used in designing the rules of a policy. They are mapped to fields which are used to derive the context under which an action is to be executed on a sensitive entity.

Sensitive Entities are logical attributes which are sensitive and need to be protected from unauthorized access.

Follow the given path:

SPRO -> SAP NetWeaver -> UI Data Protection Masking for SAP S/4HANA -> Data Protection Configuration -> Maintain Policy Details for Attribute based Authorizations

Policy for Field Level Masking

Write following logic into Policy

Policy for Data Block

Write following logic into Policy

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

Unrestricted Stock

Stock in Transfer

Restricted Stock

Stock in Quality Inspection

Blocked Stock

Returned Stock

Maintain Data Blocking 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 Data Blocking Configuration

Plant

Conclusion

In this blog post, we have learnt how Attribute-based masking with Reveal on Demand  and data blocking is achieved in transaction SE16.

Be the first to leave a comment
You must be Logged on to comment or reply to a post.