Error in inbound processing: EDI message - XML Gateway

Hello!
I've setup a DELFOR transaction in B2B and modified XML Gateway settings for internal delivery channel in order to send the message to EBS, but I'm getting weird errors in b2b.log. (XML Gateway in EBS is not setup yet, but it should't be an issue since incoming errors are handled in EBS, and I would just see an inbound transaction with processing errors in Transaction Monitor.)
In the beginning of b2b.log I see this:
2009.07.07 at 15:26:31:897: B2BStarter thread: BusinessLogicLayer - (DEBUG) Push Stack: queryInternalDeliveryChannel
2009.07.07 at 15:26:31:897: B2BStarter thread: BusinessLogicLayer - (DEBUG) Pop Stack: queryInternalDeliveryChannel
2009.07.07 at 15:26:31:897: B2BStarter thread: B2B - (DEBUG) : Tue Jul 07 15:26:31 CEST 2009 inbound initialize
2009.07.07 at 15:26:31:897: B2BStarter thread: B2B - (DEBUG) : Tue Jul 07 15:26:31 CEST 2009 Obtaining inbound connection...
2009.07.07 at 15:26:31:897: B2BStarter thread: B2B - (DEBUG) : Tue Jul 07 15:26:31 CEST 2009 inbound connect string: jdbc:oracle:thin:@server64.xa.si:1521:test2
2009.07.07 at 15:26:31:897: B2BStarter thread: B2B - (DEBUG) : Tue Jul 07 15:26:31 CEST 2009 inbound username: apps
2009.07.07 at 15:26:32:522: B2BStarter thread: B2B - (DEBUG) : Tue Jul 07 15:26:32 CEST 2009 inbound initialize exit
2009.07.07 at 15:26:32:522: B2BStarter thread: B2B - (DEBUG) oracle.tip.adapter.b2b.data.MsgListener:startListen Enter
2009.07.07 at 15:26:32:538: B2BStarter thread: B2B - (DEBUG) oracle.tip.adapter.b2b.data.MsgListener:startListen Exit
2009.07.07 at 15:26:32:538: Thread-9: B2B - (DEBUG) oracle.tip.adapter.b2b.data.MsgListener:run Thread start
2009.07.07 at 15:26:32:538: B2BStarter thread: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:initialize Exit
2009.07.07 at 15:26:32:538: B2BStarter thread: B2B - (DEBUG) B2BStarter - B2B initialized
After I copy the edi file to the incoming directory B2B starts processing the file:
2009.07.07 at 15:30:01:878: Thread-10: B2B - (DEBUG)
Protocol = File
Version = 1.0
Transport Header
filename:00003442_23.CMS
filesize:12345
file_ext:CMS
fullpath:C:\xa_endpoint\00003442_23.CMS
timestamp:2009-07-06T16:14:29.393+01:00
As I see in the log: B2B finds the trading partner and agreement and all looks fine. But later comes this:
2009.07.07 at 15:30:05:909: Thread-9: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.MessageHandler:deliverMessageToDestination Enter
2009.07.07 at 15:30:05:909: Thread-9: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.MessageHandler:deliverMessageToDestination deliver message to destination. protocol is XMLGateway Queues
2009.07.07 at 15:30:05:909: Thread-9: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.MessageHandler:deliverMessageToDestination deliver message to XMLGW
2009.07.07 at 15:30:05:909: Thread-9: B2B - (DEBUG) : Tue Jul 07 15:30:05 CEST 2009 Converting B2B message to ECX message..
2009.07.07 at 15:30:05:909: Thread-9: B2B - (DEBUG) : Tue Jul 07 15:30:05 CEST 2009 Inbound - B2BtoECX - Enter
2009.07.07 at 15:30:05:909: Thread-9: B2B - (DEBUG) : Tue Jul 07 15:30:05 CEST 2009 B2B Message -
2009.07.07 at 15:30:05:909: Thread-9: B2B - (DEBUG) : COLLABORATION_NAME : null
2009.07.07 at 15:30:05:909: Thread-9: B2B - (DEBUG) : ACTION_NAME : DELFOR
2009.07.07 at 15:30:05:909: Thread-9: B2B - (DEBUG) : DOCUMENT_TYPE : DELFOR
2009.07.07 at 15:30:05:909: Thread-9: B2B - (DEBUG) : DOCUMENT_TYPE_REVISION : D97A
2009.07.07 at 15:30:05:909: Thread-9: B2B - (DEBUG) : SOURCE_NAME : tpartner
2009.07.07 at 15:30:05:909: Thread-9: B2B - (DEBUG) : DESTINATION_NAME : Xa d.d.
2009.07.07 at 15:30:05:909: Thread-9: B2B - (DEBUG) : PAYLOAD : UNB+UNOA.............. edi message continues here
2009.07.07 at 15:30:05:925: Thread-9: B2B - (DEBUG) : PAYLOAD : <?xml version="1.0" ?><Transaction-DELFOR............... xml continues here
2009.07.07 at 15:30:05:925: Thread-9: B2B - (DEBUG) : Tue Jul 07 15:30:05 CEST 2009 ECX Message -
2009.07.07 at 15:30:05:925: Thread-9: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.MessageHandler:handleAppMessageRetry Could not deliver the message; exception message is null
2009.07.07 at 15:30:05:925: Thread-9: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.MessageHandler:handleAppMessageRetry No application side retry
2009.07.07 at 15:30:06:081: Thread-9: B2B - (ERROR) Error -: AIP-50903: Message "0A14011912255682A58000003257C600-1" retry count is zero
     at oracle.tip.adapter.b2b.msgproc.MessageHandler.handleAppMessageRetry(MessageHandler.java:394)
     at oracle.tip.adapter.b2b.msgproc.MessageHandler.deliverMessageToDestination(MessageHandler.java:344)
     at oracle.tip.adapter.b2b.msgproc.Request.putMsg(Request.java:657)
     at oracle.tip.adapter.b2b.msgproc.Request.continueRequest(Request.java:481)
     at oracle.tip.adapter.b2b.msgproc.Request.incomingRequest(Request.java:410)
     at oracle.tip.adapter.b2b.engine.Engine.processIncomingMessage(Engine.java:2062)
     at oracle.tip.adapter.b2b.engine.Engine.incomingContinueProcess(Engine.java:2574)
     at oracle.tip.adapter.b2b.engine.Engine.handleMessageEvent(Engine.java:2444)
     at oracle.tip.adapter.b2b.engine.Engine.processEvents(Engine.java:2399)
     at oracle.tip.adapter.b2b.data.MsgListener.onMessage(MsgListener.java:527)
     at oracle.tip.adapter.b2b.data.MsgListener.run(MsgListener.java:374)
     at java.lang.Thread.run(Thread.java:534)
Last message repeats once more and then:
2009.07.07 at 15:30:06:081: Thread-9: BusinessLogicLayer - (DEBUG) Authorization disabled. UserBootstrapped:false, useAuthorization:true, configType:null
2009.07.07 at 15:30:06:081: Thread-9: BusinessLogicLayer - (DEBUG) Push Stack: updateBusinessMessage
2009.07.07 at 15:30:06:096: Thread-9: BusinessLogicLayer - (DEBUG) Pop Stack: updateBusinessMessage
2009.07.07 at 15:30:06:096: Thread-9: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:updateMsgError(3 params) Exit
2009.07.07 at 15:30:06:096: Thread-9: B2B - (DEBUG) DBContext commit: Enter
2009.07.07 at 15:30:06:096: Thread-9: B2B - (DEBUG) DBContext commit: Transaction.commit()
2009.07.07 at 15:30:06:096: Thread-9: B2B - (DEBUG) DBContext commit: Leave
2009.07.07 at 15:30:06:096: Thread-9: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.MessageHandler:deliverMessageToDestination Exit
2009.07.07 at 15:30:06:096: Thread-9: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.Request:incomingRequest Exit
2009.07.07 at 15:30:06:096: Thread-9: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: processIncomingMessage setting seq numbers
2009.07.07 at 15:30:06:112: Thread-9: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processIncomingMessage Call Incoming Request Processor
2009.07.07 at 15:30:06:112: Thread-9: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.Request:incomingRequest Enter
2009.07.07 at 15:30:06:112: Thread-9: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.Request:incomingRequest TransportBindings created
2009.07.07 at 15:30:06:112: Thread-9: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.Request:incomingRequest Create a Message Table Row for Request message with message state Continue Processing
2009.07.07 at 15:30:06:112: Thread-9: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:insertMsgTblRow Enter
2009.07.07 at 15:30:06:112: Thread-9: BusinessLogicLayer - (DEBUG) Authorization disabled. UserBootstrapped:false, useAuthorization:true, configType:null
2009.07.07 at 15:30:06:112: Thread-9: BusinessLogicLayer - (DEBUG) Push Stack: queryExchangeProtocolRevision
2009.07.07 at 15:30:06:112: Thread-9: BusinessLogicLayer - (DEBUG) Pop Stack: queryExchangeProtocolRevision
2009.07.07 at 15:30:06:112: Thread-9: BusinessLogicLayer - (DEBUG) Authorization disabled. UserBootstrapped:false, useAuthorization:true, configType:null
2009.07.07 at 15:30:06:112: Thread-9: BusinessLogicLayer - (DEBUG) Push Stack: queryDocumentProtocolRevision
2009.07.07 at 15:30:06:112: Thread-9: BusinessLogicLayer - (DEBUG) Pop Stack: queryDocumentProtocolRevision
2009.07.07 at 15:30:06:112: Thread-9: BusinessLogicLayer - (ERROR) Error -: AIP-13115: Not in an active transaction
     at oracle.tip.repos.core.persistency.BaseObject.prologue(BaseObject.java:1408)
     at oracle.tip.repos.core.persistency.BaseObject.createObject(BaseObject.java:913)
     at oracle.tip.model.instance.DataStorage.create(DataStorage.java:794)
     at oracle.tip.adapter.b2b.message.MessageStorage.create(MessageStorage.java:145)
     at oracle.tip.adapter.b2b.msgproc.DbAccess.insertMsgTblRow(DbAccess.java:953)
     at oracle.tip.adapter.b2b.msgproc.Request.incomingRequest(Request.java:397)
     at oracle.tip.adapter.b2b.engine.Engine.processIncomingMessage(Engine.java:2062)
     at oracle.tip.adapter.b2b.engine.Engine.incomingContinueProcess(Engine.java:2574)
     at oracle.tip.adapter.b2b.engine.Engine.handleMessageEvent(Engine.java:2444)
     at oracle.tip.adapter.b2b.engine.Engine.processEvents(Engine.java:2399)
     at oracle.tip.adapter.b2b.data.MsgListener.onMessage(MsgListener.java:527)
     at oracle.tip.adapter.b2b.data.MsgListener.run(MsgListener.java:374)
     at java.lang.Thread.run(Thread.java:534)
2009.07.07 at 15:30:06:112: Thread-9: BusinessLogicLayer - (DEBUG) setRuntimeActiveandQuiescing()
2009.07.07 at 15:30:06:112: Thread-9: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processIncomingMessage General Exception ERROR
Error repeats a few times.
Wire message stays in Processing status, Business message is errored and an exception message is created in ip_in_queue.
Both remote and host delivery channels have retry set to 1. Agreement was re-deployed + all B2B restared, but the problem remained.
Could anyone help with this? What could be wrong?
Thanks in advance.
Kind regards,
Wanda
PS. I've checked all threads that might have anything to do with this, but found nothing useful.

Hi Anuj,
thanks for taking the time to examine the file.
Answers to your questions:
1. Yes, this is the 1st time for B2B, but the EBS I'm trying to connect to is up and running for approx. 2 years (it's a test instance).
2. Patching was done by the customer's sysadmin, so I don't really have an overview on what and how he did. Result of opatch:
Installed Patch List:
=====================
1) Patch 8298731 applied on Sat Jun 13 09:23:42 CEST 2009
2) Patch 5907304 applied on Thu Jul 17 14:26:55 CEST 2008
3. In theory the sysadmin should have run it, but how could I double-check this?
I know he had problems while applying patch 8298731, but he said it was solved later. (Customer is using windows os, which is making a lot of troubles otherwise.)
Regarding IDC log there is no success. I've restared B2B at least 5 times plus once the database, but still nothing. In tip.properties:
oracle.tip.adapter.b2b.transportTrace = C:\APPS\OAS\ip\log/transport.trc
also I tried the following values:
C:\\APPS\\OAS\\ip\\log/transport.trc (since there is a similar entry: oracle.tip.LogDirectory = C:\\APPS\\OAS\\ip\\log)
C:\\\\\\\\\\\\\\\\APPS\\\\\\\\\\\\\\\\OAS\\\\\\\\\\\\\\\\ip\\\\\\\\\\\\\\\\log/transport.trc (this was commented before; maybe it comes from some default)
true (I had no other idea)
Result is the same for all the cases: b2b_idc_transport.log file is 0 bytes, but b2b_dc_transport.log has initial data+writes log when processing.
If I remove or comment the above line from tip.properties, then no transport log files are created.
I've updated the agreement to have B2B inbound for the internal delivery channel, re-deployed it and it worked fine -> transaction(s) appeared in IP_IN_QUEUE.
Changing it back to XML Gateway (and re-deploying) causes all original problems.
Regards,
Wanda

Similar Messages

Error In inbound Processing IDoc

Dear All,
I am facing error while inbound processing of IDoc
In status record of IDoc following errors are occuring
Status 60 : EDI: Syntax error in IDoc (mandatory segment missing)
The segment E1MAKTM has the attribute 'Mandatory' in the syntax description of the basic type MATMAS05 (customer enhancement ). However, the segment is missing in the IDoc
Status 51: Application Document not posted
Log details :
Error : Material Number should be filled.
When i checked IDoc all 4 fields in E1MAKTM have the values in inbound IDoc.
Please guide me how to resolve these issues so that IDoc will be posted and Material Master will get created in reciever system.
Thanks

Hi Praveen,
I checked the data in IDoc for this segment.
It is ok as required in basic message type.
e.g. the error says that mandetory segment E1MAKTM is missing.
when i check basic type
MSGFN : Function
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 001, Offset : 0063. external length : 000003
SPRAS : Language Key
internal data type : LANG
Internal length : 000001 characters
Position in segment : 002, Offset : 0066. external length : 000001
MAKTX : Material Description (Short Text)
internal data type : CHAR
Internal length : 000040 characters
Position in segment : 003, Offset : 0067. external length : 000040
SPRAS_ISO : Language according to ISO 639
internal data type : CHAR
Internal length : 000002 characters
Position in segment : 004, Offset : 0107. external length : 000002
is information.
and data in segment of IDoc is
MSGFN     005
SPRAS     E
MAKTX     MANATA2000 TEST ALE
SPRAS_ISO     EN
which i think is ok.
I have no clue why this syntax error is coming.
Thanks
Niketan

