Once you have taken in charge the request, you need to execute the check which warnings or errors appear in the request.

Then, you should modify the request to be able to have the possibility to check it.

Go to the master data tab and click on the check button.

Once the request is approved, you will see the “call transaction” button. This button will execute the changes requested in the remote system. But before pressing “call transaction”, you need to select the lines you want to process (you might not want to process the whole request !). 

Even if you have approved the request you can only execute it partially by selecting the appropriated lines. 

If the execution is blocked by some errors, you will get an error flag on the line.

In addition, the application will provide a new log (“technical log”) below the “business rule log”.

When double clicking on the red flag, you will display the technical log. The technical log provide the details of the issues as the system does by using manually the transaction. 

Some specific errors are already known:

• This case happens when you try to process again (call transaction) a line that has already returned an error in the same session.
• To correct this issue you have to log off and log in again

• This case happens when a user is already in change mode in the standard hierarchy (i.e. KSH2 or OKEOEN).
• To correct this issue you need to ask the user to go out from that transaction.

Once the processing complete, you need to set manually the “complete” status.

Even though the workflow request shows no errors, you have to ensure that the information contained in it is in line with the standard Finance costing master data:

1) Cost Center - Master Data rules and standards

2) Check if the user is an authorized requester (GBU controller and for the GBU to which the data refers to);

3) Check consistency between the codification and the target P&L heading for PF2 or WP2.