Processing Using SAP Tasks

The tasks for the IDoc Interface are divided according to inbound and outbound processing. Formal errors can occur during inbound processing, for example, if the partner profile for the control record is not found. You can also activate the syntax check for IDocs in the partner profiles. An error which occurs during such a syntax check is assigned to a special standard task (see also Exception Handling: Procedure).

Exception handling in the IDoc Interface is enhanced in inbound processing with exception handling in the application, which can respond to status "51" (application document not posted).

The recipient of a work item can then correct the error and trigger conversion of the received IDocs again or mark the IDoc for deletion.

Permitted Agents

In all exception situations where the sender is defined in the partner profiles, the permitted agents are read from the profiles. If agents are entered for the special logical message, these are notified, otherwise the agents defined for this partner in the general partner profiles are notified.

In all exception situations where no matching partner profile could be read, the agents are determined from the system parameter table (IDoc Administration: Global Parameters). SAP strongly recommends that you enter an agent here.

As an agent, you can enter other organizational units (for example department, job) for notification, in addition to an SAP user name.

In order for the permitted agents to be notified by work item, they must be assigned to the corresponding SAP task. For more information, see Rule Resolution in Exception Handling.

Internal and External Error Messages

Internal error messages refer to errors in your SAP System. These error messages or error statuses are associated with system process codes (in the IDoc Interface). External error messages are status confirmations for errors in the external system. They are associated with status process codes. If any internal errors (status 51) are found in the application, the application itself generates the corresponding work item, that is to say, no process codes are used in the IDoc interface here.

Special Features of the "File" Port Type

Files can contain several IDocs. The IDoc Interface reads these IDocs separately and stores them in the database. Therefore, if a read error occurs, only the IDocs which have not yet been saved are affected. The point at which the error occurred is marked. If the error cannot be corrected, the file can be read again manually from the point at which the error occurred. For more information, see Exception Handling: Procedure.