Trading partner error

hi
can any body tell me the solution that in vendor balance report one of the property trading partner is missing of one particular vendor i saw the date of creation of vendor master in r/3 it was already been updated, then in bw side i checked the master data
i found an error i fixed it up but sitll it is dhowing hash can any body tell me that will this record will updated in the next load or before
thanks

Hi,
After making required changes to the master data in Bw side, did you run the attribute changerun program?
Try running the attribute change run program which may help you.
For running attribute change run, go to se37 and run the program "RSDDS_AGGREGATES_MAINTAIN".
give your infoobject as input and execute.
hope this helps,
Regards,
Sri...

Similar Messages

FB50: Trading Partner error

Hello Gurus-
In testing, when the user enters line items, 2 of which a trading partner was entered. We left the other 2 entries blank inb trading partner. When the transaction is posted, all 4 line items have a trading partner which is not what we wanted.
how do we fix that?

Hi,
   This is from the document type settings (OBA7).
   It is controlled by the flag Inter-company Postings.
   If this is not set:-
                                a) Trading partner will be copied from eg Customer / Vendor.
                                b) The same TP must be in all line items.
    If set:-
                         a) TP will not be copied from Customer / Vendor
                         b) The TP is permitted to be different in each line item.
In is advisable to use seperate Document types for when this flag is set.
Kind regards

Error validating TP...AIP-11052: Writing following objects: Trading Partner

Hi,
I am getting following error validating trading partner. I have double checked the TP setup, everything looks fine. I had earlier successfully validated, later added a document type and trying to re-validate.
AIP-11052: Writing following objects: Trading Partner failed due to following constraint violation: PARTY. CAN NOT UPDATE UNVERSIONABLE OBJECT IN A VALIDATED CONFIGURATION
Does anyone have any clues??
Thanks
Venkat

Make sure you do not have active configuration which is using this agreement.

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

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!

Unable to clear customer due to error: u201CPlease enter valid trading partner:

Hi team
i am getting this error in clearing in customer invoice
i checked out in customer master trading partner no is there :*****
and that customer is also a Vendor but in vendor master record that trading partner no is not there
but customer number is there
i need to clear against a incoming payment AB doc type with some billing document
its a bank charges i need to pay ...
i am useing transaction code f-32
if you need any inputs please do let me know
Moderator message -personal information removed
Edited by: Rob Burbank on Sep 9, 2011 9:14 AM

Hi,
seems like you have to reverse the document without trading partner and re-post with Trading partner. Then it should work. If this is automatic postings and more often to happen in future think about pre-setting it in GL accoutn if possible or validations/ substiutions.
Regards
Hein

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.

B2B SelfService Error creating Trading Partner .zip import file using ant

