Hierarchy

⤷

⤷

Basic Data
Data Element | CACS_BUSITIME_B |
Short Description | Effective from |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | CACSTIMESTAMP | |
Data Type | NUMC | Character string with only digits |
Length | 14 | |
Decimal Places | 0 | |
Output Length | 19 | |
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 | EffectFrom |
Medium | 15 | Effective from |
Long | 20 | Effective from |
Heading | 18 | Effective from |
Documentation
Definition
One of two criteria in commission system period management. Both criteria - effective and technical - must be fulfilled so that a contract version for the current period can be used as a basis for the settlement.
Use
Documents the time at which a change in the master data comes into effect. This does not have to be identical to the time at which processing takes place as changes can, for example, be backdated or take effect at some point in the future.
Technical information
The effective validity always refers to the database server clock (time stamp format: YYYY.MM.DD hh:mm:ss). This must be checked against the effective evaluation date, which may differ from the current time. The following special feature applies for the effective start date:
You must not date the effective start date before the oldest date. In the SAP standard system, this date is 01/01/1900. If you do so, there is a risk of the transactional data losing its validity.
History
Last changed by/on | SAP | 20100310 |
SAP Release Created in |