Importing Trading Partner Profiles

Greetings,
Is there an XSD that captures our notion of Trading Partner Profile? If so, is there a back door way of importing XMLs of that type into an Oracle Integration B2B (I suspect there's no way of doing that from the console)?
To elaborate, IHAC who is trying to migrate from an existing B2B deployment to Oracle Integration. In the process, we will need to recreate the tons of TP profiles they've already configured in Oracle B2B. The good news is that those existing TP profiles TPs can be exported into an XML format. If we support that format ourselves, that I was thinking of running their XMLs' through an XSLT to align it with our format, and then importing those XMLs automatically.
On a related note, I'd be interested to know if we understand ebXML CPPs and CPPAs, because in general, that would be a good way of importing TP profiles and agreements, regardless of their origin.
Regards,
Karthick

Hello Karthik,
We have the notion of Self Service API which can be used to create Trading partner and Agreement in Bulk. Please refer
http://rameshnittursblog.blogspot.com/2007/09/creating-b2b-metadata-using-self.html
Please send a test mail to [email protected] for self service API samples.
Rgds,Ramesh

Similar Messages

Get trading partner profile identifiers

Hi,
Can you advise which function/expression in BPEL Process Manager that can be call to get the B2B trading partner profile identifiers? Because I have a use case where by I'm evaluating trading partner to perform specific logic.
For example, I want to get the value of the identifier type "Name", the expected value would be "Acme".
Regards,
Scott.

Hi Anuj,
Your example is correct if the message receive from B2B partner link.
However, my scenario is the reverse. I am receiving the message from a File Adapter partner link, then I need to fetch properties in trading partner profile for decision logic.
Essentially, I'm looking for APIs that are used in the Oracle B2B partners tab. I want to call these APIs from BPEL to get trading partner profile details.
Regards,
Scott.

Reg: Importing Trading partner details

This is wrt importing trading partner details thro' Demand Management System Administrator > Collection > Legacy Systems >Legacy Collection - Flat File.
I just got this input from the bug id 6871484. Could anyone help me with the following details?
I want to know the exact functionality of this option.
And if at all it allows me to import the TP details, let me know the format of the file or some sample.
What should be ideal values for the parameters against ...
Flat File Loader
and against
Pre-Process Monitor.

I was able to get the details as shown in below code...
CalloutMessage cmIn = (CalloutMessage) input.get(0);
String fromParty = cmIn.getParameter("FROM_PARTY");
String toParty = cmIn.getParameter("TO_PARTY");
String documentType = cmIn.getParameter("DOCUMENT_NAME");
String action = cmIn.getParameter("ACTION_NAME");

Migrating Trading Partner from test to Production environment

Hi,
My Production environment has configuration for two trading partner.
I need to migrate one more trading partner from test environment to (the existing) production environment.
I see Agreement level export, TP level export, Config level export options in Oracle B2B.
Can you please suggests as to which is the fastest and most accurate way to migrate new trading partner configuration?
Regards,
Ravi Shah

There is nothing as preferred option. However you can keep few things in mind.
1. Agreement Export - Preferred option , if you would like to export only specific Trading Partner and Agreement details.
2. Repository Export - For full repository export.
3. Trading Partner Export - This option do not keep any TP in mind while taking the export, hence you may not information about Delivery channel and Agreement. This provides information about Trading partner profiles and Supported Document defition of the trading partner.
Let me know.

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!

Trading Partner Import

Does anybody has dealt with Trading Partner conversion from Legacy systems?
I want to know what are the Pros and cons of the process.

Hi,
In Case of 10g using oracle wallet manager import trusted trading partner certificate.
In case of AS11G use the below command to import the trading partner certificate into jks,
keytool -importcert -file -keypass
Please also look into the below link for more details,
http://blogs.oracle.com/oracleb2bgurus/2009/08/certificate_management_in_11g.html
Regards
Nandagopal

Import certificate from trading partner

Hi
I got a certificate from my trading partner. (Communication is AS2)
Now I have to import it to my B2B and use it while communicating with him
Can someone tell me how to import this so that I can select the certificate in the Security tab?
Thanks
Vijay Sai.S

Hi,
In Case of 10g using oracle wallet manager import trusted trading partner certificate.
In case of AS11G use the below command to import the trading partner certificate into jks,
keytool -importcert -file -keypass
Please also look into the below link for more details,
http://blogs.oracle.com/oracleb2bgurus/2009/08/certificate_management_in_11g.html
Regards
Nandagopal

Partner Profile Transport/Import

hi everyone,
Is there a way to transport a single partner profile from production server to development server? If not, what are the easiest possible way to duplicate a Partner profile?
regards,
jay

Hi Jay,
For your first question: I think you cant transport a partner profile. You have to create it on every system.
Coming to your second question i think to move a vendor from one system to another you will need to have a custom program doing it, very similar to a data load programs. May be if the ALE setup is enabled then you can push it using std ALE programs or tcodes starting with BD*
I think for Vendor it is BD14. You can use this tocde and create a Vendor from production to test. You will need to have the underlying ALE setup in place.
I dont think there is other easy ways to create a vendor from production without custom development.
Hope this helps.
Cheers
VJ

EDI partner profile copying

I need to set up hundreds of trading partners for orders, deliverys, ship confirm, etc.
Has anyone used the function modules in the EDI6 group to do this automatically. I'd like to supply a list of customer numbers and have the WE20 partner profiles all come out the same.
There are two function modules: EDI_PARTNER_COPY_COMPLETE and EDI_AGREE_PARTNER_INSERT that look promising. But, I wanted to check with other forum users for recommendations.

Hi,
When we are sending the Idoc from XI / PI system, it is taking the partner number from Partner Profile used for sending the same from XI / PI System.
We are configuring the same into tcode IDX1, please check the same.
The same partner profile is used in your port number in IDX2, where you have imported the idoc matadata.
Sandeep

Logical system and partner profile configuration

Hi,
I have a SQL server which is defined as a Business system in my landscape. It is sending records to ECC 6.0 which makes it a JDBC to IDOC scenario (inbound IDocs)
First question is do I have to mention a logical system name for the SQL server Business system too ?
Second question is do I create a Logical system in the ECC system (BD54/SALE) for the SQL system or would it be for the client of the ECC system itslef?
Third question is do I maintain partner profile configurations in WE20 for the SQL business system or for the ECC business system?
Thanks in advance.
Cheers,
S

Hi Sam,
> First question is do I have to mention a logical system name for the SQL server Business system too ?
Yes, In SLD You have to specify logical system name of the SQL server business system while creating SQL system.After importing business system into Integration directory,in Adepter-Specific Identifiers you can see logical system name of SQL server business sytem which you defined in SLD.
> Second question is do I create a Logical system in the ECC system (BD54/SALE) for the SQL system or would it be for the client of the ECC system itslef?
Yes,You have to create Logical system in ECC system for SQL system(Logical system name must be with the same name as logical system name you have given in XI SLD in previous question)
> Third question is do I maintain partner profile configurations in WE20 for the SQL business system or for the ECC business system?
In WE20 You have to maintain partner profiles for SQL server Logical system
For example: If SQL server Business system name is SQLDEVBS and logical system name is SQLDEVLS
In ECC you have to create logical system as SQLDEVLS and
Partner profiles for SQLDEVLS in WE20.
Please let me know if you have any issues.
Cheers,
JAG

Getting EDI:Partner profile not available.

Hi,
I am a newbie to SAP XI. As I am doing File to IDOC scenario, I am getting error - EDI:Partner profile not available.
My Scenario details:
1. Created RFC Destination, RFC port, logical System and Partner profile in both Sender (XI) as well as Receiver(SAP R/3) systems.
2. Created SWCV, Technical sys, Business Systems in SLD. I used the Logical system created (for SAP R/3) on XI system in my business system.
3. Created Data type, Message type, Message interface, Message Mapping and Interface mapping in Integration Repository and activated them.
4. Imported IDOC from SAP r/3 system during Namespace creation and used it for mapping.
5. used Integration Directory wizard to create Communication channels, Sender & Receiver agreements, Receiver Determination, Interface Determination.
6. Creaed a new business service for sender and added "Adapter Specific Identifier with Logical system created (for SAP R/3) on SAP XI.
7. Activated all Standard Change list items.
The file for the above Scenario has been picked up amd i am getting "Chequered Flag" on both ends in "SXMB_MONI" monitor. When i change over to SAP R/3 to check idocs created (i.e., T.code - we05) my scenario idoc status is 56 and it says.. Status; Idoc with errors added.
I have gone through many of the forum suggestions and blogs regarding this issue, but still not able to resolve my problem.
can somebody suggest me solution please.
Thanks,
Vijay.

Hi,
6. Creaed a new business service for sender and added "Adapter Specific Identifier with Logical system created (for SAP R/3) on SAP XI.
>>>Check this for Reciever Business System.. not for Sender system..
BTW, if you get chequered flag in XI, then idoc data is sent from XI. Can you check all the data from XI is populated in the idoc structure in SAP R/3 in we05...by clicking each segment.. if so, then there is no problem from XI..
check WE20 ..partner profile configuration in R/3 also check inbound parameters are given
Regards,
Moorthy

IDoc Receiver, Error in we02 - EDI: Partner profile inbound not available

Hi All,
I have a problem when creating a receiver IDoc from XI to R/3.
I have successfully tested the IDoc when populating the receiver information from the payload. However I want this information to be populated automatically based on the logical systems.
When I do this I get the following error in the IDoc in R/3:
EDI: Partner profile inbound not available
In the control record the sender information is all correct but in the recipient information the partner Number with type LS is populated, but port is not populated.
I have done the following steps.
 the sender is a Business Service so I have created a logical system directly adapter-specific identifiers in the sender service in the integration directory.
 In the receiver business system I have imported the logical system into the adapter-specific identifiers in the ID from that specified in the SLD.
 In the receiving R/3 system using SALE/BD54 I have created a logical system for the source system.
 In the receiving R/3 system using we20 I have created a partner profile of type LS with the same name as the source logical system.
 IN PI/XI system in transaction IDX1 Ive created a port (SAP<SID> where <SID> is the system ID of the receiving R/3 system) and the client of the R/3 system, and the RFC destination of that system (<SID>CLNT<clnt>, as specified in SM59).
 In the IDOC Adapter (receiver) I have entered the RFC destination and port matching those created above. All checkboxes are UN-checked eg. take sender from payload, take receiver from payload, Apply control record values from payload, etc. are all NOT checked.
I think that Ive done everything correctly, but I get the error in we02 in R/3: EDI: Partner profile inbound not available.
Any help will be greatly appreciated (and rewarded, obviously).
Thanks,
Matt.

HI Matt,
Can you please copy paste the exact error message....In your error message it will show you Exact partner Number / Logical System name and other parameters...just compared if you have all parameters set in your partner profile comparing to error message...
If you can giev screen shot of both..then probably would be easy to point out error.
Hope this will help.
Nilesh

How to update trading partner (BSEG-VBUND) in tr.code FB01/FB02?

Hi,
I need, under some circumstances, to update value of trading partner code (field BSEG-VBUND) to all items in the FI document, created/changed with transaction FB01/FB02.
I checked available user exits and bussiness events, but didn't found one, which could do the trick.
In fact, in bussiness transaction event #00001430 (CHANGE DOCUMENT: Field substitution header/line - Checks prior to posting change completed) - for FB02 I have access to the internal table T_BSEG, but it seems this table is used as import parameter only and any changes didn't take efect at the end.
Any help how can I do the trick? And this is while I'm in a transaction FB01/FB02.
My system is 4.6c.
Many thanks in advance.
Regards,
Ivaylo Mutafchiev

Svetlin, Max,
what I did until now is:
1) followed matrix substitution = callup point 3 (complete document) - I checked for existance of correct substitution field(s) in the GB01 table, and re-generated substitution code (as noticed in note 42615). That added my field in the list of fields for substtitution which are considered at the end of substtitution - in forms:
FORM EXP_REC_015
        USING
          DATA_CHANGED TYPE GB002_015
        CHANGING
          DATA_OUT TYPE GB002_015.
