Kontakt

Ansicht
Dokumentation

FAA_CMP_LDT - Define Transfer Date and Additional Parameters

FAA_CMP_LDT - Define Transfer Date and Additional Parameters

Fill RESBD Structure from EBP Component Structure   RFUMSV00 - Advance Return for Tax on Sales/Purchases  
This documentation is copyright by SAP AG.
SAP E-Book

In this app you can define settings for company codes and ledgers that are relevant for Asset Accounting.

Object Settings
Company Code: - Define Company Code Status and Set Company Code Block
- Legacy Data Transfer: Create and Change Legacy Data Transfer Segments with Parameters
Company Code Ledgers: - Define Current Fiscal Year (for a New Company Code)
- Execute Year-End Closing
- Undo Year-End Closing
- Define Planning Horizon for Evaluating Future Fiscal Years

The tree structure on the left of the screen shows the following objects:

  • Company codes that are relevant for Asset Accounting
  • For each company code: Ledgers that are relevant for Asset Accounting.
    These are the representative ledgers of an accounting principle. Extension ledgers, for example, are not displayed.
On the right of the screen, you see the following settings for a ledger: the real depreciation areas with their last closed fiscal year. The derived depreciation areas are not displayed.

To define settings for a company code or ledger, choose the corresponding entry from the tree structure.

For more information about settings, see the sections that follow.

Define Company Code Status and Set Company Code Block

On the General Settings tab page, you define the status for a company code (company code status).

You can also block a company code against further changes in Asset Accounting. As soon as the block indicator is set for a company code, it is no longer possible to make postings on fixed asset accounts or changes to the asset master record in the company code.

To define the company code status and/or to block the company code, go to the tab General Settings and proceed as follows:

  1. Select the company code for which you want to define the settings.
  2. Define the company code status if necessary.
  3. Set the relevant indicator to block a company code against changes in Asset Accounting.
  4. Choose Save.

To remove the block at a later date, delete the indicator again and choose Save.

Legacy Data Transfer: Create and Change Legacy Data Transfer Segments with Parameters

On the Legacy Data Transfer tab page, you create a legacy data transfer segment to be able to transfer fixed assets on a specific transfer date. Apart from the transfer date, you also define additional parameters for the legacy data transfer.

Important for New Customers:
Before you start with the legacy data transfer and start using Asset Accounting, note the following for a new company code:

  • The system determines the current fiscal year and the last closed fiscal year based on the transfer date of the first legacy data transfer segment. The transfer date of Asset Accounting is therefore the validity start date for a company code.
  • The transfer date of Asset Accounting is not allowed to be before the transfer date of General Ledger Accounting.
    You define the transfer date of General Ledger Accounting in the app Settings for Legacy Data Transfer in the Migration Date field.
  • SAP provides a document type for the legacy data transfer. The document type is defined in such a way that it allows postings on accounts of the account types Assets and G/L Accounts.
  • To be able to perform the legacy data transfer, a maximum of one fiscal year is allowed to be open when transferring at the end of the fiscal year, and that is the fiscal year after the transfer. With a legacy data transfer during the year, only the fiscal year in which the transfer takes place is allowed to be open.

To create a legacy data transfer segment, proceed as follows:

  1. From the tree structure, choose the company code for which you want to create the legacy data transfer segment.
  2. On the Legacy Data Transfer tab, choose the button Create Legacy Data Transfer Segment.
  3. Enter the transfer date.
  4. As the status, the system first specifies the status In Preparation.
  5. Choose a document type for the legacy data transfer in Asset Accounting.
  6. If you want to perform the legacy data transfer during the year, set the indicator Suppress Depreciation Calculation.
  7. Choose Save.

Note: You can re-delete a legacy data transfer segment as long as there are no legacy assets for this segment in the system.

Follow-on activities:

  1. Perform the legacy data transfer using the usual tools (this usually means using the SAP S/4HANA migration cockpit).
  2. Check the result and reconcile it with the legacy system.
  3. If necessary, repeat the first steps.
  4. Set the legacy data transfer status to Completed.
  5. Choose Save.

For more information about the legacy data transfer, see the application documentation (Product Assistance) under Asset Accounting -> Legacy Data Transfer.

Define Current Fiscal Year (for a New Company Code)

Before you can make postings in a new company code, you must first define the current fiscal year and perform a balance carryforward to the current fiscal year.

To define the current fiscal year, you have the following options:

  • If you want to perform a legacy data transfer, you can define the current fiscal year by stating the transfer date in the legacy data transfer segment.
    See the section above on legacy data transfers.
  • If you do not perform a legacy data transfer for the new company code, you can define the current fiscal year directly in the ledger settings.
    For this, see the following section 'Activities'.

  1. From the tree structure, choose the ledger for which you want to define the current fiscal year.
  2. Under Ledger Settings, enter the current fiscal year in the field Highest Fiscal Year.
  3. Choose Save.

Execute Year-End Closing

