Introduction:
Sensitive Data Fields provide a dual control function in SAP to provide more security when changes are made in Business Partner Master Data records. After activating the Sensitive Data Fields functionality, changes done by one user and have to be confirmed by another user (authorized person), thereby facilitating strong control over unauthorized modification. Changes made in relevant Business Partner Master Data are visible but the account is automatically blocked for payment run till the changes are confirmed.
Dual Control:
Dual control is a means of ensuring that critical application processing activities are checked and released by an additional person.
In FS-PM, dual control is integrated into the release step of the New Business, Universal Change, and Change business processes, as well as the application interface of the New Business. The release of the Change services and the Change APIs do not support dual control.
Depending on the user who enters the application data and wishes to release the application, the system checks whether dual control is required. In the Change and Universal Change business processes, the system only checks this if the user has actually changed any check-relevant values during application processing.
Dual control is performed when applications are entered into the system for the first time. Applications that are released again in a reimplementation step are not checked.In Customizing, you define checks to control the conditions under which the system triggers dual control for an application and the user who is to check the application. You can also define checks that are to be performed on a random basis as opposed to general checks.
If none of the conditions defined in Customizing apply to the dual control of an application, the user can release the application. If at least one of the conditions applies, the system categorizes the application as being subject to checking and interrupts the release of the business process.Users who are allowed to check the application receive a work item through SAP Workflow that allows them to resume processing of the application. The checker can release the application, process it, or return it to the first processor.
Symptom:
The vendor should be blocked for payments whenever there is a change in bank details.
Defining the Sensitive Data Fields:
SPRO -> IMG-> Financial Accounting-> Accounts Receivable and Account Payable-> Supplier Accounts-> Master Data-> Preparations for creating Supplier Master Data-> Define Sensitive Fields for Dual Control.
Maintaining Sensitive Fields:
| LFBK-BANKL | Bank Key |
| LFBK-BANKN | Bank Account |
| LFBK-BANKS | Bank Country/Region |
| LFBK-BANK_GUID | BP Bank GUID |
| LFBK-BKONT | Bank Control Key |
| TIBAN-IBAN | IBAN |
| TIBAN-VALID_FROM | IBAN Valid From |
Changing Sensitive Fields in Business Partner Master Data:
1. Execute Transaction Code BP.
2. Enter Supplier Number.
3. Go to Payment Transactions tap.
4. Change Bank Details
5.Save
Confirmation of Change:
Execute Transaction Code FK08
Review and Confirm the changes.
Payment Block (F110):
The vendor is blocked for payment due to unconfirmed changes.
