SAP ABAP Data Element DDPROTOCOL (Log Data Changes)
Hierarchy
☛
SAP_BASIS (Software Component) SAP Basis Component
⤷ BC-DWB-DIC-AC (Application Component) Activation Program, Conversion Program, DB Utility, MC, SPDD
⤷ SDIC (Package) ABAP Dictionary
⤷ BC-DWB-DIC-AC (Application Component) Activation Program, Conversion Program, DB Utility, MC, SPDD
⤷ SDIC (Package) ABAP Dictionary
Basic Data
Data Element | DDPROTOCOL |
Short Description | Log Data Changes |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | DDPROTOCOL | |
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 |
Medium | 15 | Log |
Long | 20 | Log |
Heading | 30 | Log |
Documentation
Definition
The logging flag defines whether changes to the data records of a table should be logged.
Use
If you have set the indicator for logging, every change (with UPDATE, DELETE) to an existing data record by a user or an application program is recorded in a log table in the database.
Note:
If you have activated logging, this slows down accesses that change the respective table. The reasons for this are as follows:
- The system must write a record in the log table for each change.
- Many users access this log table in parallel. This could cause lock situations, even though the users are working with different application tables.
Dependencies
- Logging only takes place if the parameter rec/client in the system profile is set correctly. Setting the flag on its own does not cause the table changes to be logged.
- The existing logs can be displayed using the Transaction Table History (SCU3).
History
Last changed by/on | SAP | 20110908 |
SAP Release Created in |