B2b.edi.enablePreprocess in cluster

Hi All,
i am facing an issue with the Mbean property "b2b.edi.enablePreprocess" in cluster soa instances. The input EDI document has an 80 character limit and i had set the MBean property b2b.edi.enablePreprocess on both soa_server1 and soa_server2.. however, we observe that the input edi file is picked sometimes successfully and sometimes with failure...
Could any of you suggest what could be done to fix this issue..
regards
Rakesh

There should not be any issue w.r.t cluster.
Just ensure to restart the server after adding the property.
It could be a case that the file would have been copied partially when polling listening channel. Try increasing the polling interval and see.
If the issue persists, please send the diagnostic log in trace:32 mode to my email-id (in my profile)
Regards,
Dheeraj

Similar Messages

B2B EDI translation ----Is it possible to increase the sub-element length

B2B EDI translation ----Is it possible to increase the sub-element length??
Am new to the B2B 10g- EDI Integration environment. In our production setup, am getting the following error.
B2B EDI Translation failed, because one of the fields was too long. The length of Sub-element length is '41'. The maximum allowed length is '35'.
In the segment RFF defined in the guideline at position 0070; Is it possible to increase / expand the lenght from 35 to 41.....
Thanks and Rgds,
-Srini

Hi Nitesh
I have the same problem what srini explained above.
I'm using Oracle B2B Document editor.
That corresponding element's field is in disabled state ,a red triangle displays in top right corner of that field.
Could you help me to solve this issue?
Regards
Kathir

AQ B2B-EDI fails

I have faced a typical problem while reading data from an Oracle AQ adapter and sending it to a B2B adapter.I am using a simple BPEL process for this co-ordination.I am using B2B EDI.
The problem is there is a headertype element both in AQ Adapter inboundHeader wsdl and B2b wsdl. Both having same namespace
http://xmlns.oracle.com/pcbpel/adapter/aq/inbound/ . But unfortunately though both the wsdl uses the same namespace but having different elements inside it within the complexType element headertype. Obviously at the time of compilation it throws me an error like duplicate namespace found in the bpel.xml. since both the wsdls referenced in it.anybody faced this one and may come up with solution?
Warm regards
Soumya

We are using the AQ adapter in both directions. That works. However, perhaps you can try to edit the XSD files manually and merge them so that all the elements are present in both (but not required, i.e. minoccurs=0)? While it is a bit dirty to edit generated files that may solve your problem, provided that the differences are minor.

B2B EDI File Configuration Settings

Hi All,
We are seeing some default values in our EDI files for following Segment elements.
Interchange Control Number (100000044)
Group Control Number (1044)
We are using 4010_850 format.
Let us know where to change these default values in B2B console.
Thanks,
Sid.

Hi Sid,
it's not default value. instead it is a running number automatically generated by B2B. it increments for ever interchange/group/transaction
Thanks,
Prasanna

B2B EDI X12 over FTP

I am new Oracle B2B.
I am trying to do the below task.
An EDI X12 file will be placed in a Remote Server. This file has to be picked up and after the transformed data has to be queued in IP_IN_QUEUE.
I have followed the below steps.
1. Created Business action for EDI X12 4010 document.
2. Created Remote Trading partner, and assigned the Business action created in step 1 here.
3. Configured FTP delivery channel in my Host trading partner which also have the end point uri as the Remote Trading partner point to in step 2.
4. Created the Agreement and in the internal delivery channel, I selected B2B Inbound.
5. Deployed the configuration.
Could you please tell me if the above steps are correct?
I am havign doubt on the step 3, what protocol is to be used for Delivery channel in my Host Tranding partner?
It should be the same as the one I configured in Remote Trading Partner DC?
If yes, the what will be end point uri in Host Partner DC?
And how the data read from the file will be placed in the IP_IN_QUEUE?
Could you please answer my questions?
Thanks
Praveena.

Again after this I was getting Document Protocol Error, and PROTOCOL_ENDPOINT = null
I came to know from dheeraj's reply that these errors are only due to me bad payload.
In document Editor if we say generate the data, actually the data is not valid data, I opened the .dat file in Document Editor analyser and it showed me the errors.
I corrected teh errors, and now I am still getting error "5016: A mandatory data element is missing"
Segment ISA(Interchange Control Header) at guideline position (N/A) is missing.
I am still checking with the payload for the validation against the ecs file.
Thanks Dheeraj for your answer, I got some confidence.

EDI error

