Hierarchy
SAP_BASIS (Software Component) SAP Basis Component⤷
BC-SRV-QUE (Application Component) SAP Query⤷
SQUE (Package) Application Development R/3 SAP Query
Basic Data
| Data Element | AQ_ORDER |
| Short Description | SAP Query: Sequence of code |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | AQS_N2 | |
| Data Type | NUMC | Character string with only digits |
| Length | 2 | |
| Decimal Places | 0 | |
| Output Length | 2 | |
| 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 | Sequence |
| Medium | 15 | Sequence |
| Long | 30 | Sequence of code |
| Heading | 40 | Sequence of code |
Documentation
Definition
Each query report within an InfoSet consists of several sections of code. The most important of these reads and processes data records. In the case of an InfoSet associated with a logical database, it is divided into different GET and GET LATE events for each logical database table involved. In the case of an InfoSet without any underlying database, there is only one section for reading and processing a data record.
Within each GET (or record processing) event, you include:
- SELECT statements for additional tables
- Code for additional fields
- Either the GET part of the GET / GET LATE code
(for an InfoSet associated with a logical database)
or the code for record processing
(for an InfoSet without any underlying database)
The sequence is in ascending order and depends on the sequence numbers you assign. If several sections of the code for a particular logical database table have the same sequence number, the sequence remains undefined.
History
| Last changed by/on | SAP | 20010130 |
| SAP Release Created in |
