SAP ABAP Data Element SGSECDB (IS-HCM: Segment Secondary DB Table)
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
⤷ 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 | SGSECDB |
Short Description | IS-HCM: Segment Secondary DB Table |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | TABNAME | |
Data Type | CHAR | Character String |
Length | 30 | |
Decimal Places | 0 | |
Output Length | 30 | |
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 | Second.Tab |
Medium | 15 | Second. Table |
Long | 20 | Secondary Table |
Heading | 30 | Secondary Table |
Documentation
Definition
A secondary table is a database table which contains the secondary segment data.
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 also specify the maximum number of entries for each secondary tables in the Maximum Number of Entries fields.
History
Last changed by/on | SAP | 20050224 |
SAP Release Created in |