‘Dual Control’ helps to prevent unauthorized changes to the IMPORTANT and ‘SENSITIVE’ fields in the master records in the system. (All such sensitive fields are defined in the Table T055F when customizing the application. And these fields are defined per Company Code and per Client.) Consider, for example, a sensitive field such as ‘payment block’ in a vendor master record. When a user changes this field’s content, the system requires another user (usually of HIGHER authority) to approve this change and an audit trail is maintained of all such changes. Unless ' the change is approved, in this example, this particular master is blocked by the system for considering the same in the next ‘payment RUN.’

Open table as spreadsheet Activity Customer Vendor
Display changes (accounting area) FD04 FK04
Display changes (CENTRALLY) XD04 XK04
Confirm changes, individually FD08 FK08
Confirm changes, in a list FD09 FK09

‘Dual Control’ helps to prevent unauthorized changes to the important and ‘sensitive’ fields in the master records in the system. (All such sensitive fields are defined in the Table T055F when customizing the application. And these fields are defined per Company Code and per Client.) Consider, for example, a sensitive field such as ‘payment block’ in a vendor master record. When a user changes this field’s content, the system requires another user (usually of higher authority) to approve this change and an audit trail is maintained of all such changes. Unless ' the change is approved, in this example, this particular master is blocked by the system for considering the same in the next ‘payment run.’

Open table as spreadsheet Activity Customer Vendor
Display changes (accounting area) FD04 FK04
Display changes (centrally) XD04 XK04
Confirm changes, individually FD08 FK08
Confirm changes, in a list FD09 FK09