Message Type in XML ??

Hi guys - I have a problem with the name of my MT name being part of the internal XML structure.
I have an incoming XML message from a 3rd. party supplier wich looks lige this:
<?xml version="1.0" encoding="UTF-8" ?>
- <Header>
- <Lines>
After seting this up in PI my own xml structure looks like this:
<?xml version="1.0" encoding="UTF-8" ?>
- <MT_BYGLET_ORDER> (I have to call my message type something!)
- <Header>
- <Lines>
As the two structures are not alike, becaouse of the MT name, my mapping is not working.
Any good ideas how I can make these to stuctures work together.
Thanks

Yes, there is should be a root element, if your sender system can't create it (sometimes we can't get them change their system) then you need to write an XSLT or Java mapping to add a root segment and add it before MM in OM.
thanks..
Karna...

Similar Messages

Best JMS Message Type for XML

          Which type of message is most suitable for XML file transfer? and why?
          what parameters decide the selection of message type for xml payload?


"dyn" <[email protected]> wrote in message
          news:[email protected]..
          >
          > Which type of message is most suitable for XML file transfer? and why?
          > what parameters decide the selection of message type for xml payload?
          You can use WebLogic's XML message type if you like. If you want to use
          selector expressions then it is particularly useful, especially since your
          selector expressions can run on the body of the message. However, the
          implications of this are that the selectors are more expensive (both in
          terms of the processing needed to evaluate the XPath expression, and in
          terms of the fact that the message bodies have to be in memory to do the
          evaluation).
          If you just want to transfer XML, then why not use a simple text message
          type.
          Use whatever suits your needs.
          Regards,
          Jon

Source structure of XML file as different from Message type?

Hi,
We are picking an xml file from the FTP server of the client.
We have source message type 'MT_Invoice' with data type as 'DT_Invoice'.
When we open the message mapping test tab, the source structure is as shown below.
<ns0:MT_Invoice xmlns:ns0="urn:maxxium:nordic:invoice:inbound">
   <Invoices>
      <Invoice>
      </Invoice>
   </Invoices>
