Transportation Management with SAP LES

16
EDI and IDocs
Indirect Way via Output Control
Direct Way from the Application to the
Interface
SAP Application
e.g. Delivery or Shipment Processing
SAP Application
e.g. Delivery or Shipment Processing
Document
NAST: Output
Processing
IDoc
NAST
Entry
IDoc Interface
IDoc
External Successor System
Figure 16.5 Process Overview for Outbound IDocs
Note that there is a difference between indirect and direct IDoc creation. With
direct IDoc creation, the IDoc is generated from within the application and transferred
to the IDoc interface by means of the MASTER_IDOC_DISTRIBUTE. With
indirect IDoc creation, on the other hand, output control is used.
16.3.2 Inbound IDoc Outputs
In the case of inbound IDoc outputs, all subsystems and external systems write IDocs
to the big SAP database. A process code, which is assigned to an IDoc type and the
partner profile, is used on the SAP software side to call a function module, which
in turn handles the further processing of the IDoc, creates any new entities that are
required, and makes the corresponding changes in the sales document. Figure 16.6
shows an overview of the processing steps for an inbound IDoc output.
There is both direct and indirect processing for inbound IDoc outputs, too. Both
processing types are basically the same as those in outbound processing, except
that the indirect process for inbound outputs runs via the SAP workflow and not
output control.
518
© 2014 by Galileo Press Inc., Boston (MA)