Permanant Error in Inbound Processing in BPM

Hi All,
i have done a File1->JDBC(Synch)->File2 scenario using BPM.
It works fine when i have data in input file ie File1. However when my input file empty my scenario shows green flag in "OutboundStatus" and in queue gives error "Permanant error in Inbound Processing". When i tried to see the error in details got exception in START_PROCESS....
After deleting this entry from queue and sending file with data it works fine.....
I just want to know why it happens....? My input file can be empty as i am using it for triggering the scenario.
Do i need to do any settings in BPM or scenario to handle this?
Thanks,
Atul

hi atul,
in the rec step where u set the start process check box, you give the message. it is this message that is used to start the BPM process and not ur input file... the input file is used to trigger ur scenario not ur process. therefore u have exception in 'start process'.
hope it helps.
regards,
latika.

AES filing error - Idoc Outbound Processing: EDI number cannot be compiled

Hi Gurus,
We are configuring the AES filing.
we've done the EDI configI and initally we got the error that EDI partner is not maintained. As per the suggestions from this Forum we've added the cusoms office details in geography tab.
Now when we are trying to process the same, we are getting the error "Idoc Outbound Processing: EDI number cannot be compiled"
All suggestions are welcome.........
Thanks in Advance.

Hi Shiva,
Here goes the solution: you need to maintain the Number of the Number Ranges starting with "10" and this applies only to GTS system as this is HARD-CODED in the Program, apart from 10 any number of the number range will result in an "EDI Number Range compilation" error.
Cheers
Harsha

