SAP ABAP Data Element RKE_TRPR_RECNR (Record Number for Access Log for Summarization Level)
Hierarchy
☛
BBPCRM (Software Component) BBPCRM
⤷ CRM (Application Component) Customer Relationship Management
⤷ CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
⤷ KE (Package) Profitability Analysis
⤷ CRM (Application Component) Customer Relationship Management
⤷ CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
⤷ KE (Package) Profitability Analysis
Basic Data
Data Element | RKE_TRPR_RECNR |
Short Description | Record Number for Access Log for Summarization Level |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | NUMC6 | |
Data Type | NUMC | Character string with only digits |
Length | 6 | |
Decimal Places | 0 | |
Output Length | 6 | |
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 | Number |
Medium | 15 | Record number |
Long | 20 | Record number |
Heading | 6 | Number |
Documentation
Definition
Record number in the log table (TKETRPROT) for subdividing the timestamp for when the summarization level is accessed. The record number is needed in order to make the key unique.
The values are generate via number assignment (number range object COPA_TRPR). A number range that comprise the entire range is automatically created when the trace is activated, if it did not exist already. The number assignment is cyclical, meaning that when the end of the number range is reached, the system begins with the first number again. This cannot lead to collisions, since it is not possible for an overflow to occur within one second.
History
Last changed by/on | SAP | 19980514 |
SAP Release Created in |