Hi Guru's
We setup a trading partner to send messages using AS2.We are getting the error for incoming payload. we have verified the payload with our ecs file using the data analyzer in the B2B document editor. But the same payload gives error message in the b2b log and does not get processed.
B2B - (ERROR) com.edifecs.shared.jni.JNIException: Execute failed - CECToolsException thrown - HRESULT[650007], description[The data in the file could not be parsed. Please check the file to verify that it is valid and formatted correctly. This error can occur for one of the following reasons: A) The data file may be a Word document or have some other binary format. B) The envelope data may not be formatted properly. If this is an X12 data file, please verify that the ISA segment is the correct size (exactly 106 characters). If this is an EDIFACT data file, it must have either a UNA or begin with UNB. For other standards, verify that the envelope segments conform to the specified rules. C) The segment/record delimiters in the file are incorrect.]
     at com.edifecs.shared.jni.xdata.INativeToXData.ExecuteNative(Native Method)
     at com.edifecs.shared.jni.xdata.INativeToXData.Execute(Unknown Source)
     at oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin.identifyIncomingDocument(EDIDocumentPlugin.java:310)
     at oracle.tip.adapter.b2b.engine.Engine.identifyDocument(Engine.java:2387)
     at oracle.tip.adapter.b2b.engine.Engine.processIncomingMessage(Engine.java:1263)
     at oracle.tip.adapter.b2b.transport.InterfaceListener.onMessage(InterfaceListener.java:161)
     at oracle.tip.transport.basic.HTTPReceiver.sendRequest(HTTPReceiver.java:431)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:261)
     at sun.rmi.transport.Transport$1.run(Transport.java:148)
     at java.security.AccessController.doPrivileged(Native Method)
     at sun.rmi.transport.Transport.serviceCall(Transport.java:144)
     at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:460)
     at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:701)
     at java.lang.Thread.run(Thread.java:534)
Please help us in resolving the issue. The trading partner is using Gentran as B2B server
Regards
Sahil

GOOD NEWS -
There is setting in Oracle Integration B2B Engine for Preprocessing.
The issue with carriage return in the payload received from the Trading Partner - EDI 850 has new line charaters and fails to recognise the Document Protocol Identification.
We had a support case opened on this and following is the recommendation -
Please set oracle.tip.adapter.b2b.edi.enablePreprocess = true in the ip/config/tip.properties file and restart the server.
oracle.tip.adapter.b2b.edi.enablePreprocess = true
Make sure there are no spaces after this setting.
This was done and the issue was resolved. Following is the additional DEBUG log that we noticed once this setting was turned on.
2007.06.06 at 11:55:24:466: RMI TCP Connection(2)-200.1.0.78: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:identifyIncomingDocument Enter
2007.06.06 at 11:55:24:467: RMI TCP Connection(2)-200.1.0.78: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:preProcessor enter
2007.06.06 at 11:55:24:468: RMI TCP Connection(2)-200.1.0.78: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:preProcessor edi = X12
2007.06.06 at 11:55:24:873: RMI TCP Connection(2)-200.1.0.78: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:identifyIncomingDocument preprocess result =
Sharath

End of file / parsing error for EDI document

I have an issue where a Trading partner is sending extra non readable characters after the last segment terminator in a X12 EDI document. I know there is a property to strip the CR/LF characters and that does not help me.
Do I have any other options for preprocessing in B2B ?

Hi,
Try using the property oracle.tip.adapter.b2b.edi.enablePreprocess=true in the tip.properties file.
ALso could you please let me know the property which removes CRF/LF characters from the input file to B2B.
Thanks for your help.
Regards,
Dibya

Document protocol identification error

Hi While receving Shipment from our trading partner, it showing below error in b2b, Please help me in resolving this? We are suing Custom document over internet.
Machine Info: (essaps000-u008.emrsn.com)
Description: Unable to identify the document protocol of the message
StackTrace:
Error -: AIP-50083: Document protocol identification error
     at oracle.tip.adapter.b2b.engine.Engine.identifyDocument(Engine.java:3245)
     at oracle.tip.adapter.b2b.engine.Engine.processIncomingMessage(Engine.java:1666)
     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.09.15 at 10:31:07:504: Thread-30: B2B - (DEBUG) MimePackaging:unpack:Exit
