SAP ABAP Data Element QRFC_QUEUE_NAME (Queue Name for Background RFC)
Hierarchy
☛
SAP_BASIS (Software Component) SAP Basis Component
⤷
BC-MID-RFC-BG (Application Component) Background RFC (bgRFC)
⤷
SQRFC2 (Package) ABAP Development for bgRFC
⤷
⤷
Basic Data
| Data Element | QRFC_QUEUE_NAME |
| Short Description | Queue Name for Background RFC |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | QRFC_QUEUE_NAME | |
| Data Type | CHAR | Character String |
| Length | 40 | |
| Decimal Places | 0 | |
| Output Length | 40 | |
| 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 | Q Name |
| Medium | 15 | Queue Name |
| Long | 20 | Queue Name |
| Heading | 24 | Name of qRFC Queue |
Documentation
Definition
Name extension for a queue in Background RFC
Use
You can use a queue prefix to control whether an inbound transaction is processed in classic qRFC or in bgRFC.
You can use a queue prefix to control which inbound destination is used to process the inbound bgRFC unit. The system searches for the queue prefix that best matches the unit queue name that is used. If no matching queue prefix is found, the transaction is processed in classic qRFC.
Dependencies
Example
History
| Last changed by/on | SAP | 20100420 |
| SAP Release Created in | 700 |