Hide or Encrypt Bank Account Number

[Former Member]

Hey Guys,

The client has a requirement in FK03 to hide/encrypt the bank account number in the bank details table in the tcode FK03.

When using the transaction FK03, I am having a problem with hiding or encryting a user's bank account number. When you execute the FK03 transaction, select a vendor and go to the next screen, you are then taken to the Payment Transactions Screen. User bank account information is displayed on this screen. I do not want the entire table hidden, but I am unable to hide or encrypt the bank account number. I am unable to find any authorization objects to control this specific field. Does anyone have suggestions on how to implement this?

[Former Member]

Transaction "OB23" will help you further. There was a discussion here about it a while back and a few more in the ERP forums if you search for them.

"FK03 AND bank" should work as well in the search term.

Let us know if that covers your requirement.

Cheers,

Julius

[Former Member]

Hello Tiffany,

This cannot be controlled via authorizations. You have to use transaction OMSG for your vendor account group say LIEF under General Data --> Field status group: Payment transactions you can choose to hide, display, optional entry or mandatory the field status.

You can further check the status of the field at purchasing organization level OMFK (which is not relevant in your case)and at the transaction level OMSX.

[Former Member]

Thank you for the information. I have found out that this cannot be controlled via authorizations. I need a way to hide or encrypt the bank account number to all the users in the system except the accounting department. Is there a way to encrypt or hide that particular field but display the remaining bank details?

I may not be able to use the OMSG/OMSR tcodes as I am looking to hide/encrypt a specific column (account number) in the Bank details.

[Former Member]

If all users except the accounting department may not see the number, and the accounting department must be able to see the number from the standard transactions in this application area (e.g. FK03, XK02, etc), then you will be best off looking for an enhancement point via which you can add your own coding.

The easiest and least intrusive way in my opinion would be to find one which affects only the payment transactions screen but regardless of the transaction context, and if the user fails an authority-check of your own invention - then modify the internal table to replace the real number with a bogus one.

But remember that if the user can debug in display mode, then they will display the internal table before you modify it, unless you DEFINE it in a macro... (but that is again intrusive, and there still are ways).

If you choose the encrypt / decrypt route, then you will have to fight with the field types of the bank table and can still make the same mistakes... except that someone looking directly at the table via a data broowser will not see much either... (until they find the decryption function and run that).

Please also a take a look at [SAP Note 1257033 - Cookbook: Modification/enhancement for standard SAP system|http://service.sap.com/sap/support/notes/1257033] before proceding with an enhancement.

Cheers,

Julius

[Former Member]

Hello Tiffany,

You are right since you want just field it is not possible via OMSX. Because the bank details would hide the entire table on the screen and not just the field bank account number.

[Former Member]

It was decided that we will use screen variants to achieve this.

Thanks all!