Skip to Content
Product Information

Attribute Based Access Control (ABAC) – Data Block scenario in SE16 and PA30 of SAP GUI

Introduction

In this blog post, we will learn how to configure Data Block in SE16 and PA30 transactions to block access of certain sensitive employee records.

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:

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 data block

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

Employee Number

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 – Follow below mentioned steps:

Sensitive Employee List
  • Click on “New Entries” button
  • Enter “Value Range” as “VR_EMPDTBLOCKRANGE
  • Select “Application Module” as “P Human resources
  • Enter “Description” as “Blocked Employee Range
  • Click on “Save” button

Enter entries in “VR_EMPDTBLOCKRANGE” Value Range
  • Execute Transaction Code “/UISM/V_RANGE
  • Click on “VR_EMPDTBLOCKRANGE” Value Range
  • Click on “Display<- -> Change” button
  • Click on “Add New Entry” button
  • Add following entries under “Include Value” tab and 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.

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 Programs for Data Blocking

To achieve Data Blocking for SAP GUI transactions, there is an additional mandatory step i.e. configure the program name of the SAP GUI transaction in Customizing under SPRO -> SAP NetWeaver -> UI Data Protection Masking for SAP S/4HANA -> Data Protection Configuration -> Maintain Programs for Data Blocking. Follow the below steps –

  • Click on “New Entries” button
  • Enter Calling Program as “SAPMP50A
  • Check the “Enable” checkbox
  • Enter Description as “Blocking in PA30
  • Click on “Save” button

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 – Follow below mentioned steps:

  • Click on “New Entries” button
  • Enter “Policy Name” as “POL_DATABLOCK
  • Select “Type” as “Data Blocking
  • Select “Application Module” as “P Human resources
  • Enter “Description” as “Data block in HR Module
  • Click on “Save” button

Write following logic into Policy

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

Follow below mentioned steps:
  • Click on “New Entries” button
  • Enter “Sensitive Entity” as “LA_DATABLOCK” and press “Enter” key. “Description” and “Application Module” will get populated in corresponding fields
  • Check “Enable Data Block” check-box
  • Enter “Policy Name” as “POL_DATABLOCK
  • Enter “Message Class” as “/UISM/UI
  • Enter “Message Number” as “902
  • Click on “Save” button

Conclusion

In this blog post, we have learnt how Data Blocking is achieved in transaction SE16 and PA30 for blocking access of certain employee records.

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