This chapter provides an overview of the necessary settings within the SAP R/3 system as well as information on additional adjustments made available in the R/3 customer functions.

You can also use the following information sources:

• Implementation Guidelines/SAP Reference IMG (Online)

• Master Menu (Online)

• For more in-depth knowledge the following written documentation is available:

• RFC manual

• ALE consultancy manual

• Workflow manual

Transferring IDocs using Remote Function Call takes place on the TCP/IP basis. An error occurring will break the link between the transmitter and recipient. The transmitter can use the return codes of the RFC functions used to control whether the function was successfully called up in the recipient system or not. If there are any TCP/IP errors the link must be unconnected and the IDoc must be re-transmitted.

Errors in the ALE service layer, occurring during transmitting or receiving the IDoc are indicated as technical errors. The R/3 system generates a work item for every incorrect IDoc when technical or logical errors occur (see below). A work item is part of workflow processing and functions as an error message that is sent to all the users in the system who are assigned to a certain position. The error message contains an error text. If one of the users fetches the message from the inbox, analyses the error and posts the document the error message will disappear from all inboxes.

On receipt the IDoc is saved in the database before any processing begins, thus unlinking the communication from processing. If an error occurs during processing, e.g. updating with not-permitted or incorrect transaction type, i.e. a logical application error, SAP creates a work item with the appropriate error text.

If a logical error occurs when processing an IDoc a message is sent to one or several users. The following text describes how the error processing is set up.

Technically the system triggers a standard task specific to the message category. The standard task has to be assigned to a position that has either a user or holder.

You can create one or more positions which are enclosed in a central organizational unit.

The following options then occur:

• You can enter an organizational unit in the partner definition but no further specifications in the partner profile per message category. All the messages will then go to the users assigned to that organizational unit who have a position where the standard task appeared.

• You enter a defined point instead of the organizational unit in the partner definition.

• You override the entry in the partner definition with entries in the partner profile for a message category.

Normally you would use the first alternative. However if you have two subsystems which serve two different transportation planning points, where the administrators for the errors are two different people, you could use the second alternative to send the same error via the two different partner numbers.

The display in the inbox can be individually adjusted. The following describes a setting that allows you to display the messages by IDoc category:

Call up transaction SIN1. Click on Configuration under settings and create a new configuration. Select the Start Configuration button which will ensure that this configuration is always automatically used. Save.