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

Similar Messages

Error while sending data from XI to BI System

Hello Friends,
I m facing an error while sending data from XI to BI. XI is successfully recived data from FTP.
Given error i faced out in communication channel monitoring:-
Receiver channel 'POSDMLog_Receiver' for party '', service 'Busys_POSDM'
Error can not instantiate RfcPool caused by:
com.sap.aii.af.rfc.RfcAdapterException: error initializing RfcClientPool:com.sap.aii.af.rfc.core.repository.RfcRepositoryException: can not connect to destination system due to: com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to SAP gateway failed
Connect_PM TYPE=A ASHOST=10.1.45.35 SYSNR=01 GWHOST=10.1.45.35 GWSERV=sapgw01 PCS=1
LOCATION CPIC (TCP/IP) on local host with Unicode
ERROR partner '10.1.45.35:sapgw01' not reached
TIME Fri Apr 16 08:15:18 2010
RELEASE 700
COMPONENT NI (network interface)
VERSION 38
RC -10
MODULE nixxi.cpp
LINE 2823
DETAIL NiPConnect2
SYSTEM CALL connect
ERRNO 10061
ERRNO TEXT WSAECONNREFUSED: Connection refused
COUNTER 2
Error displaying in message monitoring:-
Exception caught by adapter framework: RfcAdapter: receiver channel has static errors: can not instantiate RfcPool caused by: com.sap.aii.af.rfc.RfcAdapterException: error initializing RfcClientPool:com.sap.aii.af.rfc.core.repository.RfcRepositoryException: can not connect to destination system due to: com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=10.1.45.35 SYSNR=01 GWHOST=10.1.45.35 GWSERV=sapgw01 PCS=1 LOCATION CPIC (TCP/IP) on local host with Unicode ERROR partner '10.1.45.35:sapgw01' not reached TIME Fri Apr 16 08:15:18 2010 RELEASE 70
Delivery of the message to the application using connection RFC_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: RfcAdapter: receiver channel has static errors: can not instantiate RfcPool caused by: com.sap.aii.af.rfc.RfcAdapterException: error initializing RfcClientPool:com.sap.aii.af.rfc.core.repository.RfcRepositoryException: can not connect to destination system due to: com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=10.1.45.35 SYSNR=01 GWHOST=10.1.45.35 GWSERV=sapgw01 PCS=1 LOCATION CPIC (TCP/IP) on local host with Unicode ERROR partner '10.1.45.35:sapgw01' not reached TIME.
Kindly suggest me & provide details of error.
Regards,
Narendra

Hi Narendra,
Message is clearly showing that your system is not reachable
102) RFC_ERROR_COMMUNICATION: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=10.1.45.35 SYSNR=01 GWHOST=10.1.45.35 GWSERV=sapgw01 PCS=1 LOCATION CPIC (TCP/IP) on local host with Unicode ERROR partner '10.1.45.35:sapgw01' not reached
Please check to ping the BI server IP 10.1.45.35 from your XI server , in case its working you can check telnet to SAP standard port like 3201/3601/3301/3901 etc.
It seems to be connectivity issue only.
Make sure your both the systems are up and running.
Revert back after checking above stuff.
Regards,
Gagan Deep Kaushal

Error while sending mail from SAP

Hello All,
Recently we are facing an error while sending mail from SAP. When we try to compose a message ,it is moving to a dump error RAISE_EXCEPTION.
The details from ST22,
Short text
    Exception condition "FOLDER_NOT_EXIST" raised.
Error analysis
    A RAISE statement in the program "SA
    condition "FOLDER_NOT_EXIST".
    Since the exception was not intercep
    program, processing was terminated.
Kindly suggest..
Thank You,
Regards,
Hasan

Hello Priyanka,
Actually, I performed the following two steps in order to solve the issue:
- In transaction SICF, the node for SAPConnect must be active. In our system, this node was in inactive state. Hence I activated it.
- Then In transaction SCOT-> Settings menu--> default domain should be 'xyz.com' if the email addresses in your company are maintained with a suffix xyz.com.
But for me the problem didnt get solved here..
The problem that i am facing now is that if in my user profile, I have the email address maintained, then i get an error saying 'Sender address rejected'. However, if i goto transaction SU01 and clear the email id, the mail is successfully sent to outer world.
You can try the above mentioned two steps using SICF and SCOT. If the problem does not get solved then try clearing the mail id in ur user profile.
Hope this helps. If you find an answer to the problem of the mail id getting cleared, then please let me know..
Regards,
Himanshu

