Inbound Processing


In inbound processing, IDocs are transferred to the interface and stored in the SAP System. The document data is generated in a second step, also in the course of a workflow.


The upstream system transfers an IDoc to the IDoc Interface using the SAP System port. For this reason, you do not have to specify a port in the inbound partner profiles; the IDoc Interface only has to “recognize” the upstream system as a port. A port definition, which provides a unique ID for the upstream system, must be available for the port. The technical parameters of this port definition can (and usually are) overwritten by the upstream system.

The IDoc is “accepted”, that is, saved in the database, if the upstream system is recognized. If your partner is defined with the corresponding message in your partner profiles, the IDoc is then processed further. This is done independently in a second step. This ensures that the external system can transfer the data quickly and reliably (automatically).

The following paths are available for further processing:

·        The direct path using a function module which transfers the IDoc data to the corresponding application document.

·        The indirect path using SAP Business Workflow. When an IDoc is received, a work item is created, that the recipients are offered for execution in their Business Workplace. For more information, see Business Workplace: Workflow Functions.

IDoc type TXTRAW02 is processed using the SAP task TS30000008: A mail is sent to the user (or the organizational unit) that is entered as the recipient in segment E1TXTAD. If this segment is missing, the permitted agent is determined from the partner profiles as the recipient. The mail contains the text from the IDoc data records. You can also send mail attributes such as priority or “executability”.

The indirect path in Release 2.1/2.2 is implemented using process technology. This technology is no longer supported.


Inbound Processing: Procedure

Inbound Processing: Technical Background