SAP OBJECT_RFCCONTACT Data for Creating an RFC Destination Table data and field list

OBJECT_RFCCONTACT is a standard SAP Structure so does not store data like a database table does. It can be used to define the fields of other actual tables or to process "Data for Creating an RFC Destination" Information within sap ABAP programs.

This is done by declaring abap internal tables, work areas or database tables based on this Structure. These can then be used to store and process the required data appropriately.

i.e. DATA: wa_OBJECT_RFCCONTACT TYPE OBJECT_RFCCONTACT.

The OBJECT_RFCCONTACT table consists of various fields, each holding specific information or linking keys about Data for Creating an RFC Destination data available in SAP. These include TASK_CODE (Change Indicator Role (I = Insert, D=Delete etc. )), CONTACT_DATA (), CONTROLLER (), STANDARD_SENDER_INDICATOR ()... See below for full list along with technical details, documentation, text table, check tables, foreign key relationships, conversion routines, relevant tcodes and example ABAP select code etc. .

OBJECT_RFCCONTACT structure Technical Details:

Delivery Class:
Display/Maintenance via tcode SM30: Display/Maintenance Allowed but with Restrictions
SAP enhancement categories: Can Be Enhanced (Deep)


SAP OBJECT_RFCCONTACT structure fields - Full list of fields found in SAP data dictionary

Looking for S/4HANA specific information? Click here to explore the details, fields and extensibility available for this table in the SAP S/4HANA version of the OBJECT_RFCCONTACT table. Also check whether the table still exists or has been transformed into a CDS view as part of the HANA simplifications.
Field Description Data Element Data Type length (Dec) Check table Conversion Routine Domain Name MemoryID SHLP
CONTROLLER 0
TASK_CODEChange Indicator Role (I = Insert, D=Delete etc. ) PARTY_TASK_CODECHAR1
CONTACT_DATA 0
CONTROLLER 0
STANDARD_SENDER_INDICATOR 0
CONTROLLER 0
UPDATE_INDICATORIndicator whether an element carries an updated value or not UPDATE_INDICATORCHAR5
VALUE 0
RFCLOGICAL_DESTINATION 0
CONTROLLER 0
UPDATE_INDICATORIndicator whether an element carries an updated value or not UPDATE_INDICATORCHAR5
VALUERFC Logical Destination (Specified in Function Call) PARTY_RFCDESTINATION_NAME_CONCHAR32
STANDARD_RECIPIENT_INDICATOR 0
CONTROLLER 0
UPDATE_INDICATORIndicator whether an element carries an updated value or not UPDATE_INDICATORCHAR5
VALUE 0
CONNECTED_TO_SAPR3INDICATOR 0
CONTROLLER 0
UPDATE_INDICATORIndicator whether an element carries an updated value or not UPDATE_INDICATORCHAR5
VALUE 0
HOME_ADDRESS_INDICATOR 0
CONTROLLER 0
UPDATE_INDICATORIndicator whether an element carries an updated value or not UPDATE_INDICATORCHAR5
VALUE 0
CONSECUTIVE_NUMBER 0
CONTROLLER 0
UPDATE_INDICATORIndicator whether an element carries an updated value or not UPDATE_INDICATORCHAR5
VALUEOngoing number within the table of communication numbers, id PARTY_CONSECUTIVE_NUMBER_CONTNUMC10
ERROR_INDICATOR 0
CONTROLLER 0
UPDATE_INDICATORIndicator whether an element carries an updated value or not UPDATE_INDICATORCHAR5
VALUE 0
USAGE_DENIAL_INDICATOR 0
CONTROLLER 0
UPDATE_INDICATORIndicator whether an element carries an updated value or not UPDATE_INDICATORCHAR5
VALUE 0
VALID_FROM 0
CONTROLLER 0
UPDATE_INDICATORIndicator whether an element carries an updated value or not UPDATE_INDICATORCHAR5
VALUEProxy: Zeitstempel PARTNER_DATE_TIMESTRG0
VALID_TO 0
CONTROLLER 0
UPDATE_INDICATORIndicator whether an element carries an updated value or not UPDATE_INDICATORCHAR5
VALUEProxy: Zeitstempel PARTNER_DATE_TIMESTRG0

Key field Non-key field



How do I retrieve data from SAP structure OBJECT_RFCCONTACT using ABAP code?

As OBJECT_RFCCONTACT is a database structure and not a table it does not store any data in the SAP data dictionary. The ABAP SELECT statement is therefore not appropriate and can not be performed on OBJECT_RFCCONTACT as there is no data to select.

How to access SAP table OBJECT_RFCCONTACT

Within an ECC or HANA version of SAP you can also view further information about OBJECT_RFCCONTACT and the data within it using relevant transactions such as

SE11 (ABAP Dictionary Maintenance)
SM30 (Maintain Table Data)
SE80 (Object Navigator)
SE16 (Data Browser).