Hierarchy

⤷

⤷

Basic Data
Data Element | AQ_LPOS |
Short Description | SAP Query: Sequence |
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 |
Heading | 55 | Sequence |
Documentation
Definition
Sequence number.
Supplementary Documentation - AQ_LPOS 0120
Use
Specification of the sequence of fields in a line of the basic list.
You can assign sequence numbers between 1 and 98.
Procedure
In addition to the line number, you should also assign a sequence number to all the fields you want to appear in the basic list. You thus determine, for each line, the sequence in which you want the individual fields to be output on the line.
It makes sense to assign the sequence number for every line starting with 1 and in ascending order without breaks, this is not obligatory.
Examples
Dependencies
Supplementary Documentation - AQ_LPOS 0121
Use
Procedure
Using sequence numbers, determine the order in which you want to sort the basic list of the query. Assign the number 1 to the highest sort criterion, number 2 to the next highest, etc.
Examples
Dependencies
Supplementary Documentation - AQ_LPOS 0200
Use
Definition of the sequence of fields within a statistic.
You can assign sequence numbers between 1 and 98.
Procedure
Assign a sequence number to all fields which appear in the statistic. This determines the sequence in which they are output.
It makes sense to assign sequence numbers starting with 1 and in ascending order without breaks, but this is not obligatory.
Examples
Dependencies
When you define a statistic, the data is usually summarized, i.e. several data records are processed to determine one line. With numeric fields, only the total is output. Statistics which do not contain numeric fields make no sense because there is no data summarization.
Supplementary Documentation - AQ_LPOS 0210
Use
Definition of the sequence of fields in a ranked list.
You can assign sequence numbers between 1 and 98.
Procedure
Assign a sequence number to all the fields which appear in the ranked list. This determines in which sequence they are output.
It makes sense to assign the sequence numbers starting with 1 and in ascending order without breaks, but this is not obligatory.
Examples
Dependencies
When you define a ranked list, the data is summarized, i.e. several data records are processed to determine one line. With numeric fields, the total is always output. Every ranked list must contain at least one numeric field.
Supplementary Documentation - AQ_LPOS 1120
Use
Specification of the sort sequence in the basic list. You can assign sequence numbers between 1 and 10.
Procedure
Assign a sequence number for sorting to every field by which you want to sort (a sort criterion corresponds to a control level). The highest sort criterion must have the lowest sequence number, the next sort criterion a higher sequence number, and so on.
It makes sense to assign the sequence numbers starting with 1 and in ascending order without breaks (i.e. the highest sort criterion should be number 1), but this is not obligatory.
Examples
Dependencies
Please note that you can also sort by fields which are not output in the basic list, i.e. fields for which the columns Line and Sequence are not filled. In this case, you can use the options which the query provides for changing a sort criterion (control break) to display these fields in the list.
Supplementary Documentation - AQ_LPOS 1200
Use
Definition of the sort sequence in the statistic.
Procedure
Assign a sequence number for sorting to every field by which you want to sort. The highest sort criterion must have the lowest sequence number, the next sort criterion a higher sequence number, and so on.
It makes sense to assign the sequence numbers starting with 1 and in ascending order without breaks (i.e. the highest sort criterion should receive number 1), but this is not obligatory.
Examples
Dependencies
History
Last changed by/on | SAP | 20010130 |
SAP Release Created in |