XML Gateway Error Randomly Processed As Java Or As Plsql Error And Profile Option ECX_IN_JAVA_PROCESSING Is Set To Yes
(Doc ID 2383754.1)
Last updated on FEBRUARY 17, 2023
Applies to:
Oracle XML Gateway - Version 12.2.6 to 12.2.7 [Release 12.2]Information in this document applies to any platform.
Goal
After upgrading EBS to 12.2.6, the new profile option ECX_IN_JAVA_PROCESSING is set to yes.
On the same ECX transaction types, it was observed that some errors are processed by ecxerror.wft starting with with oracle.apps.ecx.inbound.message.receive which is plsql and some are processed with oracle.apps.ecx.inbound.process_at_java.
It was expected all ECX transaction types to process at java.
The ECXERROR is raised through an event subscription and two different "error" events are raised, one is old one (plsql) another is new one (java error).
The handling of the error was different based on the "error level" if for example party id is not passed then it is a java error, but if error is raised inside xgm through some validations then it is the plsql type of error.
Why are both of these not processed through java?
Solution
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
| Goal |
| Solution |
| References |