2009.09.15 at 10:31:07:504: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processIncomingMessage Decode the Incoming Message into B2B Message
2009.09.15 at 10:31:07:504: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.as2.AS2ExchangePlugin:AS2ExchangePlugin:decodeIncomingMessage Enter
2009.09.15 at 10:31:07:504: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.as2.AS2ExchangePlugin:AS2ExchangePlugin:decodeIncomingMessage Number of Components = 1
2009.09.15 at 10:31:07:504: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.as2.AS2ExchangePlugin:AS2ExchangePlugin:decodeIncomingMessage compInfoList[k].getValue().toLowerCase()==>text/plain
2009.09.15 at 10:31:07:504: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.as2.AS2ExchangePlugin:AS2ExchangePlugin:decodeIncomingMessage Components List= [Loracle.tip.adapter.b2b.packaging.ComponentInfo;@4fa23a
2009.09.15 at 10:31:07:505: Thread-30: B2B - (DEBUG) calling setFromPartyId() changing from null to TPName: null Type: AS2 Identifier Value: BENCHQA
2009.09.15 at 10:31:07:505: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.as2.AS2ExchangePlugin:AS2ExchangePlugin:decodeIncomingMessage File Name=>null
2009.09.15 at 10:31:07:505: Thread-30: B2B - (DEBUG) calling setToPartyId() changing from null to TPName: null Type: AS2 Identifier Value: EMRSNS
2009.09.15 at 10:31:07:505: Thread-30: B2B - (DEBUG) calling setInitiatingPartyId() changing from null to TPName: null Type: AS2 Identifier Value: BENCHQA
2009.09.15 at 10:31:07:505: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.as2.AS2ExchangePlugin:AS2ExchangePlugin:decodeIncomingMessage:Payload ï»¿<?xml version="1.0" encoding="utf-8"?><ShowShipment releaseID="9.0" systemEnvironmentCode="Production" languageCode="en-US" xmlns:ns6="http://www.openapplications.org/oagis/9/IANAMIMEMediaTypes:2003" xmlns:ns0="http://www.openapplications.org/oagis/9/unqualifieddatatypes/1.1" xmlns:ns1="http://www.openapplications.org/oagis/9/qualifieddatatypes/1.1" xmlns:ns5="http://www.openapplications.org/oagis/9/currencycode/54217:2001" xmlns:ns3="http://www.openapplications.org/oagis/9/languagecode/5639:1988" xmlns:ns2="http://www.openapplications.org/oagis/9/codelists" xmlns:ns4="http://www.openapplications.org/oagis/9/unitcode/66411:2001" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<ApplicationArea>
<Sender>
<LogicalID>SCN024538</LogicalID>
<ComponentID>SHIPMENT</ComponentID>
<TaskID>SHOW</TaskID>
<ReferenceID>TSI20090914000000000000000000000002</ReferenceID>
<ConfirmationCode>Never</ConfirmationCode>
<AuthorizationID>160</AuthorizationID>
</Sender>
<CreationDateTime>2009-09-15T11:11:21</CreationDateTime>
</ApplicationArea>
<DataArea>
<Show>
<OriginalApplicationArea>
<Sender>
<LogicalID>EMR1601000</LogicalID>
</Sender>
<CreationDateTime>2009-09-15T11:11:21</CreationDateTime>
</OriginalApplicationArea>
</Show>
<Shipment>
<ShipmentHeader>
<DocumentID xsi:type="ItemIDType">
<ID>TSI543897</ID>
</DocumentID>
<DocumentDateTime>20090914</DocumentDateTime>
<DocumentReference type="WayBillAirBill">
<DocumentID>TTSA021720000001</DocumentID>
</DocumentReference>
<DocumentReference type="BillOfLading">
<DocumentID>BTSA02172000002</DocumentID>
</DocumentReference>
<DocumentReference type="PackingSlip">
<DocumentID>TSI543897</DocumentID>
</DocumentReference>
<Attachment inline="false">
</Attachment>
<ActualShipDateTime>20090914</ActualShipDateTime>
<ScheduledDeliveryDateTime>20091012</ScheduledDeliveryDateTime>
<ShipFromParty>
<PartyIDs>
<ID>501V00041757</ID>
</PartyIDs>
<Name>BENCHMARK ELECTRONICS THAILAND</Name>
<Location>
<ID>160234567</ID>
</Location>
</ShipFromParty>
</ShipmentHeader>
<ShipmentItem>
<ItemID>
<ID>166806G1</ID>
<RevisionID>
</RevisionID>
</ItemID>
<SupplierItemID>
<ID> EML166806G1</ID>
</SupplierItemID>
<Description>ASSY GROUND CURRENT DETECTOR</Description>
<ShippedQuantity unitCode="EA">20</ShippedQuantity>
<PurchaseOrderReference>
<DocumentID xsi:type="DocumentIDType">
<ID>501LBR295816</ID>
</DocumentID>
<ReleaseNumber>
</ReleaseNumber>
<LineNumber>001</LineNumber>
<ScheduleLineNumber>1 </ScheduleLineNumber>
</PurchaseOrderReference>
</ShipmentItem>
</Shipment>
</DataArea>
</ShowShipment>
2009.09.15 at 10:31:07:506: Thread-30: B2B - (DEBUG) calling setMode() changing from -1 to 2
2009.09.15 at 10:31:07:511: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.as2.AS2ExchangePlugin:AS2ExchangePlugin:decodeIncomingMessage Exit
2009.09.15 at 10:31:07:512: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processHubMessage Enter
2009.09.15 at 10:31:07:512: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processHubMessage toTP EMRSNS
2009.09.15 at 10:31:07:512: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processHubMessage hubUrl null
2009.09.15 at 10:31:07:512: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processHubMessage Exit
2009.09.15 at 10:31:07:512: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processIncomingMessage ProtocolCollabId = null
2009.09.15 at 10:31:07:512: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processIncomingMessage CollaborationName null
2009.09.15 at 10:31:07:513: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:checkDuplicate Enter
2009.09.15 at 10:31:07:513: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:checkDuplicate check non-RosettaNet Message
2009.09.15 at 10:31:07:515: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:checkDuplicate Exit
2009.09.15 at 10:31:07:515: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processIncomingMessage Protocol Collaboration Id : null
2009.09.15 at 10:31:07:515: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:identifyIncomingDocument Enter
2009.09.15 at 10:31:07:519: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:ISelectorImpl Enter
2009.09.15 at 10:31:07:519: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:ISelectorImpl validateEnvelope = false
2009.09.15 at 10:31:07:519: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:ISelectorImpl Leave
2009.09.15 at 10:31:07:520: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:cloneSelector Enter
2009.09.15 at 10:31:07:520: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:cloneSelector Return = oracle.tip.adapter.b2b.document.edi.ISelectorImpl@23ce9f
2009.09.15 at 10:31:07:597: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:identifyIncomingDocument errcode = Execute failed - CECToolsException thrown - HRESULT[650007], description[The data in the file could not be parsed. Please check the file to verify that it is valid and formatted correctly. This error can occur for one of the following reasons: A) The data file may be a Word document or have some other binary format. B) The envelope data may not be formatted properly. If this is an X12 data file, please verify that the ISA segment is the correct size (exactly 106 characters). If this is an EDIFACT data file, it must have either a UNA or begin with UNB. For other standards, verify that the envelope segments conform to the specified rules. C) The segment/record delimiters in the file are incorrect.]
2009.09.15 at 10:31:07:598: Thread-30: B2B - (ERROR) com.edifecs.shared.jni.JNIException: Execute failed - CECToolsException thrown - HRESULT[650007], description[The data in the file could not be parsed. Please check the file to verify that it is valid and formatted correctly. This error can occur for one of the following reasons: A) The data file may be a Word document or have some other binary format. B) The envelope data may not be formatted properly. If this is an X12 data file, please verify that the ISA segment is the correct size (exactly 106 characters). If this is an EDIFACT data file, it must have either a UNA or begin with UNB. For other standards, verify that the envelope segments conform to the specified rules. C) The segment/record delimiters in the file are incorrect.]
     at com.edifecs.shared.jni.xdata.INativeToXData.ExecuteNative(Native Method)
     at com.edifecs.shared.jni.xdata.INativeToXData.Execute(Unknown Source)
     at oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin.identifyIncomingDocument(EDIDocumentPlugin.java:370)
     at oracle.tip.adapter.b2b.engine.Engine.identifyDocument(Engine.java:3226)
     at oracle.tip.adapter.b2b.engine.Engine.processIncomingMessage(Engine.java:1666)
     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.09.15 at 10:31:07:598: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.document.custom.CustomDocumentPlugin:identifyIncomingDocument Enter
