SAP ABAP Message Class CNV_20000 Message Number 199 (Consistency check for participating Operating Concerns)
Hierarchy
☛
DMIS (Software Component) DMIS 2011_1
⤷ CA-GTF-BS (Application Component) Business Application Support
⤷ CNV_20000 (Package) Fiscal year Change Package
⤷ CA-GTF-BS (Application Component) Business Application Support
⤷ CNV_20000 (Package) Fiscal year Change Package
Attribute
Message class | CNV_20000 | ||
Short Description | Messages for fiscal year change | ||
Message Number | 199 | ||
Documentation status | Space: object requires documentation | ||
Authorization check Error Message | |||
Changed On | 20141030 |
Message Text
Consistency check for participating Operating Concerns
Help Document
Consistency check for participating Operating Concern
This checkpoint is relevant for both org-dependent and org-independent fiscal year conversion.
This issue affects all generated customer tables from Profitablity Analysis (CO-PA) belonging to an operating concern that is relevant for conversion.
Background
- If a fiscal year variant that is linked to an operating concern or a fiscal year variant that is linked to a controlling area (that is assigned to the respective operating concern) participate in the fiscal year change, all generated tables from CO-PA that are related to the respective operating concern are included in the conversion.
- For operating concerns relevant for conversion, the system does a comparison between the fiscal year variant that is linked to the operating concern and the fiscal year variant that is linked to the controlling area assigned to the respective operating concern.
Ideally fiscal year variants at both these levels should be same, If different they must be customized as follows:
- Same number of posting periods (the number of special periods may vary).
- Same period limits
A difference between fiscal year variants is a inconsistency and CO-PA generated tables related to the corresponding operating concern will not participate in the conversion.
How to proceed
- If this check ends successfully ( status GREEN ), no action is required.
- If this check ends with a warning ( status YELLOW ), the following actions should be preformed:
- Ensure that the fiscal year variants of the operating concern and the assigned controlling area agree (as described above).
- Make sure that data in CO-PA customer generated tables related to such conflicting operating concerns is consistent.
History
Last changed on/by | 20141030 | SAP | |
SAP Release Created in |