Hierarchy
⤷ CA-GTF-CSC (Application Component) Country-Specific Objects
⤷ ID-DMEEA (Package) INTDEV: ABA services of Data Medium Exchange Engine
Basic Data
Data Element | DMEE_KEY_ONLY_ABA |
Short Description | DMEE: Key field is not used for sorting |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | XFELD | |
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 | No Sorting |
Medium | 15 | No Sorting |
Long | 20 | No Sorting |
Heading | 10 | No Sorting |
Documentation
Definition
If you set this indicator, the field is used as a key field but no sorting is performed by the DME Engine according to this field.
Use
This setting makes sense if the combined total length of all sort fields is limited, like for example for tree type PAYM, and if it is guaranteed that the calling application has already sorted the data according to this field before calling DMEE.
When using tree type PAYM, for each payment format you define the level of detail for the output division. Fields that have been marked there do not have to be used by the DME Engine for sorting because the calling application PMW has already used these fields for pre-sorting before calling the DMEE. If you set the indicator 'No Sorting' for such a field, you have gained some additional space for further sort fields.
You can set this indicator also for a key field of level 001 if all items have the same value in this field so that no sorting is necessary.
Example
For payment format V3, the field company code is marked in the level of detail for output division. For this reason, you can mark the indicator 'No Sorting' for the DMEE key field FPAYH-ZBUKR.
History
Last changed by/on | SAP | 20040312 |
SAP Release Created in | 640 |