Some ASN Messages Are Getting Lost When Republished Thereby Not Reaching SIM Error Hospital
Last updated on JULY 02, 2015
Applies to:Oracle Retail Integration Bus - Version 12.0.9 and later
Information in this document applies to any platform.
Checked for relevance on July 2nd, 2015
When an existing Advance Ship Notice (ASN) messages are republished on the topic 'etASNInFromRIBToISO', out of five only three messages make it to Store Inventory Management (SIM) Error Hospital and remaining two messages are getting lost.
Shipment message flow is as follows:
RWMS-->ASN Out --> ewASNOutFromRDMWH1--> etASNOut--> ewASNOutToASNInLocFromRIB --> etASNInFromRIBToISO -->ASNInSubsriber-->ASN In-->SIM
When store receives shipment (ex: with 3 container), they dump the containers but do not process it at the same time when it is received by the store. In Warehouse Management System (RWMS) the shipments related information get purged and same Container Id will be used for another shipment to a different or same store. The new ASNIn will fail in Store Inventory Management (SIM). And some messages will not go to RIB hospital and will disappear.
Steps To Reproduce:
2) Restart the Oracle Application Server (OAS).
3) Check the sequence number in which messages are submitted. for example -no: 332 --- 343
submitted in sequence :34 to 38
Following messages will appear in RIB hospital at first as per the sequence of submission, the rest were lost.
For ex: 174935
5) Change the sequence in which XML messages are submitted
For ex: submitted in sequence :38, 37, 34,35,36
Following messages will appear in RIB Hospital at first as per the sequence of submission, the rest were lost..
For ex: 174917
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms