Reprocessing of tRFC Errors

[Former Member]

Can anyone tell me whether we reprocess tRFC errors for all kind of RFC errors or reprocessing is restricted only  for specific errors ..for eg:No authorization to send IDOC..

[Former Member]

hi Kondal

What tcode you are using to reprocessing?

Regards,

Archer

[Former Member]

Hi Archer,

I reprocessed using SM58

from EDIT -Execute LUWs option

[Former Member]

Like trfc of idoc, we using BD87 to reporess, but it`s in allusion to individual idoc, not the error. In orther words when sending this idoc if have error, nomatter what kind of error, the trfc will give a message.

[Former Member]

My question is like do we need to  reprocess for all   tRFC that show exception in SM58 status column.

Or the Idocs will get transferred automatically when the target system is available as a background process without any manual intervention .And what are the table that store the details about trfc and qrfc..

[Former Member]

Kondal rao,

It is necessary to process all tRFC units. There can be many reasons why a tRFC failed. One example is target system not available. Another example from my testing scenario recently is ECC system generates idocs to PI. Lets say there were some duplicates in the buffer of PI adapters. Then the idocs will fail in ECC. This means the idocs are not transferred to PI.

Normally in this case, when the buffer is cleared the entries in SM58 should get picked up by the batch job and get pushed to PI. There can be some cases where you might want to process manually.

Tables:

When SAP issues commit work, the first ones to be processed are updates tasks (V1 - updates). Once done, SAP looks at the table ARFCSSTATE for t/qRFC. If any entries are found, those are processed.

In case of qRFC the entries are processed in the order in which they are received.

If an entry fails, the status of the same is set to SYSFAIL.

The best way to understand this process is to open SM58 and then click on the 'I' icon next to execute. It has all the good information you are looking for.

Thanks,

Vikram.M

[Former Member]

Hi Vikram,

Thanks for the explanation. So how often do we clear these  tables for tRFC and qRFC in Production environment to improve index quality

Regards

Kondal Rao

[Former Member]

And when t/qRFC are processed from ARFCSTATE table ,will the entries in these tables will get cleared automatically.And the error log what we get in SM58 , is it from these ARFCSTATE table.

Regards

Kondal

[Former Member]

Technically we should not be clearing anything from the table. If for some reason you have to clear the an entry you should do it from SM58.

How it works:

When SAP comes across a tRFC call, instead of executing the call it writes an entry to ARFCSTATE table. Same is the case with qRFC and also update task. But for update task the table is different.

Once SAP comes across a COMMIT, it then starts processing all the update task and then looks into ARFCSTATE. If it finds an entry corresponding to the LUW which issued the commit, it then processes it. If its successful, SAP automatically removes this entry from ARFCSTATE.

Thanks,

Vikram.M

[Former Member]

Ques 1) Consider a scenario where I see an error entry in SM58 logs ,does it mean that t/q RFC entry  will be present in ARFCSTATE table. And once it is processed from ARFCSTATE table , the entry in Sm58 logs will also be cleared..?

Ques 2) I see that there are enough free Update WP available, but the log in SM%* is not cleared.Does it mean that I need to manually process them or Should I wait for some time to get it picked by some Background process?

[Former Member]

Q1: Yes and No.

When you see an error in SM58, there will be a corresponding entry in ARFCSSTATE.

The other way around for you next question as a part of Q1. Once SM58 is processed, the entry will be deleted from ARFCSSTATE

Q2: It might not be related to WP. It might be because the background job that processes tRFC entries has not run. Once the same runs, you should see the entries from SM58 cleared.

Thanks,

Vikram.M