Hierarchy

⤷

⤷

Basic Data
Data Element | CACSCALCDAT |
Short Description | Effective Date of a Document/Case (Effective Status) |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | DATUM | |
Data Type | DATS | Date field (YYYYMMDD) stored as char(8) |
Length | 8 | |
Decimal Places | 0 | |
Output Length | 10 | |
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 | Effective |
Medium | 20 | Effective Date |
Long | 20 | Effective Date |
Heading | 10 | Effective |
Documentation
Definition
Date on which an object is effectively valid.
Use
The effective validity determines the exact time-spot when all the master data used in a process as well as the Customizing settings for the commission contract, remuneration type, standard contract and so on must be effectively valid.
In the commission case and commission document, the term effective time-spot is used synonymously.
Dependencies
The effective validity in the master data and Customizing settings determines the period for which the defined information is valid. This lets you store different information for an object for past, present and future periods.
The effective validity is always based on the system clock of the database server.
Example
The effective date (effective validity) of the commission case indicates which effective status of the commission contract is read. Further, the assignment of the commission contract to the organizational structure that is valid on the effective date determines which indirect participants are found.
History
Last changed by/on | SAP | 20100310 |
SAP Release Created in |