ASNOut Messages Are Getting Poisonous and Not Routed by rib-tafr ASNOutToASNInLoc Adapter (Doc ID 2049954.1)

Last updated on MARCH 13, 2024

Applies to:

Symptoms

When publishing the ASNOut Message with valid Routing Information from External system to Retail Integration Bus (RIB) using the Integration Gateway Services (IGS) webservice "publishASNOutCreateUsingASNOutDesc", it is getting poisonous in rib-tafr ASNOutToASNInLoc and is shutting down the TAFR Adapter. Further, it is not routing the messages to downstream systems. 

Below error details are observed in the rib-tafr ASNOutToASNInLoc adapter log file:

Error:

Steps To Reproduce:
1. Publish an ASNOut message from External System or SOAP UI through IGS Service "publishASNOutCreateUsingASNOutDesc".

2. Provide the valid routing info in the ASNOut message with the required details.

3. ASNOut messages reaches RMS System through below flow:
      IGS --> ASNOutPublishing --> etASNOut topic -->rib-tafr.ASNOutToASNOut_tafr --> etASNOutAT topic --> rib-rms.ASNOut_sub --> RMS

4. However the following flow is getting failed at rib-tafr.ASNOutToASNIn_tafr as routing info values are getting removed from the message and is considered as poisonous.
    IGS --> ASNOutPublishing --> etASNOut topic --> rib-tafr.ASNOutToASNIn_tafr --> etASNInFromRIBToWH{*} topic--> rib-rwms.ASNIn_sub --> RWMS

Note: The issue is only for the Store to Warehouse type of ASNOut messages. For Warehouse to Store type of ASNOut messages, they are reaching to both RMS and SIM systems.
Also if the ASNOut message is directly published onto etASNOut topic using RDMT tool, it is getting processed successfully.

Changes

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.