Solved

EDI - how do add package units in xml

  • 26 July 2023
  • 8 replies
  • 108 views

Userlevel 7
Badge +22
  • Superhero (Customer)
  • 949 replies

Hi everybody,

I’ve downloaded the xml file for despatch advise from “IFS Interface Browser” and it contains the package units. 

But if I export or send a despach advise from the screen “Shipment” it doesn’t contain the marked xml tags. Why not? Is there any settings?

 

 

icon

Best answer by Pilar Franco 11 October 2023, 14:46

View original

8 replies

Userlevel 5
Badge +13

Hi,

Please check if you can see HANDLING_UNITS tag instead:

Regards,

Pilar

Userlevel 7
Badge +22

Hi @Pilar Franco 

no I can’t see the whole block (HANDLING_UNITS) in my xml file.

Are there any basic data missing?

What can I do to export also the package units?

Userlevel 5
Badge +13

Hi,

Could you please provide an screenshot of the Handling Unit Structure of your Shipment?

Regards,

Pilar

Userlevel 7
Badge +22

Hi @Pilar Franco 

sure.

<ORDER_DISPATCH_ADVICE xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="urn:ifsworld-com:schemas:outbound_distribution_transactions_send_despatch_advise_request">

 <CONTRACT></CONTRACT>

 <DELIVERY_TERMS_DESCRIPTION></DELIVERY_TERMS_DESCRIPTION>

 <SHIP_VIA_DESCRIPTION></SHIP_VIA_DESCRIPTION>

 <EAN_LOCATION_DOCUMENT_ADDRESS>12345</EAN_LOCATION_DOCUMENT_ADDRESS>

 <EAN_LOCATION_DELIVERY_ADDRESS>1234566</EAN_LOCATION_DELIVERY_ADDRESS>

 <DELIVERY_NOTE_NO>36</DELIVERY_NOTE_NO>

 <DESPATCH_DATE>2022-08-19T17:28:40</DESPATCH_DATE>

 <RECEIVER_COMMUNICATION_ID>EDI</RECEIVER_COMMUNICATION_ID>

 <SENDER_COMMUNICATION_ID>TST</SENDER_COMMUNICATION_ID>

 <SHIPMENT_ID>47</SHIPMENT_ID>

 <TRANSPORT_DOC_NO>47</TRANSPORT_DOC_NO>

 <CONSIGNEE>1234</CONSIGNEE>

 <CONSIGNEE_NAME>Customer test</CONSIGNEE_NAME>

 <NO_OF_PALLETS>0.0</NO_OF_PALLETS>

 <NO_OF_PACKAGES>0.0</NO_OF_PACKAGES>

 <NET_WEIGHT>0.0</NET_WEIGHT>

 <GROSS_WEIGHT>50500.0</GROSS_WEIGHT>

 <VOLUME>0.0</VOLUME>

 <DELIVERY_TERMS>CII</DELIVERY_TERMS>

 <SHIP_VIA_CODE>XX</SHIP_VIA_CODE>

 <ALT_DELIVERY_NOTE_NO>36</ALT_DELIVERY_NOTE_NO>

 <MESSAGE_SEQUENCE_NO>1.0</MESSAGE_SEQUENCE_NO>

 <MESSAGE_VERSION_NO>5.0</MESSAGE_VERSION_NO>

 <UOM_FOR_WEIGHT>kg</UOM_FOR_WEIGHT>

 <UOM_FOR_VOLUME>m3</UOM_FOR_VOLUME>

 <CONSIGNEE_ASSOCIATION_NO>100000</CONSIGNEE_ASSOCIATION_NO>

 <RECEIVER_TYPE>CUSTOMER</RECEIVER_TYPE>

 <ORDER_LINES>

  <ORDER_LINE_DISPATCH_ADVICE>

   <SOURCE_REF1>O1018</SOURCE_REF1>

   <SOURCE_REF2>1</SOURCE_REF2>

   <SOURCE_REF3>1</SOURCE_REF3>

   <SOURCE_REF4>0</SOURCE_REF4>

   <SOURCE_REF_TYPE_DB>CUSTOMER_ORDER</SOURCE_REF_TYPE_DB>

   <SOURCE_PART_NO>8250000001</SOURCE_PART_NO>

   <SOURCE_PART_DESCRIPTION>S01 sales part</SOURCE_PART_DESCRIPTION>

   <SOURCE_UNIT_MEAS>PCS</SOURCE_UNIT_MEAS>

   <DESPATCHED_SOURCE_QTY>50.0</DESPATCHED_SOURCE_QTY>

   <DESPATCHED_QTY>50.0</DESPATCHED_QTY>

   <DESIRED_DELIVERY_DATE>2022-07-07T00:00:00</DESIRED_DELIVERY_DATE>

   <REAL_SHIP_DATE>2022-08-19T17:28:40</REAL_SHIP_DATE>

   <LOT_BATCH_NO>1234</LOT_BATCH_NO>

   <SERIAL_NO>*</SERIAL_NO>

   <WAIV_DEV_REJ_NO>*</WAIV_DEV_REJ_NO>

   <ENG_CHG_LEVEL>1</ENG_CHG_LEVEL>

  </ORDER_LINE_DISPATCH_ADVICE>

  <ORDER_LINE_DISPATCH_ADVICE>

   <SOURCE_REF1>O1020</SOURCE_REF1>

   <SOURCE_REF2>1</SOURCE_REF2>

   <SOURCE_REF3>1</SOURCE_REF3>

   <SOURCE_REF4>0</SOURCE_REF4>

   <SOURCE_REF_TYPE_DB>CUSTOMER_ORDER</SOURCE_REF_TYPE_DB>

   <SOURCE_PART_NO>2150720053</SOURCE_PART_NO>

   <SOURCE_PART_DESCRIPTION>S1E-Sal-Part-0000008</SOURCE_PART_DESCRIPTION>

   <SOURCE_UNIT_MEAS>PCS</SOURCE_UNIT_MEAS>

   <DESPATCHED_SOURCE_QTY>500.0</DESPATCHED_SOURCE_QTY>

   <DESPATCHED_QTY>500.0</DESPATCHED_QTY>

   <DESIRED_DELIVERY_DATE>2022-06-09T00:00:00</DESIRED_DELIVERY_DATE>

   <REAL_SHIP_DATE>2022-08-19T17:28:40</REAL_SHIP_DATE>

   <LOT_BATCH_NO>50</LOT_BATCH_NO>

   <SERIAL_NO>*</SERIAL_NO>

   <WAIV_DEV_REJ_NO>*</WAIV_DEV_REJ_NO>

   <ENG_CHG_LEVEL>1</ENG_CHG_LEVEL>

   <GTIN_NO>235987400537</GTIN_NO>

  </ORDER_LINE_DISPATCH_ADVICE>

 </ORDER_LINES>

 <CONSIGNEE_ADDRESS>

  <ADVISE_ADDRESS>

   <ADDRESS_1>Street</ADDRESS_1>

   <ADDRESS_4>test</ADDRESS_4>

   <CITY>City</CITY>

   <ZIP_CODE>41663</ZIP_CODE>

   <COUNTRY_CODE>DE</COUNTRY_CODE>

  </ADVISE_ADDRESS>

 </CONSIGNEE_ADDRESS>

 <CONSIGNOR_ADDRESS>

  <ADVISE_ADDRESS>

   <ADDRESS_1>Street</ADDRESS_1>

   <CITY>City</CITY>

   <ZIP_CODE>40162</ZIP_CODE>

   <COUNTRY_CODE>DE</COUNTRY_CODE>

  </ADVISE_ADDRESS>

 </CONSIGNOR_ADDRESS>

</ORDER_DISPATCH_ADVICE>

Userlevel 5
Badge +13

Sorry, I was referring to an screenshot of the shipment window, showing the Handling unit structure you have there. The one that should be transferred to the DESADV xml file.

Userlevel 7
Badge +22

The screenshot is from  “IFS Interface Browser”. There you see that the tag <HANDLING_UNITS> is available. 

But if I export the DESADV xml file it isn’t there.

So what is the standard in IFS? 

Do you know?

Userlevel 5
Badge +13

I just made a test and in my case, the HANDLING_UNITS tag is created in the DESADV xml file. As far as I know, there is no condition to create such tag, except to have the Handling Unit structure created and connected to the shipment.

So then, in your previous example, can you provide the screenshot in application where we can see the Handling Unit Structure tab in shipment 47?

Regards,

Pilar

Userlevel 7
Badge +22

Hi @Pilar Franco 

yes, you’re right. I need the handling unit structure. 

And now it works.

Thank you a lot.

Reply