and
FORM EXP_TAB_015_BSEG
         USING
           IN_ORIG STRUCTURE        BSEG
        CHANGING
           OUT_RESULT STRUCTURE     BSEG
           B_RESULT.
both forms are in main generated program GBTAAFI0.
My field (VBUND) is taken in account - added to the structure:
DATA: BEGIN OF TEMP_STRUCT,
        VBUND                          LIKE   BSEG-VBUND
        ZFBDT                          LIKE   BSEG-ZFBDT
        END OF TEMP_STRUCT.
here ZFBDT was the other field defined in GB01 for substitution from someone esle - perhaps by default, I don't know.
Further (in the include MF05LFB0),
almost all of the structures which contain my changes are cleared (below is extract from the code):
LOOP AT beltab WHERE xarch NE char_x.                   "Note 0383125
REFRESH xbseg.
REFRESH ybseg.
REFRESH xbsec.
REFRESH ybsec.
REFRESH xbsed.
REFRESH ybsed.
REFRESH xbset.
REFRESH ybset.
REFRESH t_bsegco.
REFRESH t_fmfich.
Further, the logic proceed with the program SAPFF011 and form 'import_*beleg', where my changes were overwritten with original data - before substitution.
2) Tried Max's proposal - and extended structure BSEG_SUBST with field VBUND, further populated the substitution table in the related BTE 1430 accordingly.
Unfortunately the flow-logic proceeded further to the same form 'import_*beleg' in the program SAPFF011 and my changes dissapeared.
I'm at dead-end - have no idea where and what is the problem...
Checked few OSS notes - 42615, 386896, 513891, 391309, 438076. Everything which is related to my exact situation is set correctly - as far as I found :-).
Just for tests I tried both ways (BTE and matrix substitution) with another field ==> BSEG-XREF3, and it was updated correctly - accorging to my logic.
Thanks guys, your suggestions were right at the time and valuable, but they didn't help me to solve my problem. Perhaps there is something messed in our system - I can't be sure. What I can say for sure is that we have working BTE-s (1430 is used in our system - I just added piece of code into it), and validations are working also.
Thanks again.
Regards,
Ivaylo
P.S. If you have any suggestions, I'll be glad to hear them from you.

