Information on item shipments can be included in the XML file. But some rules must be observed.
Generally, item shipments are not needed because for each order line item, an item shipment is automatically created. But if you already know the values of some (mostly date) fields, you can include them in the file and they will be taken into account.
-
If you insert an order without approving it at the same time or if you want to update an order that has not yet been approved, you can only include data for the one and only item shipment of an order line item.
-
If you insert an order and approve it at the same time, update an order by approving it now, or if you refer to an order that has already been approved, you can create additional item shipments for an order line item or update them.
<ISH_PROC_TYPE>
Mandatory.
Processing type.
Allowable values: I, U and N.
'I' means that the object is to be inserted; 'U' means that an update is to be performed. ‘N’ means that the item shipment is not processed, that is, neither inserted nor modified. However, this item shipment is needed to show the path for underlying orders and their line items.
<ITEM_SHIP_POS>
Mandatory.
Item shipment line item number.
Allowable values: 1 – 9999999.
<ITEM_SHIP_SUB_POS>
Mandatory.
Item shipment subline item number.
Allowable values: 0 – 99999.
<ITEM_SHIP_QTY>
Optional.
Quantity of the item shipment to be delivered.
Allowable values: 0 – 999999999999.999.
When inserting additional item shipments, the quantity is set to 0 if this tag is missing in the XML file.
<ITEM_SHIP_QTY_CODE>
Optional.
The quantity unit of an item shipment.
This tag can only be used for detail tags the corresponding order of which has already been approved.
All units that have been defined in the 'weight', 'volume', or 'quantity' unit groups are valid values.
<ITEM_SHIP_WEIGHT>
Optional.
Not to be included for updates if the corresponding order has not yet been approved.
Weight of an item shipment.
Allowable values: 0 – 999999999999.999.
When inserting additional item shipments, the weight is set to 0 if this tag is missing in the XML file.
<ITEM_SHIP_WEIGHT_CODE>
Optional.
Not to be included for updates if the corresponding order has not yet been approved.
Weight unit of the item shipment.
All units that have been defined in the ‘weight’ unit group can be used.
<ITEM_SHIP_VOLUME>
Optional.
Not to be included for updates if the corresponding order has not yet been approved.
Volume of an item shipment.
Allowable values: 0 – 999999999999.999.
When inserting additional item shipments, the quantity is set to 0 if this tag is missing in the XML file.
<ITEM_SHIP_VOL_CODE>
Optional.
Not to be included for updates if the corresponding order has not yet been approved.
Volume unit of the item shipment.
All units that have been defined in the ‘volume’ unit group are valid.
<ITEM_SHIP_DIMENSIONS>
Optional.
Not to be included for updates if the corresponding order has not yet been approved.
Dimensions of the item (x, y, z).
<DD_CODE>
Mandatory when inserting additional item shipments; optional in any other cases.
Name (code) of the delivery designation.
Delivery designations are maintained on A.10.39 Delivery Designations.
<ITEM_SHIP_RM_CODE>
Optional.
Name (code) of the routing method defined on P.10.53 Routing Methods.
You can only use routing methods the delivery designation of which equals the one provided by the 'Delivery Designation' tag.
<FAB_LOCATION>
Optional.
Not to be included for updates if the corresponding order has not yet been approved.
Location of the fabrication.
<FAB_SHOP_CNTRL_NUMBER>
Optional.
Not to be included for updates if the corresponding order has not yet been approved.
Control number of the fabrication.
<FAB_COMPLETE_PERCENT>
Optional.
Not to be included for updates if the corresponding order has not yet been approved.
Percentage of completion of fabrication.
Allowable values: 0 – 100.
The percentage is set to 0 if it is missing when inserting additional item shipments.
<FIFTY_PERCENT_FAB_COMP>
Optional.
Not to be included for updates if the corresponding order has not yet been approved.
Date when 50% of fabrication was actually completed.
<REV_PROM_SHIP_DATE>
Optional.
Not to be included for updates if the corresponding order has not yet been approved.
Date the supplier currently promises to ship the item.
<MAJ_MATL_ORDER_DATE>
Optional.
Not to be included for updates if the corresponding order has not yet been approved.
Date when most components (or quantities) of an item shipment are ordered.
<MAJ_MATL_RECV_DATE>
Optional.
Not to be included for updates if the corresponding order has not yet been approved.
Date when most components (or quantities) of an item shipment arrived at the supplier.
<ACTUAL_FAB_START_DATE>
Optional.
Not to be included for updates if the corresponding order has not yet been approved.
Day supplier started fabrication of the item.
<PROM_FAB_COMP_DATE>
Optional.
Not to be included for updates if the corresponding order has not yet been approved.
Date for which the supplier currently promises to complete fabrication.
<ACTUAL_FAB_COMP_DATE>
Optional.
Not to be included for updates if the corresponding order has not yet been approved.
Actual date fabrication has been completed by the supplier.
<ACTUAL_SHIP_DATE>
Optional.
Not to be included for updates if the corresponding order has not yet been approved.
Actual date supplier shipped the item.
<PRED_SHIP_DATE>
Optional.
Not to be included for updates if the corresponding order has not yet been approved.
Date item is predicted to be shipped.
<PRED_ON_SITE_DATE>
Optional.
Not to be included for updates if the corresponding order has not yet been approved.
Date predicted (estimated) for the arrival on-site.
<ACTUAL_ON_SITE_DATE>
Optional.
Not to be included for updates if the corresponding order has not yet been approved.
Date the item actual arrived on-site.
<ACTUAL_CONTRACT_DATE>
Optional.
Not to be included for updates if the corresponding order has not yet been approved.
Actual date of delivery.
<PROM_INSPECT_DATE>
Optional.
Not to be included for updates if the corresponding order has not yet been approved.
Promised date this item can be inspected.
<FINAL_INSPECT_DATE>
Optional.
Not to be included for updates if the corresponding order has not yet been approved.
Date this item will be finally inspected for releasing the corresponding certificate.
<READY_PREDICTED>
Optional.
Not to be included for updates if the corresponding order has not yet been approved.
Date that the item is predicted to be ready for shipment.
<READY_ACTUAL>
Optional.
Not to be included for updates if the corresponding order has not yet been approved.
Date on which the item was actually ready to be shipped.
<PROM_CONTRACT_DATE>
Optional.
Not to be included for inserts if the ZP_EXPDATE project default is set to Y; not to be included for updates if the corresponding order has already been approved and the ZP_EXPDATE project default is set to Y.
Date the supplier promises to deliver this line item.
<PROM_SHIP_DATE>
Optional.
Not to be included for inserts if the ZP_EXPDATE project default is set to Y; not to be included for updates if the corresponding order has already been approved and the ZP_EXPDATE project default is set to Y.
Date the supplier promises to ship the item.
<REQ_SITE_DATE>
Optional.
Not to be included for inserts.
Date the item is required on-site.
<ISH_EXPORT_LICENSE_REQ_IND>
Optional.
Indicates whether an export license is required for this item shipment.
Allowable values: Y, N.
The indicator is taken over from the corresponding order line item when an item shipment is inserted and this tag was not included in the XML file.
<COMMENTS>
Optional.
Comment for an item shipment.
<ISH_SPLIT_TAG>
This tag is required for a detail tag to be created for a master tag.
Include the tag; a value is not needed. This tag is only analyzed if the processing type of the item shipment is ‘U’.
In the case of item shipments, you can update the item and create a detail tag at the same time.
For more information, see Split Tags.