Community
Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Read only

tRFC data transfer for IDOCs

Former Member

‎2006 Mar 20 1:21 PM

0 Likes
782

Hi,

ALE has been configured to send data from System A to System B. The Communication IDOC in System A is at status 12 ( Dispatch OK ), while the idoc in status B is at 51.

When I checked the IDOC in System B, I found that in a particular segment,there is a field called "Initial" which is populated "#.#", when it should have been "E.M". All the fields after this are incorrectly represented as they have been shifted to the left by two spaces.

This seems to be a problem with data transfer via RFC. How can I confirm this - and what can I do in situations like these ? Is there any way to resend this data ?

Thanks,

Urmila

Hi,

ALE has been configured to send data from System A to System B. The Communication IDOC in System A is at status 12 ( Dispatch OK ), while the idoc in status B is at 51.

When I checked the IDOC in System B, I found that in a particular segment,there is a field called "Initial" which is populated "#.#", when it should have been "E.M". All the fields after this are incorrectly represented as they have been shifted to the left by two spaces.

This seems to be a problem with data transfer via RFC. How can I confirm this - and what can I do in situations like these ? Is there any way to resend this data ?

Thanks,

Urmila

Reply
4 REPLIES 4
Read only

Former Member

‎2006 Mar 20 3:14 PM

0 Likes
711

HI,

Try to force the IDOC using BD87 for the specific IDOC. If it still gives an error. Check the system dump using transaction ST22 you will most likely find a dump for every try you made to process the IDOC. The dump helps you to drill down and sort the error.

Also check the Data records and segments.

Thanks,

-Suresh Revuru

Read only

Former Member

‎2006 Mar 20 3:39 PM

0 Likes
711

Urmila,

If there is a problem with tRFC, there will be a entry in SM58 transaction. check that.

Regards,

Ravi

Note : Please mark the helpful answers if they help.

Read only

Former Member
In response to Former Member

‎2006 Mar 21 6:27 AM

0 Likes
711

Thanks, Ravi.

The Problem is that I don't have authorisation to SM58. While I am trying to get the necessary authorisation, I have another question to ask you.

Lets say that for some reason the tRFC has failed. Shouldn't the status of the received IDOC indicate a failure. The first Status on the receiving side is 50 (IDOC added) and yet the data in the received IDOC is clearly corrupted.

Does the Status mechanism of the IDOC's issue any errors in the communication layer ?

Thanks,

Urmila

Read only

Former Member
In response to Former Member

‎2006 Mar 21 6:31 AM

0 Likes
711

Urmila,

Theorotically, you are right. I would expect to see a different status. Unfortunately I have not seen that happening. I had a case where the background user was not authorized to post data in the target system and the IDOC was showing success - something like that.

Regards,

Ravi

Note : Please mark the helpful answers, if they help.