SAP ABAP Data Element LOGGINGFLG (Indicator field for update log)
Hierarchy
☛
BBPCRM (Software Component) BBPCRM
⤷ CRM (Application Component) Customer Relationship Management
⤷ CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
⤷ MCS (Package) R/3 application development: Logistics Information Warehouse
⤷ CRM (Application Component) Customer Relationship Management
⤷ CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
⤷ MCS (Package) R/3 application development: Logistics Information Warehouse
Basic Data
Data Element | LOGGINGFLG |
Short Description | Indicator field for update log |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | KEYFLAG | |
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 | Log ind. |
Medium | 15 | Logging field |
Long | 20 | Logging field |
Heading | 3 | Log |
Documentation
Definition
Choose a field in your information structure to be the key field for the update log.
SAP recommends that, where possible, you use a field which specifies the document number or something else of relevance.
Use
The Logistics Information Systems enable you to run a log of the updated records. This means that you can check the updating of the info structures for the event. More than one data record can be imported at any one time; therefore logging is carried out for one field in your communication structure.
You can then use this field to distinguish between the imported data records in the log.
History
Last changed by/on | SAP | 19971006 |
SAP Release Created in |