TDI09_1-2-3

SAP Dialogo TDI09_1-2-3 PACKAGING & SHIPPING

M. Fumagalli

March 2013

All Rights Reserved © Alcatel-Lucent 2007

TDI09_1-2-3 PACKAGING & SHIPPING

Currently in Dialogo there are 3 kind of shipping processes.

TRANS. IDOC

Type

Message

Type

Remark

ZBP02 DELVRY03

MBGMCR02

DESADV

MBGMCR02

Used when plant ship directly the items to the

Customer

ZBP022 DELVRY03

MBGMCR02

DESADV

MBGMCR02

Used when plant ship the items to a Distribution

Center

Old transaction; it will be replaced by ZBP044

ZBP044 DELVRY03

MBGMCR02

SHPCON

MBGMCR02

Used when plant ship the items to a Distribution

Center

New transaction; it will replace ZBP022



WE02

One IDOC for each Inbound Delivery (ZBP02 – ZBP022)

One IDOC for each Super Inbound Delivery (ZBP044)



One IDOC for each Commercial Item (End Item) shipped.

This IDOC is the same for all the shipping processes (ZBP02 – ZBP022 – ZBP044).

WE02



ZBP02

Fixed values

Plant

Order Type

Order Number (STO/PO)

Customer Sales Order)



User can select only the “ready to ship” Final Assembly Order; only for them the selection flag is active.In most cases the original STO/PO position “999999” is splitted in more positions; at each position correspond one Final Assembly Order.



This transaction consider only the STO/PO that plant ship directly to the customerField “Purchase order no.” contains the value of plant.



One IDOC “DELVRY03” is created for each Inbound Delivery (correspond to the Final Assembly Order in 99% of cases) enclosed in selected Final Assembly Order.



The IDOC segment E1EDL20 contains field: VBELN : Inbound Delivery

The IDOC segment E1EDL41 (one for each E1EDL24) contains fields: BSTNR : STO/PO POSEX : Item Position



In one IDOC there are many segments E1EDL24 (one for each Item in Inbound Delivery).

Each segment contains fields: POSNR : Item Position MATNR - KDMAT : Item number (Commercial Item) WERKS : Distribution Center (in this case the plant) LGORT : Storage Location (from variant) LFIMG - LGMNG : Item quantity WRKME - MEINS : Unit of Measure



One IDOC “MBGMCR02” is created for each End Item enclosed in selected Final Assembly Order.



The IDOC segment E1BP2017_GM_ITE_CREATE contains fields: MATERIAL : Item number (Commercial Item) MOVE_TYPE : B.P. Movement Type (from variant) ENTRY_QNT : Item Quantity ENTRY_UOM : Unit of Measure PO_NUMBER : STO/PO PO_ITEM : Item Position



Relatively to this interface user open VEGA “SR” ticket with following text:

Inbound Delivery (ID) xxxxxxxx generated in Dialogo is not found in Blue Planet.Please investigate on Dialogo side



Using the transaction WE09 we can retrieve the IDOC that contains the the STO/PO

Range “close” to the ticket creation date; if not find the IDOC, enlarge it

Fixed values

Segment name (Fixed value)

Field name (Fixed value)ID value



The result of WE09 transaction is the IDOC number that contains the Blue Planet STO/PO.The issue analysis can start.

Case A): IDOC found, current status = “03” : the trouble is not in Dialogo, but in Blue Planet or in EAI.Act - Communicate this to user and close the ticket.

This is the most recurring occurrence.



In this case usually user open another ticket to reprocess the IDOC.Act – Change the IDOC status from “03” (Data passed to port OK) to “30” (IDoc ready for dispatch (ALE service)) using ABAP Utility ZBBXX070 (transaction SE38).

•IDOC number

•New IDOC Status

•Current IDOC staus



•This button modifies the IDOCs status

•List of IDOCs that will be modified

Act – Reprocess the IDOC using Transaction BD87. Act - Communicate this to user and close the ticket



IDOC found, current status <> “03” : Act – Analyze the IDOC status and Discover the issue cause. In this case the investigation is complex and not recurring.When discovered:Act – Remove the issue cause. Act – Reprocess IDOCAct - Communicate this to user and close the ticket.

Case B): IDOC not found, even if the date range was enlarged since 1 month ago.Act - Contact the user to ask him the date of ZBP02 execution.Act - Enlarge the date range to include this date.

IDOC found : see Case A)

IDOC not found again.In this case the investigation is complex and not recurring (some times is not possible discover the problem, it depend of system status at execution date/time of ZBP02); in any case the ZBP02 must be executed againAct - Communicate this to user and close the ticket



ZBP022

Fixed values

Plant

Order Type

Order Number (STO/PO)

Delivery Center:FG18FPD1FPG1FPG2FPG5IG01



User can select only the “ready to ship” Final Assembly Order; only for them the selection flag is active.In most cases the original STO/PO position “999999” is splitted in more positions; at each position correspond one Final Assembly Order.



This transaction shows only the STO/PO that plant ship to the Delivery Center selected into variant Field “Purchase order no.” contains the value of Delivery Center.



The transaction ZBP022 creates the same IDOCs created by ZBP02.

The issues are the same.

It was replaced by ZBP044: this interface has same logic as ZBP022, but send more data to Blue Planet (Weights, Volumes and Dimensions of the packages).



ZBP044

Fixed values

BOX creation date

BOX number

Distribution Center:FG18FG18.1FPD1FPG1FPG2FPG5



Now the Final Assembly Order (Inbound Delivery) are srtored in BOXES (packages).Relationship : BOX -> STO -> Final Assembly Order (STO) -> Inbound Delivery

User can select only the boxes that are “ready to ship”.



This transaction shows only the STO/PO that plant ship to the Distribution Center selected into variant Fields “Purchase order no.” and “Your Reference (Storage Location)” identify the Distribution Center.



This transaction create IDOCs “DELVRY03” – msg type “SHPCON”



The IDOC segment E1EDL20 contains field: VBELN : Super Inbound Delivery : progressive number create by this interface

The IDOC segment E1EDL41-001 (one for each E1EDL24) contains fields: QUALI : 001 – Fixed value BSTNR : STO/PO POSEX : Item Position



In one IDOC there are many segments E1EDL24 (one for each Item in Inbound Delivery).

Each segment contains fields: POSNR : Item Position MATNR - KDMAT : Item number (Commercial Item) WERKS : Distribution Center (from Purchase Order) LGORT : Storage Location (from Purchase Order) LFIMG - LGMNG : Item quantity WRKME - MEINS : Unit of Measure



The IDOC segments E1EDL37 and E1EDL44-1 are new segments introduced in this interface.

Segments E1EDL37 contains data related to the package; in detail: EXIDV - EXIDV2 : BOX Number (package) BRGEW : Gross Weight NTGEW : Net Weight GWEIM : Weight OoM BTVOL : Volume NTVOL : Net Volume VOLEM : Volume UoM VHILM - VHILM_KU : Package Item LAENG : Package Length BREIT : Package Width HOEHE : Package Height MEABM : Dimensions UoM



There are many segments E1EDL44-1 (one for each Item in Inbound Delivery); all under the same segment E1EDL37 .

Each segment contains fields: VELIN : “1” – Fix value VBELN : Super Inbound Delivery POSNR : Item Position VEMNG : Item Quantity VEMEH : Unit of Measure MATNR : Commercial Item



ZBP044 is a new transaction used for a few week and so far we had not any issue on it; in any case, the logic is the same as ZBP02 – ZBP022 and we expect the same troubles.

TDI09_1-2-3

Documents

Transcript of TDI09_1-2-3