SAP ABAP Data Element ARFCDATA_D (Asynchronous RFC)
Hierarchy
☛
SAP_BASIS (Software Component) SAP Basis Component
⤷
BC-MID-RFC (Application Component) RFC
⤷
SRFC (Package) Middleware Runtime Environment
SAP_BASIS (Software Component) SAP Basis Component⤷
BC-MID-RFC (Application Component) RFC⤷
SRFC (Package) Middleware Runtime Environment
Basic Data
| Data Element | ARFCDATA_D |
| Short Description | Asynchronous RFC |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | ARFCDATADO | |
| Data Type | RAW | Uninterpreted sequence of bytes |
| Length | 255 | |
| Decimal Places | 0 | |
| Output Length | 510 | |
| 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 | ARFC data |
| Medium | 15 | ARFC data |
| Long | 20 | ARFC data |
| Heading | 0 |
Documentation
Definition
Status or error text of an asynchronous RFC
The following status values can occur:
- RECORDED : The LUW was recorded and should be executed
- EXECUTED : The LUW was executed and the entry deleted
- CPICERR : Communications error or invalid ABAP command in the LUW
- SYSFAIL : Runtime error or E message when executing the LUW
- MAILED : CMC call started
- READ : CMC call was successfully executed in the target system (SAP)
History
| Last changed by/on | SAP | 20100420 |
| SAP Release Created in |
