Troubleshooting
Problem
Attempts to run manageItem API with no change in Item feed XML creates a record in YFS_AUDIT_HEADER table in IBM Sterling Order Management.
Symptom
Steps to simulate:
- Create an Item using the below input xml using manageItem API :
ItemList>
<Item Action="Manage" ItemID="2015032101" OrganizationCode="SEPHORAUS"
UnitOfMeasure="EACH">
<PrimaryInformation AssumeInfiniteInventory="N" ItemType="Standard" Status="3000"/>
</Item>
</ItemList>
A record gets created in the YFS_ITEM table and YFS_AUDIT_HEADER table for this update.
- Now call same manageItem API with same input XML.
One more record gets created in the YFS_AUDIT_HEADER table even though there is no update in the input xml.
A new record is created in the YFS_AUDIT_HEADER table for each above update, for the same Item. This is causing performance bottleneck on ITEM AUDIT purge agent.
Cause
This is working as designed.
Resolving The Problem
Calling manageItem API with action Manage will be treated as modification of existing record or create a new if it does not exists, even though the input xml is same.
This is expected and will update MaxModifyTS and this information is always expected to be updated with every call of manageItem as required by Item synchronization.
The MaxModifyTS of an item is updated with the current timestamp whenever an item is modified. As this is considered as a modification, product will create a new record in YFS_AUDIT_HEADER table for each such update.
Related Information
Was this topic helpful?
Document Information
Modified date:
16 June 2018
UID
swg21999263