Question & Answer
Question
Why the SUPPLY_CHANGE_LIST event of Inventory_Change transaction does not work when defined at an enterprise level but works at DEFAULT/Hub level ?
Cause
Scenario -
Create an enterprise E as a child of DEFAULT and do NOT inherit it's configuration from DEFAULT.
Create an item and node, under enterprise E.
Adjust inventory of an item against above enterprise, node and check if the event works or not. It does NOT.
Now, when the event handler at default level is enabled then it does work.
Create an item and node, under enterprise E.
Adjust inventory of an item against above enterprise, node and check if the event works or not. It does NOT.
Now, when the event handler at default level is enabled then it does work.
Answer
Purpose of SUPPLY_CHANGE_LIST event is not to invoke multiple xml's but a single xml for consolidated change; which in this case might not be possible for different inventory organization as adjust inventory can handle adjustment from different inventory organization at same time.
This is not the case with SUPPLY_CHANGE event which works both at Hub level as well as Enterprise level. This is because each adjustment in adjustInventory API call is treated as a different record. Each record has its Item, Organization, etc. Thus SUPPLY_CHANGE event knows the attributes for which its invoked.
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS6PEW","label":"Sterling Order Management"},"Component":"","Platform":[{"code":"PF016","label":"Linux"}],"Version":"All Versions","Edition":"","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]
Product Synonym
Sterling OMS
Was this topic helpful?
Document Information
Modified date:
01 November 2021
UID
ibm10881914