SAP ABAP Data Element MCIDLEN (Field length within a MC ID)
Hierarchy
☛
SAP_BASIS (Software Component) SAP Basis Component
⤷ BC-DWB-DIC-AC (Application Component) Activation Program, Conversion Program, DB Utility, MC, SPDD
⤷ SMAC (Package) R/3 Matchcode Development
⤷ BC-DWB-DIC-AC (Application Component) Activation Program, Conversion Program, DB Utility, MC, SPDD
⤷ SMAC (Package) R/3 Matchcode Development
Basic Data
Data Element | MCIDLEN |
Short Description | Field length within a MC ID |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | DDLEN | |
Data Type | NUMC | Character string with only digits |
Length | 4 | |
Decimal Places | 0 | |
Output Length | 4 | |
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 | Field Lgth |
Medium | 15 | Field Length |
Long | 20 | Field Length |
Heading | 5 | Lngth |
Documentation
Definition
In a matchcode ID of update type A, S, P and K, component fields can be included by defining the offset and length (with regard to the field of the original table). The offset and length may not exceed the length of the original field.
The fields marked in the corresponding matchcode object as key fields may not be used as component fields.
Remark: No component fields may be defined for transparent matchcode IDs (update type I).
Supplementary Documentation - MCIDLEN 0001
Use
Procedure
Examples
Dependencies
If you define a field as a partial field by specifying the length and offset, you must define a suitable data element in the column Data element, i.e. the domain to which this data element refers must have the same data type and length as the partial field.
History
Last changed by/on | SAP | 19950209 |
SAP Release Created in | 50A |