Sending Inbound application log error in inbound processing through email

Hello all,
My client wants application log for failed idoc through E-mail.(The application log found in we05 for failed idocs).
Please guide me how to get/fetch the error log in inbound processing.
Thank you.
Edited by: Sanjay_lnt on Feb 9, 2010 5:32 AM

Hi,
Query EDIDS table with the relevant selection criteria like date.
Here field STATXT will give you the message text. REPLACE the place holders(&) with STAPA1, STAPA2, STAPA3 and STAPA4 to build the complete message.
Make sure that you read the message for the latest counter(Check Max counter in field COUNTER). Because same IDOC can have multiple messages.
Once you get the message, you can use normal mail sending code for sendingout the mails.
Thanks,
Vinod.
Edited by: Vinod Vemuru on Feb 9, 2010 11:21 AM

Error Occured While Processing Dimension Message:

Hi
I got error occured while processing Account dimension message (when pressed save and process)
Next,what are the steps to be followed;
rgds
srinath
Edited by: srinathgb on Dec 18, 2011 1:20 PM

Hi Nilanjan
Its true, we cannot delete master if there are any transactional data. For Eg:System is giving message for such cases and it will revert in such cases & will not allow us to delete.(Atleast give relevant msg in such cases)
Rgds
Srinath
Edited by: srinathgb on Dec 19, 2011 5:58 AM

