Question & Answer
Question
The requirement is :
When quantities are scheduled against future inventory, ship the stock available (let's say received return before future inventory ETA) at warehouse without release of the quantities. Fulfillment location will be derived based on sourcing rules and confirmShipment is being called to achieve this.
When quantities are scheduled against future inventory, ship the stock available (let's say received return before future inventory ETA) at warehouse without release of the quantities. Fulfillment location will be derived based on sourcing rules and confirmShipment is being called to achieve this.
1. Order created with Item1 , Qty 2
2. Order is scheduled successfully against DC - DC1 with estimated ship date of 2019-01-31.
3. Now, invoke confirmShipment API with input :
<Shipment Action="Create" EnterpriseCode="DEFAULT" SellerOrganizationCode="DEFAULT" ShipNode="DC1" >
<ShipmentLines >
<ShipmentLine Action="Create-Modify" OrderHeaderKey="2019020713154292601" OrderLineKey="2019020713160992603" Quantity="2" >
</ShipmentLine>
</ShipmentLines>
</Shipment>
4. Invoke confirmShipment API with input :
<Shipment ShipNode="LE-US-DC" DocumentType="0001" EnterpriseCode="102" >
<ShipmentLines>
<ShipmentLine OrderLineKey="20190117072648169667" OrderHeaderKey="20190117072647169666" Quantity="2.00"/>
</ShipmentLines>
</Shipment>
<Shipment ShipNode="LE-US-DC" DocumentType="0001" EnterpriseCode="102" >
<ShipmentLines>
<ShipmentLine OrderLineKey="20190117072648169667" OrderHeaderKey="20190117072647169666" Quantity="2.00"/>
</ShipmentLines>
</Shipment>
At this point, an error is thrown-
ErrorCode="YDM00082" ErrorDescription="Shipment line being added does not match attributes of Shipment"
ErrorCode="YDM00082" ErrorDescription="Shipment line being added does not match attributes of Shipment"
Cause
This is the current working behavior of the application.
For Orderlines that do not have a ship node stamped, trying to create a shipment line with the ship node will result in an issue with the demand updates for both order and shipment.
For Orderlines that do not have a ship node stamped, trying to create a shipment line with the ship node will result in an issue with the demand updates for both order and shipment.
Answer
If the order was released earlier, it would have been against a node. The corresponding demand update at the node would have already taken place, enabling the shipment line to validate shipnode against the orderrelease and ignore orderline info for ship node. In this case as the order line does not have ship node and is not yet released, the error is thrown.
[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SS6PEW","label":"IBM Sterling Order Management"},"Component":"","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF043","label":"Red Hat"}],"Version":"9.4,9.5,10.0","Edition":"","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]
Was this topic helpful?
Document Information
Modified date:
18 April 2019
UID
ibm10881764