2009.09.15 at 10:31:07:657: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.document.custom.CustomDocumentPlugin:identifyIncomingDocument non-XML Payload
2009.09.15 at 10:31:07:658: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.document.custom.CustomDocumentPlugin:identifyIncomingDocument iDoc ECS = null
2009.09.15 at 10:31:07:658: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.document.custom.CustomDocumentPlugin:identifyIncomingDocument continuing
2009.09.15 at 10:31:07:658: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.document.custom.CustomDocumentPlugin:identifyIncomingDocument non-XML Payload
2009.09.15 at 10:31:07:658: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.document.custom.CustomDocumentPlugin:identifyIncomingDocument iDoc ECS = null
2009.09.15 at 10:31:07:658: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.document.custom.CustomDocumentPlugin:identifyIncomingDocument could not get start pos
2009.09.15 at 10:31:07:658: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.document.custom.CustomDocumentPlugin:identifyIncomingDocument could not get end pos
2009.09.15 at 10:31:07:659: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.document.custom.CustomDocumentPlugin:identifyIncomingDocument non-XML Payload
2009.09.15 at 10:31:07:659: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.document.custom.CustomDocumentPlugin:identifyIncomingDocument iDoc ECS = null
2009.09.15 at 10:31:07:659: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.document.custom.CustomDocumentPlugin:identifyIncomingDocument continuing
2009.09.15 at 10:31:07:659: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.document.custom.CustomDocumentPlugin:identifyIncomingDocument non-XML Payload
2009.09.15 at 10:31:07:659: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.document.custom.CustomDocumentPlugin:identifyIncomingDocument iDoc ECS = null
2009.09.15 at 10:31:07:659: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.document.custom.CustomDocumentPlugin:identifyIncomingDocument could not get start pos
2009.09.15 at 10:31:07:660: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.document.custom.CustomDocumentPlugin:identifyIncomingDocument could not get end pos
2009.09.15 at 10:31:07:660: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.document.custom.CustomDocumentPlugin:identifyIncomingDocument non-XML Payload
2009.09.15 at 10:31:07:660: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.document.custom.CustomDocumentPlugin:identifyIncomingDocument iDoc ECS = null
2009.09.15 at 10:31:07:660: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.document.custom.CustomDocumentPlugin:identifyIncomingDocument could not get start pos
2009.09.15 at 10:31:07:660: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.document.custom.CustomDocumentPlugin:identifyIncomingDocument could not get end pos
2009.09.15 at 10:31:07:661: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.document.custom.CustomDocumentPlugin:identifyIncomingDocument Exit
2009.09.15 at 10:31:07:662: Thread-30: B2B - (ERROR) Error -: AIP-50083: Document protocol identification error
     at oracle.tip.adapter.b2b.engine.Engine.identifyDocument(Engine.java:3245)
     at oracle.tip.adapter.b2b.engine.Engine.processIncomingMessage(Engine.java:1666)
     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.09.15 at 10:31:07:662: Thread-30: B2B - (ERROR) Error -: AIP-50083: Document protocol identification error
     at oracle.tip.adapter.b2b.engine.Engine.identifyDocument(Engine.java:3245)
     at oracle.tip.adapter.b2b.engine.Engine.processIncomingMessage(Engine.java:1666)
     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.09.15 at 10:31:07:662: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:handleExceptionBeforeIncomingTPA Enter