</MT_Invoice>
My question is "What should be the structure of the XML file that the client is depositing on to the FTP server?".
Should it start with the tag 'MT_Invoice' with the namespace or should it simply start from    <Invoices> tag.
I have tried various combinations for the source xml structure. But all are failing.
(This is evident from the fact that the mapping is failing. That's why I have given the structure from the source structure of the message mapping tab.)
Kindly help.
Thanks,
John

>
john j wrote:
> Hi,
>
> We are picking an xml file from the FTP server of the client.
>
> We have source message type 'MT_Invoice' with data type as 'DT_Invoice'.
>
> When we open the message mapping test tab, the source structure is as shown below.
>
> <ns0:MT_Invoice xmlns:ns0="urn:maxxium:nordic:invoice:inbound">
>    <Invoices>
>       <Invoice>
> .
> .
> .
> .
>       </Invoice>
>    </Invoices>
> </MT_Invoice>
>
> My question is "What should be the structure of the XML file that the client is depositing on to the FTP server?".
>
> Should it start with the tag 'MT_Invoice' with the namespace or should it simply start from    <Invoices> tag.
>
> I have tried various combinations for the source xml structure. But all are failing.
>
> (This is evident from the fact that the mapping is failing. That's why I have given the structure from the source structure of the message mapping tab.)
>
> Kindly help.
>
> Thanks,
> John
you are picking an XML file. So you should create the MT which would represent exactly the XML format of the source file.
So ideally if your file starts with <invoice>, then name your MT as invoice

Error consuming Web service - content type text/xml;charset=utf-8 of the response message does not match the content type of the binding

Hi all,
We are trying to interact with Documentum server through DFS exposed WCF which communicates through port 9443 and we are provided with documentum issued Public Key certificates. We have successfully imported the certificates in client machine and configured
the bindings as below in our .Net web application config file.
<system.serviceModel>
<bindings>
<wsHttpBinding>
<binding
name="ObjectServicePortBinding1">
<security
mode="Transport">
<transport
clientCredentialType="None"
proxyCredentialType="None"
realm=""
/>
<message
clientCredentialType="Certificate"
algorithmSuite="Default"
/>
</security>
</binding>
<binding
name="QueryServicePortBinding">
<security
mode="Transport">
<transport
clientCredentialType="None"
proxyCredentialType="None"
realm=""
/>
<message
clientCredentialType="Certificate"
algorithmSuite="Default"
/>
</security>
</binding>
</wsHttpBinding>
</bindings>
Also, we set the message encoding as MTOM and the wcf client object initialization code snippet is as below,
ObjectServicePortClient
serviceClient = new
ObjectServicePortClient(new
WSHttpBinding("ObjectServicePortBinding1"),
new
EndpointAddress(UriUtil.ObjectServiceUri));
if (serviceClient.Endpoint.Binding
is
WSHttpBinding)
   WSHttpBinding
wsBinding = serviceClient.Endpoint.Binding as
WSHttpBinding;
wsBinding.MessageEncoding =
"MTOM".Equals(transferMode) ?
WSMessageEncoding.Mtom :
WSMessageEncoding.Text;
serviceClient.Endpoint.Behaviors.Add(new
ServiceContextBehavior(Config.RepositoryName,
Config.DocumentumUserName,
Config.DocumentumPassword));
When we execute the above code, we are getting error message as below,
Exception: The content type text/xml;charset=utf-8 of the response message does not match the content type of the binding (multipart/related; type="application/xop+xml"). If using a custom encoder, be sure that the IsContentTypeSupported
method is implemented properly. The first 407 bytes of the response were: '<?xml version="1.0" ?><S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/"><S:Body><S:Fault xmlns:ns4="http://www.w3.org/2003/05/soap-envelope"><faultcode>S:VersionMismatch</faultcode><faultstring>Couldn't
create SOAP message. Expecting Envelope in namespace http://schemas.xmlsoap.org/soap/envelope/, but got http://www.w3.org/2003/05/soap-envelope </faultstring></S:Fault></S:Body></S:Envelope>'
Then, we changed the bindings as below
<system.serviceModel>
<bindings>
<wsHttpBinding>
<binding
name="ObjectServicePortBinding1">
<security
mode="Transport">
<transport
clientCredentialType="Certificate"
proxyCredentialType="None"
realm=""
/>
<message
clientCredentialType="Certificate"
algorithmSuite="Default"
/>
</security>
</binding>
<binding
name="QueryServicePortBinding">
<security
mode="Transport">
<transport
clientCredentialType="
Certificate"
proxyCredentialType="None"
realm=""
/>
<message
clientCredentialType="Certificate"
algorithmSuite="Default"
/>
</security>
</binding>
</wsHttpBinding>
</bindings>
We are getting another error message,
Exception: The client certificate is not provided. Specify a client certificate in ClientCredentials.
Any pointers on resolving this issue would be highly helpful.
Thanks

Hi Dhanasegaran,
As per your case, the corresponding details which may guide you to resolve this issue:
1. First of all, you can try to call the wcf service directly from the browser & check where it will point out the correct location.
2. In config file ,Set IncludeExceptionDetailInFaults to true to enable exception information to flow to clients for debugging purposes .
Set this to true only during development to troubleshoot a service like below :
<serviceBehaviors>
<behavior name="metadataAndDebugEnabled">
    <serviceDebug
      includeExceptionDetailInFaults="true"
/>
    <serviceMetadata
      httpGetEnabled="true"
      httpGetUrl=""
/>
</behavior>
</serviceBehaviors>
3. I suggest you to change that <security mode ="TransportWithMessageCredential"> instead of <security mode ="Transport">
for more information, refer the following link :
https://msdn.microsoft.com/en-us/library/aa354508(v=vs.110).aspx

What is inbound XML message type and idoc type in Purchase Order response

Hi ,
We are on SRM 7 ECS , support pack SAPKIBKV08.
We have a process in which vendor will send a Purchase Order response which will be
converted to XML format by a middleware. This XML message will come to
SRM and post a POR. I want to do the EDI mapping for this XML message,
but there is no message type and idoc type in SRM for Purchase Order
response. How do I map my message type in SRM to the vendor sent fields
in middleware .
Please advise
Rgds
Sumendra

Hi,
You can process with XML without IDoc.
Vendor-> (XML) -> PI -> (XML) -> SRM.
Please check PurchaseOrderConfirmation_In in namespace "http://sap.com/xi/SRM/Procurement/Global".
http://esworkplace.sap.com
Regards,
Masa

Handling multiple XML message types in a webservice

My below scenario is
I have a webservice that receives XML messages from third party. The webservice populates 3 database tables through Mediator and DBAdapter from these XML files. Data for each table comes in a single XML file. How will I design the single werbservice to receive all the three different types of messages. eg: Customer, Order, OrderItem.
My WSDL is given below:
<?xml version= '1.0' encoding= 'UTF-8' ?>
<wsdl:definitions
name="receiveData"
targetNamespace="http://xmlns.oracle.com/sca/soapservice/receiveData"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
xmlns:inp1="http://xmlns.oracle.com/pcbpel/adapter/db/top/Order"
xmlns:tns="http://xmlns.oracle.com/sca/soapservice/ESTAProcessing/receiveData" >
<wsdl:types>
<schema xmlns="http://www.w3.org/2001/XMLSchema" >
<import namespace="http://xmlns.oracle.com/pcbpel/adapter/db/top/Order" schemaLocation="xsd/Order.xsd" />
</schema>
</wsdl:types>
<wsdl:message name="requestMessage">
<wsdl:part name="request" element="inp1:Order"/>
</wsdl:message>
<wsdl:portType name="execute_ptt">
<wsdl:operation name="execute">
<wsdl:input message="tns:requestMessage"/>
</wsdl:operation>
</wsdl:portType>
</wsdl:definitions>
Any similar example will be really good. Let me know if it does make sense. Here what I am looking for is whether a single operation can handle all three types of XML schema defintions and if yes how to put that in the WSDL

Technically you can do with XSD switch option however you should rethink towards your design of accepting three different message in single web service. specially the case you have taken customer and order.

Deleting Message Type name and namespace tag from XML payload

Hi Gurus,
Need help. My payload looks like this
<?xml version="1.0" encoding="utf-8" ?>
- <ns1:MT_O_sss xmlns:ns1="http://sap.com/xi/tm">
- <Job>
   <Field name="xxxx" value="" />
<Field name="xxx" value="" />
<Field name="xxx" value="" />
   </Job>
</ns1:MT_O_sss>
But The soap webservice is expecting it in
<?xml version="1.0" encoding="utf-8" ?>
- <Job>
   <Field name="xxxx" value="" />
<Field name="xxx" value="" />
<Field name="xxx" value="" />
   </Job>
I have to remove the message type name and namespace tag.
So how can I achieve this. I am sending this payload using a Receiver Soap Adapter. Please help. I am kind of stuck.

hi,
you have to simply add one module in your communication channel
that is XMLAnonymizerBean
you can refer below for help:
Remove namespace prefix or change XML encoding with the XMLAnonymizerBean
http://help.sap.com/saphelp_nw04/helpdata/en/2e/bf37423cf7ab04e10000000a1550b0/frameset.htm
hope it helps.
regards,
ujjwal kumar

Wrong message type while sending response from TP

Hi,
We are simulating a scenario in which the host is sending a Rosetta over RNIF request to TP. The request is getting completed and acknowledgement is reaching the host properly.
Now we are trying to send back a response from TP for the above request. But the following error is being observed:-
2009.03.03 at 11:31:21:884: Thread-24: B2B - (DEBUG) oracle.tip.adapter.b2b.data.MsgListener:onMessage Enter
2009.03.03 at 11:31:21:884: Thread-24: B2B - (DEBUG) DBContext beginTransaction: Enter
2009.03.03 at 11:31:21:884: Thread-24: B2B - (DEBUG) DBContext beginTransaction: Transaction.begin()
2009.03.03 at 11:31:21:884: Thread-24: B2B - (DEBUG) DBContext beginTransaction: Leave
2009.03.03 at 11:31:21:884: Thread-24: B2B - (DEBUG) oracle.tip.adapter.b2b.data.MsgListener:onMessage Action Name: null
2009.03.03 at 11:31:21:884: Thread-24: B2B - (DEBUG) Generic Wizard:getTradingPartnerNames Enter
2009.03.03 at 11:31:21:884: Thread-24: B2B - (DEBUG) Generic Wizard:getTradingPartnerNames tpitValue >>
2009.03.03 at 11:31:21:884: Thread-24: B2B - (DEBUG) Generic Wizard:getTradingPartnerNames Exit
2009.03.03 at 11:31:21:884: Thread-24: B2B - (DEBUG) oracle.tip.adapter.b2b.data.MsgListener:onMessage All TPs list for broadcasting[]
2009.03.03 at 11:31:21:884: Thread-24: B2B - (DEBUG) oracle.tip.adapter.b2b.data.MsgListener:onMessage ipmsgold.get_MSG_ID()>G20090303035936810.34565d:11fc706dc89:-7fbc@706519011<
2009.03.03 at 11:31:21:884: Thread-24: B2B - (DEBUG) oracle.tip.adapter.b2b.data.MsgListener:onMessage ipmsg.getMessageID() >G20090303035936810.34565d:11fc706dc89:-7fbc@706519011<
2009.03.03 at 11:31:21:884: Thread-24: B2B - (DEBUG) AQJMSCorrelationID = 91217C8567EB4A3EAC135BD382FD14E3
2009.03.03 at 11:31:21:884: Thread-24: B2B - (DEBUG) oracle.tip.adapter.b2b.data.MsgListener:onMessage ipmsg.getMessageID()>G20090303035936810.34565d:11fc706dc89:-7fbc@706519011<
2009.03.03 at 11:31:21:884: Thread-24: B2B - (DEBUG) oracle.tip.adapter.b2b.data.MsgListener:onMessage msgIdFrmBkEnd>G20090303035936810.34565d:11fc706dc89:-7fbc@706519011<
2009.03.03 at 11:31:21:900: Thread-24: B2B - (INFORMATION) oracle.tip.adapter.b2b.engine.Engine:processOutgoingMessage Enter
2009.03.03 at 11:31:21:900: Thread-24: B2B - (DEBUG) DBContext beginTransaction: Enter
2009.03.03 at 11:31:21:900: Thread-24: B2B - (DEBUG) DBContext beginTransaction: Leave
2009.03.03 at 11:31:21:900: Thread-24: B2B - (DEBUG) calling setFromPartyId() changing from null to TPName: COMSTOR Type: null Value: null
2009.03.03 at 11:31:21:900: Thread-24: B2B - (DEBUG) calling setToPartyId() changing from null to TPName: BTGS Type: null Value: null
2009.03.03 at 11:31:21:900: Thread-24: B2B - (DEBUG) calling setInitiatingPartyId() changing from null to TPName: null Type: null Value: null
2009.03.03 at 11:31:21:900: Thread-24: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processOutgoingMessage To TP NameBTGS
2009.03.03 at 11:31:21:900: Thread-24: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processOutgoingMessage From TP NameCOMSTOR
2009.03.03 at 11:31:21:900: Thread-24: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processOutgoingMessage business action name: null
2009.03.03 at 11:31:21:900: Thread-24: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processOutgoingMessage doctype name: Pip3A4PurchaseOrderConfirmation
2009.03.03 at 11:31:21:900: Thread-24: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processOutgoingMessage doctype revision: V02.03.00
2009.03.03 at 11:31:21:900: Thread-24: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processOutgoingMessage AppMsgIdG20090303035936810.34565d:11fc706dc89:-7fbc@706519011
2009.03.03 at 11:31:21:915: Thread-24: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processOutgoingMessage ipmsg.get_MSG_TYPE = 1
2009.03.03 at 11:31:21:915: Thread-24: B2B - (DEBUG) calling setInitiatingPartyId() changing from TPName: null Type: null Value: null to TPName: COMSTOR Type: null Value: null
2009.03.03 at 11:31:21:915: Thread-24: B2B - (DEBUG) Engine AQJMSCorrelationID = 91217C8567EB4A3EAC135BD382FD14E3
2009.03.03 at 11:31:21:915: Thread-24: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processOutgoingMessage using appMsgId as b2bMsgId
2009.03.03 at 11:31:21:915: Thread-24: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processOutgoingMessage B2B Message ID is G20090303035936810.34565d:11fc706dc89:-7fbc@706519011
2009.03.03 at 11:31:21:915: Thread-24: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processOutgoingMessage RefTo B2B Message ID is null
2009.03.03 at 11:31:21:915: Thread-24: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processOutgoingMessage isSignalMsg() == false; call outgoingTPA
2009.03.03 at 11:31:21:915: Thread-24: B2B - (DEBUG) oracle.tip.adapter.b2b.tpa.TPAProcessor:processOutgoingTPA() Begin TPA Processing..
2009.03.03 at 11:31:21:915: Thread-24: B2B - (DEBUG) oracle.tip.adapter.b2b.tpa.TPAProcessor:processTPA() PARTIES (before calling processParty) :
initial : null
from : TPName: COMSTOR Type: null Value: null
to : TPName: BTGS Type: null Value: null
final : null
initiating : TPName: COMSTOR Type: null Value: null
2009.03.03 at 11:31:21:915: Thread-24: B2B - (DEBUG) oracle.tip.adapter.b2b.tpa.TPAProcessor:processTPA() direction is outgoing
2009.03.03 at 11:31:21:915: Thread-24: B2B - (DEBUG) oracle.tip.adapter.b2b.tpa.TPAProcessor:processTPA() calling processparty with : TPName: COMSTOR Type: null Value: null
2009.03.03 at 11:31:21:915: Thread-24: B2B - (DEBUG) oracle.tip.adapter.b2b.tpa.RepoDataAccessor:processParty() Begin..
2009.03.03 at 11:31:21:931: Thread-24: B2B - (DEBUG) oracle.tip.adapter.b2b.tpa.RepoDataAccessor:processParty() COMSTOR is hosted party
2009.03.03 at 11:31:21:931: Thread-24: B2B - (DEBUG) oracle.tip.adapter.b2b.tpa.RepoDataAccessor:processParty() End..
2009.03.03 at 11:31:21:931: Thread-24: B2B - (DEBUG) oracle.tip.adapter.b2b.tpa.TPAProcessor:processTPA() after calling processparty with : TPName: COMSTOR Type: null Value: null
2009.03.03 at 11:31:21:931: Thread-24: B2B - (DEBUG) oracle.tip.adapter.b2b.tpa.TPAProcessor:processTPA() PARTIES (after calling processParty):
initial : null
from : TPName: COMSTOR Type: null Value: null
to : TPName: BTGS Type: null Value: null
final : null
initiating : TPName: COMSTOR Type: null Value: null
2009.03.03 at 11:31:21:931: Thread-24: B2B - (DEBUG) oracle.tip.adapter.b2b.tpa.TPAProcessor:processTPA() docTypeName: Pip3A4PurchaseOrderConfirmation docTypeRevision: V02.03.00
2009.03.03 at 11:31:21:931: Thread-24: B2B - (DEBUG) oracle.tip.adapter.b2b.tpa.TPAProcessor:processTPA() actionName: PurchaseOrderConfirmationAction actionRevision: V02.03.00
2009.03.03 at 11:31:21:931: Thread-24: B2B - (DEBUG) oracle.tip.adapter.b2b.tpa.RepoDataAccessor:getCollaborationDetails() Begin.. Activity Name : PurchaseOrderConfirmationAction Activity Version: V02.03.00
2009.03.03 at 11:31:21:962: Thread-24: B2B - (DEBUG) calling setMode() changing from -1 to 2
2009.03.03 at 11:31:21:977: Thread-24: B2B - (DEBUG) calling setMode() changing from 2 to 2
2009.03.03 at 11:31:21:977: Thread-24: B2B - (DEBUG) calling setValidationEnabled() changing from null to false
2009.03.03 at 11:31:21:977: Thread-24: B2B - (DEBUG) oracle.tip.adapter.b2b.tpa.RepoDataAccessor:addCollaborationDetails() End..
2009.03.03 at 11:31:21:977: Thread-24: B2B - (DEBUG) oracle.tip.adapter.b2b.tpa.TPAProcessor:processTPA() eventName:<PurchaseOrderConfirmationAction>
2009.03.03 at 11:31:21:977: Thread-24: B2B - (DEBUG) oracle.tip.adapter.b2b.tpa.TPAProcessor:processTPA() messageType:1
2009.03.03 at 11:31:21:977: Thread-24: B2B - (DEBUG) calling setInitiatingPartyId() changing from TPName: COMSTOR Type: null Value: null to TPName: COMSTOR Type: null Value: null
2009.03.03 at 11:31:21:977: Thread-24: B2B - (DEBUG) oracle.tip.adapter.b2b.tpa.TPAProcessor:processTPA() TPA Name : null
2009.03.03 at 11:31:21:977: Thread-24: B2B - (DEBUG) oracle.tip.adapter.b2b.tpa.TPAIdentifier:identifyTPA() Begin..
2009.03.03 at 11:31:21:977: Thread-24: B2B - (DEBUG) oracle.tip.adapter.b2b.tpa.TPAIdentifier:identifyTPA()
From Party -> null-null-COMSTOR-Buyer To Party -> null-null-BTGS-Seller Collaboration -> 3A4
2009.03.03 at 11:31:21:977: Thread-24: B2B - (DEBUG) RepoDataAccessor:getAgreementName(partyNAMES) Begin..
2009.03.03 at 11:31:21:977: Thread-24: B2B - (ERROR) Error -: AIP-50501: Trading partner agreement not found for the given input values: From party [NAME-ROLE] "COMSTOR-Buyer", To party [NAME-ROLE] "BTGS-Seller", Collaboration name "3A4"; also verify agreement effectiveToDate
     at oracle.tip.adapter.b2b.tpa.RepoDataAccessor.getAgreementName(RepoDataAccessor.java:2133)
     at oracle.tip.adapter.b2b.tpa.TPAIdentifier.identifyTPA(TPAIdentifier.java:180)
     at oracle.tip.adapter.b2b.tpa.TPAProcessor.processTPA(TPAProcessor.java:561)
     at oracle.tip.adapter.b2b.tpa.TPAProcessor.processOutgoingTPA(TPAProcessor.java:216)
     at oracle.tip.adapter.b2b.engine.Engine.processOutgoingMessage(Engine.java:1041)
     at oracle.tip.adapter.b2b.data.MsgListener.onMessage(MsgListener.java:833)
     at oracle.tip.adapter.b2b.data.MsgListener.run(MsgListener.java:400)
     at java.lang.Thread.run(Thread.java:534)
2009.03.03 at 11:31:21:977: Thread-24: B2B - (ERROR) Error -: AIP-50501: Trading partner agreement not found for the given input values: From party [NAME-ROLE] "COMSTOR-Buyer", To party [NAME-ROLE] "BTGS-Seller", Collaboration name "3A4"; also verify agreement effectiveToDate
     at oracle.tip.adapter.b2b.tpa.RepoDataAccessor.getAgreementName(RepoDataAccessor.java:2133)
     at oracle.tip.adapter.b2b.tpa.TPAIdentifier.identifyTPA(TPAIdentifier.java:180)
     at oracle.tip.adapter.b2b.tpa.TPAProcessor.processTPA(TPAProcessor.java:561)
     at oracle.tip.adapter.b2b.tpa.TPAProcessor.processOutgoingTPA(TPAProcessor.java:216)
     at oracle.tip.adapter.b2b.engine.Engine.processOutgoingMessage(Engine.java:1041)
     at oracle.tip.adapter.b2b.data.MsgListener.onMessage(MsgListener.java:833)
     at oracle.tip.adapter.b2b.data.MsgListener.run(MsgListener.java:400)
     at java.lang.Thread.run(Thread.java:534)
2009.03.03 at 11:31:21:977: Thread-24: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processOutgoingMessage B2BDomainException
2009.03.03 at 11:31:21:977: Thread-24: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:handleOutboundException Updating Error Message: Error -: AIP-50501: Trading partner agreement not found for the given input values: From party [NAME-ROLE] "COMSTOR-Buyer", To party [NAME-ROLE] "BTGS-Seller", Collaboration name "3A4"; also verify agreement effectiveToDate
2009.03.03 at 11:31:21:977: Thread-24: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Enter
2009.03.03 at 11:31:22:008: Thread-24: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Wire message not found.
2009.03.03 at 11:31:22:008: Thread-24: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Creating new b2berror object
2009.03.03 at 11:31:22:008: Thread-24: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Updating business message error information
2009.03.03 at 11:31:22:024: Thread-24: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Exit
2009.03.03 at 11:31:22:024: Thread-24: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:handleOutboundException Updating Native Event Tbl Row
2009.03.03 at 11:31:22:024: Thread-24: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:updateNativeEvtTblRow Enter
2009.03.03 at 11:31:22:024: Thread-24: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:
** DbAccess:updateNativeEvtTblRow:tip_wireMsg wiremsg not found
2009.03.03 at 11:31:22:024: Thread-24: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:handleOutboundException notifying App
2009.03.03 at 11:31:22:024: Thread-24: B2B - (DEBUG) Engine:notifyApp Enter
2009.03.03 at 11:31:22:024: Thread-24: B2B - (DEBUG) Enqueue Engine AQJMSCorrelationID = 91217C8567EB4A3EAC135BD382FD14E3
2009.03.03 at 11:31:22:024: Thread-24: 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>G20090303035936810.34565d:11fc706dc89:-7fbc@706519011</correlationId>
<b2bMessageId>G20090303035936810.34565d:11fc706dc89:-7fbc@706519011</b2bMessageId>
<errorCode>AIP-50501</errorCode>
<errorText>Trading partner agreement not found for the given input values: From party [NAME-ROLE] "COMSTOR-Buyer", To party [NAME-ROLE] "BTGS-Seller", Collaboration name "3A4"; also verify agreement effectiveToDate</errorText>
<errorDescription>
<![CDATA[Machine Info: (punin1879150941)
Description: Unable to identify the trading partner agreement from the given input values. Also verify agreement effectiveToDate
StackTrace:
Error -: AIP-50501: Trading partner agreement not found for the given input values: From party [NAME-ROLE] "COMSTOR-Buyer", To party [NAME-ROLE] "BTGS-Seller", Collaboration name "3A4"; also verify agreement effectiveToDate
     at oracle.tip.adapter.b2b.tpa.RepoDataAccessor.getAgreementName(RepoDataAccessor.java:2133)
     at oracle.tip.adapter.b2b.tpa.TPAIdentifier.identifyTPA(TPAIdentifier.java:180)
     at oracle.tip.adapter.b2b.tpa.TPAProcessor.processTPA(TPAProcessor.java:561)
     at oracle.tip.adapter.b2b.tpa.TPAProcessor.processOutgoingTPA(TPAProcessor.java:216)
     at oracle.tip.adapter.b2b.engine.Engine.processOutgoingMessage(Engine.java:1041)
     at oracle.tip.adapter.b2b.data.MsgListener.onMessage(MsgListener.java:833)
     at oracle.tip.adapter.b2b.data.MsgListener.run(MsgListener.java:400)
     at java.lang.Thread.run(Thread.java:534)
]]>
</errorDescription>
<errorSeverity>2</errorSeverity>
</Exception>
2009.03.03 at 11:31:22:024: Thread-24: B2B - (DEBUG) AQJMSCorrelationID = 91217C8567EB4A3EAC135BD382FD14E3
2009.03.03 at 11:31:22:039: Thread-24: B2B - (DEBUG) Engine:notifyApp Exit
2009.03.03 at 11:31:22:039: Thread-24: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:handleOutboundException Updated the Error Message Successfully: Error -: AIP-50501: Trading partner agreement not found for the given input values: From party [NAME-ROLE] "COMSTOR-Buyer", To party [NAME-ROLE] "BTGS-Seller", Collaboration name "3A4"; also verify agreement effectiveToDate
2009.03.03 at 11:31:22:039: Thread-24: B2B - (DEBUG) DBContext commit: Enter
2009.03.03 at 11:31:22:055: Thread-24: B2B - (DEBUG) DBContext commit: Transaction.commit()
2009.03.03 at 11:31:22:055: Thread-24: B2B - (DEBUG) DBContext commit: Leave
2009.03.03 at 11:31:22:055: Thread-24: B2B - (DEBUG) oracle.tip.adapter.b2b.data.MsgListener:onMessage Exit
As it can be seen from the logs, the message type is being set to 1. However it should be 2 in case of response.
The following header properties are being used in the AQ stub:-
msgID = G20090303035936810.34565d:11fc706dc89:-7fbc@706519011
from = COMSTOR
to = BTGS
doctypeName = Pip3A4PurchaseOrderConfirmation
doctypeRevision = V02.03.00
payload = Pip3A4_Response_POA10170020309.xml
attachment =
Can you please let us know the reason for the wrong message type being set?
Regards,
Ravi Shah

Dheeraj,
We have included msgType=2 as a part of the AQ header.
The logs show that message type is getting set to 2 but still COMSTOR is Buyer and BTGS is Seller.
Because of this, agreement look-up is getting failed.
2009.03.04 at 11:53:01:825: Thread-13: B2B - (DEBUG) oracle.tip.adapter.b2b.data.MsgListener:onMessage Enter
2009.03.04 at 11:53:01:825: Thread-13: B2B - (DEBUG) DBContext beginTransaction: Enter
2009.03.04 at 11:53:01:825: Thread-13: B2B - (DEBUG) DBContext beginTransaction: Transaction.begin()
2009.03.04 at 11:53:01:825: Thread-13: B2B - (DEBUG) DBContext beginTransaction: Leave
2009.03.04 at 11:53:01:825: Thread-13: B2B - (DEBUG) oracle.tip.adapter.b2b.data.MsgListener:onMessage Action Name: null
2009.03.04 at 11:53:01:825: Thread-13: B2B - (DEBUG) Generic Wizard:getTradingPartnerNames Enter
2009.03.04 at 11:53:01:825: Thread-13: B2B - (DEBUG) Generic Wizard:getTradingPartnerNames Exit
2009.03.04 at 11:53:01:825: Thread-13: B2B - (DEBUG) oracle.tip.adapter.b2b.data.MsgListener:onMessage All TPs list for broadcasting[]
2009.03.04 at 11:53:01:825: Thread-13: B2B - (DEBUG) oracle.tip.adapter.b2b.data.MsgListener:onMessage ipmsgold.get_MSG_ID()>G20090304062204707.e44c79:11fcbe016e5:-7fdc@706519011<
2009.03.04 at 11:53:01:825: Thread-13: B2B - (DEBUG) oracle.tip.adapter.b2b.data.MsgListener:onMessage ipmsg.getMessageID() >G20090304062204707.e44c79:11fcbe016e5:-7fdc@706519011<
2009.03.04 at 11:53:01:825: Thread-13: B2B - (DEBUG) AQJMSCorrelationID = 72E9465AA77D4B70A1D1F327F359E819
2009.03.04 at 11:53:01:825: Thread-13: B2B - (DEBUG) oracle.tip.adapter.b2b.data.MsgListener:onMessage ipmsg.getMessageID()>G20090304062204707.e44c79:11fcbe016e5:-7fdc@706519011<
2009.03.04 at 11:53:01:825: Thread-13: B2B - (DEBUG) oracle.tip.adapter.b2b.data.MsgListener:onMessage msgIdFrmBkEnd>G20090304062204707.e44c79:11fcbe016e5:-7fdc@706519011<
2009.03.04 at 11:53:01:825: Thread-13: B2B - (INFORMATION) oracle.tip.adapter.b2b.engine.Engine:processOutgoingMessage Enter
2009.03.04 at 11:53:01:825: Thread-13: B2B - (DEBUG) DBContext beginTransaction: Enter
2009.03.04 at 11:53:01:825: Thread-13: B2B - (DEBUG) DBContext beginTransaction: Leave
2009.03.04 at 11:53:01:825: Thread-13: B2B - (DEBUG) calling setFromPartyId() changing from null to TPName: COMSTOR Type: null Value: null
2009.03.04 at 11:53:01:825: Thread-13: B2B - (DEBUG) calling setToPartyId() changing from null to TPName: BTGS Type: null Value: null
2009.03.04 at 11:53:01:825: Thread-13: B2B - (DEBUG) calling setInitiatingPartyId() changing from null to TPName: null Type: null Value: null
2009.03.04 at 11:53:01:825: Thread-13: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processOutgoingMessage To TP NameBTGS
2009.03.04 at 11:53:01:825: Thread-13: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processOutgoingMessage From TP NameCOMSTOR
2009.03.04 at 11:53:01:825: Thread-13: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processOutgoingMessage business action name: null
2009.03.04 at 11:53:01:825: Thread-13: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processOutgoingMessage doctype name: Pip3A4PurchaseOrderConfirmation
2009.03.04 at 11:53:01:825: Thread-13: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processOutgoingMessage doctype revision: V02.00
2009.03.04 at 11:53:01:825: Thread-13: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processOutgoingMessage AppMsgIdG20090304062204707.e44c79:11fcbe016e5:-7fdc@706519011
2009.03.04 at 11:53:01:825: Thread-13: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processOutgoingMessage ipmsg.get_MSG_TYPE = 2
2009.03.04 at 11:53:01:825: Thread-13: B2B - (DEBUG) Engine AQJMSCorrelationID = 72E9465AA77D4B70A1D1F327F359E819
2009.03.04 at 11:53:01:825: Thread-13: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processOutgoingMessage using appMsgId as b2bMsgId
2009.03.04 at 11:53:01:825: Thread-13: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processOutgoingMessage B2B Message ID is G20090304062204707.e44c79:11fcbe016e5:-7fdc@706519011
2009.03.04 at 11:53:01:825: Thread-13: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processOutgoingMessage RefTo B2B Message ID is null
2009.03.04 at 11:53:01:825: Thread-13: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processOutgoingMessage isSignalMsg() == false; call outgoingTPA
2009.03.04 at 11:53:01:825: Thread-13: B2B - (DEBUG) oracle.tip.adapter.b2b.tpa.TPAProcessor:processOutgoingTPA() Begin TPA Processing..
2009.03.04 at 11:53:01:825: Thread-13: B2B - (DEBUG) oracle.tip.adapter.b2b.tpa.TPAProcessor:processTPA() PARTIES (before calling processParty) :
initial : null
from : TPName: COMSTOR Type: null Value: null
to : TPName: BTGS Type: null Value: null
final : null
initiating : TPName: null Type: null Value: null
2009.03.04 at 11:53:01:825: Thread-13: B2B - (DEBUG) oracle.tip.adapter.b2b.tpa.TPAProcessor:processTPA() direction is outgoing
2009.03.04 at 11:53:01:825: Thread-13: B2B - (DEBUG) oracle.tip.adapter.b2b.tpa.TPAProcessor:processTPA() calling processparty with : TPName: COMSTOR Type: null Value: null
2009.03.04 at 11:53:01:825: Thread-13: B2B - (DEBUG) oracle.tip.adapter.b2b.tpa.RepoDataAccessor:processParty() Begin..
2009.03.04 at 11:53:01:825: Thread-13: B2B - (DEBUG) oracle.tip.adapter.b2b.tpa.RepoDataAccessor:processParty() COMSTOR is hosted party
2009.03.04 at 11:53:01:825: Thread-13: B2B - (DEBUG) oracle.tip.adapter.b2b.tpa.RepoDataAccessor:processParty() End..
2009.03.04 at 11:53:01:841: Thread-13: B2B - (DEBUG) oracle.tip.adapter.b2b.tpa.TPAProcessor:processTPA() after calling processparty with : TPName: COMSTOR Type: null Value: null
2009.03.04 at 11:53:01:841: Thread-13: B2B - (DEBUG) oracle.tip.adapter.b2b.tpa.TPAProcessor:processTPA() PARTIES (after calling processParty):
initial : null
from : TPName: COMSTOR Type: null Value: null
to : TPName: BTGS Type: null Value: null
final : null
initiating : TPName: null Type: null Value: null
2009.03.04 at 11:53:01:841: Thread-13: B2B - (DEBUG) oracle.tip.adapter.b2b.tpa.TPAProcessor:processTPA() docTypeName: Pip3A4PurchaseOrderConfirmation docTypeRevision: V02.00
2009.03.04 at 11:53:01:841: Thread-13: B2B - (DEBUG) oracle.tip.adapter.b2b.tpa.TPAProcessor:processTPA() actionName: PurchaseOrderConfirmationAction actionRevision: V02.00
2009.03.04 at 11:53:01:841: Thread-13: B2B - (DEBUG) oracle.tip.adapter.b2b.tpa.RepoDataAccessor:getCollaborationDetails() Begin.. Activity Name : PurchaseOrderConfirmationAction Activity Version: V02.00
2009.03.04 at 11:53:01:856: Thread-13: B2B - (DEBUG) calling setMode() changing from -1 to 2
2009.03.04 at 11:53:01:872: Thread-13: B2B - (DEBUG) calling setMode() changing from 2 to 2
2009.03.04 at 11:53:01:872: Thread-13: B2B - (DEBUG) calling setValidationEnabled() changing from null to false
2009.03.04 at 11:53:01:872: Thread-13: B2B - (DEBUG) oracle.tip.adapter.b2b.tpa.RepoDataAccessor:addCollaborationDetails() End..
2009.03.04 at 11:53:01:872: Thread-13: B2B - (DEBUG) oracle.tip.adapter.b2b.tpa.TPAProcessor:processTPA() eventName:<PurchaseOrderConfirmationAction>
2009.03.04 at 11:53:01:872: Thread-13: B2B - (DEBUG) oracle.tip.adapter.b2b.tpa.TPAProcessor:processTPA() messageType:2
2009.03.04 at 11:53:01:872: Thread-13: B2B - (DEBUG) calling setInitiatingPartyId() changing from TPName: null Type: null Value: null to TPName: COMSTOR Type: null Value: null
2009.03.04 at 11:53:01:872: Thread-13: B2B - (DEBUG) oracle.tip.adapter.b2b.tpa.TPAProcessor:processTPA() cpaID=null
2009.03.04 at 11:53:01:872: Thread-13: B2B - (DEBUG) oracle.tip.adapter.b2b.tpa.TPAProcessor:processTPA() TPA Name : null
2009.03.04 at 11:53:01:872: Thread-13: B2B - (DEBUG) oracle.tip.adapter.b2b.tpa.TPAProcessor:processTPA() TPA Name : null
2009.03.04 at 11:53:01:872: Thread-13: B2B - (DEBUG) oracle.tip.adapter.b2b.tpa.TPAIdentifier:identifyTPA() Begin..
2009.03.04 at 11:53:01:872: Thread-13: B2B - (DEBUG) oracle.tip.adapter.b2b.tpa.TPAIdentifier:identifyTPA()
From Party -> null-null-COMSTOR-Buyer To Party -> null-null-BTGS-Seller Collaboration -> 3A4
2009.03.04 at 11:53:01:872: Thread-13: B2B - (DEBUG) RepoDataAccessor:getAgreementName(partyNAMES) Begin..
2009.03.04 at 11:53:01:872: Thread-13: B2B - (ERROR) Error -: AIP-50501: Trading partner agreement not found for the given input values: From party [NAME-ROLE] "COMSTOR-Buyer", To party [NAME-ROLE] "BTGS-Seller", Collaboration name "3A4"; also verify agreement effectiveToDate
     at oracle.tip.adapter.b2b.tpa.RepoDataAccessor.getAgreementName(RepoDataAccessor.java:2133)
     at oracle.tip.adapter.b2b.tpa.TPAIdentifier.identifyTPA(TPAIdentifier.java:180)
     at oracle.tip.adapter.b2b.tpa.TPAProcessor.processTPA(TPAProcessor.java:589)
     at oracle.tip.adapter.b2b.tpa.TPAProcessor.processOutgoingTPA(TPAProcessor.java:221)
     at oracle.tip.adapter.b2b.engine.Engine.processOutgoingMessage(Engine.java:1060)
     at oracle.tip.adapter.b2b.data.MsgListener.onMessage(MsgListener.java:833)
     at oracle.tip.adapter.b2b.data.MsgListener.run(MsgListener.java:400)
     at java.lang.Thread.run(Thread.java:534)
2009.03.04 at 11:53:01:872: Thread-13: B2B - (ERROR) Error -: AIP-50501: Trading partner agreement not found for the given input values: From party [NAME-ROLE] "COMSTOR-Buyer", To party [NAME-ROLE] "BTGS-Seller", Collaboration name "3A4"; also verify agreement effectiveToDate
     at oracle.tip.adapter.b2b.tpa.RepoDataAccessor.getAgreementName(RepoDataAccessor.java:2133)
     at oracle.tip.adapter.b2b.tpa.TPAIdentifier.identifyTPA(TPAIdentifier.java:180)
     at oracle.tip.adapter.b2b.tpa.TPAProcessor.processTPA(TPAProcessor.java:589)
     at oracle.tip.adapter.b2b.tpa.TPAProcessor.processOutgoingTPA(TPAProcessor.java:221)
     at oracle.tip.adapter.b2b.engine.Engine.processOutgoingMessage(Engine.java:1060)
     at oracle.tip.adapter.b2b.data.MsgListener.onMessage(MsgListener.java:833)
     at oracle.tip.adapter.b2b.data.MsgListener.run(MsgListener.java:400)
     at java.lang.Thread.run(Thread.java:534)
2009.03.04 at 11:53:01:872: Thread-13: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processOutgoingMessage B2BDomainException
2009.03.04 at 11:53:01:872: Thread-13: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:handleOutboundException Updating Error Message: Error -: AIP-50501: Trading partner agreement not found for the given input values: From party [NAME-ROLE] "COMSTOR-Buyer", To party [NAME-ROLE] "BTGS-Seller", Collaboration name "3A4"; also verify agreement effectiveToDate
2009.03.04 at 11:53:01:872: Thread-13: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Enter
2009.03.04 at 11:53:01:872: Thread-13: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Wire message not found.
2009.03.04 at 11:53:01:888: Thread-13: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Creating new business message
2009.03.04 at 11:53:01:888: Thread-13: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:insertMsgTblRow Enter
2009.03.04 at 11:53:01:903: Thread-13: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:insertMsgTblRow toparty name BTGS
2009.03.04 at 11:53:01:903: Thread-13: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:insertMsgTblRow toparty type and value nullnull
2009.03.04 at 11:53:01:903: Thread-13: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:insertMsgTblRow BusinessAction for the given name PurchaseOrderConfirmationAction BusinessAction_9516
2009.03.04 at 11:53:01:903: Thread-13: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Creating new b2berror object
2009.03.04 at 11:53:01:903: Thread-13: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Updating business message error information
2009.03.04 at 11:53:01:903: Thread-13: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Exit
2009.03.04 at 11:53:01:903: Thread-13: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:handleOutboundException Updating Native Event Tbl Row
2009.03.04 at 11:53:01:903: Thread-13: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:updateNativeEvtTblRow Enter
2009.03.04 at 11:53:01:919: Thread-13: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:
** DbAccess:updateNativeEvtTblRow:tip_wireMsg wiremsg not found
2009.03.04 at 11:53:01:919: Thread-13: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:handleOutboundException notifying App
2009.03.04 at 11:53:01:919: Thread-13: B2B - (DEBUG) Engine:notifyApp Enter
2009.03.04 at 11:53:01:919: Thread-13: B2B - (DEBUG) Enqueue Engine AQJMSCorrelationID = 72E9465AA77D4B70A1D1F327F359E819
2009.03.04 at 11:53:01:919: Thread-13: 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>G20090304062204707.e44c79:11fcbe016e5:-7fdc@706519011</correlationId>
<b2bMessageId>G20090304062204707.e44c79:11fcbe016e5:-7fdc@706519011</b2bMessageId>
<errorCode>AIP-50501</errorCode>
<errorText>Trading partner agreement not found for the given input values: From party [NAME-ROLE] "COMSTOR-Buyer", To party [NAME-ROLE] "BTGS-Seller", Collaboration name "3A4"; also verify agreement effectiveToDate</errorText>
<errorDescription>
<![CDATA[Machine Info: (punin1879150986)
Description: Unable to identify the trading partner agreement from the given input values. Also verify agreement effectiveToDate
StackTrace:
Error -: AIP-50501: Trading partner agreement not found for the given input values: From party [NAME-ROLE] "COMSTOR-Buyer", To party [NAME-ROLE] "BTGS-Seller", Collaboration name "3A4"; also verify agreement effectiveToDate
     at oracle.tip.adapter.b2b.tpa.RepoDataAccessor.getAgreementName(RepoDataAccessor.java:2133)
     at oracle.tip.adapter.b2b.tpa.TPAIdentifier.identifyTPA(TPAIdentifier.java:180)
     at oracle.tip.adapter.b2b.tpa.TPAProcessor.processTPA(TPAProcessor.java:589)
     at oracle.tip.adapter.b2b.tpa.TPAProcessor.processOutgoingTPA(TPAProcessor.java:221)
     at oracle.tip.adapter.b2b.engine.Engine.processOutgoingMessage(Engine.java:1060)
     at oracle.tip.adapter.b2b.data.MsgListener.onMessage(MsgListener.java:833)
     at oracle.tip.adapter.b2b.data.MsgListener.run(MsgListener.java:400)
     at java.lang.Thread.run(Thread.java:534)
]]>
</errorDescription>
<errorSeverity>2</errorSeverity>
</Exception>
2009.03.04 at 11:53:01:919: Thread-13: B2B - (DEBUG) AQJMSCorrelationID = 72E9465AA77D4B70A1D1F327F359E819
2009.03.04 at 11:53:01:950: Thread-13: B2B - (DEBUG) Engine:notifyApp Exit
2009.03.04 at 11:53:01:950: Thread-13: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:handleOutboundException Updated the Error Message Successfully: Error -: AIP-50501: Trading partner agreement not found for the given input values: From party [NAME-ROLE] "COMSTOR-Buyer", To party [NAME-ROLE] "BTGS-Seller", Collaboration name "3A4"; also verify agreement effectiveToDate
2009.03.04 at 11:53:01:950: Thread-13: B2B - (DEBUG) DBContext commit: Enter
2009.03.04 at 11:53:01:950: Thread-13: B2B - (DEBUG) DBContext commit: Transaction.commit()
2009.03.04 at 11:53:01:950: Thread-13: B2B - (DEBUG) DBContext commit: Leave
2009.03.04 at 11:53:01:950: Thread-13: B2B - (DEBUG) oracle.tip.adapter.b2b.data.MsgListener:onMessage Exit
Can you please look into this?
Regards,
Ravi Shah

Message interface with two types of message types

Hi experts,
I am having problem that a proxy cannot be generated because of the (mixed) types of the message types that the interface is using.
The first message type is defined in the repository and another is defined as an external definition, imported in from an outside source.
Here is the SAP message I received when I tried to generate the proxy for this interface.
+++++++++++++++++++++++++++++++++++++++++++++
Interface uses external and internal message definitions
Message no. SPRX122
Diagnosis
In a message interface you can use messages from different sources:
1. Message types and fault message types edited in the Integration Repository
2. Messages imported into the Integration Repository (external definitions, RFC, IDoc)
In the current message interface, message types from different sources have been used.
Since messages from these different sources must be handled differently during proxy generation, such a mixture of messages within a message interface is not possible.
System Response
The interface cannot be generated.
Procedure
Change the interface definition accordingly in the Integration Repository.
++++++++++++++++++++++++++++++++++++++++++
The imported xsd is quite large and also contain many large includes. I don't have the option of creating the message type manually.
Any suggestions?
Thank you,
-michelle

Hi all,
I tried several things and the problem is still not resolved. This is what I learned.
First of all, I believed the SAP message about mixing of internal and external message is misleading or even wrong. I tried with both message types being external but I still get the same message that the interface has one internal and the other external message type.
Secondly, since Arvind suggested that I might have used an xml element that is not currently supported by ABAP proxy, I then change to another definition with the most simplest elements. I then attached this other definition to the interface and tried generating the proxy again. I still get the same system message that I am using mixing of message types in one interface.
My conclusion is XI still is not capable of generating ABAP proxy from external definition.
Does anyone have any comments/suggestion/experience on this issue?
Best regards,
-michelle

Creation of New Message Type for Extended IDoc

Dear Friends,
I want to create New Message Type for MATMAS and want to Active Change Pointers accordingly. Thru this Message Type how can I able to use Extended IDoc which I have created for Basic Idoc Type MATMAS05.
I am Sending Data from SAP to XI ; Any one can help me in this How can I create the Message Type with the IDoc Extn .
for Change Pointers.
Warm Regards,
Naveen Mutyapu.

Hi naveen mutyapu,
see these links
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm#_Toc8400404
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a6620507d11d18ee90000e8366fc2/frameset.htm
http://www.sappoint.com/presentation.html
http://www.allsaplinks.com/idoc_search.html
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://www.erpgenie.com/sapedi/idoc_abap.htm
http://www.allinterview.com/rss/interview-questions/new/SAP-ALE-IDocs.xml
happy learning.
thanks
karthik

How to change the HTTP Response as XML (Content Type "text\xml") When Post

Hi Friends ,
I have created one RFC Destination TYPE H . When i am trying to post some XML Message to that particular HTTP Service using POST method . It succesfully accepted the XML File but , it is returning the String as " OK" . In the connection test trace i have seen the Content Type as "text/html" but * I need to get as XML format no Srting ( Type "text\xml" . ) *
I need to get response back as XML not plain text .
1 Any Configuration setting do we need to do on Service (SICF ) ?
2. Or any other place we need to modify to get the HTTP Response as XML not plain text
Can you please help to solve the problem . Any clue ?
Thanks & Regards.,
V.Rangarajan

Dear users,
we have requirement sending SMS to the customers mobiles. I am successfully sending the messages to the customers mobiles by using the above method. Facing issues with response message. The response messages is in plain text fromat in single line like...Sent
Using HTTP_AAE Receiver adapter.
The response message was failed while excution of the message mapping with the error
Mapping failed in runtimeRuntime Exception when executing application mapping program com/sap/xi/tf/_MM_SMS_CUST_RES_; Details: com.sap.aii.utilxi.misc.api.BaseRuntimeException; Content is not allowed in prolog.
please share the comments how to pass the Status of the message to SAP ECC from SAP HTTP adapter
Regards,
Sudir.

Guide for Fault Message Type

Hi,
I search a guide for configuration a "Fault Message Type".
I have read, if there is a mapping error, XI will create a error handling in a xml-file.
But I can not find this file.
Can you help me please?
Thanks.
Regards
Stefan

Hi Stefan,
Exception can be declared in BPM steps like Transform,send,Block and handled in Exception Branch.
TO know more about BPM and its exception go throught this link,
http://help.sap.com/saphelp_nw04/helpdata/en/3c/831620a4f1044dba38b370f77835cc/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/3c/831620a4f1044dba38b370f77835cc/frameset.htm
Cheers,
Rashmi

How to convert an ISO 8583 message format to XML and vice versa within OSB.

Hi Guys,
Can anyone help me out with this problem.
ISO8583 message is used in bank or financial institutes for card-originated transactions
Example of an ISO8583 message:
02004200040000000002161234567890123456060
9173030123456789ABC1000123456789012345678
90123456789012345678901234567890123456789
0123456789012345678901234567890123456789
Where:
0200 - MTI (Message Type Indicator),
4200040000000002 - primary bitmap,
1234567890123456 - field 2,
0609173030 - field 7,
123456789ABC - field 22,
012345678901234567890123456789012345678901234567890\
1234567890123456789012345678901234567890123456789 - field 63.

Hi guys,
I was trying to do this transformation(ISO8583-XML). But I am stuck in the process of creating the MFL file. Can somebody help me with the details.
Can somebody help me with the following.
Field Type:
Field Occurance:
Field Attributes:
Termination:
Code Page:
salil

Removing message type tag in output file

Hi guys,
I'm new to XI. I have done an xml file to xml file scenario. It is working successfully
The output file has a format
<?xml version="1.0" encoding="UTF-8"?>
<ns0:mt_xml_receiver xmlns:ns0="http://xml2xml">
     <DETAILS>
          <ID>111</ID>
          <NAME>Varun</NAME>
          <LOCATION>India</LOCATION>
          <ADD>Bangalore</ADD>
          <MOBILE>46572727</MOBILE>
          <EMAIL>[email protected]</EMAIL>
     </DETAILS>
</ns0:mt_xml_receiver>
I want to remove the additional tag present for the message type and i want the output in the format
<?xml version="1.0" encoding="UTF-8"?>
     <DETAILS>
          <ID>111</ID>
          <NAME>Varun</NAME>
          <LOCATION>India</LOCATION>
          <ADD>Bangalore</ADD>
          <MOBILE>46572727</MOBILE>
          <EMAIL>[email protected]</EMAIL>
     </DETAILS>
Can any one help me on how to achieve this???
Pl help me on this guys
Regards
Varun

HI Varun,
This will help you..
In the message type <b>mt_xml_receive</b>r there is a box where the namespace name is specified.
Simply delete the same and activate the message type.
In your case what you can do is as you dont want the message type name also.
you can create the message type name as DETAILS instead of mt_xml_receiver.
Regards,
Sumit
ps : reward points if tht helped u.

Sender File/FTP Adapter - Matching Input to Message Type

Hi,
I have a sender file/ftp adapter which is using content conversion to generate an XML document from the contents of a text file. This works fine and when I go into the SXI Monitor I can see the XML document I expect:
<ns:DN_360BalanceExtract xmlns:ns="http://xxx">
<ns:RN_360BalanceExtract xmlns:ns="http://xxx">
<BalanceRecord>
   <SerialNo>xx10000780</SerialNo>
   <RegNo>A1</RegNo>
   <LocationTicketIssued>ALBERT ROAD SOUTH</LocationTicketIssued>
   <DateOfOffence>2008-02-15</DateOfOffence>
   <TimeOfOffence>13:38</TimeOfOffence>
   <OffenceDescription>xxx</OffenceDescription>
   <CurrentStateOfCase>RE-OPENED; CLOSED IN ERROR</CurrentStateOfCase>
   <OutstandingBalance>70.00</OutstandingBalance>
   </BalanceRecord
<BalanceRecord>
   <SerialNo>xx90001245</SerialNo>
   <RegNo>S849KMR</RegNo>
   <LocationTicketIssued>ALBION PLACE</LocationTicketIssued>
   <DateOfOffence>2011-03-01</DateOfOffence>
   <TimeOfOffence>10:59</TimeOfOffence>
   <OffenceDescription>xxx1</OffenceDescription>
   <CurrentStateOfCase>xxx</CurrentStateOfCase>
   <OutstandingBalance>60.00</OutstandingBalance>
</BalanceRecord>
</ns:RN_360BalanceExtract>
</ns:DN_360BalanceExtract>
Having created the XML document from a text file I now wish to use the XML as input to a web service. This will of course involve mapping the XML document to a message in the inbound interface. Question is how do associate the XML generated with a Message Type in the outbound interface. Do I need to make sure the Document or Recordset names match that of a Message Type ?
Cheers,
PaulC.

Hi Paul
The content conversion will create a document like that if you insert DN_360BalanceExtract as Document name, "http://xxx" as namespace.
RN_360BalanceExtract will probably be your recordset, with its namespace.
More information about content conversion on sender file adapter:
http://help.sap.com/saphelp_nw04/helpdata/EN/ae/d03341771b4c0de10000000a1550b0/frameset.htm
I'm not sure what you mean by bound. If you mean that PI has to execute mapping you created for that DN_360BalanceExtract message type, you need to associate DN_360BalanceExtract to a message interface and then create all configuration objects and choose that message mapping when you create the interface determination object.
Regards,
Giuseppe

Message Type in XML ??

Similar Messages

Maybe you are looking for