The fiscal year version defines the number and relation to the calendar of the depreciation periods in the fiscal year in Asset Accounting. Asset Accounting generally uses the same fiscal year version as Financial Accounting (general ledger). In this case, the depreciation periods of Asset Accounting correspond to the posting periods of Financial Accounting (without special periods). The system therefore automatically defaults the fiscal year version of FI-GL when you define the FI-AA system settings for a company code. You do not need to make any system settings in this section if your depreciation periods and G/L posting periods are identical.
In some cases, however, the G/L posting periods are not suitable for determining depreciation in Asset Accounting. In this step, you define the FI-AA-specific fiscal year versions when this is the case.
You can specify your own fiscal year version in the following implementation activities in the FI-AA definition of the company code below the company code for each FI-AA depreciation area
You cannot define fiscal year versions in this step. You enter the actual definitions of the fiscal year versions and their relationship to the calendar in the general section of FI Customizing.
However, a different fiscal year version can only be used in Asset Accounting if the start and end dates of the versions in Asset Accounting and Financial Accounting are the same. This also applies to depreciation areas that do not post automatically to the general ledger (when you have fiscal year versions that are specifically for given depreciation areas).
You can only change the fiscal year version in Asset Accounting as long as the company code does not have production status.
If a fiscal year version with 13 (normal) posting periods is used in the general ledger, then you normally need a different fiscal year version to represent a number of FI-AA period controls (for example, first-year convention). The reason is that the depreciation calculation only works with full periods, but the middle of the year in this example is 6.5 posting periods.
You can find the Fiscal Year Variant customzing under the following IMG / Transaction SPRO:
It is NOT recommend to change a Fiscal Year Variant that has already been assigned to a company code and already has some postings. This may create database inconsistencies in your system.
SAP System Landscape Optimization (SLO) provides a service for"Prolonged fiscal year consulting".
For details about the scope and proceeding of this service you can usethe service desciption for "Shortened fiscal year consulting". You find our service description on the SAP Service Marketplace (link: http://service.sap.com/slo -> SAP Conversion Services/Data Harmonization Consulting -> Detailed Information -> Shortened fiscal year consulting.
Useful notes / adverse effects :
672255 Shortened fiscal year/changing fiscal periods
10945 F4554: Entry for 12/31 is missing
427920 Analysis program for fiscal year conversion
210861 Changing fiscal year variant in production system
193713 SAPF070: Change of fiscal year variant
123026 Shortened fiscal year is not recognized/AA653
Please notice that as mentioned in the notes, if you decide to change the Fiscal Year variant, and any inconsistencies arise, it will be considered as consulting issue, see note 83020 for more information.