2009.09.15 at 10:31:07:662: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: handleInboundException Enter
2009.09.15 at 10:31:07:663: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: handleInboundException Error message is Error -: AIP-50083: Document protocol identification error
2009.09.15 at 10:31:07:663: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: isFARequired Enter
2009.09.15 at 10:31:07:665: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: isFARequired {CONTENT-TRANSFER-ENCODING=binary, CONNECTION=Keep-Alive, AS2-FROM=BENCHQA, CONTENT-TYPE=application/pkcs7-mime; smime-type=enveloped-data; name="smime.p7m", MIME-VERSION=1.0, RECEIPT-DELIVERY-OPTION=http://b2b-qa.bench.com/BenchmarkAS2Receive_QA/BTSHTTPReceive.dll, AS2-VERSION=1.1, EXPECT=100-continue, USER-AGENT=Microsoft(R) BizTalk(R) Server 2006 R2 3.0.1.0, AS2-TO=EMRSNS, CONTENT-LENGTH=5137, ORACLE-ECID=1253032264:10.236.2.145:16396:0:3376,0, MESSAGE-ID=<ANG-QA-BT01_09D55C86-117A-4E5A-90C1-03C8B96EDB2E>, HOST=emersonb2b-s.emrsn.com, B2B_SERVLET_URI_PATTERN=/b2b/transportServlet, DISPOSITION-NOTIFICATION-TO=http://b2b-qa.bench.com/BenchmarkAS2Receive_QA/BTSHTTPReceive.dll}
2009.09.15 at 10:31:07:665: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: isFARequired returning false
2009.09.15 at 10:31:07:665: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: handleInboundException FA not required
2009.09.15 at 10:31:07:666: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:handleInboundException Updating Error Message: Error -: AIP-50083: Document protocol identification error
2009.09.15 at 10:31:07:666: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Enter
2009.09.15 at 10:31:07:666: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Wire message found
2009.09.15 at 10:31:07:666: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Creating new b2berror object
2009.09.15 at 10:31:07:667: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState enum0 not null
2009.09.15 at 10:31:07:667: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Updating wire message error information
2009.09.15 at 10:31:07:671: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Updating wire message protocol message id
2009.09.15 at 10:31:07:684: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Updating wire message payload storage
2009.09.15 at 10:31:07:694: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Creating new business message
2009.09.15 at 10:31:07:694: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:insertMsgTblRow Enter
2009.09.15 at 10:31:07:734: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:insertMsgTblRow toparty name null
2009.09.15 at 10:31:07:734: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:insertMsgTblRow toparty type and value AS2 IdentifierEMRSNS
2009.09.15 at 10:31:07:769: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:insertMsgTblRow BusinessAction for the given name null null
2009.09.15 at 10:31:07:815: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Updating business message error information
2009.09.15 at 10:31:07:827: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Exit
2009.09.15 at 10:31:07:828: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:handleInboundException Updating Native Event Tbl Row
2009.09.15 at 10:31:07:828: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:updateNativeEvtTblRow Enter
2009.09.15 at 10:31:07:830: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateNativeEvtTblRow msgInfo.id = <ANG-QA-BT01_09D55C86-117A-4E5A-90C1-03C8B96EDB2E>
2009.09.15 at 10:31:07:830: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:
** DbAccess:updateNativeEvtTblRow:tip_wireMsg protocolCollabID = null
2009.09.15 at 10:31:07:841: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:handleInboundException notifying App
2009.09.15 at 10:31:07:841: Thread-30: B2B - (DEBUG) Engine:notifyApp Enter
2009.09.15 at 10:31:07:848: Thread-30: B2B - (DEBUG) notifyApp:notifyApp Enqueue the ip exception message:
<Exception xmlns="http://integration.oracle.com/B2B/Exception" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<correlationId>null</correlationId>
<b2bMessageId>0AEC0291123BE8B0DB800000B91B0200</b2bMessageId>
<errorCode>AIP-50083</errorCode>
<errorText>Document protocol identification error</errorText>
<errorDescription>
<![CDATA[Machine Info: (essaps000-u008.emrsn.com)
Description: Unable to identify the document protocol of the message
StackTrace:
Error -: AIP-50083: Document protocol identification error
     at oracle.tip.adapter.b2b.engine.Engine.identifyDocument(Engine.java:3245)
     at oracle.tip.adapter.b2b.engine.Engine.processIncomingMessage(Engine.java:1666)
     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)
]]>
</errorDescription>
<errorSeverity>2</errorSeverity>
</Exception>
2009.09.15 at 10:31:07:859: Thread-30: B2B - (DEBUG) Engine:notifyApp Exit
2009.09.15 at 10:31:07:859: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:handleInboundException Updated the Error Message Successfully: Error -: AIP-50083: Document protocol identification error
2009.09.15 at 10:31:07:859: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: handleInboundException Exit
2009.09.15 at 10:31:07:860: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:handleExceptionBeforeIncomingTPA Exit
2009.09.15 at 10:31:07:860: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:incomingContinueProcess Exit
2009.09.15 at 10:31:07:860: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:handleMessageEvent Exit
2009.09.15 at 10:31:07:860: Thread-30: B2B - (INFORMATION) oracle.tip.adapter.b2b.engine.Engine:processEvents Exit
2009.09.15 at 10:31:07:861: Thread-30: B2B - (DEBUG) DBContext commit: Enter
2009.09.15 at 10:31:07:865: Thread-30: B2B - (DEBUG) DBContext commit: Transaction.commit()
2009.09.15 at 10:31:07:865: Thread-30: B2B - (DEBUG) DBContext commit: Leave
2009.09.15 at 10:31:07:865: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.data.MsgListener:onMessage Exit
Edited by: user8653471 on Sep 15, 2009 10:55 PM

