B2B 11g: Callout Message Parameters do not Contain "DOCTYPE_NAME, DOCTYPE_REVISION, FROM_PARTY, TO_PARTY" - Usage Results in Error: BEA-000000
(Doc ID 1302771.1)
Last updated on NOVEMBER 13, 2023
Applies to:
Oracle SOA Suite - Version 11.1.1.1.0 to 11.1.1.4.0 [Release 11gR1]Information in this document applies to any platform.
Symptoms
The 10g callout message parameters; DOCTYPE_NAME, FROM_PARTY, TO_PARTY, DOCTYPE_NAME,DOCTYPE_REVISION, MSG_ID, are not available in 11g. Use of these parameters results in BEA-000000 errors.
For example, this code:
results in the following errors:
<Paramter: OracleServices>
<Dec 20, 2010 2:29:57 PM EST> <Error> <oracle.soa.b2b.engine> <BEA-000000>
<Paramter: 50783808>
<Dec 20, 2010 2:29:57 PM EST> <Error> <oracle.soa.b2b.engine> <BEA-000000>
<Paramter: close>
<Dec 20, 2010 2:29:57 PM EST> <Error> <oracle.soa.b2b.engine> <BEA-000000>
<msgID : null>
<Dec 20, 2010 2:29:57 PM EST> <Error> <oracle.soa.b2b.engine> <BEA-000000>
<fromParty:null>
<Dec 20, 2010 2:29:57 PM EST> <Error> <oracle.soa.b2b.engine> <BEA-000000>
<toParty:null>
<Dec 20, 2010 2:29:57 PM EST> <Error> <oracle.soa.b2b.engine> <BEA-000000>
<documentName:null>
<Dec 20, 2010 2:29:57 PM EST> <Error> <oracle.soa.b2b.engine> <BEA-000000>
<documentRevision:null>
<Dec 20, 2010 2:29:57 PM EST> <Error> <oracle.soa.b2b.engine> <BEA-000000>
<actionName:null>
<Dec 20, 2010 2:29:57 PM EST> <Error> <oracle.soa.b2b.engine> <BEA-000000>
<EXIT: CalloutController.execute(CalloutContext calloutContext, List
input,List output)>
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 |
Cause |
Solution |
References |