ABAON - trading partner

HI ALL
while posting in ABAON is what is the importance of giving the field "trading partner" under the tab additional details.
if i select trading partner it's throwing some error.
if i dont select trading partner it's working fine.
please let me know what is the impact if i dont select trading partner
useful answers will be rewarded with points
regards
prasad

HI
thans for your response
what happens if i dont select trading partner?
and i am getting the below error:
T.code AO90
when i am trying to assing GL account under account determination balance sheet accounts it's throwing the following error:
Gl xxxxxxxxxx is not a balance sheet account
GL xxxxxxxxxx not allowed to be PL account
(in master data of the GL shall i make it to Balance sheet,
what about the second error "not a PL account")
how to rectify this error
regards
prasad

Trading partner agreement not found for the given input values

Hi,
I am working on EDI X12 over generic exchange outbound.
In enqueue script:
replyToMsgID =
from =TEE
to =RF
actionName =BASFEDI841
doctypeName =841
doctypeRevision =4010
msgType =1
payload =RF_841_4010_1_12.xml
attachment=
I am getting the Trading partner agreement not found.
B2B log:
***** REQUEST MESSAGE *****
Exchange Protocol: Generic Version 1.0
Transport Protocol: FTP
Unique Message ID: TEE_2009Mar01_15_37_29_170.dat
Trading Partner: RF
Message Signed: No
Payload encrypted: No
Information incomplete
2009.03.01 at 15:37:29:477: Thread-20: B2B - (INFORMATION) oracle.tip.adapter.b2b.engine.Engine:processOutgoingMessage Exit
2009.03.01 at 15:37:29:477: Thread-20: B2B - (DEBUG) DBContext commit: Enter
2009.03.01 at 15:37:29:477: Thread-20: B2B - (DEBUG) DBContext commit: Leave
2009.03.01 at 15:37:29:478: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.data.MsgListener:onMessage Exit
2009.03.01 at 15:37:32:910: Thread-21: B2B - (DEBUG)
Protocol = FTP
Version = 1.0
Transport Header
filename:TEE_2009Mar01_15_37_29_170.dat
filesize:7787
file_ext:dat
fullpath://users/dab2b01/RF841/TEE_2009Mar01_15_37_29_170.dat
timestamp:1970-01-01T00:00:00.000-00:00
2009.03.01 at 15:37:32:973: Thread-21: B2B - (DEBUG) DBContext beginTransaction: Enter
2009.03.01 at 15:37:32:974: Thread-21: B2B - (DEBUG) DBContext beginTransaction: Transaction.begin()
2009.03.01 at 15:37:32:974: Thread-21: B2B - (DEBUG) DBContext beginTransaction: Leave
2009.03.01 at 15:37:32:974: Thread-21: B2B - (DEBUG) InterfaceListener:onMessage - Invoke inbound callout - null - null
2009.03.01 at 15:37:32:975: Thread-21: B2B - (DEBUG) InterfaceListenersyncAckEBMSchecking header names
2009.03.01 at 15:37:32:975: Thread-21: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:insertNativeEvtTblRow(2 params) Enter
2009.03.01 at 15:37:32:998: Thread-21: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:insertNativeEvtTblRow(2 params) Exit
2009.03.01 at 15:37:32:999: Thread-21: B2B - (DEBUG) oracle.tip.adapter.b2b.transport.InterfaceListener:onMessage sendEventtrue
2009.03.01 at 15:37:33:005: Thread-21: B2B - (DEBUG) DBContext commit: Enter
2009.03.01 at 15:37:33:011: Thread-21: B2B - (DEBUG) DBContext commit: Transaction.commit()
2009.03.01 at 15:37:33:011: Thread-21: B2B - (DEBUG) DBContext commit: Leave
2009.03.01 at 15:37:33:012: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.data.MsgListener:onMessage Enter
2009.03.01 at 15:37:33:013: Thread-20: B2B - (DEBUG) DBContext beginTransaction: Enter
2009.03.01 at 15:37:33:013: Thread-20: B2B - (DEBUG) DBContext beginTransaction: Transaction.begin()
2009.03.01 at 15:37:33:013: Thread-20: B2B - (DEBUG) DBContext beginTransaction: Leave
2009.03.01 at 15:37:33:014: Thread-20: B2B - (INFORMATION) oracle.tip.adapter.b2b.engine.Engine:processEvents Enter
2009.03.01 at 15:37:33:014: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processEvents begin transaction
2009.03.01 at 15:37:33:015: Thread-20: B2B - (DEBUG) DBContext beginTransaction: Enter
2009.03.01 at 15:37:33:015: Thread-20: B2B - (DEBUG) DBContext beginTransaction: Leave
2009.03.01 at 15:37:33:015: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:handleMessageEvent Enter
2009.03.01 at 15:37:33:015: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:incomingContinueProcess Enter
2009.03.01 at 15:37:33:015: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:getWireMessage Enter
2009.03.01 at 15:37:33:019: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:getWireMessage Exit
2009.03.01 at 15:37:33:020: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:formTransportMessage Enter
2009.03.01 at 15:37:33:027: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:formTransportMessage Exit
2009.03.01 at 15:37:33:028: Thread-20: B2B - (INFORMATION) oracle.tip.adapter.b2b.engine.Engine:processIncomingMessage Enter
2009.03.01 at 15:37:33:042: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processIncomingMessage Identify Business Protocol
2009.03.01 at 15:37:33:042: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processIncomingMessage Do Unpack using the BP specific package class
2009.03.01 at 15:37:33:043: Thread-20: B2B - (DEBUG) MimePackaging:unpack:Enter
2009.03.01 at 15:37:33:043: Thread-20: B2B - (DEBUG) MimePackaging:doUnpack:Enter
2009.03.01 at 15:37:33:044: Thread-20: B2B - (DEBUG) MimePackaging:unpackNonMimeMessage:Enter
2009.03.01 at 15:37:33:044: Thread-20: B2B - (DEBUG) MimePackaging:unpackNonMimeMessage:encoding = UTF-8
2009.03.01 at 15:37:33:045: Thread-20: B2B - (DEBUG) MimePackaging:unpackNonMimeMessage:oracle.tip.adapter.b2b.packaging.Component@8a2023
2009.03.01 at 15:37:33:045: Thread-20: B2B - (DEBUG) MimePackaging:unpackNonMimeMessage:Exit
2009.03.01 at 15:37:33:046: Thread-20: B2B - (DEBUG) MimePackaging:unpack:Exit
2009.03.01 at 15:37:33:046: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processIncomingMessage Decode the Incoming Message into B2B Message
2009.03.01 at 15:37:33:046: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.generic.GenericExchangePlugin:GenericExchangePlugin:decodeIncomingMessage Enter
2009.03.01 at 15:37:33:046: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.generic.GenericExchangePlugin:GenericExchangePlugin:decodeIncomingMessage Number of Components = 1
2009.03.01 at 15:37:33:047: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.generic.GenericExchangePlugin:decodeIncomingMessage Transport Protocol = {FTP}
2009.03.01 at 15:37:33:047: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.generic.GenericExchangePlugin:decodeIncomingMessage filename = TEE_2009Mar01_15_37_29_170.dat
2009.03.01 at 15:37:33:048: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.generic.GenericExchangePlugin:decodeIncomingMessage FILE_FORMAT = FROM_PARTY - TEE
2009.03.01 at 15:37:33:048: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.generic.GenericExchangePlugin:decodeIncomingMessage File TP Host name = TEE
2009.03.01 at 15:37:33:048: Thread-20: B2B - (DEBUG) calling setInitiatingPartyId() changing from null to TPName: TEE Type: null Value: null
2009.03.01 at 15:37:33:048: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.generic.GenericExchangePlugin:decodeIncomingMessage fromParty = TEE
2009.03.01 at 15:37:33:048: Thread-20: B2B - (DEBUG) calling setFromPartyId() changing from null to TPName: TEE Type: null Value: null
2009.03.01 at 15:37:33:049: Thread-20: B2B - (DEBUG) calling setToPartyId() changing from null to TPName: null Type: null Value: null
2009.03.01 at 15:37:33:049: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.generic.GenericExchangePlugin:GenericExchangePlugin:decodeIncomingMessage security info NULL
2009.03.01 at 15:37:33:056: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.generic.GenericExchangePlugin:GenericExchangePlugin:decodeIncomingMessage Exit
2009.03.01 at 15:37:33:056: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processHubMessage Enter
2009.03.01 at 15:37:33:056: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processHubMessage toTP null
2009.03.01 at 15:37:33:057: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processHubMessage hubUrl null
2009.03.01 at 15:37:33:057: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processHubMessage Exit
2009.03.01 at 15:37:33:057: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processIncomingMessage ProtocolCollabId = null
2009.03.01 at 15:37:33:057: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processIncomingMessage CollaborationName null
2009.03.01 at 15:37:33:057: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:checkDuplicate Enter
2009.03.01 at 15:37:33:058: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:checkDuplicate check non-RosettaNet Message
2009.03.01 at 15:37:33:060: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:checkDuplicate Exit
2009.03.01 at 15:37:33:060: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processIncomingMessage Protocol Collaboration Id : null
2009.03.01 at 15:37:33:060: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:identifyIncomingDocument Enter
2009.03.01 at 15:37:33:063: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:preProcessor enter
2009.03.01 at 15:37:33:064: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:preProcessor edi = X12
2009.03.01 at 15:37:33:064: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:preProcessor segment delimiter is 27
2009.03.01 at 15:37:33:073: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:identifyIncomingDocument preprocess result =
ISA~00~Authorizat~00~Security I~01~Interchange Sen~01~Interchange Rec~090301~1935~U~00401~000001101~0~I~+'GS~SP~Application Sen~Application Rec~20090301~1537~1101~T~004010'ST~841~5709'SPI~00~01~Reference Identification~Entity Title~Entity Purpose~A~00~01~00~10~Source Subquali~773~1~AA~0001'RDT~A~Revision Value~001~~~01'RDT~A~Revision Value~001~~~01'RDT~A~Revision Value~001~~~01'RDT~A~Revision Value~001~~~01'NTE~AAA~Description'X1~C~Export Licen~C~~1~1~COU~SCHEDULE B~D~252876~59154.0269~A~01~8~U~Identification Code'X2~Import License Number~~20090301~~20090301~20090301'X7~Free-Form Message~Free-Form Message'AMT~1~1~C'REF~01~Reference Identification~Description~01+Reference Identification+01+Reference Identification+01+Reference Identification'DTM~001~~~01~CC~Date Time Period'PER~1A~Name~AA~Communication Number~AA~Communication Number~AA~Communication Number~Contact Inquiry Refe'N1~01~Name~1~Identification Code~01~01'N2~Name~Name'N3~Address Information~Address Information'N4~City Name~ST~POSTAL CODE~COU~A~Location Identifier'REF~01~Reference Identification~Description~01+Reference Identification+01+Reference Identification+01+Reference Identification'PER~1A~Name~AA~Communication Number~AA~Communication Number~AA~Communication Number~Contact Inquiry Refe'HL~1~~1~0'SPI~00~01~Reference Identification~Entity Title~Entity Purpose~A~00~01~00~10~Source Subquali~4~1~AA~0001'RDT~A~Revision Value~001~~~01'PRR~Assigned Identificat~10~Source Subquali~BRK~Description~10~Source Subquali~A~10~Source Subquali~1'PRT~EXC~10~Source Subquali~N'PRS~1~Description'LIN~Assigned Identificat~A1~Product/Service ID~A1~Product/Service ID~A1~Product/Service ID~A1~Product/Service ID~A1~Product/Service ID~A1~Product/Service ID~A1~Product/Service ID~A1~Product/Service ID~A1~Product/Service ID~A1~Product/Service ID~A1~Product/Service ID~A1~Product/Service ID~A1~Product/Service ID~A1~Product/Service ID~A1~Product/Service ID'PER~1A~Name~AA~Communication Number~AA~Communication Number~AA~Communication Number~Contact Inquiry Refe'MSG~Free-Form Message Text~AA~3'N1~01~Name~1~Identification Code~01~01'N2~Name~Name'N3~Address Information~Address Information'N4~City Name~ST~POSTAL CODE~COU~A~Location Identifier'PER~1A~Name~AA~Communication Number~AA~Communication Number~AA~Communication Number~Contact Inquiry Refe'N9~01~Reference Identification~Free-form Description~~~01~01+Reference Identification+01+Reference Identification+01+Reference Identification'PID~F~01~10~Product Desc~Description~1S~Source Subquali~N~LAN'PKD~AMM01~Source Subquali~10~Packagi~L'QTY~01~1~01+3+60.42665+01+5+3+01+1+51887.5+01+6+7.79+01+2+3953.97808'MEA~9L~1~6~01+5+56318.8+01+1+30.72+01+1+1+01+7+8887.19467+01+6+661.97698~6~7~01~~1S~BM'MEA~9L~1~5~01+3+696.4+01+4+4+01+3+1221.27922+01+1+994232.001+01+3+872.859~3~9~01~~1S~BM'MEA~9L~1~3~01+8+8+01+1+7.75+01+2+6.395+01+1+2.1+01+6+7.59~6~4~01~~1S~BM'MEA~9L~1~6~01+6+7393.71+01+3+54258.8579+01+8+28012.940+01+5+8+01+7+8.8~9~9~01~~1S~BM'MEA~9L~1~8~01+5+8661152.98+01+7+6356848.72+01+7+1010847.39+01+5+4939.33859+01+3+7.84050~8~4~01~~1S~BM'UIT~01+7+8.3+01+2+8.702047+01+8+323.16049+01+8+40699.4+01+5+30.909~1~AA'LOC~01~Reference Identification~Description~Reference Identification~Catego~01~Reference Identification~Description~Reference Identification~6~01+7+257.30155+01+1+963640.085+01+1+9.42+01+4+1+01+3+67.61~8~01+6+3.6+01+2+20.5+01+4+6.99+01+7+5+01+5+213.507492~5~01+2+3077486.5+01+7+78023.621+01+3+6.74+01+7+138554.0+01+3+4111.4~2~01+9+2.6+01+8+91290.0173+01+9+1.9+01+2+6.168+01+1+26.9~2~01+2+1+01+6+67348.246+01+4+8.50+01+7+37.63+01+5+130691508.0~1~01+5+8.39+01+1+2.0+01+6+7.3+01+5+173.68084+01+5+550.4928~01~Reference Identification~Description'PWK~01~1~26~01~1~Identification Code~Description~1+1+1+1+1~AR'PKG~F~01~10~Packagi~Description~01'MEA~9L~1~6~01+9+99.2217+01+5+6.5043+01+8+30.76+01+9+3+01+1+7~3~2~01~~1S~BM'REF~01~Reference Identification~Description~01+Reference Identification+01+Reference Identification+01+Reference Identification'DTM~001~~~01~CC~Date Time Period'PER~1A~Name~AA~Communication Number~AA~Communication Number~AA~Communication Number~Contact Inquiry Refe'LX~6'LIN~Assigned Identificat~A1~Product/Service ID~A1~Product/Service ID~A1~Product/Service ID~A1~Product/Service ID~A1~Product/Service ID~A1~Product/Service ID~A1~Product/Service ID~A1~Product/Service ID~A1~Product/Service ID~A1~Product/Service ID~A1~Product/Service ID~A1~Product/Service ID~A1~Product/Service ID~A1~Product/Service ID~A1~Product/Service ID'TMD~01~10~Product Desc~01~01~Description~~Reference Identification~Source Subquali'MEA~9L~1~4~01+7+71.1+01+2+277.0+01+2+9.19003+01+1+901.516+01+3+7803582.87~8~7~01~~1S~BM'PSD~01~01~9661549~01+2+140318.0112+01+3+30.74740+01+9+67.17+01+7+5.1130+01+3+56743.0~01~01~01~Description'SPS~193487350~66823328~472426~5.6~01+3+519.45554+01+6+145146.03+01+2+63994262.5+01+3+1.3166+01+8+4.7~440443'DTM~001~~~01~CC~Date Time Period'REF~01~Reference Identification~Description~01+Reference Identification+01+Reference Identification+01+Reference Identification'REF~01~Reference Identification~Description~01+Reference Identification+01+Reference Identification+01+Reference Identification'REF~01~Reference Identification~Description~01+Reference Identification+01+Reference Identification+01+Reference Identification'REF~01~Reference Identification~Description~01+Reference Identification+01+Reference Identification+01+Reference Identification'REF~01~Reference Identification~Description~01+Reference Identification+01+Reference Identification+01+Reference Identification'REF~01~Reference Identification~Description~01+Reference Identification+01+Reference Identification+01+Reference Identification'REF~01~Reference Identification~Description~01+Reference Identification+01+Reference Identification+01+Reference Identification'REF~01~Reference Identification~Description~01+Reference Identification+01+Reference Identification+01+Reference Identification'REF~01~Reference Identification~Description~01+Reference Identification+01+Reference Identification+01+Reference Identification'EFI~00~Free-Form Message Text~9A~Version Identifier~Program Identifier~Version Identifier~Interchange Format~Version Identifier~Compression Technique~A0~File Name~Bloc~7~84410~Version Identifier~ASB'BIN~3~hii'CID~1~01~10~Product Desc~Description~Source Subquali~N'UIT~01+6+940.5+01+3+4.7+01+9+3.1+01+6+58.1+01+2+115728.9010~3~AA'TMD~01~10~Product Desc~01~01~Description~~Reference Identification~Source Subquali'PSD~01~01~595~01+1+5.139+01+3+1+01+5+4+01+5+19.1+01+5+3441.57231~01~01~01~Description'CSS~GC~01+1+33832819.6+01+1+1.5332+01+5+1.1+01+1+12173.83+01+5+813.282453~874~27~1~2~38'SPS~9~1154210~75~9.5~01+2+473.9+01+5+28.394421+01+6+755.69932+01+3+8407.2+01+3+1~54261910'MSG~Free-Form Message Text~AA~66511'MEA~9L~1~3~01+6+4.979+01+8+60.167241+01+8+48.03003+01+1+1.6086+01+5+2417168.92~3~1~01~~1S~BM'DTM~001~~~01~CC~Date Time Period'REF~01~Reference Identification~Description~01+Reference Identification+01+Reference Identification+01+Reference Identification'STA~01~9~01+6+66133.5+01+1+1+01+6+45813032.4+01+3+3329.6+01+7+63878.29~1~9L~3~5~01'DTM~001~~~01~CC~Date Time Period'REF~01~Reference Identification~Description~01+Reference Identification+01+Reference Identification+01+Reference Identification'CRF~01+6+7050.3+01+3+892.07605+01+6+847.7520+01+7+4+01+4+1.7~59.926'LS~CID'CID~1~01~10~Product Desc~Description~Source Subquali~N'MEA~9L~1~1~01+2+316324.35+01+8+852.8+01+7+4.2+01+8+6.3+01+7+9.3~2~4~01~~1S~BM'STA~01~6~01+2+751.60984+01+2+5+01+7+60.63+01+3+5366069.5+01+7+1.891~1~9L~1~8~01'LE~CID'EFI~00~Free-Form Message Text~9A~Version Identifier~Program Identifier~Version Identifier~Interchange Format~Version Identifier~Compression Technique~A0~File Name~Bloc~2~64~Version Identifier~ASB'BIN~3~hii'SE~91~5709'GE~1~1101'IEA~1~000001101'

