SAP ABAP Message Class CNV_20000 Message Number 231 (Consistency check for accounting documents:)
Hierarchy
☛ DMIS (Software Component) DMIS 2011_1
   ⤷ 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 231  
Documentation status       Space: object requires documentation
Authorization check Error Message      
Changed On 20141030   
Message Text
Consistency check for accounting documents:
Help Document

Consistency check for Accounting documents

This check is relevant for both org-dependent and independent fiscal year conversion.

This check is made in correspondence to the analysis check 'Number range conflict in non-leading ledgers', if same number range is used by participating and non-participating non-leading ledgers of a company code (check logs of activity 'Start Fiscal Year Analysis').

Background

While reducing or increasing the fiscal year in the conversion service, issue of duplicate accounting document in fiscal year conversion might come in a system where number ranges are defined year dependent and also having the same period limit (i.e. from number # to number) due to fact that number range is shared between at-least 2 non leading ledgers of a company code which are using different fiscal year variants (one ledger is participating and other is not).

Example:
Document number 100000 was posted in company code 0001 in fiscal year 1999 for non-leading ledger L1 and same document got posted for same company code in fiscal year 2000 for non-leading ledger L2.

Company code 0001-ledger L2 participates in the conversion as associated with participating fiscal year variant, while company code 0001-Ledger L1 associated with non-participating fiscal year variant does not participate in conversion.

If a fiscal year conversion was now carried out then fiscal year for document 100000 of company code 0001 Ledger-L2 would be reset (from 2000 to 1999), while for company code 0001- Ledger L1 the fiscal year would remain the same, so that document 100000 for fiscal year 1999 would cause a dump while updating BKPF table.

This check will list all the accounting document numbers which cause duplicate issue during conversion. Those accounting documents will be considered which are posted before the execution date of activity 'Start Fiscal year Analysis''(rest of the documents will be scanned in the downtime).

How to proceed:

  • If this check ends successfully ( status GREEN ), no action required.
  • If this check ends with warning ( status YELLOW ), following actions will be performed.
    • Conflicting accounting document numbers needs to be renamed, mapping will be created for accounting documents in phase 'Preprocessing programs DURING system lock '.

Accounting documents using internal number ranges:

  • For internal number ranges mapping will be created for accounting document numbers in activity 'Mapping of Accounting Documents using Internal Number Ranges'' based on the current NRLEVELof the number range, for details please refer to Mapping of Accounting Documents using Internal Number Ranges
  • While creating a mapping if internal number range is exhausted, following action needs to be performed:
    • Extend number range for respective company code.
    • In case existing number range cannot be extended, provide a new number range.

Note: This approach will create gaps in FI document numbering.

All above suggestions needs to be agreed with your auditors and then proceed with the conversion.

Accounting documents using external number ranges:

  • For external number ranges mapping will be created for accounting documents numbers in activity 'Mapping of Accounting Documents using External Number Ranges' based on the prefix given for each impacted number range number, for details please refer to Mapping of Accounting Documents using External Number Ranges
  • Old number range number should be adjusted in a way that accounting documents after adding prefix should lie in respective intervals.

Note: This approach will create gaps in FI document numbering.

All above suggestions needs to be agreed with your auditors and then proceed with the conversion.

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