Message type for Inbound SD EDI message : Sales Order Confirmation

Hi,
There is an EDI message coming into SAP for sales order confirmation post delivery.
The data in the Idoc should then proceed to update the system and create the delivery document.
I need a standard Message Type which when triggered, will perform the above actions.
Will ORDRSP Message type be useful here.
Thanks ,
Ankit

Hi,
Message type/Idoc type
"ORDERS / ORDERS04 --For orders
ORDCHG / ORDERS04 -Order change
ORDRSP / ORDERS04 --PO
DESADV / DELVRY02 --Deivery
INVOIC / INVOIC02"-Invoice
Thanx,
Pramod

AS2 adapter error during inbound processing

Hello,
We have upgraded PI to version 7.1 and now we are testing the Seeburger AS2 adapter.
We have received a testmessage from an AS2 partner and it is shown in the message monitoring of the Seeburger adapter workbench, with status succesfull.
Only the message is not on the integration server. The message is not shown in sxmb_moni or the message monitor of the RWB.
In the RWB the communication channel (CC_AS2_Sender) gives the following error:
"Message inititiation failed: Processing error"
The message itself gives the following error:
"Inbound message processing failed! performing rollback
Can anyone help us with this?
Thanks in advance.
Regards,
Marco

Hi Marco,
the message is not forwarded to the intergration egine because there might be an error in your communication channel.
Are there any other modules in the module chain of this communication channel?
Can you check "default_trace" and "application_log" for exceptions (/j2ee/cluster/serverXX/log)?
Did you also restart the Java Stack after the Upgrade?
regards,
Daniel
Edited by: Daniel Rexter on Jun 30, 2010 2:59 PM

Error in Inbound Invoice EDI

Hi Everyone !
             When i try to post an inbound invoice in SAP (idoc type INVOIC02), i am getting following error message. "Assigning a new tax key for and VAT not possible".In the Header Tax segment , neither the tax code nor Tax jurdisction code is specifed.
