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*****
Similar Messages
-
How to send inforecord conditions using ALE (message type COND_A)?
Hi,
I have sent Purchasing Inforecords through ALE using t-code ME18.
Now, I would like to know how to transfer the conditions through ALE (message type is COND_A).
Thanks a lot,
KaveriHi,
Please go through this thread.
[Pricing Condition Records initial upload - COND_A] -
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 ShahDheeraj,
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 -
Details for ALE Message type 'INVOICE' for intercompany billing ?
Hi all,
I have a requirement that i have to create the Invoice receipt for FI when the billing document is created ( VF01) in the same client?
Please provide me the details for this
such as output type , process code and other master data settings that have to fill?
Thanks,
Vamshi.Hi prakash,
Thanks for the reply and it is very helpful.
But i am using message type RD00 and shall i use this?
Else, please specify the details that i have to maintain to use RD04 clearly stap-by-step?
Thanks,
Vamshi. -
Distribution Model (ALE) - Message type has to be deleted from model view
Hello,
I want to delete a message type from an existing model view in the distribution model (of the maintenance system).
But when I mark the concerning message type and press Edit->Delete the message 'Action cannot be carried out on the nodes selected' occures. Deleting the complete model view would work...
Does anyone know how I can get this without setting up a new model view?
Many thanks in advance,
Juergenhi,
>>'Action cannot be carried out on the nodes selected'
you get this message if you try to delete a message type
from a model view that was not created on your system
(it has been replicated and it's maintained on another system)
so you can only delete this message type on the system that has
"master" distribution model
if it's not master then it's usually grey and you can only delete if it's black in change mode
>Deleting the complete model view would work...
if you try that you will see info that it's not the "master" system for this model
check it and let me know
Regards,
Michal Krawczyk -
Output message type External send - Suppress spool number in SOST title
Dear all,
Using an external send output type, we send order confirmation from by mail.
Depending of printer we use, we have different behaviors :
With a normal printer, the mail title we get in SOST is exactly the content of field <NAST-TDTITLE>.
This field can be changed in the print program, so we can set exactly the title we want.
With a PDF2MAIL printer (printer defined in SPAD with property host spool access method : M (Email to Receiver/Owner), the mail title we get in SOST is the following : <SystemID><Spool Number><NAST-TDCOVTITLE>.
Do you know whether it is possible to suppress standard information <SystemID><Spool Number>
and therefore have only <NAST-TDCOVTITLE>.
Setting both fields <NAST-TDCOVTITLE> and <NAST-TDTITLE> using print program, the goal is to have allways same title in SOST ...
Can you help me ?
J.C.Hi,
I am not got your reuirement clearly, but i feel your reuirement is close to this thread:
RLB_INVOICE program for sending mail to muliple mail's Id's
I have used the Cl_BCS class to send mail to muliplte vendor mail id's
If needed code will be send.
Hope this will help. -
Hi all
I have created a z-message tyoe and attatch with the basic and extention idoc type in WE82 .
Now if i go to database table TBDME or in EDP13 i did not found my enteries.
How can i acheive that. Please suggest me.
ThanksHi
no it wont worked with BD57 i already Tries with that.
othere solutions? -
1 IDoc message type to send to multiple ports
Hi all,
Currently I have one port and already configure to send Material Master(MATMAS)
to outbound to target XML port successfully.
We have additional requirement from another system to send out the same message structure to File port in order to generate plain text file for another external system.
My question is that how can we configure in order to send out material master to both target file ports . (XML and normal file ports) ?
Is it possible to config this way?
Kindly advise.
Thank youHi.
How to implement HRMD_A? With an Event?
In other words, If a change in Infotype 0002, when the user save, the idoc start and in bw the infopackage load the data passed by idoc?
Regards
Angela -
ALE Message type HRMD_A Infotype 0001 is incorrect using PROOF flag = X
Hi
We have an issue using HRMD_A for Infotype 0001 with the PROOF flag swithed on. Using the PROOF flag triggers a call of HR_MAINTAIN_MASTERDATA instead of a direct write to db tables. However sometimes the update of Infotype 1 is incomplete and records are lost. The data goes through a transformation in the inbound BAdi, here I have checked the sequence is still correct. But when the data is written to Infotype 1 it seems to overwrite the last entries.
If anyone has any experience with this, I would be very interested for any input.
Thanks in advance
SonnyHi Sandip
Thx for your response. If I understand you correctly you suggest I use the HR_INFOTYPE_OPERATION. This could be an alternative, but I would prefer to understand the reason behind the error.
HR_INFOTYPE_OPERATION actually calls HR_MAINTAIN_MASTERDATA, so this FM might not solve the issue, but it does give the option for updating one record at a time.
Sonny -
ALE Configuration for PEXR2002 IDoc and PAYEXT message type sending to XI
Hi all,
I need ALE Configuration for PEXR2002(Basic Type) IDoc , it's message type PAYEXT.
I don't know ALE Configuration for sending data from SAP IDS to SAP XI.????
I need ALE Configuration doc/pdf??
Please give me some guidline for this..
Regards,
UmeshUmesh,
I was wondering if you have had any luck creating the configuration for PEXR2002 Idoc, PAYEXT message types, and sending the result set to XI.
I need to perform the same task within our R3 environment using the FTP protocol in XI to send the file to the Bank to be processed.
Any help or direction would be great.
Thanks,
Dave -
Ale with user created message type
Hello,
I have a created a segment ,idoc and message type and done the assignment of Idoc with message type also.
i have to send the material 800 to 810 client through ALE.
By using the Standard Message type MATMAS i m getting the material on 810 client.
But when i am using my message type ie ZMAT_MSG in tcode BD10 on client 800 to send the material it is saying error that message type does not exist.
I am not getting the problem
Or it is not possible to use your message type to send the material through Tcode BD10.You have to always use the standard message type MATMAS.
If yes then how to use our own message type to transfer the data from client 800 to 810.
Please reply .
ManishHi Vasu,
Please try this.
1. Create distribution model (BD64) for message type MATMAS_BAPI.
2. Create inbound partner profile (WE20) for message type MATMAS_BAPI and IDoc type MATMAS_BAPI01 and process code BAPI.
3. Create IDoc ports (WE21)
4. Setup RFC destination (SM59).
Hope this will help to start with.
Regards,
Ferry Lianto
Please reward points if helpful. -
How to recreate Idoc - message type FIDCC1
Hi Experts,
We have configured sending IDoc using ALE during execution of Tcode FPG1 with message type FIDCC1- Send entire FI documents (user exit 003/4) and basic type FIDCCP01
We are facing issues sometimes, the financial entry is posted but the IDoc is not created for the same. Is there any way we can regenerate the IDoc ?
Any suggestion will be of great help.
Thanks & Regards
SatyajeetHI,
You can use WE19 but make sure you test this in TEST client.
This is quickfix solution and shall not be use regularly.
Regards,
Paresh -
[HR] About message type HRSM_D
Hi to all
As a migration issue I was asked to migrate personnel absence records (infotype 2001) data from an SAP 4.6 legacy system to an ECC5 system. Actually, I have no PT knowledge but I want to use HRSM_D message type to transfer data through LSMW. Does anyone know any FM or report filling this IDoc structure like "RH_OBJECT_IDOCDATA_CREATE" does for HRMD_A?
I would welcome any other ideas for migrating 2001 data through LSMW as well.
ThanksHi Suresh
Thank you for the answer. The BAPI you've mentioned belongs to BO 'ABSENCE' and it has no ALE message type in standard. I do not want to genarate, either. Besides, it is obsolete as of Release 4.6A. However, it may be replaced by BO BUS7007.
Actually, what I want is an outbound FM handling the HRSM_D message type.
There are more than one legacy system and this way is prefered by the client.
Thanks -
Invoice Response Message Type ?
Does anyone know if there is a Standard Message type to send an IDOC response back after receiveing a Logistics Invoice ?
Hi,
Please go through this [ document. |http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/f6d2d790-0201-0010-9382-b50b499b3fbe?quicklink=index&overridelayout=true]
Thanks,
Abhijit -
Message Type ( Idoc Type ) for customer master & Pending invoice
Hi
My Client is doing sale in POS for credit customers and credit customer master should be sent to POS as outbound Idoc.
1.What is the standard message type for sending Customer masters to POS. WP_PER01 is not activated for version 700 ( message getting on WE60 ). Plse let us know is there any another message type for customer master.
2. Also i need to send the credit limit of the customer to POS . Is this possible by standard message type or we need to go for ZIdoc?.
3.Is there standard Outbound Idoc ( Message type ) available to send the Pending invoice list toPOS?
plse help me on the above
Regards
AnisHi ,
you can use DEBMAS message type for customer master IDOC ,
Tcode Bd12
Thanks,
Amit
Maybe you are looking for
-
Hi, I've created an ALE distribution model to process the interface concerning Set Up HR and Accounting. Initialy we make it all and distribute it to the receiving system (FI) and it seems to be ok. After that the funcional team generate some movemen
-
Functional acknowledgement posting to PO confirmation tab
Hi Gurus, Can anbybody please throw some light on the followin scenario. is it possible to have the functional acknowledgement posted to the confirmation tab of the PO. If so what kind of confirmation control key has to be used and other settings th
-
TS2167 how do i upload to another ftp site
my iweb site on is down and I've been told that I have to upload my site to another sever or host... how do I do that?
-
I'm having a problem with <cfdocument> hanging and eventually timing out on one of my servers. The server is running CF 7,0,2,142559 Enterprise version with the latest hot fixes. The JVM is Sun 1.4.2_11. I've been through many of the ssl/https issues
-
I've been trying for a week now. This one is new: Error ERR-1014 Application not found. OK application=4755 workspace=10 Please fix.