Overriding AS2 Identifier Not Used in Functional or MDN Acknowledgement
(Doc ID 1969768.1)
Last updated on APRIL 09, 2019
Applies to:
Oracle SOA Suite - Version 11.1.1.7.0 and laterInformation in this document applies to any platform.
Symptoms
On : 11.1.1.7.0 version, B2B Engine
ACTUAL BEHAVIOR
---------------
B2B is not using the overriding AS2 identifier when acknowledging receipt of a document.
EXPECTED BEHAVIOR
-----------------------
It is expected that the overriding AS2 identifier is used when sending a functional (and MDN) acknowledgement.
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1) Create an Acme B2B 850 agreement configuration in one B2B instance:
5) On the GlobalChips side, check the 850 inbound wire message and it shows the correct AS2 identifier (GlobalChips2_AS2).
6) Now check the 997 outbound wire message and it shows an incorrect AS2 identifier (GlobalChips_AS2) is being used for the functional acknowledgement.
Changes
Cause
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
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |