Errors and Error Handling

In the automated Action Handler, error handling controls who is to be informed in the case of an error, that is, if an action cannot be posted.

Prerequisites

See Automated Action Handler.

Features

Error

If an individual function cannot be carried out within an action, the system resets all functions belonging to this action which have already been carried out (as far as possible), so that the data is consistent again. According to the data security concept, the action is then not considered as posted.
For example, if you have assigned several actions to an action point and the second action is canceled, the system still tries to carry out the subsequent actions. According to the data security concept, only the action which was canceled is then considered as not posted.
Actions which have not been posted are put in the error queue of the workflow. The user responsible can call up the event queue (transaction SWEQADM) in order to deliver the event which triggered the action again; the system then repeats the action. You define which user is to be responsible in error handling (see below).

Note
In order to improve runtime, events are bundled within the system on the level of actions and processed as a package. Such a package can contain several orders.

Example:

Event 1: Order 4711 reached AP1

Event 2: Order 4712 reached AP1

Action A1 with the functions production tracking and productions backflush is assigned to action point AP1.

First, the system carries out the production tracking function for the orders 4711 and 4712 at action point AP1; then it carries out the production backflush function for both orders in a separate step.

If an error occurs, for example during the production backflush for the order 4712, the system resets the entire action A1 for both orders. If no error occurs, the action A1 is posted as a package.

If an error occurred in the action A1, and the action A2 has been assigned to the action point AP1, the system then tries to carry out the action A2 for both orders.

End of the note.

Error Handling

If an error occurs in the automated Action Handler, an SAPOffice notification (mail and possibly an additional express mail) can be sent to the system user responsible. This can be

the system user who has been entered as the person responsible for the combination of action point and action
the system user who has been entered as the person responsible for the action point itself (if there is no person responsible as described above in point 1)
the workflow administrator (if there is no person responsible as described above in points 1 and 2)

Note Note

If you have assigned several actions to one action point, error handling is carried out individually for each action.

End of the note.

As an alternative to SAPOffice notifications you can also implement customer-specific error handling via SAP Business Workflow. If you do so, the person responsible receives a work item instead of a mail in his SAPOffice inbox.

Note Note

For this purpose, choose Start of the navigation path Tools Next navigation step Business Workflow Development Administration Event Manager Type Linkages End of the navigation path or transaction SWETYPV, and enter object type /SAPAPO/MF, event ACTIONHANDLER_ERROR_OCCURRED, receiver type SWW_WI_CREATE_VIA_EVENT.

End of the note.

Activities

Delivery of Events with Errors

In order to deliver an event from the event queue of the workflow again, proceed as follows:

Choose Tools Business Workflow Development Administration Event Manager Event Queue (transaction SWEQADM).
This takes you to event queue administration.
Choose the tab page Linkages with errors.
Select the line with the event for which an error occurred, and choose (Start delivery).

Information on Error Handling

You make all entries for error handling within the action point maintenance. Proceed as described in the following sections: