SAP ABAP Data Element SGMXLDB (IS-HCM: Max. Number of Entries in Secondary Table per Segmt)
Hierarchy
☛
BBPCRM (Software Component) BBPCRM
⤷
CRM (Application Component) Customer Relationship Management
⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
⤷
NBAS (Package) Appl. development Hospital System master data, catalogs

⤷

⤷

⤷

Basic Data
Data Element | SGMXLDB |
Short Description | IS-HCM: Max. Number of Entries in Secondary Table per Segmt |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | CHAR1 | |
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 | Max. Rows |
Medium | 14 | Max. Rows |
Long | 20 | Max. Number of Rows |
Heading | 3 | Max |
Documentation
Definition
The specification is relevant for the generation of automatic data retrieval. When creating customer segments by copying a reference, the (correct) specification is also copied. This need not be changed.
In a secondary table, several entries can be relevant for an individual segment (or object). This is significant for the automatically generated data retrieval (performance!). Therefore, you should specify the maximum number of entries for each secondary tables, here.
The figure "9" stands for any number greater than 8.
History
Last changed by/on | SAP | 20050224 |
SAP Release Created in |