If a logical error occurs when an IDoc is being processed, a message will be sent to one or several users. This procedure, in accordance with which an error is processed, is described below.

From a technical point of view, the system initiates a standard message-type-specific task. The standard task must be allocated to a position which, in turn, must be assigned users or owners.

You can create one or several positions. These are parenthesized in a central organizational unit.

Various options are available here:

1. You can enter the organizational unit globally in the partner definition and make no further specifications for any of the messages types in the actual partner profile. All of the messages are then sent to the users, who are assigned to the organizational unit, with whose position the Standard task is associated.
2. You can enter a specific position in the partner definition and not the organizational unit.
3. You can also override the entry in the partner definition with entries in the partner profile for a message type.

Under normal circumstances version 1 will suffice. If, however, you have two external systems that have two different warehouse numbers, and the persons dealing with the errors are two different warehouse employees, you can use version 2 to handle the same error via the two different partner numbers.

The hierarchy is illustrated in the following diagram:

All settings can be made via the Implementation Guide or directly via transaction /nPPOM.

1. An organizational unit must first be defined. This corresponds to a root to which many positions can be connected.
2. Create a position.
3. Assign the appropriate users.
4. Assign the standard tasks.

• Error inventory count data

• Error confirm TO

• Error goods movements

• Error transfer orders

• Error moving storage unit

• Error blocking storage bins

• Error transfer requirement

• Information

• Error shipping element data confirmation

• Error picking confirmation