I have checked in transaction OBCD, there is an entry for the Vendor i am specifying...
          Would appreicate your quick response !
Regards,
Mohit.

Hi Sana,
            Thanks for your reply. However the issue is even though TAX Code and TAX Jurdiction Code is not assigned , it still throws error message "Assigning a new tax key for and VAT not possible".
           Also checked Header Segment, no place to fill Tax Code n Tax Jurdiction code there !
          Any more suggestions pls ?
Regards,
Mohit.

XML Gateways Doubts

Dear All,
Can anyone provide me the reusable of XML Gateway or let me know the steps or processes involved in XML Gateway?
I have a requirement of outbound interface between the Oracle Apps and Supplier Application where data should be travel in the format of XML. As i am very new in this regards so wanted to know from where i should start and how can i complete?
Anyone who would have worked please help with possible with re-usables.
Thanks in advanced,
CAK

Hi,
Look for some explanation and related links on:
OracleApps Adapter VS Oracle XML Gateway
Arik

Getting different namespace in inbound XML message consumed by BPEL after translated from EDI to XML in B2B using Inbound Agreement

Hello B2B Gurus,
I am able to process B2B inbound files successfully from Trading Partner --> B2B --> BPEL. When it comes to BPEL i am not able to parse/transform the received XML as i am getting selection failures in assign and empty nodes in transformation. When i look at the input XML payload which i received in ReceiveB2BConsume Payload i observed that i am getting namespace as " xmlns="NS_495C37A0921C418BB66A86A6E75B2CA120070312140549" instead of actual namespace xmlns="urn:oracle:b2b:X12/V4010/856" which is in my XSD as well and i am getting the XML start tag <?xml version="1.0" encoding="UTF-8" ?> 2 times. :
<?xml version="1.0" encoding="UTF-8" ?>
<?xml version="1.0" encoding="UTF-8" ?>
<Transaction-856 xmlns="NS_495C37A0921C418BB66A86A6E75B2CA120070312140549" mlns:xsi="http://www.w3.org/2001/XMLSchema-instance" XDataVersion="1.0" Standard="X12" Version="V4010" CreatedDate="2013-08-21T16:33:57" CreatedBy="XEngine_2956" GUID="{00C28978-0AA1-11E3-88B9-80C16E7DC6DA}">
<Internal-Properties>
</Transaction-856>
I went back and checked the XSD which i loaded in the B2B Console and i am having the following namespace
"<xsd:schema xmlns="urn:oracle:b2b:X12/V4010/856" targetNamespace="urn:oracle:b2b:X12/V4010/856" xmlns:xsd="http://www.w3.org/2001/XMLSchema" version="1.0" elementFormDefault="qualified">"
I am not sure why the XML translated from EDI in B2B console has the different namespace and XML start tag 2 times. Can you please help me resolve the issue. Let me know if i am missing anything.
Thanks in Advance..

Hi,
Please set property as b2b.setDynamicNameSpace=false.
To use EDI ecs and xsd files from Oracle B2B 10g version, set this property to true.
When using EDI ecs and xsd files in Oracle B2B 11g which were used in Oracle B2B 10g, the XEngine may generate dynamic namespace for the translated xml. For example,
xmlns="NS_31CA8D0F33324F95A0BF15D85539C27E20060518215520"
To turn off dynamic namespace generation for inbound EDI messages, set this property to false.
Thanks
Satendra Pare

[URGENT] Get Inbound Message in EBS Using XML Gateway + SOAP