Hi Anuj,
Please set oracle.tip.adapter.b2b.edi.enablePreprocess = true in the ip/config/tip.properties file and restart the server.
Do above statement is related to EDI? I am using Custom document over internet
I did not find any unreadable/non-xml characters in the xml file, here i am attaching the xml fille.
<?xml version="1.0" encoding="utf-8"?><ShowShipment releaseID="9.0" systemEnvironmentCode="Production" languageCode="en-US" xmlns:ns6="http://www.openapplications.org/oagis/9/IANAMIMEMediaTypes:2003" xmlns:ns0="http://www.openapplications.org/oagis/9/unqualifieddatatypes/1.1" xmlns:ns1="http://www.openapplications.org/oagis/9/qualifieddatatypes/1.1" xmlns:ns5="http://www.openapplications.org/oagis/9/currencycode/54217:2001" xmlns:ns3="http://www.openapplications.org/oagis/9/languagecode/5639:1988" xmlns:ns2="http://www.openapplications.org/oagis/9/codelists" xmlns:ns4="http://www.openapplications.org/oagis/9/unitcode/66411:2001" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<ApplicationArea>
<Sender>
<LogicalID>SCN024538</LogicalID>
<ComponentID>SHIPMENT</ComponentID>
<TaskID>SHOW</TaskID>
<ReferenceID>TSI20090914000000000000000000000002</ReferenceID>
<ConfirmationCode>Never</ConfirmationCode>
<AuthorizationID>160</AuthorizationID>
</Sender>
<CreationDateTime>2009-09-15T11:11:21</CreationDateTime>
</ApplicationArea>
<DataArea>
<Show>
<OriginalApplicationArea>
<Sender>
<LogicalID>EMR1601000</LogicalID>
</Sender>
<CreationDateTime>2009-09-15T11:11:21</CreationDateTime>
</OriginalApplicationArea>
</Show>
<Shipment>
<ShipmentHeader>
<DocumentID xsi:type="ItemIDType">
<ID>TSI543897</ID>
</DocumentID>
<DocumentDateTime>20090914</DocumentDateTime>
<DocumentReference type="WayBillAirBill">
<DocumentID>TTSA021720000001</DocumentID>
</DocumentReference>
<DocumentReference type="BillOfLading">
<DocumentID>BTSA02172000002</DocumentID>
</DocumentReference>
<DocumentReference type="PackingSlip">
<DocumentID>TSI543897</DocumentID>
</DocumentReference>
<Attachment inline="false">
</Attachment>
<ActualShipDateTime>20090914</ActualShipDateTime>
<ScheduledDeliveryDateTime>20091012</ScheduledDeliveryDateTime>
<ShipFromParty>
<PartyIDs>
<ID>501V00041757</ID>
</PartyIDs>
<Name>BENCHMARK ELECTRONICS THAILAND</Name>
<Location>
<ID>160234567</ID>
</Location>
</ShipFromParty>
</ShipmentHeader>
<ShipmentItem>
<ItemID>
<ID>166806G1</ID>
<RevisionID>
</RevisionID>
</ItemID>
<SupplierItemID>
<ID> EML166806G1</ID>
</SupplierItemID>
<Description>ASSY GROUND CURRENT DETECTOR</Description>
<ShippedQuantity unitCode="EA">20</ShippedQuantity>
<PurchaseOrderReference>
<DocumentID xsi:type="DocumentIDType">
<ID>501LBR295816</ID>
</DocumentID>
<ReleaseNumber>
</ReleaseNumber>
<LineNumber>001</LineNumber>
<ScheduleLineNumber>1 </ScheduleLineNumber>
</PurchaseOrderReference>
</ShipmentItem>
</Shipment>
</DataArea>
</ShowShipment>

EDI - B2B - BPEL Data exchange

Hi All,
I am new to EDI and B2B but knows BPEL very well.
My doubts are:
1. How and what format the data exchange happened between BPEL --> B2B and also between B2B ---> EDI ?
2. Do we need EDI Adapter to support EDI over B2B ?
Thanks in advance,
Kamleshwar

Hi Kamleshwar,
If you are working with 10g, then below links will explain you everything -
http://www.oracle.com/technology/products/integration/b2b/pdf/edi_cookbook_oracle_b2b.pdf
http://www.oracle.com/technology/products/integration/b2b/pdf/B2B_TN_022_Enabling_B2B_BPEL_Interop.pdf
http://www.oracle.com/technology/products/integration/b2b/pdf/B2B_TU_001_B2B_BPEL.pdf
Do we need EDI Adapter to support EDI over B2B ?Oracle B2B has in-built EDI adapter and you don't need one explicitly.
Regards,
Anuj

How to use Callout in B2B on the basis of STATUS