You can close a fiscal year from an accounting view for a ledger or for a depreciation area. It is then not possible to make postings or change values (for example, by recalculating depreciation) in Asset Accounting for the closed fiscal year.

The fiscal year that is closed is always the year following the last closed fiscal year. The current fiscal year should not be closed unless you want to deactivate the company code.

  • The system found no errors during the calculation of depreciation (such as, incorrectly defined depreciation keys).
  • Planned Depreciation was not Posted Completely to the General Ledger
  • All assets acquired in the fiscal year have already been capitalized.
This prerequisite does not apply to assets under construction as this would not make any sense. The system therefore does not make any corresponding check for assets under construction.
  • All incomplete assets (master records) have been completed.

You can either close the fiscal year at ledger level or at the level of the individual depreciation areas.

Year-End Closing at Ledger Level:

This involves closing the fiscal year for all depreciation areas of the ledger. Prerequisite for this therefore is that all depreciation areas have the last closed fiscal year.

  1. From the tree structure, choose the ledger for which you want to perform the year-end closing. You can close the fiscal year using the context menu.
  2. Choose Save.

Year-End Closing at the Level of Individual Depreciation Areas:

If you want to do this, you must choose one or more depreciation areas and close it/them. (If you choose all depreciation areas, it is the same as performing a year-end closing at ledger level).

This option makes sense when you expect that you will have to reopen some depreciation areas and close them again later (for tax reasons, for example).

  1. Choose the depreciation areas you require and then close the fiscal year using the corresponding pushbutton.
  2. Choose Save.

Note:
On ledger level, you can jump to the Display Balance Carryforward Status app. To do this, next to the Highest Fiscal Year field, press the Display Balance Carryforward Status pushbutton. The system then displays the balance carryforward for the highest fiscal year (that is, the latest fiscal year opened by a fiscal year change). From the Display Balance Carryforward Status app, you can jump to the balance carryforward log.

Undo Year-End Closing

If you have closed a fiscal year by mistake and still have to make adjustments, you can reopen the last closed fiscal year for one or more depreciation areas of a company code.

Note:
A fiscal year that is already closed from an accounting point of view and has been certified by an external auditor is not allowed to be reopened. However, it is worth checking with your external auditor to see if this is still possible.

To reopen the last closed fiscal year for individual or all depreciation areas of a company code, perform the following steps on the General Settings tab:

  1. From the tree structure, choose the ledger for which you want to reopen the fiscal year.
  2. Select the depreciation areas and open the previous year for them using the corresponding button.
  3. Choose Save.

Follow-on activities:

  1. Make your adjustments in the previous year. (The corresponding posting periods must be open in General Ledger Accounting for this.)
  2. Execute all necessary year-end closing operations.
  3. Make sure that the previous year is closed again in both Asset Accounting and General Ledger Accounting.
    To close the fiscal year in Asset Accounting, proceed as described above.

Define Planning Horizon for Evaluating Future Fiscal Years

Reports, such as the asset history sheet or the asset list, do not support the evaluation of planned values of future fiscal years. However, if you want to see planned values for fiscal years after the current fiscal year in your reports, you can specify a planning horizon in years for each company code and ledger. The planning horizon defines the number of years for which the planned values are updated after the current fiscal year and are then available in reporting. The planned values are calculated for each fiscal year and period, and are saved so that reporting can be period-based.

The planning horizon only affects reporting. In the Manage Fixed Assets app however, you can also calculate and display all future asset values of a fixed asset irrespective of the defined planning horizon.

You define the planning horizon at ledger level; it is therefore valid for all depreciation areas of the ledger.

The upper limit for the planning horizon is five years. For more information, see the field help for the Planning Horizon in Years.

To define the planning horizon, follow these steps:

  1. From the tree structure, choose the ledger for which you want to define the planning horizon.
  2. Under Ledger Settings, make the following entries:
If you would like to have future fiscal years in reporting, enter the number of years you want for the planning horizon; a value between one and five is allowed.
- If you had defined a planned value calculation but would like to deactivate this, then enter 0 years as the planning horizon.
  1. Choose Save.

Recalculating Depreciation After Changing the Planning Horizon:

If you either first defined the planning horizon or changed it, then you must recalculate depreciation for the affected ledger in the company code. This recalculates the planned values for the newly configured planning horizon and the planned values will then be available in reporting.

Caution: If you change the planning horizon without recalculating depreciation, this can cause incomplete planned values in reporting.

Recalculating Depreciation After the Balance Carryforward:

After the balance carryforward, you must recalculate depreciation for all company codes and ledgers that have a defined planning horizon. This recalculation generates planned records for the year that is now missing at the end of the planning horizon. For example, if you have defined a planning horizon of three years and have executed the balance carryforward for the following year YYYY+1, then the recalculation of depreciation generates the additional planned values for the year YYYY+1+3.






SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up   ABAP Short Reference  
This documentation is copyright by SAP AG.

Length: 15605 Date: 20240523 Time: 203603     sap01-206 ( 310 ms )