Ansicht
Dokumentation
FINSC_UI_SHADOW_LED - Create Ledger for Alternative Fiscal Year Variant
TXBHW - Original Tax Base Amount in Local Currency General Material DataThis documentation is copyright by SAP AG.
You can create a parallel ledger and assign it to company codes for which you need alternative fiscal year variants.
------------------------------------------------------------------------------------------------------------------------------------------------------------
Important Note
Do not use this configuration activity to create a new ledger for an alternative fiscal year variant. Only use this configuration activity to maintain company code settings.
If you want to assign an alternative fiscal year variant to a new company code, use the Assign Fiscal Year Variants to Ledgers and Company Codes configuration activity instead.
------------------------------------------------------------------------------------------------------------------------------------------------------------
Fiscal year variants (FYV) define the relationship between the calendar and fiscal year. They specify the number of periods and the start and end date of a fiscal year. By default, the fiscal year variant delivered by SAP is set to a common fiscal year variant (that is, K4 - calendar year) for all company codes and countries.
Globally acting companies, however, might need different fiscal year for group close and for local close.
In countries such as Australia, Japan, and India, for example, the local close has to be conducted at a legally binding and predetermined date (on March 31st, for example). This date usually differs from the group closing date (taking place on December 31st, for example). This means that in addition to the group fiscal year, the relevant company codes need a second alternativefiscal year.
If you need an additional fiscal year variant due to legal reasons, you can create an additional parallel ledger, that is, a non-representative ledger, that is grouped together with one of the predefined ledgers 0L, 2L, or 3L (called reference ledger of the non-representative ledger). Then you assign the company codes which require a parallel alternative FYV to the non-representative ledger.
Based on this grouping, the system posts to both the additional parallel ledger and the reference ledger you assigned it to. For example, you create a new parallel ledger Z1 and assign it to reference ledger 0L. When a journal entry is now posted to the reference ledger (0L), the system simultaneously updates the parallel ledger Z1. If you, however, want to post a journal entry to ledger Z1 only and not to its reference ledger 0L, you can to this by posting a manual journal entry to ledger group Z1 (see also the example given below).
Caution
You can assign a non-representative ledger to the ledger for the group accounting principle and/or to the ledger for the local accounting principles.
If you need to assign the non-representative ledger to the ledger for a group accounting principle (2L - IFRS or 3L - US-GAAP), you can only create a non-representative ledger in a new system where no journal entries have been posted in the productive system for any company code yet.
If you need to assign the non-representative ledger to the ledger for the local accounting principles, you can only create a non-representative ledger if no postings exist for this local accounting principle and thus for all company codes assigned to this accounting principle and corresponding country.
After you have saved the non-representative ledger, you can no longer update or delete settings, such as changing the reference ledger or unassigning an already assigned company code.
You can, however, assign new company codes to a non-representative ledger at a later point in time, as long no journal entry has been posted for the company code (in the production system).
If you are using the Asset Accountingapplication component, you
might need to make manual correction postings because the depreciation procedure is only based on the
fiscal year variant of the reference ledger (which is copied to the non-representative ledger). For more information, see SAP notes 844029, 1951069, and 2640035.
You should therefore consider carefully whether you need to make use of this solution as severe errors may occur if the non-representative ledger is not used correctly.
Using ledger groups in business transactions
Please be aware of the importance to use the correct ledger groups in business transactions, such as in manual journal entries.
You have created a non-representative ledger Z1 for reference ledger 0L, and common ledger group ZL.
- Without a ledger group entry, the journal entry will be posted in all ledgers, 0L, Z1, and 2L.
- With ledger group Z1 you only post to ledger Z1. This might be useful if you want to adjust figures only in ledger Z1 but not in 0L, for example, because you need a manual correction of depreciation figures in Asset Accounting which might be inaccurate because the depreciation procedure is based on the group fiscal year variant assigned to the representative ledger 0L. To report your data and values for the alternative fiscal year variant (which is assigned to your non-representative ledger Z1), you will have to use generic accounting reports for your value evaluation, such as Trial Balanceor Display Line Items. The depreciation values for this non-representative ledger Z1, which uses the alternative fiscal year variant, cannot be evaluated using Asset Explorer or any other reports in Asset Accounting.
- With ledger group 0L, the system will automatically update also your non-representative ledger Z1.
- With ledger group 2L or 3L your posting will only affect ledger 2L or 3L, respectively. This is only useful for postings relevant for the group accounting principles IFRS or US-GAAP.
For more information on creating parallel ledgers, see SAP note 2568382.
TXBHW - Original Tax Base Amount in Local Currency TXBHW - Original Tax Base Amount in Local Currency
This documentation is copyright by SAP AG.
Length: 6564 Date: 20240523 Time: 204621 sap01-206 ( 141 ms )