Hi,
If there occurs a validation error in the B2B EDI contents, what mechanism can be used to update that status back to the source system?
We are using B2B Adapter in the BPEL Process to pass the XML file and B2B generates an EDI file for us. Now, if there are any validation errors due to which the EDI file doesn't get generated. What mechanism in B2B I can use to take that status and message and respond back to the caller?
Have heard about "Callout" in B2B, can we use it? If yes, then how?
Thanks
Priyanka

Hi Priyanka,
Let me see if I understood. You want to be able to do some specific processing after an EDI message has an error when sending the message but also when the message is sent properly. Correct?
For the first case: When an EDI message has an error when sending:
you can use what I described earlier and set an exception queue. You will then receive all exceptions on a back-end SOA process and can apply your specific processing there.
For the second case: When an EDI message is sent properly, you can perhaps use one of these 2 options:
Using the B2B BAM connection for communicating to the back-end. Set the BAM to true under Administration -> Configuration. You need then to configure a JMS queue linked to the Remote JNDI AQ of B2B_BAM_QUEUE. Then, you can read from this JMS on your composite level and filter for the messages that you desire and continue your process from there.
Use the FA for the Agreement. This should force that an ACK message is sent back to your B2B if message is properly delivered. Upon receiving this message you can then process it to your back-end application and once again apply your specific processing there.
I hope this helps.
Cheers
Tiago

B2B identifying TP from file name and not Interchange

We want B2B to identify trading partner from ISA/GS segment, but B2B is taking it from file name. We have property oracle.tip.adapter.b2b.edi.identifyFromTP set to "Interchange". As I understand based on the tip.property it should always take from the ISA/GS segment in dat file.
We also have Trading Partner Identification Type set to EDI Interchange ID while setting up trading partner and it is set to the same value as Interchange Receiver Id in the Document Protocol.
Anyone has any ideas?
Thanks

Hello Venkat,
ideally this should work. Guess you have not restarted b2b after changing the tip.properties. If you still have issues, please raise an SR and also send the b2b.log in DEBUG mode.
Rgds,Ramesh

Handling Multiple Host GS ID in SOA 11g B2B

Hi,
Greetings to B2B Gurus !!!
We have a requirement to map different Host Group Interchange ID based on Input data and we are getting an error saying that, not able to identify the Trading Partner since the values are same. We have already added below property but it looks it handles only Remote Trading Partner for multiple Group Interchange ID not for the Host TP.
oracle.tip.adapter.b2b.edi.identifyFromTP = Group
Please find the Header details below.
Host Group Interchange ID#1
ISA*00* *00* *01*196938484 *01*00169129 *120525*2238*U*00400*000000895*0*P*>~
GS*IN*196938484L*00169129*20120525*2238*386*X*004010~
Host Group Interchange ID#2
ISA*00* *00* *01*196938484 *01*00169129 *120525*2239*U*00400*000000896*0*P*>~
GS*IN*196938484M*00169129*20120525*2239*252*X*004010~
Host Group Interchange ID#3
ISA*00* *00* *01*196938484 *01*00169129 *120525*2253*U*00400*000000897*0*P*>~
GS*IN*196938484S*00169129*20120525*2253*239*X*004010~
Any Pointers on this is highly appreciated.
Thanks,
Saravana

Hi Anuj,
We have tried the option that you told and its not even allowing us to create the Agreement. Please find the error message that we got during agreement creation.
Error -: B2B-52291: Duplicate agreement Name: AGFA_M_810_INO_Agreement, AgreementID: AGFA_M_810_INO_Agreement & Name: AGFA_L_810_INO_Agreement, AgreementID: AGFA_L_810_INO_Agreement found with same combination of trading partners Ricoh, AGFA-Lease, and document type 4010 and document protocol version 810.
Its checking for the combination of Host and Remote Trading Partner, Document Type and Document Protocol Version and its same for both the customer accounts. Only change is Group Interchange ID of Host Trading partner.
Could you please advise.
Thanks,
Saravana

EDI X12 over File Protocol - Handling multiple Interchange Ids

Hi
I am having two types of EDI X12 payloads (with different names). With different Interchange Ids.
In my Agreement I have give given one Interchange Id.
my tip.properties:
allTPInoneDirectory= true
identifyFromTP= ANY
oracle.tip.adapter.b2b.edi.ignoreValidation=InterchangeReceiverID,InterchangeSenderID,GroupReceiverID,GroupSenderID,GroupSenderQual,GroupReceiverQual,InterchangeSenderQual,InterchangeReceiverQual
My TP name and directory name are equal.
I am not identifying by File Name.
The file whose InterchangeId I have given in the Agreement is passign through successfully.But the other is not passing throgh.
It is giving Business action -> 'BA Name'
No Agreement found with the XR and POL (my Host Trading Partner name)
Ex: My File name: XR_XYZ.dat
other File XR_XYV.dat
I have changed the Trading Partner Identification to by Name, instead of Interchange ID. Then also it is giving the same Error.
Could you please tell me what can be the problem.
Thanks
Praveena