Error While sending infopackages from OLTP to BI/urgent

Hi BW friends
im workin on production support and im new to it.while
running infopackage X ,it is throwing a error
error:While sending infopackages from OLTP to BI/urgent
In status tab it shows traingular yellow colour
and diagnosis says that No idocs could be sent to bi using rfc.
so if u know please reply me
Thank you
Amarnath k

while loading data into the target we got this message and the solution is do manual update for that.

"...an error occurred while sending data from the iPhone" - caused by latest iPhone update today?

I've been syncing my iPhone to my (non-apple) desktop for several months without difficulty.
Today I accepted the latest upgrade to my iPhone software.
Since it installed, it will not sync.
It gives the error message "iTunes could not sync calendars to the iPhone "Steve's iPhone" because an error occurred while sending data from the iPhone." After rebooting the desktop, the error repeats, and it's now in hour 2 of the continuing message "Syncing Steve's iPhone (Step 2 of 2) - Finishing sync"
Has anyone else run into this Undocumented Feature of the latest upgrade?
As bugs go, this is pretty serious for those of us who depend on syncing the iPhone and desktop for our business!
Thanks to anyone who can help!
Steve Callender

Tried rebooting the phone, and now it works.
Guess there's 2 lessons here -
Boot again when installing new SW, even if the phone reboots itself during installation, and
Boot to see if that fixes a problem before posting it.
Steve

Deadlock issue while sending data from PI to JDBC !!!

Hi All,
We are getting below error while sending data from PI to JDBC (Database).
Error - JDBC message processing failed; reason Error processing request in sax parser: Error when executing statement for table/stored proc. 'store_order_details' (structure 'Order_details_Statement'): com.microsoft.sqlserver.jdbc.SQLServerException: Transaction (Process ID 61) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.
This is happening when more than one PI message is trying to deliver data at the same time to database.
Can anyone let us know the root cause of this issue and how we can rectify this.
Is there some setting which we can use to do parallel processing as Delivering one message at a time to database is causing performance issues & taking lot of time.
Thanks
Neha Verma

Hello Neha,
Strange but can please get below information.
Please check with the DB admin about if the user is getting locked or is there any hanging threads related to user.
Also confirm with DB admin if the exclusive lock is on table or on the row when you try insertign or updating information.
You can share the user from the receiver channel.
Regards,
Hiren A.

IDOC FAILURE while sending data from ZEB_HCm systen to ZRA-EREC SYS

Hi
Experts
I am having idoc failure while sending data from HCM SYSTEM to EREC systems.
From that Data records i found the failure recored containing PERNR.
and from status record the
ERROE IS : No status information available for object CANDIDATE
Message no. HRRCF0001073
usually i used to run PFAL for these king of issues , when i tried to run PFAL for the PERNR it is giving the same errroe,
So pls suggest how to send the data to resiolve this .
Regards
Suresh

Hi Nitin,
The IDOC when came in Erec system is in error status ( 51).
When i saw the data records, only pernr were mentioned.
Then i send the idoc thru PFAL again by sending all information as O-C-S-P.
Still it is giving me the same error.

Why would I be receiving texts on iPad,but now cannot send response from the iPad?

Wondering why I am receiving texts on iPad, but now cannot send response from it.

Have you tried resetting your iPad? Press on the Home and Power buttons and hold both down until the Silver Apple appears. Once the Home screen displays, try messaging again.
Cheers,
GB

Authentication Error while Sending Email from SMTP server.

Authentication Error while Sending Email from SMTP server. Can receive emails but cannot send emails from this account.

no email account was setup on the phone unless it was issued by your company.
gmail is required but no server address ports to enter.
my gmail account was setup before i took delivery of the phone but could have been done when phone was activated.
i added cox pop3 email and had to manually enter both pop3 and smtp servers with both boxes checked on both servers.
i doubt if it's a verizon issue.

Need solution for the following sync error: "iTunes could not sync calendars to the iPad "iPad name" because an error occurred while sending data from the iPad"

Need solution for the following sync error: "iTunes could not sync calendars to the iPad "iPad name" because an error occurred while sending data from the iPad"

I want to add that I deleted all the old back-ups and created a new back-up without any issues except sync problem.

IDOC - message type WMMBXY(Stock transfer from quality to unrestricted)

Hi Gurus,
I have IDOC problem.
Inbound message type WMMBXY(Stock transfer from quality to unrestricted), The status if I check in WM02 of Doc is "51-Application document not posted"
Error Message ""Required function
MB_CREATE_GOODS_MOVEMENT is not being processed".
Please Help.
Prashant

