on 11-21-2006 5:31 PM
My RFC call is not producing the output I expected.
(scenario: file ->XI->remote RFC call)
When I go into the debugger for the RFC and plug in the
same values as in my text file, I get no error messages, and
I get my desired output (creates a Purch Request on remote system).
However, when set up to run from within XI, there is no output.
Questions --
1. Where on the remote system can I look for possible error msgs?
ABAP dump analysis shows no entries for this RFC
SM58 RFC log has no entries.
2. SXMB_MONI on XI shows no error msgs. Where else can I look?
No dumps on XI either.
Hi,
1. Check if the RFC needs explicit commit, if so handle the same in the receiver RFC adapter.
2. Check if there is any conversion exit needs to be done for any field.
For eg:
If the vendor number is 123 it should be passed as 0000000123.
3. For testing purpose you can try with a sync call so that you will have the return parameter as response so you can debug easily.
4. Did you check the Adapter /communication channel monitoring and is it succesful?
Regards,
Prakash
Regards,
Prakash
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
>. Check if the RFC needs explicit commit, if so handle the same in the receiver RFC adapter.
Commit is in the RFC. It works, at least when run in debug mode on remote system.
>2. Check if there is any conversion exit needs to be done for any field.
I found some earlier problems with the input file, but fixed them.
Plugging the same exact values into the debugger nets a result.
>3. For testing purpose you can try with a sync call so that you will have the return parameter as response so you can debug easily.
Haven't tried this one yet.
>4. Did you check the Adapter /communication channel monitoring and is it succesful?
Yes, the commx channel is working. I know the RFC is being run, since I had previous
errors that showed up in the remote systems dumps. Fixed those problems, but now
I get no feedback and no output.
OK, I found part of the reason -- after running the debugger again,
it errors out with a data problem.
So let me rephrase the question -- If my RFC fails for some small reason,
is there a way I can find the error without using the debugger? Is this
same error message stored on a log somewhere on the remote system
where the RFC is run?
Berkeley DBC,
See if the commit statement is missing in the RFC.
-Naveen.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
87 | |
10 | |
10 | |
9 | |
7 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.