on 07-27-2007 2:34 AM
HI,
can we test whether message has reached XI by triggering FM in Sender SAP system just by creating RFC destination in sender SAP and a communication channel in XI with RFC Sender Adapter?
I think, we cant right.
we tested FM in sender SAP but we get short dump error (TCode: ST 22 call_function_remote_error)in sender SAP.
so we just need to do all the steps as usually we do ,right?
is there any way we can test our Async RFC whether data reaching XI system/
thank you.
Babu
Hey
>>we tested FM in sender SAP but we get short dump error (TCode: ST 22 call_function_remote_error)in sender SAP.
i think it should be possible,you are getting the short dump in SAP most probably coz of some fault in ABAP code to trigger the FM.
if you dont do all the steps in XI system(like IR,ID etc),then you will see error in RWB or sxmb_moni(not in SAP system),but if you dont see any error in sender SAP system,that means the message is reachin XI properly
Thanx
Ahmad
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
logically I thought ,only RFC destination and Communication channel(may be sender agreement) are required for message to reach from sender SAP to Xi once we trigger FM in sender SAP,but not sureif its possible in practical.
do you have any idea how can we see whether message reached xi or not,with monis?
thank you .
Babu
Ahmad,
we sent a message from sender SAP system using an ABAP report which trggers FM for that I have needed importing of FM into XI and sender RFC communication channel and sender agreement.after we are able to see atleast FM able to reach XI but in SXMB_MONI we are not able to see the inbound payload,what might be the reason?
and do I need to create Message interface using the imported FM as message type ?or can I use FM as the message interface for outbound(sender)
thank you.
You need to release the RFC FM. Goto Function Module/Release/Release. This can avoid dump and reachs the XI.
Provide points if this helps.
Thanks,
Rama.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi babu..
Have you checked the RFC destination? This could be as basic as incorrect password for WF-BATCH.
Use SWU3 to test the RFC destination, then run the verification workflow and choose the "[...] in background" option. If this works, your RFC destination is OK.
refer this...
http://help.sap.com/saphelp_nw04s/helpdata/en/f9/3f69fd11a80b4e93a5c9230bafc767/frameset.htm
regards,
vasanth
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
77 | |
9 | |
9 | |
7 | |
6 | |
6 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.