SAP ABAP Data Element CACSTECHTIME (Technical Validity (Time Stamp: YYYY.MM.DD hh:mm:ss))
EA-APPL (Software Component) SAP Enterprise Extension PLM, SCM, Financials
   ICM (Application Component) Incentive and Commission Management (ICM)
     CACSVERS (Package) ICM: Versioning
Basic Data
Short Description Technical Validity (Time Stamp: YYYY.MM.DD hh:mm:ss)  
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 Tech.Vald. 
Medium 15 Techn. Validity 
Long 20 Technical Validity 
Heading 15 Techn. Validity 


Point at which an object is technically valid.


The technical validity determines the exact time-spot when the process determines the editing status of the master data and Customizing settings.

The technical validity is generally set to the current time-spot. This means that the current editing status of the master data and Customizing settings are taken into account by the process. By specifying a historical time-spot (such as the correction of a historical commission case), it is possible to run the process with the editing status of master data and Customizing settings that was valid at that point in the past.

In the commission case and commission document, the term calculation time-spot is used synonymously.


In the master data and Customizing settings, the technical validity documents the exact time of processing. This means that the different change statuses for a master data object or Customizing object are stored like a change history.

During editing, new versions are created with a technical validity period starting from the editing time-spot through to the HIGH-DATE (12/31/9999). Previously valid versions now end with the editing time-spot.

The technical validity is always based on the system clock of the database server.

Last changed by/on SAP  20100310 
SAP Release Created in