19.09.2016 Views

Transportation Management with SAP LES

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

IDocs 16.3<br />

Indirect Way via the <strong>SAP</strong> Business<br />

Workflow<br />

Direct Way via Function Modules into<br />

the Document<br />

<strong>SAP</strong> Application<br />

e.g. Delivery or Shipment Processing<br />

<strong>SAP</strong> Application<br />

e.g. Delivery or Shipment Processing<br />

Document<br />

Workflow<br />

Document<br />

IDoc<br />

IDoc Interface<br />

IDoc<br />

External Successor System<br />

Figure 16.6 Process Overview for Inbound IDocs<br />

16.3.3 Structure of an IDoc<br />

In general, when the term “IDoc” is used, it means an (electronic) document. The <strong>SAP</strong><br />

system has standardized this kind of document, and also given it a specific task.<br />

IDoc Type, Output Type<br />

This task is correctly referred to as the IDoc type. The IDoc type can take on the task<br />

of reporting a shipment to the forwarding agent, for example, IDoc type SHPMNT.<br />

Once the forwarding agent has accepted the shipment order, he can confirm this<br />

using the IDoc type SHPCON. To ensure that you do not have to set up separate<br />

agreements <strong>with</strong> every partner, the <strong>SAP</strong> system has standardized the content of<br />

the IDocs. For example, the SHPMNT IDoc type always has the same structure,<br />

regardless of which forwarding agent you are dealing <strong>with</strong>.<br />

Segments in the IDoc<br />

As just indicated, IDocs have a specific structure. Related data, such as data on<br />

address, packaging, and dangerous goods, is grouped together in the IDoc itself.<br />

Personal Copy for Tina Mastrup, user id 9f19c686-d5e1-4016-94fd-ebc72e1b8f7e<br />

519

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!