SAP ABAP Data Element GLINDEX (Check index table for superfluous entries)
Hierarchy
☛
BBPCRM (Software Component) BBPCRM
⤷ CRM (Application Component) Customer Relationship Management
⤷ CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
⤷ GBAS (Package) FI-SL Customizing / integration / Basis
⤷ CRM (Application Component) Customer Relationship Management
⤷ CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
⤷ GBAS (Package) FI-SL Customizing / integration / Basis
Basic Data
Data Element | GLINDEX |
Short Description | Check index table for superfluous entries |
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 | IndexTable |
Medium | 15 | Index table |
Long | 20 | Check index table |
Heading | 0 |
Documentation
Definition
This field is only important if the indicator for deleting the line items is also set.
If you select this field, a check will be performed for the index files managed in FI-SL (GLIDXA, GLIDXB, and GLIDXC) after the line items have been deleted. This check is used to find and delete superfluous index records. There should only be superfluous index records in the system if, for example, the transaction data was deleted using a user-programmed ABAP program and the deletion was therefore inconsistent.
Since a lot of CPU time is required to read the index files, you should only select this option (if at all) directly before the production startup.
History
Last changed by/on | SAP | 20100310 |
SAP Release Created in |