Agreements Configured with Different AS2 Identifiers not Processing Correct Documents

(Doc ID 1589015.1)

Last updated on NOVEMBER 19, 2016

Applies to:

Oracle B2B (Business to Business) - Version and later
Information in this document applies to any platform.


On : version, Core B2B Platform

When a document is sent using a different AS2 identifier, which you use to identify the document type, the correct agreement is not chosen.

You expect each trading partner agreement configured with different AS2 identifiers to pick up the document assigned to that agreement.

The issue can be reproduced at will with the following steps:

1) Create 3 custom document definitions (using the same XSD) that use the same criteria to identify an incoming document.
2) Create an agreement for each AS2 identifier configured in the Profile for a trading partner.
3) Trading partner sends a document.
4) The correct agreement is not chosen as expected.



Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms