Show TOC

 FI-AA (New): Functions

 

The following explains which functions were changed in SAP Accounting 1503 (Initial Shipment) powered by SAP HANA and the effects of these changes.

Technical Details

Product Feature Is

Changed

Country Dependency

Valid for all countries

Software Component Version

SAP_FIN 720

Application Component

FI-AA (Asset Accounting)

Available As Of

SAP Accounting 1503 (Initial Shipment) powered by SAP HANA

Updating Journal Entries

The journal entries are updated in Financial Accounting at asset level. The entry also contains the asset number.

Depreciation Posting Run

The determination of the accumulated depreciation of an asset and the posting of depreciation expense takes place in the system from now on at different points in time:

  1. Calculate depreciation (transaction AFAR):

    The planned depreciation is determined with each master record change and with each posting on the asset and updated in the database accordingly.

  2. Post depreciation (transaction AFAB):

    The depreciation run adopts the planned asset values and posts them in Financial Accounting. The posting document is updated in Financial Accounting at asset level.

The new program for posting depreciation (depreciation run) has the following characteristics:

  • For the update of accumulated depreciation and depreciation expense, the following applies:

    • The planned depreciation is determined with master record changes and with postings on the asset and updated in the database accordingly.

    • The depreciation run adopts the planned asset values and posts them.

    • The journal entry is updated in Financial Accounting at asset level.

  • Errors with individual assets do not necessarily need to be corrected before period-end closing; period-end closing can still be performed. You have to make sure that all assets are corrected by the end of the year only so that depreciation can be posted completely.

  • It is possible to execute a mid-year test run (also the first run of a period) with a restriction on assets.

  • The following applies to parallel processing: The program always carries out parallel processing.

    Caution Caution

    You can still specify a server group.

    • If you specify a server group, the system behaves as it has until now.

    • Until now if nothing was specified for the server group then no parallel processing took place. However, in the new program parallel processing takes place for the depreciation run on all available servers.

    End of the caution.

  • Only the following statuses exist now for the depreciation run:

    • Errors occurred

    • Documents posted successfully

    • No documents to post

    You can check the status of the depreciation run in the log (job log or spool output) or in the Schedule Manager.

  • The following constraints still apply:

    • In a test run, the depreciation run can be started in dialog with a limit to a maximum of 1000 assets.

    • The update run can only be started in the background.

    • It must be possible to post the company code during the update run.

  • If the program is started in the background, an entry is written in the Schedule Manager for each combination of company code/accounting principle (ledger group).

One difference now is that it is no longer necessary to specify a run type because the program recognizes whether the depreciation run is being run for the first time or whether it is a repeat run.

It is no longer possible to display journal entries in the test run of the depreciation run.

The smoothing method is no longer necessary and is therefore no longer supported.

Periodic Asset Postings

As of SAP Accounting 1503 powered by SAP HANA, all APC changes in Asset Accounting are posted to the general ledger in real time or immediately. Periodical APC postings are therefore superfluous and are no longer supported. This also applies for the procesing of reserves for special depreciation.

This affects the Customizing settings for the depreciation area as follows: All options previously used to post APC to the general ledger periodically are now inapplicable. Instead the following indicator must be set for the affected depreciation area:

Depreciation Area

Indicator

Reserve for special depreciation area

4 - Area Posts APC Immediately, Depreciation Periodically

Area for parallel valuation with the accounts approach

4 - Area Posts APC Immediately, Depreciation Periodically

Area for parallel valuation with the ledger approach

1 - Area Posts in Real Time

The migration guide explains how the indicator is adjusted in the charts of depreciation under Migration to New Asset Accounting (FI-AA (New)).

Reconciliation Between Asset Accounting and the General Ledger

It is no longer necessary to reconcile the general ledger with the subledger of Asset Accounting as from now on Asset Accounting is automatically reconciled with the general ledger. The programs that existed until now for reconciliation (RAABST01, RAABST02 and FAA_GL_RECON) are therefore no longer available.

Fiscal Year Change/Balance Carryforward

The balance carryforward of Asset Accounting is integrated with the balance carryforward of Financial Accounting with the universal journal entry:

  • With the balance carryforward of Financial Accounting, values carried forward are written on both account and ledger level for each asset.

  • The new year is opened in Asset Accounting only when all representative ledgers of a company code have been carried forward.

  • In order to determine the planned depreciation values for the depreciation run, the system automatically triggers a recalculation of values for all fixed assets in the new year.

  • If errors occurred, you should start the recalculation again manually.

The program Fixed Assets-Fiscal Year Change (RAJAWE00) is no longer necessary and no longer has to be performed at fiscal year change.

Reports for Posted Depreciation

Reports for posted depreciation that are based on table ANLP (especially report Posted Depreciation, Cost Center-Related, transaction S_ALR_87010175, InfoSet /SAQPQUERY/AM27) can no longer work on the basis of the account assignment objects of the fixed asset they are based on. Exception: The accumulated depreciation accounts are managed as a statistical cost element. Whilst there is no new fixed asset-specific report, you can display the Fiori app G/L Account Line Items with the corresponding filter criteria instead. The expense items are from now on updated with the information of the source fixed asset.

Legacy Data Transfer

The legacy data transfer had to be adjusted in Asset Accounting due to the introduction of the universal journal entry.

Manual Legacy Data Transfer

The manual legacy data transfer is now divided into the following steps:

  1. You create asset master records for the legacy data transfer using transaction AS91.

  2. You post the transfer values using transaction ABLDT; In doing so, a universal journal entry is posted for the fixed asset.

  3. With this transaction AB01, you post, for a legacy data transfer during the year, the transactions that occurred in the fiscal year of the legacy data transfer between the start of the fiscal year and the date of the legacy data transfer.

  4. You use transaction ABLDT_OI to post the open items for an asset under construction with line item processing.

The following functions are also available with the manual legacy data transfer:

  • If wrong transfer values were posted, you must reverse the journal entry and then recreate it.

  • You can use transaction AS92 to change master data; transaction AS93 to display master data; and transaction AS94 to create subnumbers for the asset master record.

  • There are corresponding transactions for group assets with the legacy data transfer (transactions AS81 to AS84).

You can find the changed Customizing activities and functions for the legacy data transfer in Customizing for Asset Accounting (New) under Asset Data Transfer.

Automatic Legacy Data Transfer

In addition to the manual transfer, the following automatic (mass-compatible) transfer methods are available:

  • Legacy data transfer using Microsoft Excel (transaction AS100)

    Transaction AS100 is still available; it has been completely adapted to the logic of the universal journal entry.

  • Legacy data transfer using Legacy System Migration Workbench (transaction LSMW)

    With the legacy data transfer using transaction LSMW, you can only transfer legacy assets using the business object method. The options Batch Input and Direct Input are no longer available.

  • Legacy data transfer using BAPI

    With this you create a customer-defined program that calls module BAPI_FIXEDASSET_OVRTAKE_CREATE.

    This corresponds with choosing method CREATEINCLVALUES of business object BUS1022 in transaction LSMW.

  • Transfer of mid-year transactions

    You cannot only transfer mid-year transactions when creating legacy assets; You can also post them subsequently using the standard BAPI for Asset Accounting. All standard functions of the relevant posting BAPI are available with this. The system posts these transactions automatically against the migration clearing account.

Due to extensive changes in the data store of Asset Accounting, the following mass-compatible transfer methods are no longer supported:

  • Program RAALTD01

  • Program RAALTD11

  • Program RAALTD11_UNICODE

  • Any type of batch input on the transactions AS91, AS92, AT91, AT92, AS81, AS82, AT81 and AT82 only allows the creation and change of master data. Values cannot be transferred this way. You must rather use transaction ABLDT; however this is not mass-compatible. The AT** transactions were also deleted; the above also and explicitly refers to customer-defined replacement transactions created analog.

Archiving

The reload program for archiving RAARCH03 is no longer supported. Archived documents of Asset Accounting can only be written if they have not been reloaded.

More Information

For more information, see: