EDI 810 transaction error: Cannot uniquely identify a trading partner

Hi,
I am facing following error on B2B 11g version 11.1.1.6.0. Please provide the solution if you are aware of the issue.
Error Description: Cannot uniquely identify a trading partner. The trading partners PARTNER-A, PARTNER-B have the same set of identifications.
Partner Identification parameter for PARTNER-A and PARTNER-B
EDI Interchange ID: xxxx
EDI Interchange ID Qualifier: yyyy
EDI Group ID: 111
Name: PARTNER-A
EDI Interchange ID: xxxx
EDI Interchange ID Qualifier: yyyy
EDI Group ID: 111
Name: PARTNER-B
Thank you
Ram

Two TPs can not have same identification.
There are two ways to come out of this problem.
1. Change the identification criteria for the TP.
2. Use exchange level Identification for one TP.

Similar Messages

AIP-52251: Error identifying remote trading partner at MLLP Exchange with

used HL7 over MLLP, one trading partner is EAI(B2B Localhost), another is EchoServer(a java application, the hostname is is4-nb4.corp.ha.org.hk). used a script to enqueue message. like below:
DECLARE
enqueue_options dbms_aq.enqueue_options_t;
message_properties dbms_aq.message_properties_t;
msg_handle RAW(16);
ipmsg b2b.IP_MESSAGE_TYPE;
xml_clob clob;
msg_id number(10);
subscribers dbms_aq.aq$_recipient_list_t;
BEGIN
select message_seq.nextval into msg_id from dual;
xml_clob := '<?xml version="1.0" ?><ADT_A01 xmlns="http://www.edifecs.com/xdata/200" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" XDataVersion="2.0" Standard="HL7" Version="2.3.1" CreatedDate="2005-08-16T16:52:26" CreatedBy="ECXEngine_826" GUID="{1A2726C6-B00E-DA11-8F7A-080020C8D296}"><MSH><MSH.1>|</MSH.1><MSH.2>^~\&</MSH.2><MSH.3><HD.1>EDI</HD.1></MSH.3><MSH.4><HD.1>PWH</HD.1></MSH.4><MSH.5><HD.1>EchoPac</HD.1></MSH.5><MSH.6><HD.1>PWH</HD.1></MSH.6><MSH.7><TS.1>20050804162010</TS.1></MSH.7><MSH.8 xsi:nil="true"></MSH.8><MSH.9><MSG.1>ADT</MSG.1><MSG.2>A01</MSG.2></MSH.9><MSH.10>TEST007</MSH.10><MSH.11><PT.1>#Property(ProcessingID)#</PT.1></MSH.11><MSH.12><VID.1>2.3.1</VID.1></MSH.12><MSH.13 xsi:nil="true"></MSH.13><MSH.14 xsi:nil="true"></MSH.14><MSH.15>AL</MSH.15><MSH.16>ER</MSH.16><MSH.17>#Property(CountryCode)#</MSH.17><MSH.18>ASCII</MSH.18><MSH.19><CE.1>ENG</CE.1></MSH.19></MSH><PID><PID.1>1</PID.1><PID.2 xsi:nil="true"></PID.2><PID.3><CX.1>A0000010</CX.1></PID.3><PID.4 xsi:nil="true"></PID.4><PID.5><XPN.1><FN.1>TEST, Patient 01_10</FN.1></XPN.1></PID.5><PID.6 xsi:nil="true"></PID.6><PID.7><TS.1>20001001</TS.1></PID.7><PID.8>F</PID.8></PID><PV1><PV1.1>1</PV1.1><PV1.2 xsi:nil="true"></PV1.2><PV1.3 xsi:nil="true"></PV1.3><PV1.4 xsi:nil="true"></PV1.4><PV1.5 xsi:nil="true"></PV1.5><PV1.6 xsi:nil="true"></PV1.6><PV1.7 xsi:nil="true"></PV1.7><PV1.8 xsi:nil="true"></PV1.8><PV1.9 xsi:nil="true"></PV1.9><PV1.10 xsi:nil="true"></PV1.10><PV1.11 xsi:nil="true"></PV1.11><PV1.12 xsi:nil="true"></PV1.12><PV1.13 xsi:nil="true"></PV1.13><PV1.14 xsi:nil="true"></PV1.14><PV1.15 xsi:nil="true"></PV1.15><PV1.16 xsi:nil="true"></PV1.16><PV1.17 xsi:nil="true"></PV1.17><PV1.18 xsi:nil="true"></PV1.18><PV1.19><CX.1>10010</CX.1></PV1.19></PV1></ADT_A01>
subscribers(1) := SYS.AQ$_AGENT('b2buser', null, null);
message_properties.RECIPIENT_LIST := subscribers;
ipmsg := b2b.IP_MESSAGE_TYPE (msg_id, null,'EAI','EchoServer','Echo_ADTA01_Process', 'ADT_A01', '2.3.1', 1, xml_clob, null);
dbms_aq.enqueue(queue_name => 'b2b.IP_OUT_QUEUE',
enqueue_options => enqueue_options,
message_properties => message_properties,
payload => ipmsg,
msgid => msg_handle);
commit;
END;
show errors;
then go to the B2B Report tab, can see two message like below
EAI EchoServer MLLP - 1.0 HL7 - 2.3.1 Echo_ADTA01_Process WaitFA 2007年11月12日星期一下午05:51:37
Acknowledgement Invalid 2007年11月12日星期一下午
and in the log file, like this:
2007.11.12 at 17:51:43:064: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.mllp.MLLPExchangePlugin:decodeIncomingMessage Could not find a Trading Partner with MLLP ID = is4-nb4. Please check the Trading Partner Identification section of your Trading Partner
2007.11.12 at 17:51:43:064: Thread-10: B2B - (ERROR) Error -: AIP-52251: Error identifying remote trading partner at MLLP Exchange with MLLP ID is4-nb4
     at oracle.tip.adapter.b2b.exchange.mllp.MLLPExchangePlugin.decodeIncomingMessage(MLLPExchangePlugin.java:247)
     at oracle.tip.adapter.b2b.engine.Engine.processIncomingMessage(Engine.java:1177)
     at oracle.tip.adapter.b2b.engine.Engine.incomingContinueProcess(Engine.java:2030)
     at oracle.tip.adapter.b2b.engine.Engine.handleMessageEvent(Engine.java:1962)
     at oracle.tip.adapter.b2b.engine.Engine.processEvents(Engine.java:1920)
     at oracle.tip.adapter.b2b.data.MsgListener.onMessage(MsgListener.java:463)
     at oracle.tip.adapter.b2b.data.MsgListener.run(MsgListener.java:335)
     at java.lang.Thread.run(Thread.java:534)
2007.11.12 at 17:51:43:064: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.mllp.MLLPExchangePlugin:decodeIncomingMessage identify trading partner by MLLP Id failed for is4-nb4 with ExceptionError -: AIP-52251: Error identifying remote trading partner at MLLP Exchange with MLLP ID is4-nb4
2007.11.12 at 17:51:43:064: Thread-10: B2B - (ERROR) Error -: AIP-52251: Error identifying remote trading partner at MLLP Exchange with MLLP ID is4-nb4
     at oracle.tip.adapter.b2b.exchange.mllp.MLLPExchangePlugin.decodeIncomingMessage(MLLPExchangePlugin.java:257)
     at oracle.tip.adapter.b2b.engine.Engine.processIncomingMessage(Engine.java:1177)
     at oracle.tip.adapter.b2b.engine.Engine.incomingContinueProcess(Engine.java:2030)
     at oracle.tip.adapter.b2b.engine.Engine.handleMessageEvent(Engine.java:1962)
     at oracle.tip.adapter.b2b.engine.Engine.processEvents(Engine.java:1920)
     at oracle.tip.adapter.b2b.data.MsgListener.onMessage(MsgListener.java:463)
     at oracle.tip.adapter.b2b.data.MsgListener.run(MsgListener.java:335)
     at java.lang.Thread.run(Thread.java:534)
2007.11.12 at 17:51:43:064: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:handleExceptionBeforeIncomingTPA Enter
2007.11.12 at 17:51:43:064: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: handleInboundException Enter
2007.11.12 at 17:51:43:064: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: handleInboundException Error message is Error -: AIP-52251: Error identifying remote trading partner at MLLP Exchange with MLLP ID is4-nb4
2007.11.12 at 17:51:43:064: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: isFARequired Enter
2007.11.12 at 17:51:43:064: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: isFARequired {From=is4-nb4, FromIP=160.19.23.102, FARequired=true, protocolVersion=1.0, ToIP=160.19.55.114, Port=4911, Message-Id=1194861102002-1207274363, protocol=TCP, To=is4wingw02}
2007.11.12 at 17:51:43:064: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: isFARequired returning true
2007.11.12 at 17:51:43:064: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: handleInboundException Error Set
2007.11.12 at 17:51:43:064: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: createAndSendFA Enter
2007.11.12 at 17:51:43:064: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: createAndSendFA processed by HL7
2007.11.12 at 17:51:43:064: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.hl7.HL7DocumentPlugin:createFA Enter
2007.11.12 at 17:51:43:064: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.hl7.HL7DocumentPlugin:createFA Not creating an ACK for an incoming ACK Message
2007.11.12 at 17:51:43:064: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: createAndSendFA B2BMessage is null
2007.11.12 at 17:51:43:064: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: createAndSendFA Exit
2007.11.12 at 17:51:43:064: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: handleInboundException FA Sent
2007.11.12 at 17:51:43:064: Thread-10: B2B - (DEBUG) DBContext beginTransaction: Enter
2007.11.12 at 17:51:43:064: Thread-10: B2B - (DEBUG) DBContext beginTransaction: Leave
2007.11.12 at 17:51:43:064: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:handleInboundException Updating Error Message: Error -: AIP-52251: Error identifying remote trading partner at MLLP Exchange with MLLP ID is4-nb4
2007.11.12 at 17:51:43:064: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Enter
2007.11.12 at 17:51:43:064: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Wire message found
2007.11.12 at 17:51:43:064: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState enum not null
2007.11.12 at 17:51:43:064: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Updating wire message error information
2007.11.12 at 17:51:43:064: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Updating wire message protocol message id
2007.11.12 at 17:51:43:064: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Updating wire message payload storage
2007.11.12 at 17:51:43:080: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Creating new business message
2007.11.12 at 17:51:43:080: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:insertMsgTblRow Enter
2007.11.12 at 17:51:43:080: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:insertMsgTblRow BusinessAction for the given name null null
2007.11.12 at 17:51:43:080: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Updating business message error information
2007.11.12 at 17:51:43:080: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Exit
2007.11.12 at 17:51:43:080: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:handleInboundException Updating Native Event Tbl Row
2007.11.12 at 17:51:43:080: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:updateNativeEvtTblRow Enter
2007.11.12 at 17:51:43:080: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateNativeEvtTblRow msgInfo.id = 1194861102002-1207274363
2007.11.12 at 17:51:43:096: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:handleInboundException notifying App
2007.11.12 at 17:51:43:096: Thread-10: B2B - (DEBUG) Engine:notifyApp Enter
2007.11.12 at 17:51:43:096: Thread-10: 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>A0133772116334587C90000068CD8000</b2bMessageId>
<errorCode>AIP-52251</errorCode>
<errorText>Error identifying remote trading partner at MLLP Exchange with MLLP ID is4-nb4</errorText>
<errorDescription>
<![CDATA[Machine Info: (is4wingw02)
Error -: AIP-52251: Error identifying remote trading partner at MLLP Exchange with MLLP ID is4-nb4 ]]>
</errorDescription>
<errorSeverity>2</errorSeverity>
</Exception>
2007.11.12 at 17:51:43:096: Thread-10: B2B - (DEBUG) Engine:notifyApp Exit
2007.11.12 at 17:51:43:096: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:handleInboundException Updated the Error Message Successfully: Error -: AIP-52251: Error identifying remote trading partner at MLLP Exchange with MLLP ID is4-nb4
2007.11.12 at 17:51:43:096: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: handleInboundException Exit
2007.11.12 at 17:51:43:096: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:handleExceptionBeforeIncomingTPA Exit
2007.11.12 at 17:51:43:096: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:incomingContinueProcess Exit
2007.11.12 at 17:51:43:096: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:handleMessageEvent Exit
2007.11.12 at 17:51:43:111: Thread-10: B2B - (INFORMATION) oracle.tip.adapter.b2b.engine.Engine:processEvents Exit
2007.11.12 at 17:51:43:111: Thread-10: B2B - (DEBUG) DBContext commit: Enter
2007.11.12 at 17:51:43:111: Thread-10: B2B - (DEBUG) DBContext commit: Transaction.commit()
2007.11.12 at 17:51:43:111: Thread-10: B2B - (DEBUG) DBContext commit: Leave
2007.11.12 at 17:51:43:111: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.data.MsgListener:onMessage Exit
here said not find the remote partner, but in B2B server, can ping Echoserver.
what is wrong?

Hello again,
I have tried all different combinations with the IP addresses and host names, but to no avail. Then I changed the Trading Partner Identification Type from MLLP Id to Sending Application (one of the customer requirements is to be able to identify the Trading Partner by the combination of Sending App/Sending Facility, since they are running multiple HL7 applications on one host). However, I still see the same error in the log file - for some reason, B2B is still trying to identify the Trading Partner by the MLLP Id. Redeploying the configuration didn't help, the requested identification type is ignored.
Please help! If needed, I can send the B2B log file, but maybe I'm missing something obvious.
BTW, the customer has installed the patch for bug 6439217 on October 10th. The B2B version is 10.1.2.2.0.
Thanks in advance!

Cannot uniquely identify member

Hi all,
while Building the dimensions in essbase i am getting a warning "Can not uniquely identify member......" in dataload.err file.
Has any body come across this kind of error.
also i am building the dimensions from relational database using parent/child references.
i have enabled duplicate members in the outline.
awaiting reply at the earliest.
thanks in advance.

As Glenn said...
Turning duplicates on is one of those "grab gun, aim at foot, pull trigger" options. Apart from the dataload issues, the issues associated with "disambiguation" on the reporting side is utter insanity! It may not get you right away, but sooner or later you are guaranteed to find yourself "in the ermergency room" when you use this option.
It's bad enough when accounting/finance calls down to ask why their "revenue is wrong" and you have to play 20 questions to narrow the issue down to something actionable, now you have even more vagueness to deal with.
Of course, there are times when this seems perfectly "okay", as in using Month names in a year structure of a time dimension... but the additional context should have just been added to the members in the first place to avoid the redundancy of having to use them everywhere you turn anyway.
I cannot imagine a situation in which turning the duplicate member names on is better than the two or three common alternatives to this nightmare.

Seeburger EDI Adapter Deployment Error: Cannot register EarLoader

Hello,
we currently have updated our SAP Netweaver Development Environment 2004s to SP20. This installation runs on IBM iSeries.
We also have to deploy a Seeburger EDI Adapter (Version 1.8) but we faced following error in the deployment:
---snipped
PM Error: Aborted: development component
'SeeFunctionsEar'/'seeburger.com'/'SEEBURGER
AG'/'20090701183537.1.8.1'/'1', grouped by software component
'SeeXIExtendedTools'/'seeburger.com'/'LOCAL'/'20090701183537.1.8.1''/'1':
Caught exception during application deployment from SAP J2EE Engine's
deploy service:
java.rmi.RemoteException: Cannot register EarLoader for application
seeburger.com/SeeFunctionsEar..
Reason: null; nested exception is:
java.lang.NullPointerException
(message ID:
com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
---snipped
We've deployed not only with the JSPM but also with developer Studio. (The SDM-Tool has a big problem after upgrating to SP20 - SAP knows the error and with the next SP this will be fixed. So this tool cannot be used!)
First of all, I think it is very useful for us to know what is the EarLoader but unfortunately we can't find any information on the sap help, documentation or here in the SDN. Neither on the Web .....
Could someone explain the issue to me, please?
Thanks in advance.
Christian Sperlich

Hi,
1)Can you check your class path, whether it is configured correctly
2)Check whether you have included the latest class file while importing
3)Check whether you have activated the objects after you have made changes are imported
Regards
Agasthuri Doss

EDI-810 Invois error

