
Inbound EDI messages
Use
You can create or change shipment using EDI output.
In this way, the following tasks are possible:
Collective Goods Traffic
The forwarding agent picks up deliveries from the vendor during the preliminary leg. Then the agent puts together the shipment for the main leg and passes on this information to the customer as a shipment notification. Now the customer can easily post a goods issue for the entire shipment (more precisely, for the deliveries it contains).
Transportation planning
A vendor supplies the forwarding agent with the outbound deliveries as transfer requirements. The forwarding agent plans the shipment and informs the vendor of the result, who can then start the appropriate activities for goods issue of the respective outbound deliveries. To create shipments at the customer site, you can use message SHPADV (shipment message or shipment notification). To create or change your own shipments, use message SHPMNT. Both messages are based on IDoc type SHPMNT03; processing is executed through process code SHPM. You can maintain these parameters within the EDI partner profile. For this purpose, select Tools ->Business Communication -> IDoc -> Partner profile.
Output for deadline and status
The forwarding agent confirms the planned or actual deadline via EDI, including the status for the end of the shipment with the respective time.

The inbound deliveries to which the shipment refers must exist in the system. The reference is made through the delivery number of the vendor (collective goods traffic) or directly (transportation planning). Therefore, it is necessary to notify the customer of the deliveries where collective goods traffic is concerned. You can do this using the DESADV (shipping notification) message. It is not possible to create deliveries in the initial processing of shipments, as required for direct shipments. Also, no change is made to the delivery (with effects on material planning) if there is a change in the shipment (planned arrival date, for example).
Prerequisites
The deliveries that the shipment refers to must exist in the receiving system.
Features
Control of IDoc Receipt SHPMNT03
You can control the processing of the receipt of IDoc SHPMNT03 using the specifications in the segment E1EDT18. For this purpose, you can use the following E1EDT18-QUALF qualifiers:
QUALF |
= |
ORI |
Shipment document is created |
||
QUALF |
= |
CHA |
Shipment document is changed |
||
QUALF |
= |
PID |
Specification of an identification field for the shipment document. |
Processing and copy control
If you use the qualifier ORI or CHA, you can control the data transfer strategy from the IDoc into the shipment document using the parameter field. Basically, there are four strategies which are indicated by the first character in the E1EDT18-PARAM field. The respective marker characters are in the second character in the E1EDT18-PARAM field:
0 IDoc fields are always copied; empty ID fields cause document fields to be deleted (standard case; will be processed if no specification is made).
1 IDoc fields are only copied if they are empty
2 Similar to strategy 0, but an IDoc field is not transferred if it is filled completely with the marker character.
3 Similar to strategy 1, but an IDoc field is not transferred if it is filled completely with the marker character.
Example of segment E1EDT18:
QUALF |
PARAM |
|
ORI |
2! |
Copy all fields, except those containing a ! |
CHA |
3% |
Copy fields that are filled in and delete fields with %%%%... in the document. |
Control of identification
You can control the identification link between the IDoc and the shipment document in segment E1EDT18 with qualifier PID, which can appear up to three times per IDoc.
In most day-to-day cases, the PID qualifier is not present. In this case, the E1EDT20-TKNUM field is copied into VTTK-EXTI1 during creation. The system assigns the shipment number VTTK-TKNUM internally. If there is a change, the system searches for a suitable shipment document using the following criteria:
E1EDT20-TKNUM |
= |
VTTK-EXTI1 |
and
E1ADRE4-EXTEND_D |
= |
VTTK-TDLNR (where you must have E1ADRE4-EXTEND_Q = 300) |
If PID qualifiers are specified in E1EDT18, no data is copied from TKNUM to EXTI1.
If the shipment number is to have external number assignment, you can specify the shipment number as a primary identification with E1EDT18-QUALF = PID and E1EDT18-PARAM = TKNUM. The shipment is created using VTTK-TKNUM = E1EDT20-TKNUM, and is searched for with the same condition if you want to change it.
You can use the IDoc fields EXTI1, EXTI2, and TKNUM for the identification.
Examples of segment E1EDT18:
QUALF |
PARAM |
Function for creating |
Function for changing |
None |
None |
Copy E1EDT20-TKNUM to VTTK-EXTI1 Internal number assignment |
Search for shipment with VTTK-EXTI1 = E1EDT20-TKNUM and VTTK-TDLNR = E1ADRE4-EXTEND_D |
PID |
TKNUM |
External number assignment VTTK-TKNUM = E1EDT20-TKNUM |
Search with VTTK-TKNUM = E1EDT20-TKNUM |
PID |
EXTI1 |
Internal number assignment |
Search with VTTK-EXTI1 = E1EDT20-EXTI1 |
PID PID |
TKNUM EXTI2 |
External number assignment |
Search with VTTK-TKNUM = E1EDT20-TKNUM and VTTK-EXTI2 = E1EDT20-EXTI2 |
PID PID |
EXTI1 EXTI2 |
Internal number assignment |
Search with VTTK-EXTI1 = E1EDT20-EXTI1 and VTTK-EXTI2 = E1EDT20-EXTI2 |
Activities
You must also enter the following values for outbound partner profiles and any additional outbound parameters under message control.
Field |
Value |
Output type |
SHPMNT or SHPADV |
Partner type |
LI (vendor/creditor) |
Basic type |
SHPMNT03 |
Application |
V7 |
Output type |
SEDI, or your modified copy of SEDI |
Process code |
SHPM |