SOA 11g 11.1.1.5 B2B - We are trying to create an import file for out trading partners into SOA B2B 11g but are getting errors when we run the ant script to build the import zip file.
We ran the ant-b2b-util to get the b2bselfservice.xsd file, loaded that into jDev to show the selfservice.xml structure.
We have built a trading partner xml file and at this point have stripped it down to one TP just to see if we could get it to work and we keep getting the same error messages.
From the $SOA_ORACLE_HOME/bin directory (where we have placed our TP xml file: TPD_NA.xml) here is the command and results from running the ant script:
[oracle@nalinoap05 bin]$ ant -f ant-b2b-util.xml b2bselfservice -Dinput=$ORACLE_HOME/bin/TPD_NA.xml -Doutput=$ORACLE_HOME/bin/TP_Docs.zip
Buildfile: ant-b2b-util.xml
b2bselfservice:
weblogic_dependencies:
[echo]
[echo] Weblogic server location: /oracle/SOAWDEV/11.1.1.5/Oracle/Middleware/wlserver_10.3
[echo] JNDI properties folder location: /oracle/SOAWDEV/11.1.1.5/Oracle/Middleware/Oracle_SOAWDEV/bin
[echo]
verifyargs:
utility:
[echo]
[echo] java.naming.provider.url=${java.naming.provider.url}
[echo] java.naming.factory.initial=${java.naming.factory.initial}
[echo] java.naming.security.principal=${java.naming.security.principal}
[echo] java.naming.security.credentials=*****
[echo]
[echo]
[echo] args=selfservice
[echo]
[java] Commandline arguments 1: [selfservice]
[java] 2012.04.10 at 13:27:35:559: main: (INFO) Input file location(s) :[oracle/SOAWDEV/11.1.1.5/Oracle/Middleware/Oracle_SOAWDEV/bin/TPD_NA.xml]
[java] 2012.04.10 at 13:27:35:559: main: (INFO) Output file location :/oracle/SOAWDEV/11.1.1.5/Oracle/Middleware/Oracle_SOAWDEV/bin/TP_Docs.zip
[java] 2012.04.10 at 13:27:35:596: main: (INFO) TradingPartner created :/soa/b2b/tp_id1AC191488133.xml
[java] 2012.04.10 at 13:27:35:600: main: (SEVERE) TPD_NA.xml: Combination of Documentprotocol=EDI_X12 docVersion=4010VICS docType=852 docDef=852Def not found in doc_*.xml file
[java] 2012.04.10 at 13:27:35:600: main: (SEVERE) TPD_NA.xml: Combination of Documentprotocol=EDI_X12 docVersion=4010 docType=997 docDef=997Def not found in doc_*.xml file
[java] 2012.04.10 at 13:27:35:600: main: (SEVERE) TPD_NA.xml: Combination of Documentprotocol=EDI_X12 docVersion=5010 docType=850 docDef=850Def not found in doc_*.xml file
[java] 2012.04.10 at 13:27:35:601: main: (SEVERE) TPD_NA.xml: Combination of Documentprotocol=EDI_X12 docVersion=5010 docType=860 docDef=860Def not found in doc_*.xml file
[java] 2012.04.10 at 13:27:35:601: main: (SEVERE) TPD_NA.xml: Combination of Documentprotocol=EDI_X12 docVersion=4010VICS docType=864 docDef=864Def not found in doc_*.xml file
[java] 2012.04.10 at 13:27:35:601: main: (SEVERE) TPD_NA.xml: Combination of Documentprotocol=EDI_X12 docVersion=5010 docType=864 docDef=864Def not found in doc_*.xml file
[java] 2012.04.10 at 13:27:35:601: main: (SEVERE) TPD_NA.xml: Combination of Documentprotocol=EDI_X12 docVersion=5010 docType=997 docDef=997Def not found in doc_*.xml file
[java] 2012.04.10 at 13:27:35:602: main: (SEVERE) TPD_NA.xml: Combination of Documentprotocol=EDI_X12 docVersion=5010 docType=856 docDef=856Def not found in doc_*.xml file
[java] 2012.04.10 at 13:27:35:602: main: (SEVERE) TPD_NA.xml: Combination of Documentprotocol=EDI_X12 docVersion=5010 docType=810 docDef=810Def not found in doc_*.xml file
[java] 2012.04.10 at 13:27:35:691: main: (SEVERE) TPD_NA.xml: Error in Validation:
[java] [org.xml.sax.SAXParseException: XML-24536: (Error) Missing Attribute 'documentDefinitionRef',
               org.xml.sax.SAXParseException: XML-24536: (Error) Missing Attribute 'documentDefinitionRef',
               org.xml.sax.SAXParseException: XML-24536: (Error) Missing Attribute 'documentDefinitionRef',
               org.xml.sax.SAXParseException: XML-24536: (Error) Missing Attribute 'documentDefinitionRef',
               org.xml.sax.SAXParseException: XML-24536: (Error) Missing Attribute 'documentDefinitionRef',
               org.xml.sax.SAXParseException: XML-24536: (Error) Missing Attribute 'documentDefinitionRef',
               org.xml.sax.SAXParseException: XML-24536: (Error) Missing Attribute 'documentDefinitionRef',
               org.xml.sax.SAXParseException: XML-24536: (Error) Missing Attribute 'documentDefinitionRef',
               org.xml.sax.SAXParseException: XML-24536: (Error) Missing Attribute 'documentDefinitionRef']
