Multiple Document Definitions In B2b Not Working As Expected
(Doc ID 2722148.1)
Last updated on OCTOBER 22, 2020
Applies to:Oracle SOA Suite - Version 220.127.116.11.0 and later
Information in this document applies to any platform.
B2B is unable to identify the document definition for the incoming messages from different sources, when the message structure is same for all of them. (Identical cXML structure)
Basic Requirement :Initially there was one partner which used to send cXML message, to process in B2B we have created a Document definition which identifies firstly, the type of document as per the Xpath Expression and later on using the IDExtraction it identifies the remote trading partner.
Expected Behavior:Generally, when the message arrives from the remote trading partner, b2b engine identifies the type of document with the Xpath expression. After identifying the document type it should proceed to identify the remote trading partner using ID-Extraction. So once the document type and the remote trading partner is identified it will look up for agreement with the combination of identified document type and the remote trading partner and then executes the agreement.Current Behavior: The above behavior was achieved until there were remote trading partner sending messages which satisfied the Xpath expression and IDExtraction.
Later on, after few months, there was an onboarding of different remote trading partner which is going to send the same message structure as the initial trading partner(cXML), but the content of the message was so confined from the source system that, we had to create new document definition with different Xpath expression for document type identification along with Identification value in place and. Also making use of IDExtraction to identify the remote trading partner (The later ones have Different Xpath Expression and the IDExtraction expression).
On observing the behavior further, we have noticed that whenever the message is being sent by the new trading partner its being picked up by the old document definition configs and resulting in error rather than using the new document setup configurations.So with this problem, whenever remote trading partner is sending the messages it is picking up the wrong document configuration and resulting in failures (Agreement Not Found Exception)
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document