Contents

Introduction ............................................................................................................................................ 2
Configuration Guide ................................................................................................................................ 2
1. Define Sensitive fields ...................................................................................................................... 2
Master Data ............................................................................................................................................ 6
1. Making changes to master data ....................................................................................................... 6
2. Confirming changes to master data.................................................................................................. 7

Introduction
SAP provides dual control functionality to control and securely manage changes made to sensitive fields
in Vendor and Customer master data records.
Once this functionality is activated changes made by one user role, needs to be confirmed/authorized by
another user role for the change to take effect. Till then the changes remain visible but the account will
be blocked for transactions such as payment runs etc. This facilitates tight control over unauthorized
modifications to vendor and customer master fields.
In this document we will discuss the configuration that needs to be in place for activating dual control for
vendor master fields, keeping in mind that similar functionality is available for customer master as well.

Configuration Guide
There are few configurations that are needed to be setup before dual control is activated. Note that this
customization will be applicable for all account groups.

1. Define Sensitive fields

IMG Path:

When you click and New Entries and click on the drop down (F4) on the Field Name the following
available fields will be shown. As shown below there are many fields from general, company code and
purchasing org available.

For example we will be defining Back account as a sensitive field.

Note Multiple fields can be defined based on the requirement.

Master Data
1. Making changes to master data
Transaction: XK02
The bank account details are added.

The following information popup will appear.

When the record is saved the following message will be displayed.

2. Confirming changes to master data

Transaction: FK08
For confirming changes for one vendor master at a time we can use this transaction.

Once we hit the Confirm button the record will be release for transactions.
Transaction: FK09
This transaction can be used to confirm changes to multiple account in one go and can be run at
Company code level to select all vendor to be confirmed.

You are able to double click on each record to drill into see what level change it is and confirm all
changes using the highlighted button.

Note The person confirming the changes should be a different to the person who made the change, if
not this will not be allowed as shown below.

10

Author: Malith Tharaka Perera

E-Mail: malith_p@hotmail.com / tharakap@learnsaptips.com
Website: www.learnsaptips.com
View my profile in LinkedIn

Disclaimer
This article is done based on my research and readings, unless otherwise stated. The views expressed are
my own and not of anyone else.
Author accepts no liability for the content of the articles in this website or for the consequences of any
actions taken on the basis of the information provided. Using this information is at the users own
discretion and responsibility.

11