Hi
The Idoc whcile Posting using Message type WMMBXY calls the Function module L_IDOC_INPUT_WMMBXY & in turn this calls the function module MB_CREATE_GOODS_MOVEMENT.
This function is not getting executed.
Please check if the Movemnt type used is not active for WM movemnts.
If you have used previously this movemnt type & now it is not working. Please take hlep of ABAPer for debugging & finding the Root cause
Thanks & Regards
Kishore

ALE message type WMTORD sending ST meins

good morning/afternoon to all,
we are in the process of setting up a 3rd party warehouse/miniload system and they connect using ALE. the 3rd party system is not a SAP system. our system is 4.7C. we are being asked to use this message type (WMTORD - standard) to send transport orders. they receive the idoc successfully with correct information, except for the unit of measure field meins. they receive the untranslated unit of measure ST, instead of EA.
is there a fix for this? can this be changed with standard code, or is a user exit needed. and, if the user exit is needed, why does for example the message type MATMAS send a EA and not the ST? i do have the global unit or measure ST setup to send EA in spro.
thanks in advance.

it looks like no one knows the answer...
here is what i found (for future reference)
enhancement MWMIDO01
component(fm) - EXIT_SAPLLIDO_001
include - ZXLIDU01
code example
tables: e1ltori.
loop at t_idoc_data.
if t_idoc_data-segnam = 'E1LTORI'.
    move t_idoc_data-sdata to e1ltori.
    if e1ltori-meins = 'ST'.
      move 'EA' to e1ltori-meins.
    endif.
    move e1ltori to t_idoc_data-sdata.
    modify t_idoc_data.
endif.
endloop.
*****solved*****

Error while sending emails from SOA 11G BPEL

Hi All,
I have configured an error email in my catch/catch-all blocks. Incase I dont have any retry action in my faultpolicies.xml file, the error email is sent fine. However if any remote/binding fault occurs and retry is done on partnerlink, in those cases the Error Notification service fails with below error:
ORABPEL-31015
Error while sending notification.
Error while sending notification to email.
Possible causes : SDPMessaging Driver not configured; Invalid To Address is used; Email server/Messaging gateway is down; using IP address as part of email ID instead of domain name;.
Caused by: javax.naming.NameNotFoundException: While trying to look up comp/env/ejb/services/NotificationServiceBean in /app/ejb/ejb_ob_engine_wls.jar#BPELActivityManagerBean.; remaining name 'comp/env/ejb/services/NotificationServiceBean'
sendEmailNotification WSIF Exception occured. Please check stack trace "Cannot get Object part 'Responses'. No parts are set on the message"
If I throw a remote/binding fault (throw activity), the error email gets sent. However whenever the retry happens incase of a fault, the above error comes.
Any idea what can be reason behing this...
Regards
Subhankar

try to call a sub process from your catch all block and use the email activity in that subprocess. this should work

Issue while sending SMS from JavaMail in languages like Russian & Japanese

Hi,
We have a requirement to send multi lingual SMS to users mobile number.
We are using JavaMail API for this. The only changes we have done to send SMS (instead of EMAIL) using a standard JavaMail code are –
1)     Use the suffix @sms after the mobile number. For eg: 919923456789@sms.<domain>.com.
2)     Use “text/plain” instead of “text/html” while setting the content type.
The SMS is sent fine for English and French but we get junk characters for languages like Japanese and Russian even on phones which support these languages.
Could anyone please advice on the below points –
1)     Is this a limitation with respect to JavaMail? If yes, is there any other api that can be used?
2)     Does some setting needs to be done in the SMS gateway to enable sending SMS in Japanese and Russian?
3)     Does some setting needs to be done in the mobile phone to receive SMS in Japanese and Russian?
Any help on this issue will be appreciated.
Thanks and Regards,
Jacob

Thanks for your replies...... Please find below the code snippet where I am setting the encoding.....Could you please confirm if this is the correct way?
String subject = "\u0421\u0442\u0430\u0442\u0443\u0441 \u043F\u043E\u0441\u043B\u0435\u0434\u043D\u0435\u0433\u043E \u043E\u0431\u043D\u043E\u0432\u043B\u0435\u043D\u0438\u044F";
String body = "\u0421\u0442\u0430\u0442\u0443\u0441 \u043F\u043E\u0441\u043B\u0435\u0434\u043D\u0435\u0433\u043E \u043E\u0431\u043D\u043E\u0432\u043B\u0435\u043D\u0438\u044F";
*//Both 'body' and 'subject' are set as the russian translation of 'Status last updated'.*
MimeMessage msg = new MimeMessage(mailSession);
msg.setHeader("Content-Type", "text/plain; charset=UTF-16");
msg.setSubject(subject, "UTF-16");
msg.setText(body, "UTF-16");
I tried this but still not getting correct text. If I try with "UTF-16BE"/"UTF-16LE", then I do not get an SMS at all. I have tried with UTF-8 as well.
Does it matter if I change the phone language before/after I receive the message in a language different from the currently set phone language?
I am based out of India and am trying to send these messages to some of my colleagues who are all using Indian service providers. I have tried this on phones which have Russian as a language option.
Regards,
Jacob

Variable initialized with wrong message type

Hi,
I have a BPEL process variableA of Message type A as defined in the partnerlink WSDL file. This variable get initialized during operation A from the partnerlink. The WSDL has another message type B defined for another operation B.
During runtime when operation A is called variable A gets initialized with message type A, however when operation B is invoked with mesage type B variableA gets initialized again with the content of message type B even though it's defined to be of message type A. Below are the snippets from the WSDL and BPEL process file
WSDL file ..
<message name="MessageTypeA">
<part name="payload" element="mpx:MessageARequest"/>
</message>
<message name="MessageTypeB">
<part name="payload" element="mpx:MessageBRequest"/>
</message>
<portType name="MutilPort">
<operation name="A">
<input message="tns:MessageTypeA"/>
</operation>
<operation name="BA">
<input message="tns:MessageTypeB"/>
</operation>
</portType>
Process BPEL file
<variable name="VariableA"
messageType="tns1:MessageTypeA"/>
<variable name="VariableB"
messageType="tns1:MessageTypeB"/>
<pick name="Pick_2" createInstance="yes">
<onMessage portType="tns1:MutilPort" operation="square"
variable="VariableA" partnerLink="Multiplex">
<sequence name="Sequence_1">
<assign name="Assign_2">
<copy>
<from variable="VariableA" part="payload"
query="/ns1:MessageARequest/ns1:Operand1"/>
<to variable="ResponseVariable" part="payload"
query="/ns1:AllOpProcessResponse/ns1:Result1"/>
</copy>
</assign>
</sequence>
</onMessage>
<onMessage portType="tns1:MutilPort" operation="addition"
variable="VariableB" partnerLink="Multiplex">
<sequence name="Sequence_2">
<assign name="Assign_1">
<copy>
<from variable="VariableB" part="payload"
query="/ns1:MessageBRequest/ns1:Operand5"/>
<to variable="ResponseVariable" part="payload"
query="/ns1:AllOpProcessResponse/ns1:Result1"/>
</copy>
</assign>
</sequence>
</onMessage>
</pick>
Please can anyone shed some light on why and how this can happen and where is it going wrong.
Thanks,
Shishir

Looks like the destination which is used by your EG has default settings,
particulary the RedeliveryLimit param. If it is set to -1 (default setting)
WL will try to redeliver the message forever in case of any error. Just set
it to something else. You can also specify an ErrorDestination and hadle
error messages specifically in it.
Denis.
<Gunjan Shukla> wrote in message news:[email protected]..
Hi,
We are using WLI 8.1, in one of our applications I have a message broker
channel configured to listen to rawdata type messages. A jms event
generator is configured to publish messages, which are sent to a jms
topic, on this channel.
We have no control over type of messages sent by client applications, when
some client application sends an ObjectMessage instead of BytesMessage,
following error is thrown
####<Jun 1, 2006 10:47:14 AM GMT-07:00> <Error> <WLW> <P931467> <cgServer>
<ExecuteThread: '11' for queue: 'weblogic.kernel.Default'> <<anonymous>>
<BEA1-004324CB0C4F26C12C0A> <000000> <Cannot publish non-BytesMessage to
channel of type RAWDATA>
####<Jun 1, 2006 10:47:14 AM GMT-07:00> <Error> <WLI-Core> <P931467>
<cgServer> <ExecuteThread: '11' for queue: 'weblogic.kernel.Default'>
<<anonymous>> <BEA1-004324CB0C4F26C12C0A> <BEA-489048> <Not a
BytesMessage>
server keeps throwing this exception and fills the logs and ultimately
server needs to be re-started.
Can somebody point me to whether its possible to catch these exceptions in
a process?
Or alternatively is it possible to somehow ignore the messages with
mismatched message type?
Any ideas are greatly appreciated.
Thanks and regards,
Gunjan

Wrong message type while sending response from TP

Similar Messages

Maybe you are looking for