Child pages
  • ARFSSTATE - To find out which destination causes the problem in BW Extraction
Skip to end of metadata
Go to start of metadata

To find out which destination causes the problem, you can use the TID.

Consider Eg:
if you have a job called ARFC : AC14007B00CB4AE7131B00D2 ,
Then you will find the same time an entry in ARFCSSTATE table with below split up.

ARFCIPID             AC14007B
ARFCPID              00CB
ARFCTIME           4AE7131B

Sample ARFCSSTATE table content

Here we could find the destination causing this job in the field "ARFCDEST".

But, unfortunately if the job was successful this entry will be deleted from the table.

For each unsuccessful ARFC found in table ARFCSSTATE it starts a job by name AFRC<xxxxxxx>.
In table ARFCSSTATE you can see the destination for the ARFC call.

In the maintenance of the RFC destinations you can set that no repeat jobs are scheduled in case an error occurs. As a result, the TRFC is no longer executed after it has been called once.

These TRFCs can either be started manually or are to be processed via a batch job (RSARFCEX).