[java] Java Result: 255
BUILD SUCCESSFUL
Total time: 1 second
Here is the contents of TPD_NA.xml:
<?xml version="1.0" encoding="UTF-8"?>
<SelfService xmlns="http://xmlns.oracle.com/integration/b2b/selfservice/profile">
<TradingPartners>
<TradingPartner hosted="false" name="OvvvvvvvX" >
<Identification name="EDI Interchange ID" value="18xxxxxxxxxX" />
<Identification name="EDI Interchange ID Qualifier" value="14" />
<Identification name="DUNS" value="18xxxxxxxxxX" />
<Identification name="Generic Identifier" value="18xxxxxxxxxX" />
<Identification name="AS2 Identifier" value="18xxxxxxxxxX" />
<SupportedDocumentDefinition initiator="true" docTypeName="852" docProtocolVersion="4010VICS" docProtocolName="EDI_X12" docDefName="852Def" />
<SupportedDocumentDefinition initiator="true" docTypeName="997" docProtocolVersion="4010" docProtocolName="EDI_X12" docDefName="997Def" />
<SupportedDocumentDefinition initiator="true" docTypeName="850" docProtocolVersion="5010" docProtocolName="EDI_X12" docDefName="850Def" />
<SupportedDocumentDefinition initiator="true" docTypeName="860" docProtocolVersion="5010" docProtocolName="EDI_X12" docDefName="860Def" />
<SupportedDocumentDefinition initiator="true" docTypeName="864" docProtocolVersion="4010VICS" docProtocolName="EDI_X12" docDefName="864Def" />
<SupportedDocumentDefinition initiator="true" docTypeName="864" docProtocolVersion="5010" docProtocolName="EDI_X12" docDefName="864Def" />
<SupportedDocumentDefinition initiator="true" docTypeName="997" docProtocolVersion="5010" docProtocolName="EDI_X12" docDefName="997Def" />
<SupportedDocumentDefinition initiator="false" docTypeName="856" docProtocolVersion="5010" docProtocolName="EDI_X12" docDefName="856Def" />
<SupportedDocumentDefinition initiator="false" docTypeName="810" docProtocolVersion="5010" docProtocolName="EDI_X12" docDefName="810Def" />
</TradingPartner>
</TradingPartners>
</SelfService>
We have exported our metadata and looked at the doc_EDI_X12.xml file and ALL of these referenced documents exist in that file and can be seen by going to Administration --> Document and under the Document Protocols navigation --> EDI_X12 --> 5010 --> 810 --> 810Def (as an example).
If we strip out all of the SupportedDocumentDefiinition lines then the ant script will build an import file with just the trading partners and Identifications.
What are we doing incorrectly or what is not working properly to get the ant script to build the import zip file??
Thanks for any assistance,
Ken

Does that mean we have to create all of the document type definitions in the selfservice file?
We have created (installed) all of the document types by installing them from the B2B Administration --> Document page.
The definitions in the Trading Partner xml file exactly match the definitions of the installed documents.
In the selfservice.xsd the <element> SelfService shows the profile:DocumentProtocols as minOccurs as 0 :
     <element name="SelfService">
          <complexType>
               <sequence>
                    <element minOccurs="0" maxOccurs="1"
                         ref="profile:DocumentProtocols" />
                    <element minOccurs="0" maxOccurs="1"
                         ref="profile:TradingPartners" />
                    <element minOccurs="0" maxOccurs="1"
                         ref="profile:Agreements" />
               </sequence>
               <attribute name="version" type="profile:non-empty-string"
                    use="optional" />
          </complexType>
     </element>
so we thought that since the documents had already been defined (created/installed) to B2B they would not have to be redefined in the selfservice xml.
If we have to define all of the document types in the selfservice xml file that we are using for the trading partners what are the minimum values that we need to include?
Could we use minimal definitions such as this:
<DocumentProtocols>
<DocumentProtocol name="EDI_X12">
<DocumentProtocolVersion name="4010">
<DocumentType name="850">
<DocumentDefinition name="850def" />
</DocumentType>
<DocumentType name="997">
<DocumentDefinition name="997def" />
</DocumentType>
</DocumentProtocolVersion>
</DocumentProtocol>
</DocumentProtocols>
before the <TradingPartners> section of the seflxervice xml file?
Thanks for your assistance!

"Invalid Trading Partner Setup" Error for Invoice Inbound Propagation.

Hi,
I am trying to post xml data into the invoice interface tables through the link <http://<<server name>>:port/servlets/oracle.apps.ecx.oxta.ECXOTAInbound>.I have created an xml with repect to the transaction map. But when I post this xml i get an error in ecx error tables: ECX_INVALID_TP_SETUP. Though the trading partner setup is correct. I am unable to proceed further.
Please provide your inputs, if anyone has worked on the similar scenario.
thanks,
Danish

Please check the validation in GGB0.
The document which you are trying to post is not matching as per the validation.

IDOC Error - Trading Partner Required

Hello Expert,
I am trying to post a document through an idoc, but getting an error "Trading Partner required".
Where i have to update these details?
Thanks,
Satya

Hi Ashish,
The IDOC type is a customized one...
Then where i can check this field, can you give me some light on this?
In which segment it will be ?
Thanks,
Satya

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

Communicating message processing errors to trading partner

