SAP ABAP Message Class CNV_20100 Message Number 454 (Validity period of &1 differs from &2 in controlling area &3 (CSKB-DATAB))
Hierarchy
DMIS (Software Component) DMIS 2011_1
   CA-GTF-BS (Application Component) Business Application Support
     CNV_20100 (Package) CNCC: Chart of accounts conversion
Attribute
Message class CNV_20100  
Short Description Messageclass for chart of account conversion    
Message Number 454  
Documentation status       Space: object requires documentation
Authorization check Error Message      
Changed On 20141030   
Message Text
Validity period of &1 differs from &2 in controlling area &3 (CSKB-DATAB)
Help Document

Diagnosis

According to the mapping table, you want to merge the cost elements &V1& and &V2& in controlling area &V3& into a cost element called &V4&. Due to the validity periods, which are different for the two original cost elements, overlaps may occur.

Depending on the settings in the mapping table maintenance (priority indicator), changes in the start end end dates of the cost element as well as overlaps of the validity periods for the still existing validity intervals for a cost element may occur.

The system resolves these inconsistencies in the activity Adapt Validity Dates for Cost Elements in the phase Postprocessing Programs During System Lock by processing all validity intervals that exist for a cost element at this point in accordance with the following rules:

  • The system looks at all validity intervals for a cost element starting from the oldest interval (oldest valid-from date) and proceeding into the future.
  • The valid-from date that lies furthest in the past after the conversion (CSKB-DATAB) is set to the valid-from date that lay furthest in the past before the conversion.
  • If the valid-from date of the next interval is smaller than the valid-to date of the interval that is currently being processed, the valid-from date of the next interval is set to the valid-to date of the interval that is currently being processed (plus one day).
  • The valid-to date that lies furthest in the future after the conversion (CSKB-DATBI) is set to the valid-to date that lay furthest in the future before the conversion.

System Response

Procedure

Note that checks or adjustments regarding the validity of cost elements may be required after the conversion.

Make sure that the adjustment logic corresponds to your requirements. If necessary, adjust the validity periods manually after the conversion.

Procedure for System Administration

This message is merely a warning that postprocessing may be necessary after the conversion.

The log of the program for adjusting the validity dates for cost elements contains detailed information about where to make the adjustments.

History
Last changed on/by 20141030  SAP 
SAP Release Created in