Skip to Content
Product Information

UI Data Protection – Role based masking scenario in SE16, FB03, and FBL1N

Introduction

In this blog post, we will learn how to mask “Amount in Document Currency” field in BSEG table in transactions SE16, FB03, and FBL1N.

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

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

Amount in Document Currency

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_AMT_DOC_CURRENCY” 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

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.

Amount in Document Currency
  • Click on “New Entries” button
  • Enter “Table Name” as “RFPOSXEXT
  • Enter “Field Number” as “WRSHB
  • Enter “Logical Attribute” as “LA_AMT_DOC_CURRENCY
  • Enter “Description” as “Amount in Document Currency
  • Click on “Save” button
  • Click on “Mass Configuration” button which is required to generate technical addresses for Module Pool Programs

Conclusion

In this blog post, we have learnt how Role-based masking is achieved in transactions SE16, FB03, and FBL1N for maskingAmount in Document Currency” field.

9 Comments
You must be Logged on to comment or reply to a post.
  • Thanks Amit Kumar Singh for the blog. I have few queries regarding the same.

    • Will this solution support custom transactions?
    • Secondly i noticed you did not provide any tcode etc. details only field level how does it work under the hood?
    • Thirdly how will it work in SAPUI5 apps as you don’t have technical details, will we use the object id’s of something?

    Nabheet

    • Hi Nabheet,

      Please find my response –

      1. UI Masking supports Custom Transactions, prerequisite is Technical details of field should be available
      2. UI Masking works on Program Name, Screen Number, and Field Name so it is not dependent on transaction level
      3. For SAPUI5 there is separate configuration. Service Name, Entity, and Property should be configured. Please refer Product Documentation for more details

      Thanks,

      Amit Kumar Singh

    • Hi Manos,

      Please let us know what do you want to mask in BW4HANA.

      Generally, we do not cover Analytics reports in BW4HANA.

      Regards,

      Amit Kumar Singh

  • Hi Amit – by following the admin guide, we config a role based authorization for a field in transaction code FI03. But it’s not working, the field is not masked for an unauthorized user. Can you share some tips/advise if I missed something? Thank you in advance.

    • Hi Rimwell,

      Please check that you have configured correct Technical Address for the field. Also, make sure that PFCG Role is not assigned to the logged-in user.

      If you still face issue, please raise a ticket with us so that we can check and apply proper configuration.

      Regards,

      Amit Kumar Singh

  • Hi Rimwell

    Did you manage to solve your query. If not, please raise a message in GRC-UDS-DO and the team will be happy to help.

    Best,

    Deepak

    Product Management – UI data protection

  • I am trying to mask employee bank data, but unable to find – UI Data Protection Masking for SAP S/4HANA in SPRO tree. I am using 1909 system, is it a separate add-on. Can you please advise how I can get – UI Data Protection Masking for SAP S/4HANA.

    • Hi Manoj,

      As I have mentioned in the “Prerequisite” section of my blog post that in order to achieve masking in S/4HANA system, “UI data protection masking for SAP S/4HANA” solution must be installed so you need this solution to get the fields masked.

      You need to purchase the following Add-on for masking –

      UI data protection masking for SAP S/4HANA

      Regards,

      Amit Kumar Singh