Change Approval Process

To create an actual change approval transaction based on the changes made, a server script must run.

The default name of this script is “Create new change approval processes”.

(Note: It can be different in the customer environment)

During implementation, a schedule is set up which will run this server script periodically (e.g., every 1 or 5 minutes). After execution, the actual change approval process is created.

(Your application manager is able to see the schedule for change approval creation)

A change approval will appear in the worklist of the user(s) linked to the role ‘Business Controller’ in the activity ‘approve’.

In the transaction information regarding when it was changed, by whom, for whom and what the old and new values of the changed field are.

In the example for supplier ‘DEMO’ a new bank account was added.

There are now to options: Approve and Reject.

If the user will approve, the change approval process will be fully approved, and the change is accepted.

If the user will reject, the change is reverted (the bank account is in this example deleted) and the transaction is sent (back) to the worklist of the initiator of the change.

The initiator can only reject the process (which will lead to full rejection of the process). If needed, the change can be executed again by the same user, considering the possible feedback given in the rejected change approval transaction.