.... b2b.log:
2009.03.01 at 15:37:33:077: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:ISelectorImpl Enter
2009.03.01 at 15:37:33:078: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:ISelectorImpl validateEnvelope = false
2009.03.01 at 15:37:33:078: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:ISelectorImpl Leave
2009.03.01 at 15:37:33:078: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:cloneSelector Enter
2009.03.01 at 15:37:33:079: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:cloneSelector Return = oracle.tip.adapter.b2b.document.edi.ISelectorImpl@43da1b
2009.03.01 at 15:37:33:085: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Param Name = SeverityConfig
2009.03.01 at 15:37:33:085: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Value = null
2009.03.01 at 15:37:33:107: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:processNode ISA Key = InterchangeSenderID Val = Interchange Sen
2009.03.01 at 15:37:33:108: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:processNode ISA Key = InterchangeSenderQual Val = 01
2009.03.01 at 15:37:33:108: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:processNode standard = X12
2009.03.01 at 15:37:33:108: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:processNode ISA Key = InterchangeReceiverID Val = Interchange Rec
2009.03.01 at 15:37:33:109: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:processNode ISA Key = InterchangeControlVersion Val = 00401
2009.03.01 at 15:37:33:109: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:processNode ISA Key = InterchangeReceiverQual Val = 01
2009.03.01 at 15:37:33:109: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:processNode Group Key = GroupSenderID Val = Application Sen
2009.03.01 at 15:37:33:110: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:processNode X12 Doc Revision : 004010
2009.03.01 at 15:37:33:110: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:processNode X12 Doc Revision : 4010
2009.03.01 at 15:37:33:110: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:processNode Group Key = GroupReceiverID Val = Application Rec
2009.03.01 at 15:37:33:110: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:processNode Transaction Count = 1
2009.03.01 at 15:37:33:111: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:processNode DocType = 841
2009.03.01 at 15:37:33:111: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:traceParameters Parameter InterchangeReceiverQual = 01
2009.03.01 at 15:37:33:112: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:traceParameters Parameter InterchangeSenderID = Interchange Sen
2009.03.01 at 15:37:33:112: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:traceParameters Parameter InterchangeReceiverID = Interchange Rec
2009.03.01 at 15:37:33:112: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:traceParameters Parameter GroupReceiverID = Application Rec
2009.03.01 at 15:37:33:112: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:traceParameters Parameter InterchangeControlVersion = 00401
2009.03.01 at 15:37:33:113: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:traceParameters Parameter GroupSenderID = Application Sen
2009.03.01 at 15:37:33:113: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:traceParameters Parameter InterchangeSenderQual = 01
2009.03.01 at 15:37:33:113: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:identifyIncomingDocument exit
2009.03.01 at 15:37:33:113: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Correlation:incomingCorrelate Enter
2009.03.01 at 15:37:33:113: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Correlation:incomingCorrelate msginfo reftomsgid is null, nothing to correlate
2009.03.01 at 15:37:33:114: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Correlation:incomingCorrelate Exit
2009.03.01 at 15:37:33:114: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processIncomingMessage number of b2b messages 1
2009.03.01 at 15:37:33:114: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processIncomingMessage msgtype = 1
2009.03.01 at 15:37:33:115: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.tpa.TPAProcessor:processIncomingTPA() Begin TPA Processing..
2009.03.01 at 15:37:33:115: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.tpa.TPAProcessor:processTPA() PARTIES (before calling processParty) :
initial : null
from : TPName: TEE Type: null Value: null
to : TPName: null Type: null Value: null
final : null
initiating : TPName: TEE Type: null Value: null
2009.03.01 at 15:37:33:115: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.tpa.TPAProcessor:processTPA() direction is incoming
2009.03.01 at 15:37:33:115: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.tpa.TPAProcessor:processTPA() calling processparty with : TPName: null Type: null Value: null
2009.03.01 at 15:37:33:116: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.tpa.RepoDataAccessor:processParty() Begin..
2009.03.01 at 15:37:33:119: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.tpa.TPAProcessor:processTPA() after calling processparty : TPName: TEE Type: null Value: null
2009.03.01 at 15:37:33:119: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.tpa.TPAProcessor:processTPA() PARTIES (after calling processParty):
initial : null
from : TPName: TEE Type: null Value: null
to : TPName: TEE Type: null Value: null
final : null
initiating : TPName: TEE Type: null Value: null
2009.03.01 at 15:37:33:120: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.tpa.TPAProcessor:processTPA() docTypeName: 841 docTypeRevision: 4010
2009.03.01 at 15:37:33:127: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.tpa.TPAProcessor:processTPA() actionName: BARFEDI841 actionRevision: 1.0
2009.03.01 at 15:37:33:127: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.tpa.RepoDataAccessor:getCollaborationDetails() Begin.. Activity Name : BARFEDI841 Activity Version: 1.0
2009.03.01 at 15:37:33:131: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.tpa.TPAProcessor:processTPA() eventName:<BARFEDI841>
2009.03.01 at 15:37:33:131: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.tpa.TPAProcessor:processTPA() messageType:1
2009.03.01 at 15:37:33:136: Thread-20: B2B - (DEBUG) calling setMode() changing from -1 to 2
2009.03.01 at 15:37:33:137: Thread-20: B2B - (DEBUG) calling setInitiatingPartyId() changing from TPName: TEE Type: null Value: null to TPName: TEE Type: null Value: null
2009.03.01 at 15:37:33:137: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.tpa.TPAProcessor:processTPA() cpaID=null
2009.03.01 at 15:37:33:137: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.tpa.TPAProcessor:processTPA() TPA Name : null
2009.03.01 at 15:37:33:137: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.tpa.TPAProcessor:processTPA() TPA Name : null
2009.03.01 at 15:37:33:138: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.tpa.TPAIdentifier:identifyTPA() Begin..
2009.03.01 at 15:37:33:138: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.tpa.TPAIdentifier:identifyTPA()
From Party -> null-null-TEE-null To Party -> null-null-TEE-null Business Action name -> BARFEDI841
2009.03.01 at 15:37:33:138: Thread-20: B2B - (DEBUG) RepoDataAccessor:getAgreementNameByBaTPName() Begin..
2009.03.01 at 15:37:33:138: Thread-20: B2B - (DEBUG) RepoDataAccessor:getAgreementNameByBaTPName() fromParty: TPName: TEE Type: null Value: null toParty: TPName: TEE Type: null Value: null initiatingParty: TPName: TEE Type: null Value: null
2009.03.01 at 15:37:33:139: Thread-20: B2B - (DEBUG) RepoDataAccessor:getAgreementNameByBaTPName() SELECT ag.name FROM TIP_BusinessAction_ra ba1, TIP_Party_ra tp1, TIP_BusinessAction_ra ba2, TIP_Party_ra tp2, TIP_SupportedBusinessAction_ra sba1, TIP_SupportedBusinessAction_ra sba2, TIP_Participant_ra tpp1, TIP_Participant_ra tpp2, TIP_Agreement_ra ag WHERE tp1.name = ? AND ba1.name = ? AND ba1.revision = ? AND sba1.isinitiator = ? AND tpp1.agreement = ag.ID AND tpp1.supportedbusinessaction = sba1.ID AND sba1.tradingpartner = tp1.ID AND sba1.businessaction = ba1.ID AND tp2.name = ? AND ba2.name = ? AND ba2.revision = ? AND sba2.isinitiator = ? AND tpp2.agreement = ag.ID AND tpp2.supportedbusinessaction = sba2.ID AND sba2.tradingpartner = tp2.ID AND sba2.businessaction = ba2.ID AND tpp1.agreement = tpp2.agreement AND ((ag.effectivefromdate <= SYSDATE) OR (ag.effectivefromdate IS NULL)) AND ((ag.effectivetodate +1 >= SYSDATE) OR (ag.effectivetodate IS NULL))
2009.03.01 at 15:37:33:139: Thread-20: B2B - (DEBUG) RepoDataAccessor:getAgreementNameByBaTPName() bind vars: TEE,BARFEDI841,1.0,Y,TEE,BARFEDI841,1.0,N
2009.03.01 at 15:37:33:145: Thread-20: B2B - (ERROR) Error -: AIP-50547: Trading partner agreement not found for the given input values: From party[NAME] "TEE", To party[NAME] "TEE", Business action name "BARFEDI841"; also verify agreement effectiveToDate
at oracle.tip.adapter.b2b.tpa.RepoDataAccessor.getAgreementNameByBaTPName(RepoDataAccessor.java:2345)
at oracle.tip.adapter.b2b.tpa.TPAIdentifier.identifyTPA(TPAIdentifier.java:186)
at oracle.tip.adapter.b2b.tpa.TPAProcessor.processTPA(TPAProcessor.java:587)
at oracle.tip.adapter.b2b.tpa.TPAProcessor.processIncomingTPA(TPAProcessor.java:238)
at oracle.tip.adapter.b2b.engine.Engine.processIncomingMessage(Engine.java:1832)
at oracle.tip.adapter.b2b.engine.Engine.incomingContinueProcess(Engine.java:2573)
at oracle.tip.adapter.b2b.engine.Engine.handleMessageEvent(Engine.java:2443)
at oracle.tip.adapter.b2b.engine.Engine.processEvents(Engine.java:2398)
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.03.01 at 15:37:33:145: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: processIncomingMessage B2BDE
2009.03.01 at 15:37:33:146: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:handleExceptionBeforeIncomingTPA Enter
2009.03.01 at 15:37:33:146: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: handleInboundException Enter
2009.03.01 at 15:37:33:146: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: handleInboundException Error message is Error -: AIP-50547: Trading partner agreement not found for the given input values: From party[NAME] "TEE", To party[NAME] "TEE", Business action name "BARFEDI841"; also verify agreement effectiveToDate
2009.03.01 at 15:37:33:146: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: isFARequired Enter
2009.03.01 at 15:37:33:147: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: isFARequired {filename=TEE_2009Mar01_15_37_29_170.dat, filesize=7787, file_ext=dat, fullpath=//users/dab2b01/RF841/TEE_2009Mar01_15_37_29_170.dat, timestamp=1970-01-01T00:00:00.000-00:00}
2009.03.01 at 15:37:33:147: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: isFARequired returning false
2009.03.01 at 15:37:33:147: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: handleInboundException FA not required
2009.03.01 at 15:37:33:148: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:handleInboundException Updating Error Message: Error -: AIP-50547: Trading partner agreement not found for the given input values: From party[NAME] "TEE", To party[NAME] "TEE", Business action name "BARFEDI841"; also verify agreement effectiveToDate
2009.03.01 at 15:37:33:148: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Enter
2009.03.01 at 15:37:33:149: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Wire message found
2009.03.01 at 15:37:33:149: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Creating new b2berror object
2009.03.01 at 15:37:33:149: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState enum0 not null
2009.03.01 at 15:37:33:149: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Updating wire message error information
2009.03.01 at 15:37:33:155: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Updating wire message protocol message id
2009.03.01 at 15:37:33:171: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Updating wire message payload storage
2009.03.01 at 15:37:33:182: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Creating new business message
2009.03.01 at 15:37:33:182: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:insertMsgTblRow Enter
2009.03.01 at 15:37:33:189: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:insertMsgTblRow toparty name TEE
2009.03.01 at 15:37:33:189: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:insertMsgTblRow toparty type and value nullnull
2009.03.01 at 15:37:33:196: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:insertMsgTblRow BusinessAction for the given name BARFEDI841 BusinessAction_0E95
2009.03.01 at 15:37:33:207: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Updating business message error information
2009.03.01 at 15:37:33:217: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Exit
2009.03.01 at 15:37:33:218: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:handleInboundException Updating Native Event Tbl Row
2009.03.01 at 15:37:33:218: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:updateNativeEvtTblRow Enter
2009.03.01 at 15:37:33:220: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateNativeEvtTblRow msgInfo.id = TEE_2009Mar01_15_37_29_170.dat@0A4DBD5D11FC2AEDA770000018E26600
2009.03.01 at 15:37:33:220: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:
** DbAccess:updateNativeEvtTblRow:tip_wireMsg protocolCollabID = null
2009.03.01 at 15:37:33:226: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:handleInboundException notifying App
2009.03.01 at 15:37:33:226: Thread-20: B2B - (DEBUG) Engine:notifyApp Enter
2009.03.01 at 15:37:33:232: Thread-20: 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>0A4DBD5D11FC2AEDA680000018E265F0</b2bMessageId>
<errorCode>AIP-50547</errorCode>
<errorText>Trading partner agreement not found for the given input values: From party[NAME] "TEE", To party[NAME] "TEE", Business action name "BARFEDI841"; also verify agreement effectiveToDate</errorText>
<errorDescription>
<![CDATA[Machine Info: (dgia21a.TEEis.com)
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] "TEE", To party[NAME] "TEE", Business action name "BARFEDI841"; also verify agreement effectiveToDate
at oracle.tip.adapter.b2b.tpa.RepoDataAccessor.getAgreementNameByBaTPName(RepoDataAccessor.java:2345)
at oracle.tip.adapter.b2b.tpa.TPAIdentifier.identifyTPA(TPAIdentifier.java:186)
at oracle.tip.adapter.b2b.tpa.TPAProcessor.processTPA(TPAProcessor.java:587)
at oracle.tip.adapter.b2b.tpa.TPAProcessor.processIncomingTPA(TPAProcessor.java:238)
at oracle.tip.adapter.b2b.engine.Engine.processIncomingMessage(Engine.java:1832)
at oracle.tip.adapter.b2b.engine.Engine.incomingContinueProcess(Engine.java:2573)
at oracle.tip.adapter.b2b.engine.Engine.handleMessageEvent(Engine.java:2443)
at oracle.tip.adapter.b2b.engine.Engine.processEvents(Engine.java:2398)
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.03.01 at 15:37:33:244: Thread-20: B2B - (DEBUG) Engine:notifyApp Exit
2009.03.01 at 15:37:33:244: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:handleInboundException Updated the Error Message Successfully: Error -: AIP-50547: Trading partner agreement not found for the given input values: From party[NAME] "TEE", To party[NAME] "TEE", Business action name "BARFEDI841"; also verify agreement effectiveToDate
2009.03.01 at 15:37:33:245: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: handleInboundException Exit
2009.03.01 at 15:37:33:245: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:handleExceptionBeforeIncomingTPA Exit
2009.03.01 at 15:37:33:245: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:incomingContinueProcess Exit
2009.03.01 at 15:37:33:245: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:handleMessageEvent Exit
2009.03.01 at 15:37:33:245: Thread-20: B2B - (INFORMATION) oracle.tip.adapter.b2b.engine.Engine:processEvents Exit
2009.03.01 at 15:37:33:246: Thread-20: B2B - (DEBUG) DBContext commit: Enter
2009.03.01 at 15:37:33:263: Thread-20: B2B - (DEBUG) DBContext commit: Transaction.commit()
2009.03.01 at 15:37:33:263: Thread-20: B2B - (DEBUG) DBContext commit: Leave
2009.03.01 at 15:37:33:264: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.data.MsgListener:onMessage Exit

Importing Trading Partner Profiles

Similar Messages

Maybe you are looking for