Hi
I am able to solve this.
In my second EDI payload EDI Interchange Id(ABC) is different from the first EDI Payload(XYZ).
My First config which was not working:
In my Remote Trading Partner , I have given Identifications as
1. EDI Interchange ID: XYZ.
2. Name: TP name.
In the Agreement, I have selected Name as Identification.
Second Config Which is working:
In my Remote Trading Partner , I have given Identifications as
1. EDI Interchange ID: XYZ.
2. EDI Interchange ID: ABC
2. Name: TP name.
In the Agreement, I have selected Name as Identification.
With this second EDI Payload is also passing through.
My question: As we are giving TP name as the Trading Partner Identification in the agreement, why does it matter for all other Identification types which we give in Remote Trading Partner. This is inbound operation.
Could you please answer my question?

ORA-24816 Error on EDI inbound processing

We are encountering an issue for EDI X12 inbound data files which have extraneous characters. B2B initially failed throwing “ Document Protocol Identification error “ .
To resolve this, we enabled flag “b2b.edi.enablePeprocess” to true , after which it started processing fine in DEV environment , however it throws below exception in QA environment .
Internal Exception: java.sql.SQLException: ORA-24816: Expanded non LONG bind data supplied after actual LONG or LOB column
Error Code: 24816
Call: INSERT INTO B2B_WIRE_MESSAGE (ID, JOB_ID, ACKNOWLEDGEMENT_MODE, LABEL, ATTRIBUTE2, MESSAGE_DIGEST, ATTRIBUTE4, MESSAGE_ID, ATTRIBUTE3, ATTRIBUTE5, CPST_INST_CREATED_TIME, CREATED, LAST_RESUBMITTED_TIME_STAMP, MODIFIED, LAST_VIEWED_TIME_STAMP, MSG_SIZE, DELIVERED_ENDPOINT, PASSWORD, DIRECTION, PORT, ENCRYPTION_CERTIFICATE, PROTOCOL_COLLABORATION_ID, ERROR_CODE, PROTOCOL_MESSAGE_ID, ERROR_DESCRIPTION_CLOB, PROTOCOL_TRANSPORT_BINDING, ERROR_TEXT_CLOB, REFER_TO_PROTOCOL_MESSAGE_ID, EXCHANGE_REMAINING_RETRY, RESUBMIT_COUNT, FROM_ADDRESS, SIGNING_ALGORITHM, SIGNING_CERTIFICATE, MESSAGE_STATUS, SIGNING_PROTOCOL, LAST_VIEWED_USER_NAME, STATE, DIGEST_ALGORITHM, TO_ADDRESS, ENCRYPTION_PROTOCOL, TRANSPORT_CERTIFICATES, ERROR_TEXT, TRANSPORT_CORRELATION_ID, EXCHANGE_RETRY_INTERVAL, TRANSPORT_HEADERS, ATTRIBUTE1, TRANSPORT_PROTOCOL, CHANNEL_NAME, TRANSPORT_PROTOCOL_VERSION, ERROR_DESCRIPTION, TRANS_SECURITY_PROTOCOL, HOST_NAME, TRANS_SECURITY_PROT_VERSION, ENCRYPTION_ALGORITHM, URL, LAST_RESUBMITTED_USER_NAME, USER_NAME, EXCHANGE_ATTEMPT_COUNT, VERSION, PAYLOAD_STORAGE, PACKED_MESSAGE, RESUBMIT_REF_TO) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)
bind => [A513532C140185965980000010261DFC, null, SYNC, null, null, rLdBG4pYQf76lQXJZdl43gE7QqE=^M
We checked many options for the differences between Dev & QA , but could not find a root cause .
Version : 11.1.1.6

Hi,
I am getting the same error.
Can u please help me on this.
Thanks and Regards
Neha Kapoor

B2B Trading partner identification

We have the following scenario:
1. Trading Partner sends X12 PO 850 ( one Interchange ID) But at our side we have multiple Interchange ID's . So file comes from single customer ( single sender ID) but having multiple Receiver ID's.
So is this true that only way to handle this is to create multiple Partners in Oracle B2B and attach Sender Receiver ID's on aggrement?
I tried above option but B2B is not able to identiify TP based on SENDER RECEIVED ID combination. We have b2b.edi.identifyToTP =true.
Error Code B2B-50549
Error Description Machine Info: (xyz.americas.com) Description: Cannot uniquely identify a trading partner. The trading partners CA_SEARS, SCA_SEARS have the same set of identifications.
Error Level ERROR_LEVEL_COLLABORATION
Error Severity ERROR
Error Text Cannot uniquely identify a trading partner. The trading partners CA_SEARS, SCA_SEARS have the same set of identifications
Vijay.

Now problem is with outbound.... we need to send outbound docs to different channels for same Tp based on our different Sender ID's. So I thought to create 2 different tp is B2B and use seperate channels for both.Ok. If I understood it correctly, then in your scenario you have to send same document (doctype and docrevision) to same TP on different URL's based on your different sender ID's. If this is the case then definitely you have to have two remote TP's in your B2B configuration but both remote TP's should use different receiver ID's (your TP should have two interchange id's).
What happening currently is that you have created two separate TP's but both of them are using same interchange id's which is not possible in B2B scenario. All TP's must have unique Interchange ID's
Regards,
Anuj

B2b.edi.enablePreprocess in cluster

Similar Messages

Maybe you are looking for