Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM (Application Component) Customer Relationship Management⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages⤷
KBAS (Package) Overhead Cost Controlling
Basic Data
| Data Element | HIREL |
| Short Description | Selection for time-based fields |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | AS4FLAG | |
| 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 | Time-based |
| Medium | 15 | Time-based |
| Long | 20 | Time-based fields |
| Heading | 33 | Select time-based fields |
Documentation
Definition
Indicator for marking fields as historically relevant.
Use
If you activate the indicator, the master data table field is marked as historically relevant (cost centers, cost elements, activity types,and business processes).
During maintenance, if you change master data fields marked as historically relevant, and define a new analysis timeframe for the changed fields, the SAP system automatically creates a new database record for this processing interval, and changes the time-based validity of existing records. If you do not define a new timeframe, the changed data applies to the lifetime of the master data record.
If you change day-based fields not marked as historically relevant, the changed data also applies to the entire master data record. You can view the changes in the change document.
Note
A great number of changes in mulitple timeframes will result in a correspondingly great number of data records. Mark only important fields as historically relevant.
Consecutive intervals in a master data record become a single record automatically if the field contents are all identical and marked as historically relevant.
Example
Object 1000 has one master data record created with a fiscal year of 12 periods and the cost center name AAAAAAAAAA. During master data maintenance, you change the cost center name in period 5 to BBBBBBBBBB. The SAP R/3 System reacts with one of two options.
- "Name" is marked as historically relevant. The existing master data record for periods 1 - 12 must now become three records:
1000 01-04 AAAAAAAAAA
1000 05 BBBBBBBBBB
1000 06-12 AAAAAAAAAA
- "Name" is not marked as historically relevant. The existing master data record remains intact, with the name changed for the entire existence of the record:
1000 01-12 BBBBBBBBBB
History
| Last changed by/on | SAP | 19940316 |
| SAP Release Created in |
