Troubleshooting
Problem
Substitution(supersession) not working for items unless ShipNode or DG is stamped on the order line explicitly.
Symptom
Configuration Required:
Have a main item say Item12(inventory not available).
Open Application manager--> CM--> Products--> Items and search for Item12.
Set ‘Item Substitution on Order Allowed’ to Yes in the Sourcing/Transportation tab.
Under the Associations tab, configure an associated item for this Item12 say Item123 with association type as Supersession.
Adjust inventory for Item123 at Node1.
Open Application manager--> Application Platform--> Participant Modelling, search for Node1 and check ‘Substitution is Allowed’ under the Node Attributes tab.
Create a Distribution Group say DG1 and add Node1 in DG1.
Set up the default sourcing rule, add Node1 or DG1 in the Sourced From List(Check the Substitution is Allowed option on the Sourcing Template)
Under Scheduling Rules, check ‘Cancel Order For Inventory Shortage’.
Steps to reproduce:
Scenario1:
1. Create an order for Item12, do not specify the node/DG/Fulfillment Type on the orderline.
2. Schedule the order.
Ø Order gets cancelled.
Scenario2:
1. Create an order for Item12.
2. On the orderline explicitly specify the node/DG.
3. Schedule the order.
Ø Order gets scheduled.
Ø In the YFS_ORDER_LINE_SCHEDULE table, the OVERRIDE_ITEM_ID field is set to Item123.
Cause
In case of supersession the product internally considers it as a procurement to replenish the inventory.
Resolving The Problem
Procurement should be allowed at the Sourcing Rule. Our scheduling logic, first looks for the preferred substitute item, then the original item and finally the superssion comes into picture. Enabling the procurement flags would not create a procurement order for considering the supersession item. This is only used internally by the product to replenish the inventory.
Was this topic helpful?
Document Information
Modified date:
16 June 2018
UID
swg21653564