Hi,
We have configured B2B to receive OAG inbound messages.
How can we communicate inbound message processing errors to the remote trading partner?
I found that we can use oag CONFIRM_BOD_004 message for that? How do we that? Do we need to create a separate agreement with the trading partner for the confirm_bod or is there any way to bind it to existing agreement?
Is CONFIRM_BOD_004 the only way of informing the trading partner or there are some other ways of doing it?
Thanks in Advance.
Anil

Hi Anil,
Oracle B2B can send two kind of acknowledgements to partner to intimate whether received message processed successfully -
1. Exchange level ack - This is supported with specific exchange protocols (AS2, ebMS, RNIF etc.) only. Generic exchange does not have this capability. To understand, how it behaves in case of inbound error, please refer section "D.5 Inbound Exception Handling Scenarios" at-
http://download.oracle.com/docs/cd/E17904_01/integration.1111/e10229/app_except.htm#BCEIEEFF
2. Functional Ack - This is supported as part of document protocol's specification. For e.g. 997 in EDI X12, CONTRL in EDIFACT and CBOD (Confirm BOD) in OAG. Oracle B2B can handle Functional ACK automatically but you have to create a document definition for the same and deploy the respective agreement. Remember, Functional Ack is generally used to communicate to partner whether received message passed the business validation.
You may refer below blog to understand difference between functional ack and exchange ack -
http://www.b2bgurus.com/2009/02/document-vs-exchange-level.html
Remember that this blog is intended for 10g so please ignore any settings defined there.
You may define at an agreement level whether FA is required and if yes then whether Oracle B2B will handle it or middleware will send it to B2B to pass it to TP. You may refer section "Step 4: Select validation, translation, and functional acknowledgment options" at -
http://download.oracle.com/docs/cd/E17904_01/integration.1111/e10229/bb_agree_flow.htm#CEGDGCAH
Regards,
Anuj

Error msg . while creating a GR w.r.t. PO --"ENTER A VALID TRADING PARTNER"

Hi ,
While creating a GR w.r.t. Purchase Order (MB01) getting a following msg:
"ENTER A VALID TRADING PARTNER "
In Vendor Master : Partner function has the vendor details
OA     Ordering Address
VN     Vendor
PI     Invoice presented by
Any thread would be helpful .
regards,
chait

Hi ,
THere is no entry in field :Trading partner LFA1 -
VBUND
ALso the vendor has acccount group : RMIT : Remit to Address
PArtner functions are maintained in vendor master viz. OA ,VN , PI .
regards,
chait

ACC GL Posting idoc requires trading partner

Hello all,
I have created a new interface, which posts an ACC_GL_POSTING Idoc to SAP.
However this idoc runs into error as follows:
CLIA: Line item 000 - G/L account 5590041 has to be posted with trading partner.
I know which trading partner this account has to be posted with. However this partner is used for multiple company codes.
The document type is ZA. When I look in OBA7 the "Inter-company postings" checkbox is not ticked. The "Enter trading partner" checkbox is ticked.
Do you have any tips for me? Are there some specific settings I should check? What options do I have to get this Idoc processed succesfully automatically? Any help would be greatly appreciated.
- Mike

Hello Gaurav,
Thanks for your fast response.
I haven't defaulted the trading partner as the trading partner can vary for the same GL Account.
I am trying to get GL Postings processed using the ACC_GL_POSTING idoc type. However I was wondering whether there is a way to avoid entering the trading partner manually. Or how it is possible to enter the trading partner manually when trying to use idoc processing.
- Mike

Account 12221001 requires trading partner to be filled

Hi
The user had some old documents and he is trying to clear them.
During clearing he is facing an error "Account 12221001 requires trading partner to be filled"
Trading partner field is blank in the reconciliation account 12221001 and also customer account.
BSEG of the document which gives the problem. The reconciliation account is 12221001, the trading partner for the customer line is not filled in.
How can we fill the trading partner on this line item?
Thanks in Advance,
Deepthi.

hi,
trading partner field is populated from account , customer or vendor.
if your customer wants to clear old documents, most probably, some documents are filled with trading partner field and others are not.
in this situation you cannot clear these documents.
i have faced the same iproblem. to solve it, you should determine the balance of trading partner included documents,
you should post two documents using a dummy document.
lets say the balance is 20.000 usd
you should post: (initially you should maintain trading partner field in customer data)
DR/CR customer.........20.000usd
CR/DR dummy acc. ..........20.000 usd
second posting ( you should clear the trading partner field in customer data)
CR/DR custoemr......20.0000usd
DR/CR dummy acc.....20.000 usd
now you can clear items with trading partner is filled.

Trading partner error

Similar Messages

Maybe you are looking for