SAP ABAP Data Element RFCENABLE (Allow RFC for ENQUEUE/DEQUEUE function modules)
Hierarchy
☛
SAP_BASIS (Software Component) SAP Basis Component
⤷
BC-DWB-DIC-AC (Application Component) Activation Program, Conversion Program, DB Utility, MC, SPDD
⤷
SMAC (Package) R/3 Matchcode Development

⤷

⤷

Basic Data
Data Element | RFCENABLE |
Short Description | Allow RFC for ENQUEUE/DEQUEUE function modules |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | AS4FLAG | |
Data Type | CHAR | Character String |
Length | 1 | |
Decimal Places | 0 | |
Output Length | 1 | |
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 | RFC |
Medium | 15 | Allow RFC |
Long | 20 | Allow RFC |
Heading | 4 | RFC |
Documentation
Definition
If this flag is set, the function modules generated when the lock object is activated can be called to set and release locks with Remote Function Calls (RFC).
If RFC is allowed, the parameters of these function modules have the following refrence fields:
Parameter Reference fields
X_<Fieldname> DDENQ_LIKE-XPARFLAG
_WAIT DDENQ_LIKE-WAITFLAG
_SCOPE DDENQ_LIKE-SCOPE
Dependencies
If you activate Allow RFC for an exisitng lock object, you must make sure that the call of the generated function module has parameters of the right type. Before you activate the lock object with the new option, you should check all the programs that use the corresponding function modules.
History
Last changed by/on | SAP | 19950209 |
SAP Release Created in |