Child pages
  • TRFC ARFC Deletion
Skip to end of metadata
Go to start of metadata

Purpose

This Wiki give brief introduction about the TRFC and ARFC deletion process.

Overview

An overview about the report used for deleting the entries in table ARFCSSTATE and  ARFCSDATA

Procedure

The report RSARFCER will delete entries in the tables ARFCSSTATE and  ARFCSDATA. There is no need to use the report RSTRFCER, unless user  wish to delete entries in the table ARFCRSTATE. The program RSARFCER  is designed to delete tRFC's. The report RSTRFCER is designed to  delete ARFCSTATE .

Originally, this report was delivered as automatically scheduled.  However, due to the fact that the batch job was created with the ID  of the user applying specific hotpacks, it was owned by that user.  If the user left the compnay, or the ID changed, it became an  administrative issue for System Admins, so this report is no  longer scheduled automatically.  Check SAP Note 366807
for more details on this, as well as alternative methods for removing  data from the system.  It is a supported method to schedule this  report to run peridically as a clean up job in the system, just be sure  to create it with a static user ID (one that will always be available),  or at least keep track of the ID assigned.  In order to kick off processing of the LUW's in TRFC Monitor, user
can run report RSARFCEX (also can be a periodic running batchjob),  or manually via the tRFC monitoring (SM58).  The report RSARFCER will delete entries in the tables ARFCSSTATE and ARFCSDATA.  It is not needed to use the report RSTRFCER, unless user  wish to delete entries in the table ARFCRSTATE.

The program RSARFCER is designed to delete tRFC's. The report RSTRFCER is designed to delete ARFCSTATE (internal application).Originally, this report was delivered as automatically scheduled.  However, due to the fact that the batch job was created with the ID of the user applying specific hotpacks, it was owned by that user.If the user left the compnay, or the ID changed, it became an administrative issue for System Admins, so this report is no longer scheduled automatically.  See SAP Note 366807 for more details on this, as well as alternative methods for removing data from the system.  It is a supported method to schedule this report to run peridically as a clean up job in the system, just be sure to create it with a static user ID (one that will always be available), or at least keep track of the ID assigned.

In order to kick off processing of the LUW's in TRFC Monitor, we can run report RSARFCEX (also can be a periodic running batchjob),or manually via the tRFC monitoring (SM58).

 

 

  • No labels