3782158 - RS_CLEAR_RFC_TABLES FAQ: Purpose, Scope, Risks, and Supported Usage

Customers require information about report RS_CLEAR_RFC_TABLES and its impact on RFC runtime data.

Typical scenarios include:

• Cleanup after a system copy, client copy, or system refresh.
• Deleting large amounts of bgRFC, qRFC, or tRFC runtime data.
• Inability to delete bgRFC destinations due to existing units.
• Obsolete RFC runtime data copied from another system.
• RFC scheduler activities referring to a source system after refresh.
• Large tables such as:
  • ARFCSDATA
  • ARFCSSTATE
  • bgRFC runtime tables
• Questions regarding the correct deletion tool for:
  • tRFC
  • qRFC
  • bgRFC

Examples of observed symptoms:

• Units still exist for destination <destination>; no deletion possible
• RS_BGRFC_DAILY_REORG continues to contact source system
• CALL_FUNCTION_SIGNON_REJECTED
• Large numbers of entries remain in ARFCSDATA and ARFCSSTATE

• ABAP Platform
• SAP NetWeaver
• SAP S/4HANA

RS_CLEAR_RFC_TABLES, ARFCSDATA, ARFCSSTATE, TRFCQOUT, bgRFC, qRFC, tRFC, RSARFCER, RSTRFCQDS, RSTRFCEG, RS_BGRFC_MASS_OPERATIONS, system copy, client copy, system refresh, cleanup, BGRFC_SRV_STATE, RS_BGRFC_DAILY_REORG, CALL_FUNCTION_SIGNON_REJECTED, Units still exist for destination, All bgRFC units, Classic outbound qRFC, Classic inbound qRFC, runtime data cleanup, RFC runtime tables , KBA , BC-MID-RFC-BG , Background RFC (bgRFC) , BC-MID-RFC-QT , Queued RFC (qRFC) and transactional RFC (tRFC) , BC-MID-RFC , RFC , Problem