Uncaught exception (see the 'inner exception' below) has suspended an instance of service 'ABC.Orchestrations.ABC810Orchestration(8b18a26d-a248-06g0-c3f3-8345c1aa820r)'.
The service instance will remain suspended until administratively resumed or terminated.
If resumed the instance will continue from its last persisted state and may re-throw the same unexpected exception.
InstanceId: 27af0eb1-76cb-4239-8629-7293e67c04de
Shape name: ABCThrowException_abc
ShapeId: 2675139a-f81f-40af-87f2-11e55f96c95b
Exception thrown from: segment 4, progress 3
Inner exception: Root element is missing.
Exception type: XmlException
Source: Microsoft.XLANGs.Engine
Target Site: Void ExceptionRaised()
The following is a stack trace that identifies the location where the exception occured
at Microsoft.XLANGs.Core.Context.ExceptionRaised()
at ABCIntegration.Orchestrations.ABC810Orchestration.segment4(StopConditions stopOn)
at Microsoft.XLANGs.Core.SegmentScheduler.RunASegment(Segment s, StopCondi
TVS Apache

The error is very clear - "Root Element is missing", this implies that either the message is "" or has multiple nodes at root level in the same message.
Use the BizTalk Administration console to view the exact message that has been suspended and that will give you a better idea.
When (If) using custom components, very often after the disassembly one forgets to rewind the message stream as a result of which the stream pointer points to the EOS and when BizTalk tries to read the message stream it gets an EOS and assumes that it is
an empty message. Also when you try to perform a XmlDocument.Load(stream) you will get the error you see.
Regards.

Error -: AIP-16012: Parameter: trading Partner is unique for object Trading

Hi Gurus,
When I go to rename the b2b server under trading partners, I receive the following error:
An error occurred when updating the trading partner.
1. Error -: AIP-16012: Parameter: trading Partner is unique for object Trading Partner Identification
2. TradingPartner.TradingPartner - Error -: AIP-11052: Writing following objects: Trading Partner Identification failed due to following constraint violation: TRADINGPARTNERIDENTIFICATION_UK. UNIQUE CONSTRAINT VIOLATION
3. PartyIdentificationType.TradingPartnerIdentificationType - Error -: AIP-11052: Writing following objects: Trading Partner Identification failed due to following constraint violation: TRADINGPARTNERIDENTIFICATION_UK. UNIQUE CONSTRAINT VIOLATION
4. Value - Error -: AIP-11052: Writing following objects: Trading Partner Identification failed due to following constraint violation: TRADINGPARTNERIDENTIFICATION_UK. UNIQUE CONSTRAINT VIOL
This occurs after I purge the b2b and even manually delete the trading partner that has the name that I require to change the server to (required for quality assurance testing). When I check the identifiers, there are two name ones (one of them is the one I am trying to change to) but I cannot delete any of them as it is grayed out.
Any thoughts?
Thanks
Gerald
Edited by: Gerald M. on Nov 30, 2009 8:50 AM -addtional info

Solved the issue, I manually delete entries in b2b.tip_tradingpartneriden_aud and b2b.tip_tradingpartneridentifica_t.
Is this safe to be doing this?
Thanks
Gerald

Trading Partner Agreement Not found error in EDI EDIFACT Scenario

Hello all,
I am getting the following error in the trace file in the EDI EDIFACT over Generic Exchange Scenario,i have verified the agreement effective to date,i also have checked the enq_orders.properties & enq_ordrsp.properties on both the servers and the FromParty Name and ToParty Name are shown correctly.so where does the actual problem occur can anyone plz help me out to solve this issue.
MsgID = C0A8010111EF3AC936E0000068CB7800
ReplyToMsgID = null
FromParty = Acme
ToParty = Acme
EventName = Exception
DoctypeName = Exception
DoctypeRevision = 1.0
MsgType = 3
payload length = 1820
*<Exception xmlns="http://integration.oracle.com/B2B/Exception" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">*
*<correlationId>null</correlationId>*
*<b2bMessageId>C0A8010111EF3AC936E0000068CB7800</b2bMessageId>*
*<errorCode>AIP-50547</errorCode>*
*<errorText>Trading partner agreement not found for the given input values: From partyNAME "Acme", To partyNAME "Acme", Business action name "Process_ORDERS"; also verify agreement effectiveToDate</errorText>*
*<errorDescription>*
*<![CDATA[Machine Info: (mcity94)*
*Description: Unable to identify the trading partner agreement from the given input values. Also verify agreement effectiveToDate*
*StackTrace:*
*Error -: AIP-50547: Trading partner agreement not found for the given input values: From party[NAME|http://forums.oracle.com/forums/] "Acme", To partyNAME "Acme", Business action name "Process_ORDERS"; also verify agreement effectiveToDate*
**     at oracle.tip.adapter.b2b.tpa.RepoDataAccessor.getAgreementNameByBaTPName(RepoDataAccessor.java:2225)**
**     at oracle.tip.adapter.b2b.tpa.TPAIdentifier.identifyTPA(TPAIdentifier.java:181)**
**     at oracle.tip.adapter.b2b.tpa.TPAProcessor.processTPA(TPAProcessor.java:511)**
**     at oracle.tip.adapter.b2b.tpa.TPAProcessor.processIncomingTPA(TPAProcessor.java:229)**
**     at oracle.tip.adapter.b2b.engine.Engine.processIncomingMessage(Engine.java:1715)**
**     at oracle.tip.adapter.b2b.engine.Engine.incomingContinueProcess(Engine.java:2404)**
**     at oracle.tip.adapter.b2b.engine.Engine.handleMessageEvent(Engine.java:2303)**
**     at oracle.tip.adapter.b2b.engine.Engine.processEvents(Engine.java:2258)**
**     at oracle.tip.adapter.b2b.data.MsgListener.onMessage(MsgListener.java:500)**
**     at oracle.tip.adapter.b2b.data.MsgListener.run(MsgListener.java:348)**
**     at java.lang.Thread.run(Thread.java:534)**
*]]>*
*</errorDescription>*
*<errorSeverity>2</errorSeverity>*
*</Exception>*
Thanx
Sunny
Edited by: sunny kay on Jan 20, 2009 7:45 AM

Hi
Since the error states "Process_ORDERS" as the Business action I assume you are trying to enq the ORDERS document from Acme to GlobalChips. The issue then would be due to the fact that there is a trailing space character after the GlobalChips
Please check for a space (or spaces) after
to = GlobalChips
Also ensure that the UI has the trading partner with the same spelling ie. GlobalChips and not Globalchips
Thanks,
--Arun

Identify Trading Partner EDI X12 over File Protocol

Hi
I am working on EDI X12 (835) over File Protocol.
The EDI payloads I will be getting will hold same EDI InterchangeIds, Group, or Exchange.
oracle.tip.adapter.b2b.edi.identifyFromTP = ANY
and I have given oracle.tip.adapter.b2b.allTPInOneDirectory = false.
So that it identifies based on the directory name.
For this I changed my trading partner name same as directory name.
Could you please suggest me is there any other way of identifying From Trading partner than changing the Trading partner name to directory name?
Thanks & Regards,
Praveena.

Hi Praveena,
Yes, TP name and directory name should be same.
Put oracle.tip.adapter.b2b.allTPInOneDirectory = true (Idetifies the Trading partner by the directory name) in your tip.properties file.
Check below thread for more information on TP identification -
Re: Internal Delievery channel AIP-51505: General Validation Error
Regards,
Anuj
Edited by: Anuj Dwivedi on May 5, 2009 4:31 PM

IDOC Status 26: EDI: Syntax error in IDoc (segment cannot be identified).

Hi All,
I have created IDOC extension for IDOC Basic type "PROACT01" and have followed all required necessary steps but getting IDOC
Status 26. EDI: Syntax error in IDoc (segment cannot be identified). The exact error is:
Please check Error Details and the details of the steps I followed for Setting up IDOC Extension:
Error Detail :
EDI: Syntax error in IDoc (segment cannot be identified)
Message no. E0078
Diagnosis
The segment ZPROSEG does not occur at the current level of the basic type PROACT01 (extension PROACTEX).
This error can have several reasons:
The segment ZPROSEG is assigned to a group whose header segment does not occur.
The segment ZPROSEG does not exist in the syntax description of the basic type PROACT01 (extension PROACTEX).
The sequence of segments in the group in which the segment appears is incorrect.
Previous errors ('mandatory' segment or group missing) may be due to this error.
Procedure
Please check the IDoc or the syntax description of the basic type PROACT01 (extension PROACTEX).
Can you please look at this problem and suggest what is wrong with IDOC Extension/Custome Segment?
Below is the Details of the Steps which I have followed:
1. Tcode WE31 - Created new custom Segment ZPROSEG with 4 fields. Released segment.
2. TCode WE30 - Created IDOC Extension PROACTEX for Basic Type PROACT01. Released IDOC extension.
Here when I run syntax check warning appears "No predecessors exist". I am not sure if its okay!!
3. TCode WE82 - Added Extension PROACTEX in the Message Type PROACT with BASIC Type PROACT01.
4. TCode WE20 - Added IDOC Extension PROACTEX in the predefined partner profile in WE20 transaction.
5. Added the following code in the Customer Exit EXIT_SAPLWVMI_001 include ZXWVMIU01 .
DATA segnam(27).
READ TABLE dedidd WITH KEY segnam = 'ZPROSEG'.
IF sy-subrc NE 0.
LOOP AT dedidd WHERE segnam = 'E1EDP31'.
CLEAR dedidd.
dedidd-segnam = 'ZPROSEG'.
zproseg-matnr = 'Mat1'.
zproseg-lgort = '001'.
zproseg-gernr = 'SNo1'.
zproseg-labst = 2.
dedidd-sdata = zproseg.
APPEND dedidd.
ENDLOOP.
ENDIF.
Finally ran transaction WVM2 (Transfer of Stock & Sales Data) to generate IDOC, its creating IDOC but when checked IDOC in WE05 its getting Status Error "26".
Looking forward for your reply.
Many thanks in advance.

Hello,
Actually you are appending the Z segment instead of inserting into the correct position. So the segment is added at the last, so hierarchy of segments is collapsed.
So get the index of the previous segment E1EDP31 and increase the index by 1 and INSERT the Z segment with that new index as below.
LOOP AT dedidd WHERE segnam = 'E1EDP31'.
lv_index = sy-tabix. " <<--
ADD 1 TO lv_index. " <<--
CLEAR dedidd.
dedidd-segnam = 'ZPROSEG'.
zproseg-matnr = 'Mat1'.
zproseg-lgort = '001'.
zproseg-gernr = 'SNo1'.
zproseg-labst = 2.
dedidd-sdata = zproseg.
*APPEND dedidd.
INSERT dedidd INDEX lv_index. " <<---
ENDLOOP.
Here actually we are insering the record inside the LOOP and it regenerates the index again. It is not actually a good practice.
So the best practice is get the index and generate the segment inside the loop, store them into another internal table, come out the loop and insert the Z segments into DEDIDD by looping the new internal table.

Idoc Error - EDI: Syntax error in IDoc (segment cannot be identified)

Hi All,
have created a new reduced message type for our new vendor A/C group through BD53. Also done reqd config for sending the vendor master through this message type. .
I have created couple of vendors for testing with X01 with withholding tax functionality and when try to send these vendors , Idocs are getting failed .
When I create vendor without withholding tax functionality , idoc is getting posted succesfully . If create vendor with entries in the feild whih are related to withholding tax . Idocs are getting failed .
If I see the status in WE05 ,Idocs which are posted succefully are showing the basic type as CREMAS03 . For idocs which are getting failed have the basic type as CREMAS04 and also the extension as Z1CREMAS . I don`t understand why the system is defaulting CREMA04 & Z1CREMAS when I send the vendor master with withholding tax feild entries.
I am not much familiar with ALE /Idoc set up. Please can any body help me to resolve the issue.
The error message in we05 as below
EDI: Syntax error in IDoc (segment cannot be identified)
Message no. E0078
Diagnosis
The segment Z1LFA1M does not occur at the current level of the basic type CREMAS04 (extension Z1CREMAS).
This error can have several reasons:
The segment Z1LFA1M is assigned to a group whose header segment does not occur.
The segment Z1LFA1M does not exist in the syntax description of the basic type CREMAS04 (extension Z1CREMAS).
The sequence of segments in the group in which the segment appears is incorrect.
Previous errors ('mandatory' segment or group missing) may be due to this error.
Procedure
Please check the IDoc or the syntax description of the basic type CREMAS04 (extension Z1CREMAS).
Thanks

Hi,
I don`t understand what do you mean release after adding segment.
Message type works i.e. Idoc get posted if I send with the vendor w/o withholding tax field entries. Idoc fails when send vendor with withholding tax field entry.
Regards

EDI: Syntax error in IDoc (segment cannot be identified)

Hi All,
Im facing the below error EDI: Syntax error in IDoc (segment cannot be identified).
And this error is coming only for few idocs rest are getting processed successfully.
Message no. E0078
Diagnosis
The segment E1EDP03 does not occur at the current level of the basic type ORDERS05 (extension ).
This error can have several reasons:
The segment E1EDP03 is assigned to a group whose header segment does not occur.
The segment E1EDP03 does not exist in the syntax description of the basic type ORDERS05 (extension ).
The sequence of segments in the group in which the segment appears is incorrect.
Previous errors ('mandatory' segment or group missing) may be due to this error.
Procedure
Please check the IDoc or the syntax description of the basic type ORDERS05 (extension ).
Please suugest.
Thanks,
Spandana

Hi,
Is this standard program or custom program?
you might be appending the Z segment instead of inserting it. Always best practice is get the index of the segment and instert it.
If all the data is not populated then segment position will change incase of appending. Please check your code and revert back.
Refer the below link for detailed information.
IDOC Status 26: EDI: Syntax error in IDoc (segment cannot be identified).
Thank you

Regarding EDI: Syntax error in IDoc (segment cannot be identified)

Hi,
My requirement is that I was adding two diffrent field values under two diffrent segments as "E1EDKA1" and "E1EDK02" in outbound invoice IDOCS, INVOIC02 (process code: SD09 - IDOC_OUTPUT_INVOIC).
I am getting the IDOC number through Tcode "VF02". Can any body give me idea how to check that syntax error in debug mode.
Please find the following error details using TCODE "WE02".
*EDI: Syntax error in IDoc (segment cannot be identified)*
*Message no. E0 078*
*Diagnosis*
*The segment E1EDKA1 does not occur at the current level of the basic type INVOIC02 (extension ).*
*This error can have several reasons:*
*The segment E1EDKA1 is assigned to a group whose header segment does not occur.*
*The segment E1EDKA1 does not exist in the syntax description of the basic type INVOIC02 (extension ).*
*The sequence of segments in the group in which the segment appears is incorrect.*
*Previous errors ('mandatory' segment or group missing) may be due to this error.*
Please help me to resolve this problem. <REMOVED BY MODERATOR>
Regards,
Skumar.
Edited by: Alvaro Tejada Galindo on Apr 28, 2008 1:09 PM

It seems that you added segment E1EDKA1 at a place where it is not supposed to be. That's where this error is coming from. The structure of every IDOC is definded by SAP standard and you cannot change the sequence or the level of standard segments. If you require a certain field at a certain level you have to add that field to a Z-segment and then add that Z-segment where appropriate in your extension.
Hope that helps,
Michael

In App Purchase Error, ( Transaction Failed Cannot connect to iTunes Store)

O.k. on my iPhone when I'm in an app I tried to purchase something and it won't let me by saying, Transaction Failed, Cannot Connect to iTunes Store.. But I'm able to use the same app on my iPod touch and I can purchase what I needed.... So can somebody help me figure out what the reason is behind it? Both the iPhone and the Ipod has the same account information and both uses the same computer to connect to iTunes.... So why does one work and the other doesn't? Also its an iPhone 3Gs...

Although you may be using the same iTunes Account, things can get a little strange if you have different AppleID's for each device. On your device, check settings ==> Store. The AppleID for that device is listed there. It can be confusing because syncing to the same iTunes account is not the same as managing App and purchases through the iTunes Store Account.
On your iTunes window the uppe right corner shows which AppleStore ID is logged in. If it turns out they are different, simply log out of the store on iTunes, and log in with the other account. Download the updates. Log out and then back in to the other account.
As an alternative, download the updates on the device they were purchased. Sync to iTunes, and the updated download be transferred back to iTunes and available to the other devices syncing with iTunes.
Or....... if your iPhone is Airplane Mode, turn that Airplane mode off and ignore everything from above.

What does the error message 'valid source cannot be identified' when trying to download acrobat read

I get the message 'valid source cannot be identified' when trying to download adobe acrobat. what should I do?

If it's Adobe Reader, download the full installer from http://get.adobe.com/reader/enterprise/
If it's Adobe Acrobat, post in the Acrobat forum.
If you are still having troubles with Adobe Reader, please specify your operating system & version.

Agreement lookup failed as From trading partner cannot be identified

Hi,
I am working on custom document over HTTPS.
I configured B2B to send custom document over Generic Exchange(transport - HTTPS).
I enqueue the XML document with AQ header to IP_OUT_QUEUE. B2B is able to read the data from IP_OUT_QUEUE and invokes the client Webapplication.
I changed the IP_OUT_QUEUE to custom AQ. B2B is able to read data from custom AQ, but B2B throws "Trading partner agreement lookup failed as From trading partner cannot be identified"
b2b.log:
2010.02.15 at 13:03:44:470: Thread-19: B2B - (DEBUG) oracle.tip.adapter.b2b.data.MsgListener:run Thread start
2010.02.15 at 13:03:44:471: B2BStarter thread: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:initialize Exit
2010.02.15 at 13:03:44:497: Thread-22: B2B - (DEBUG)
Protocol = AQ
Version = null
Transport Header
aq.receiver.expiration:-1
aq.receiver.delay:0
aq.receiver.priority:1
aq.receiver.correlation:b2buser
2010.02.15 at 13:03:44:881: Thread-19: B2B - (DEBUG) oracle.tip.adapter.b2b.data.MsgListener:run initialize Enter
2010.02.15 at 13:03:44:907: Thread-19: B2B - (DEBUG) oracle.tip.adapter.b2b.data.MsgListener:run initialize B2BListen turned on, will listen on IP_OUT_QUEUE for messages
2010.02.15 at 13:03:44:921: Thread-19: B2B - (DEBUG) oracle.tip.adapter.b2b.data.MsgListener:run start listening on message
2010.02.15 at 13:03:45:069: Thread-22: B2B - (DEBUG) oracle.tip.adapter.b2b.transport.AppInterfaceListener:onMessage calling processOutgoingMessage
2010.02.15 at 13:03:45:069: Thread-22: B2B - (INFORMATION) oracle.tip.adapter.b2b.engine.Engine:processOutgoingMessage Enter
2010.02.15 at 13:03:45:070: Thread-22: B2B - (DEBUG) DBContext beginTransaction: Enter
2010.02.15 at 13:03:45:070: Thread-22: B2B - (DEBUG) DBContext beginTransaction: Transaction.begin()
2010.02.15 at 13:03:45:071: Thread-22: B2B - (DEBUG) DBContext beginTransaction: Leave
2010.02.15 at 13:03:45:076: Thread-22: B2B - (DEBUG) calling setFromPartyId() changing from null to TPName: null Type: null Value: null
2010.02.15 at 13:03:45:077: Thread-22: B2B - (DEBUG) calling setToPartyId() changing from null to TPName: null Type: null Value: null
2010.02.15 at 13:03:45:077: Thread-22: B2B - (DEBUG) calling setInitiatingPartyId() changing from null to TPName: null Type: null Value: null
2010.02.15 at 13:03:45:077: Thread-22: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processOutgoingMessage To TP Namenull
2010.02.15 at 13:03:45:078: Thread-22: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processOutgoingMessage From TP Namenull
2010.02.15 at 13:03:45:078: Thread-22: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processOutgoingMessage business action name: null
2010.02.15 at 13:03:45:079: Thread-22: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processOutgoingMessage doctype name: null
2010.02.15 at 13:03:45:079: Thread-22: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processOutgoingMessage doctype revision: null
2010.02.15 at 13:03:45:079: Thread-22: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processOutgoingMessage AppMsgIdnull
2010.02.15 at 13:03:45:094: Thread-22: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processOutgoingMessage ipmsg.get_MSG_TYPE = 1
2010.02.15 at 13:03:45:095: Thread-22: B2B - (DEBUG) calling setInitiatingPartyId() changing from TPName: null Type: null Value: null to TPName: null Type: null Value: null
2010.02.15 at 13:03:45:095: Thread-22: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processOutgoingMessage B2B Message ID is 0A4DBD67126D1BA2FC700000136A1AD0
2010.02.15 at 13:03:45:099: Thread-22: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processOutgoingMessage RefTo B2B Message ID is null
2010.02.15 at 13:03:45:100: Thread-22: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processOutgoingMessage isSignalMsg() == false; call outgoingTPA
2010.02.15 at 13:03:45:100: Thread-22: B2B - (DEBUG) oracle.tip.adapter.b2b.tpa.TPAProcessor:processOutgoingTPA() Begin TPA Processing..
2010.02.15 at 13:03:45:100: Thread-22: B2B - (DEBUG) oracle.tip.adapter.b2b.tpa.TPAProcessor:processTPA() PARTIES (before calling processParty) :
initial : null
from : TPName: null Type: null Value: null
to : TPName: null Type: null Value: null
final : null
initiating : TPName: null Type: null Value: null
2010.02.15 at 13:03:45:101: Thread-22: B2B - (DEBUG) oracle.tip.adapter.b2b.tpa.TPAProcessor:processTPA() direction is outgoing
2010.02.15 at 13:03:45:102: Thread-22: B2B - (DEBUG) oracle.tip.adapter.b2b.tpa.TPAProcessor:processTPA() calling processparty with : TPName: null Type: null Value: null
2010.02.15 at 13:03:45:102: Thread-22: B2B - (DEBUG) oracle.tip.adapter.b2b.tpa.RepoDataAccessor:processParty() Begin..
2010.02.15 at 13:03:45:112: Thread-22: B2B - (DEBUG) oracle.tip.adapter.b2b.tpa.TPAProcessor:processTPA() after calling processparty with : TPName: Acme Type: null Value: null
2010.02.15 at 13:03:45:112: Thread-22: B2B - (DEBUG) oracle.tip.adapter.b2b.tpa.TPAProcessor:processTPA() PARTIES (after calling processParty):
initial : null
from : TPName: Acme Type: null Value: null
to : TPName: null Type: null Value: null
final : null
initiating : TPName: Acme Type: null Value: null
2010.02.15 at 13:03:45:113: Thread-22: B2B - (DEBUG) oracle.tip.adapter.b2b.tpa.TPAProcessor:processTPA() docTypeName: null docTypeRevision: null
2010.02.15 at 13:03:45:118: Thread-22: B2B - (DEBUG) oracle.tip.adapter.b2b.tpa.TPAProcessor:processTPA() actionName: null actionRevision: null
2010.02.15 at 13:03:45:119: Thread-22: B2B - (DEBUG) oracle.tip.adapter.b2b.tpa.TPAProcessor:processTPA() Set actionRevision in MessageInfo: null
2010.02.15 at 13:03:45:119: Thread-22: B2B - (DEBUG) oracle.tip.adapter.b2b.tpa.TPAProcessor:processTPA() Obtain DocType using actionName and actionRevision.
2010.02.15 at 13:03:45:124: Thread-22: B2B - (DEBUG) oracle.tip.adapter.b2b.tpa.RepoDataAccessor:getCollaborationDetails() Begin.. Activity Name : null Activity Version: null
2010.02.15 at 13:03:45:125: Thread-22: B2B - (DEBUG) oracle.tip.adapter.b2b.tpa.TPAProcessor:processTPA() eventName:<null>
2010.02.15 at 13:03:45:125: Thread-22: B2B - (DEBUG) oracle.tip.adapter.b2b.tpa.TPAProcessor:processTPA() messageType:1
2010.02.15 at 13:03:45:126: Thread-22: B2B - (DEBUG) calling setInitiatingPartyId() changing from TPName: Acme Type: null Value: null to TPName: Acme Type: null Value: null
2010.02.15 at 13:03:45:127: Thread-22: B2B - (DEBUG) oracle.tip.adapter.b2b.tpa.TPAProcessor:processTPA() cpaID=null
2010.02.15 at 13:03:45:127: Thread-22: B2B - (DEBUG) oracle.tip.adapter.b2b.tpa.TPAProcessor:processTPA() TPA Name : null
2010.02.15 at 13:03:45:128: Thread-22: B2B - (DEBUG) oracle.tip.adapter.b2b.tpa.TPAProcessor:processTPA() TPA Name : null
2010.02.15 at 13:03:45:128: Thread-22: B2B - (DEBUG) oracle.tip.adapter.b2b.tpa.TPAIdentifier:identifyTPA() Begin..
2010.02.15 at 13:03:45:129: Thread-22: B2B - (DEBUG) oracle.tip.adapter.b2b.tpa.TPAIdentifier:identifyTPA()
From Party -> null-null-Acme-null To Party -> null-null-null-null Business Action name -> null
2010.02.15 at 13:03:45:130: Thread-22: B2B - (ERROR) Error -: AIP-50548: Trading partner agreement lookup failed as From trading partner cannot be identified
at oracle.tip.adapter.b2b.tpa.TPAIdentifier.identifyTPA(TPAIdentifier.java:230)
at oracle.tip.adapter.b2b.tpa.TPAProcessor.processTPA(TPAProcessor.java:598)
at oracle.tip.adapter.b2b.tpa.TPAProcessor.processOutgoingTPA(TPAProcessor.java:222)
at oracle.tip.adapter.b2b.engine.Engine.processOutgoingMessage(Engine.java:1074)
at oracle.tip.adapter.b2b.transport.AppInterfaceListener.onMessage(AppInterfaceListener.java:141)
at oracle.tip.transport.basic.aq.AQDequeuer.dequeue(AQDequeuer.java:348)
at oracle.tip.transport.basic.aq.AQDequeuer.run(AQDequeuer.java:211)
2010.02.15 at 13:03:45:131: Thread-22: B2B - (ERROR) Error -: AIP-50548: Trading partner agreement lookup failed as From trading partner cannot be identified
at oracle.tip.adapter.b2b.tpa.TPAIdentifier.identifyTPA(TPAIdentifier.java:230)
at oracle.tip.adapter.b2b.tpa.TPAProcessor.processTPA(TPAProcessor.java:598)
at oracle.tip.adapter.b2b.tpa.TPAProcessor.processOutgoingTPA(TPAProcessor.java:222)
at oracle.tip.adapter.b2b.engine.Engine.processOutgoingMessage(Engine.java:1074)
at oracle.tip.adapter.b2b.transport.AppInterfaceListener.onMessage(AppInterfaceListener.java:141)
at oracle.tip.transport.basic.aq.AQDequeuer.dequeue(AQDequeuer.java:348)
at oracle.tip.transport.basic.aq.AQDequeuer.run(AQDequeuer.java:211)
2010.02.15 at 13:03:45:131: Thread-22: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processOutgoingMessage B2BDomainException
2010.02.15 at 13:03:45:132: Thread-22: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:handleOutboundException Updating Error Message: Error -: AIP-50548: Trading partner agreement lookup failed as From trading partner cannot be identified
2010.02.15 at 13:03:45:132: Thread-22: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Enter
2010.02.15 at 13:03:45:209: Thread-22: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Wire message not found.
2010.02.15 at 13:03:45:211: Thread-22: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Creating new business message
2010.02.15 at 13:03:45:212: Thread-22: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:insertMsgTblRow Enter
2010.02.15 at 13:03:45:353: Thread-22: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:insertMsgTblRow toparty name null
2010.02.15 at 13:03:45:354: Thread-22: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:insertMsgTblRow toparty type and value nullnull
2010.02.15 at 13:03:45:367: Thread-22: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:insertMsgTblRow BusinessAction for the given name null null
2010.02.15 at 13:03:45:397: Thread-22: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Creating new b2berror object
2010.02.15 at 13:03:45:398: Thread-22: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Updating business message error information
2010.02.15 at 13:03:45:471: Thread-22: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Exit
2010.02.15 at 13:03:45:472: Thread-22: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:handleOutboundException Updating Native Event Tbl Row
2010.02.15 at 13:03:45:472: Thread-22: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:updateNativeEvtTblRow Enter
2010.02.15 at 13:03:45:476: Thread-22: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:
** DbAccess:updateNativeEvtTblRow:tip_wireMsg wiremsg not found
2010.02.15 at 13:03:45:477: Thread-22: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:handleOutboundException notifying App
2010.02.15 at 13:03:45:477: Thread-22: B2B - (DEBUG) Engine:notifyApp Enter
2010.02.15 at 13:03:45:485: Thread-22: 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>0A4DBD67126D1BA2FC700000136A1AD0</b2bMessageId>
<errorCode>AIP-50548</errorCode>
<errorText>Trading partner agreement lookup failed as From trading partner cannot be identified</errorText>
<errorDescription>
<![CDATA[Machine Info: (dgda21a)
Description: Make sure the trading partner has name, type, and value information
StackTrace:
Error -: AIP-50548: Trading partner agreement lookup failed as From trading partner cannot be identified
        at oracle.tip.adapter.b2b.tpa.TPAIdentifier.identifyTPA(TPAIdentifier.java:230)
        at oracle.tip.adapter.b2b.tpa.TPAProcessor.processTPA(TPAProcessor.java:598)
        at oracle.tip.adapter.b2b.tpa.TPAProcessor.processOutgoingTPA(TPAProcessor.java:222)
        at oracle.tip.adapter.b2b.engine.Engine.processOutgoingMessage(Engine.java:1074)
        at oracle.tip.adapter.b2b.transport.AppInterfaceListener.onMessage(AppInterfaceListener.java:141)
        at oracle.tip.transport.basic.aq.AQDequeuer.dequeue(AQDequeuer.java:348)
        at oracle.tip.transport.basic.aq.AQDequeuer.run(AQDequeuer.java:211)
]]>
</errorDescription>
<errorSeverity>2</errorSeverity>
</Exception>
2010.02.15 at 13:03:45:512: Thread-22: B2B - (DEBUG) Engine:notifyApp Exit
2010.02.15 at 13:03:45:513: Thread-22: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:handleOutboundException Updated the Error Message Successfully: Error -: AIP-50548: Trading partner agreement lookup failed as From trading partner cannot be identified
2010.02.15 at 13:03:45:513: Thread-22: B2B - (DEBUG) DBContext commit: Enter
2010.02.15 at 13:03:45:516: Thread-22: B2B - (DEBUG) DBContext commit: Transaction.commit()
2010.02.15 at 13:03:45:516: Thread-22: B2B - (DEBUG) DBContext commit: Leave
Kindly help me to resolve this issue.

hi Anuj,
I am enqueuing from BPEL process. I have set the AQ header.
<b2bMsgHeader><Header xmlns="http://xmlns.oracle.com/pcbpel/adapter/aq/publishB2BMessage/">
<QueueHeader/>
<PayloadHeader>
<MSG_ID xmlns="">2SY16SY_TEST_FEB15_07E01null2010021513270041</MSG_ID>
<INREPLYTO_MSG_ID xmlns=""/>
<FROM_PARTY xmlns="">Acme</FROM_PARTY>
<TO_PARTY xmlns="">GlobalChips</TO_PARTY>
<ACTION_NAME xmlns="">ProcessBusiness</ACTION_NAME>
<DOCTYPE_NAME xmlns="">DocType</DOCTYPE_NAME>
<DOCTYPE_REVISION xmlns="">1.0</DOCTYPE_REVISION>
<MSG_TYPE xmlns="">1</MSG_TYPE>
<PAYLOAD xmlns="">XML payload</PAYLOAD>
<ATTACHMENT xmlns=""/>
</PayloadHeader>
</Header>
</b2bMsgHeader>

EDI 810 transaction error: Cannot uniquely identify a trading partner

Similar Messages

Maybe you are looking for