Error While Using RFC Error

[Former Member]

Hello,

We are using a scenario where an XML file is read by XI and the contents of the file are transfered to R/3 via a RFC. We have used a BPM to achieve it. The problem we are facing is: <b>We are getting chequered flags in SXMB_MONI; But our data is not being posted to R/3</b>. The workflow log also shows that every step has been completed successfully. But when we run the RFC from R/3 side via SE37, we can see that the data is being posted. Can anyone point out where the problem lies or how to debug the above scenario?

Points will be rewarded to helpful answers. Awaiting your reply.

Thanks and Warm Regards,

Amitabha

[Former Member · Accepted solution]

Check SM58. Do you see any entries there.

[Former Member · Accepted solution]

Hi Abinash,

I do not see any entries corresponding to my user name in SM58.

[Shabarish_Nair · Accepted solution]

check for entries corresponding to the user provided in the RFC recv. adapter.

[Former Member · Accepted solution]

Hello Shabarish,

The entries in SM58 show 'Nothing Selected' for the credentials of the user that We used at the RFC receiver channel end.

[Former Member · Accepted solution]

Hi,

1. Put '*' in the user name if there are any errors

2. If you are updating any tables see if you have put commit work in the RFC

3. Check in the transaction SXMB_MONI for the step 'Call Adapter' if the payload is complete and containes the data before the call is being made.

Regards

Vijaya

[Former Member · Accepted solution]

Hi Vijaya,

I have checked SM58 as you mentioned..nothing is present for the particular user credentials.

Checked whether "Commit Work" statement was included..indeed it is included.

Step before Call Adapter contains the appropriate data.

Regards,

Amitabha

[Former Member]

Hi People,

First of all really sorry for the severely late reply. We had solved the problem ages ago, just forgot to mark the thread 'Answered'. The problem was with data format, means, the data that was passed to the RFC import parameters from XI did not fulfill some requirements of the BAPI that was called within the RFC. The BAPI required fields to be of exact character length, meaning material number 18 char, production order 12 char,etc with zero-padded in case the values were of shorter length. Problem was, XI was passing the values as-is, so the BAPI was rejecting it. Running the RFC from front-end was working because in ABAP, the fields were being converted internally to the required format. Debugging the RFC call from XI at runtime revealed the problem and a subsequesnt mapping to incorporate the above requirement did the trick.

Thanks for all the help, people...and I sincerely say sorry to the Forum and the Moderators for violating the rule stated in:

Regards,

Amitabha

[Shabarish_Nair]

check the RFC adapter in RWB and see the log.

[Former Member]

Thanks Shabarish..But all the entries show a status of 'OK'.