Hi experts,
I want to ask you about how to process the inbound message using XML Gateway and SOAP protocol.
I have 2 EBS instances, let's called it A (source) and B (destination).
FYI, I'm following this ebook: "Oracle E-Business Suite Development and Extensibility Handbook" in chapter 12 regarding Oracle XML Gateway.
So I don't use BPEL PM to do this.
I'm just using EBS with XML Gateway and Integrated SOA Gateway responsibilities.
When I tried to send the XML from A to B using OXTA, it's success, the data can be processed in B and could store in the database.
But when I tried to use SOAP, the XML message that has been sent from A is success, and when I check it on B (Integrated SOA Gateway -> SOA Monitor), the message is in there and I can see the SOAP request and response as well.
SOAP request:
<?xml version="1.0" encoding="UTF-8" ?>
- <env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:ns0="http://xmlns.oracle.com/apps/fnd/XMLGateway" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">
- <env:Header>
- <ns0:XMLGateway_Header>
<ns0:MESSAGE_TYPE>XML</ns0:MESSAGE_TYPE>
<ns0:MESSAGE_STANDARD>OAG</ns0:MESSAGE_STANDARD>
<ns0:TRANSACTION_TYPE>XKLB</ns0:TRANSACTION_TYPE>
<ns0:TRANSACTION_SUBTYPE>ORDER_DETAILS_XO</ns0:TRANSACTION_SUBTYPE>
<ns0:DOCUMENT_NUMBER>9282</ns0:DOCUMENT_NUMBER>
<ns0:PARTY_SITE_ID>142</ns0:PARTY_SITE_ID>
<ns0:USERNAME>cons.ade</ns0:USERNAME>
<ns0:PASSWORD>cons.ade</ns0:PASSWORD>
</ns0:XMLGateway_Header>
</env:Header>
- <env:Body>
<ns0:ReceiveDocument xsi:type="xsd:string"><ORDER_DETAILS_XO xmlns=""> <ORDER> <ORDNO>100002</ORDNO> <ORDWT>100002</ORDWT> <RDATE/> <CITY>JAKARTA</CITY> <ZIP>17121</ZIP> </ORDER> </ORDER_DETAILS_XO></ns0:ReceiveDocument>
</env:Body>
</env:Envelope>
SOAP response:
- <env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">
<env:Header />
- <env:Body>
- <ReceiveDocument_Response xmlns="http://xmlns.oracle.com/apps/fnd/XMLGateway">
<ResponseCode xmlns="http://xmlns.oracle.com/apps/fnd/XMLGateway">200</ResponseCode>
<ResponseMsgId xmlns="http://xmlns.oracle.com/apps/fnd/XMLGateway">BD4EAD91E76051D5E0440021287448DA</ResponseMsgId>
<ResponseInfo xmlns="http://xmlns.oracle.com/apps/fnd/XMLGateway">Document received and pushed into queue for asynchronous processing. Enqueued message id is 'BD4EAD91E76051D5E0440021287448DA'.</ResponseInfo>
</ReceiveDocument_Response>
</env:Body>
</env:Envelope>
But the problem is the message that has been got in B can't store into the database yet.
I had already changed the Queue in the XML Gateway -> Define Transaction, from APPLSYS.ECX_IN_OAG_Q (this is for OXTA) to APPLSYS.WF_WS_JMS_IN.
After I invoke the webservice and the SOAP message has been got in B, I checked APPLSYS.WF_WS_JMS_IN in database and there is 1 record, the value of USER_DATA column is:
((, , , , , , ((BES_EVENT_NAME, 100, oracle.apps.fnd.wf.ws.inbound.xmltx.receive, , 27), (BES_EVENT_KEY, 100, 796550960, , 27), (BES_PRIORITY, 200, , 1, 23), (BES_FROM_AGENT, 100, [email protected], , 27), (BES_TO_AGENT, 100, [email protected], , 27), (MSG_ID, 100, 1334117503435, , 27), (ECX_MESSAGE_TYPE, 100, XML, , 27), (ECX_MESSAGE_STANDARD, 100, OAG, , 27), (ECX_PARTY_SITE_ID, 100, 142, , 27), (WS_PORT_OPERATION, 100, ReceiveDocument, , 27), (ECX_TRIGGER_ID, 100, 7101, , 27), (UserId, 100, 3020, , 27), (ECX_USERNAME, 100, CONS.ADE, , 27), (ECX_TRANSACTION_SUBTYPE, 100, ORDER_DETAILS_XO, , 27), (ECX_PASSWORD, 100, CONS.ADE, , 27), (ECX_DOCUMENT_NUMBER, 100, 9285, , 27), (BES_PAYLOAD_OBJECT, 100, false, , 27), (ECX_ATTACHMENTS, 100, , , 27), (ECX_TRANSACTION_TYPE, 100, XKLB, , 27), , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , )), 0, , )
When I tried to select APPLSYS.WF_WS_JMS_IN for the 2nd time, there is no result, which means the business event has been triggered, right?
So in this point I still don't have any idea why the process is (likely) ended after enter the Queue and the message can't store into B's database yet.
Do I miss any setup when changing from OXTA into SOAP protocol to send XML message?
Any urgent help most appreciated.
Best Regards,
Rheza

