SAP ABAP Data Element RFCREGID (Identification of a registered RFC server program)
Hierarchy
☛
SAP_BASIS (Software Component) SAP Basis Component
⤷
BC-MID-RFC (Application Component) RFC
⤷
SRCX (Package) Development Class for Remote Communication: RFC and RMC
SAP_BASIS (Software Component) SAP Basis Component⤷
BC-MID-RFC (Application Component) RFC⤷
SRCX (Package) Development Class for Remote Communication: RFC and RMC
Basic Data
| Data Element | RFCREGID |
| Short Description | Identification of a registered RFC server program |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | RFCEXEC | |
| Data Type | CHAR | Character String |
| Length | 64 | |
| Decimal Places | 0 | |
| Output Length | 64 | |
| Value Table |
Further Characteristics
| Search Help: Name | ||
| Search Help: Parameters | ||
| Parameter ID | ||
| Default Component name | ||
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | Program |
| Medium | 15 | Program ID |
| Long | 23 | Program ID |
| Heading | 64 | Program ID |
Documentation
Definition
With an SAP gateway, an RFC server program can be registered under this ID and then wait for RFC calls from different SAP systems.
The registered server program thus no longer has to be started locally by an SAP instance (applications server, gateway or SAPgui) or via remote shell.
You must maintain the specifications made via the SAP Gateway (host name and service) if registration is not being made via the gateway of the current applications server.
The program ID or host name and service of the SAP gateway in this entry must match the registration parameters (through RfcAccept).
History
| Last changed by/on | SAP | 20100420 |
| SAP Release Created in |