Hi,
Did you ever get any answers to this? We are thinking about the same thing.
Thanks
Darma
[email protected]

Error in XML Gateway Processing - java.lang.OutOfMemoryError

Hi All,
We have B2B Customizations for Processing Orders in our Applications .
While an Inbound Document(ORDERSTATUS Document) got processed in our Application, we could find the Document being errored out in XML gateway with the following errors:
(Note: Partners are on E2Open Gateway and we dont use Webmethods)
1) ORA-29532: Java call terminated by uncaught Java exception: java.lang.OutOfMemoryError- ECX_INBOUND_NEW.PROCESS_XML_DOC
2) ORA-29532: Java call terminated by uncaught Java exception: java.lang.OutOfMemoryError - ecx_utils.INITIALIZE:
The Error has occured only twice (one in the month of May and the other in June) and its not replicable.
We verified all the Trending aspects (If the Issue is due to XML Document content, Specific to a particular Partner etc).
But we didnt find any clue about the occurence of this error.
Kindly provide your views on the occurence of the error.
Thanks in Advance,
Mangala.

Hi Mangala,
This error comes when JVM runs out of memory. Few cause may be -
1. You are trying to operate on a very large file (comparing to your system's primary memory)
2. You are trying to parse an xml, use SAX parser for best performance
3. Your JVM_OPTIONS value is not sufficient
You may consider increasing your JVM_OPTIONS value to some appropriate limit.
Are you working with Matthew Sullivan/Richard's team?
Regards,
Anuj

Order Import after PO Inbound via XML Gateway Error

I am using Apps Adapter (11g) to connect to EBiz Suite 11.5.10. I am doing PO Inbound and using XML Gateway to create the sales order. Even though I am populating order type in <POTYPE> under the <POORDERHDR>, during order import, I keep getting the error that "please provide order type". Can you please let me know which xml tag I need to populate the order type.
Thanks
Shanthi

Following are some of the pros of using XML Gateway:
1) XML is being accepted and more and more technologies are moving towards XML, so that "seems" to a future ready solution
2) XML processing is real-time.
3) Most of the maps for universally accepted standards are seeded in Oracle.
4) You can use Oracle Supplier Network(Free service provided by Oracle) with your XML gateway to transmit/receive xml documents to a supplier who may or may not be accepting the format you are generating(e.g. if your PO is in OAG standard and your supplier is accepting cXML format, OSN takes care of translating your document)
You might want to consider these points while deciding the technology.
Nitin S. Darji

BPEL Process Errors at XML Gateway

Hi
I am in the process of developing AP Invoice Inbound process using BPEL.
Process errored outs at XML Gateway with below error.
The Standard:OAG, Transaction Type:AP , Transaction SubType:INI and Location Code 1 is not enabled in the XML Gateway Server. Pls check your Setup.
I have gone through the XML Gateway setup but could not able to locate what exactly the problem.
Could anybody help me out to fix this problem.
Regards
Kiran Akkiraju

Hi,
I am also experiencing the very same problem - does anyone have a solution for this or is this a bug?
Thanks.
Tony.

Error in inbound processing: EDI message - XML Gateway

Similar Messages

Maybe you are looking for