New Asset Accounting

• Features in New Asset Accounting
• Advantages in New Asset Accounting
• Technical changes to the Table
• Configuration changes
• Changes and deleted functions
• New BAPIs
• Technical clearing account
• Migration procedure
• SAP Notes for more information

​

1

�Features in New Asset Accounting�

1. Using new AA is mandatory
2. ACDOCA now includes fields like Dep Area, Transaction type Asset value date and Asset number
3. FI-AA reconciliation (ABST2)is abolished
4. Asset balance (AJAB) carry forward with the GL balances
5. Depreciation posting program is simplified and performance improved
6. Depreciation posting is made per Asset
7. Each depreciation area must be assigned to a ledger grp
8. Multiple depreciation areas can post in real time( each accounting principle can have its own ledger grp)
9. Delta depreciation postings are no longer needed (only one depreciation area per accounting principle)

​

2

�Features in New Asset Accounting�

10. Periodic posting (ASKBN) is now obsolete

11. Assignment of posting indicators to depreciation areas simplified

12. For each parallel currency in FI, a corresponding depreciation must exist

13. Smoothing of depreciation over remaining periods is now obsolete

14. New Asset APC posting logic introduced. Separate for each accounting principle

15. Settlement of AUC at depreciation area level

16. New posting logic in AA requires Technical clearing account for Assets acquisition posting

17. Postings are divided into Operation view and valuation view

​

3

�Features in New Asset Accounting�

18. Both multiple valuation approaches are possible: Ledger approach and Account approach. But a mixture of two is not supported (Ledger with accounts approach)

19. Legacy upload GL account is part of Configuration

20. Legacy upload document type is part of configuration

21. Technical clearing account is part of configuration

4

�Advantages in New Asset Accounting�

• Instant Access to Correct Up-to-Date Values
• When a change is made to an asset, its planned depreciation (used to post actual depreciation) is immediately updated, and all reports show up-to date values.
• Single Source of Truth
• FI and Asset Reconciliation is by design
• Simplification of Posting Logic
• New transactions and accounts have been introduced that allow you to post independently to individual depreciation areas, accounting principles, or ledger groups, if required.
• Transparency
• A separate line item is produced for each asset posting, including the acquisition and retirement values, the depreciation P&L charge, and the accumulated depreciation, which allows full visibility in FI.
• No Redundancy of Data
• New Asset Accounting no longer requires the use of delta depreciation areas in addition to normal depreciation areas.

​

5

�Advantages in New Asset Accounting�

• Smart Migration
• Compatibility views in SAP S/4 HANA have the same name as previous tables to allow custom reports when migrating from SAP to S/4 HANA and certain program to continue as earlier.
• Easy reporting structure
• Because of Universal general reporting is easy to fetch the data
• Smooth Period end closing

​

6

Technical Changes to the Tables

7

aa

BKPF

ACDOCA

ANEK

ANEP

ANEA

ANLP

ANLC

FAAT_DOC_IT

FAAT_PLAN_VALUES

FAAT_YDDA

�Configuration changes�

• Depreciation area with accounting principles
• Technical clearing account at account determination level
• Setting depreciation for Quantity update in case of collective low value Assets
• Define alternative document type for ledger postings
• For every additional currency type defined on the company code a corresponding depreciation area needs to be set up
• Define revenue distribution for fixed Asset retirement
• In new Asset Accounting, it is not possible and also not necessary to restrict transaction types to depreciation areas.
• Smoothing is no more available
• Post NBV instead of Gain/Loss

​

​

​

​

​

​

​

​

​

8

�Configuration changes�

• Unilateral Assets
• Depending on the legal requirements, it may be necessary to manage a fixed asset in one accounting principle (such as local valuation) as an asset, but in a different accounting principle (for example, IFRS) not to manage it as an asset, but post the costs directly to profit and loss instead.

9

Changes and deleted functions

• You enter post-capitalization both gross and net in the same transaction (transaction ABNAL). The system always calculates the depreciation values, meaning in the standard system it assumes that you are entering gross values.
• A revaluation is always posted accounting principle-specific.
• The Accounting Principle field in transaction ABAWL is therefore a required entry field.
• With a partial retirement it is no longer possible to adjust the retirement amount manually, for example for cost-accounting areas.
• Instead you must perform an adjustment posting in an extra step for the cost-accounting area.
• 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.

​

​

​

​

Changes and deleted functions

• Insurance Values
• Until now there were two ways to map insurable values in the system:
1. Defining specific information for insuring the complex fixed asset in the asset master record
2. Managing insurance values in a dedicated depreciation area.
• In SAP S/4HANA only the second option
• The leasing opening entry from the asset master record is not supported in SAP S/4HANA.
• It is no longer necessary (or possible) to restrict the transaction types to individual depreciation areas.
• The user exit APCF_DIFFERENT_AMOUNTS_GET is no longer supported.
• The reload program for archiving RAARCH03 is no longer supported.
• Archived documents of Asset Accounting can only be written but not reloaded.

​

New BAPIs

​

​

�����Technical Clearing Account�����

• Purpose�To post multiple ledgers at the same time it is necessary to split the postings into operational and valuated document
• It is a Reconciliation account

​

​

​

​

​

​

​

​

​

​

​

​

13

Ledger Approach�Because we’ve left the Ledger Group field blank when posting, all ledger�groups were posted to, producing a separate document for each accounting�principle/ledger group.�

14

Simple Nonintegrated IFRS Posting

Simple Nonintegrated Local GAAP Posting

15

Account Approach

​

A separate range of accounts has been set up for the second accounting principle, named Group Accounting with a Ledger Group of A1, but in the same ledger. The accounts are similar but two digits shorter.

Simple Nonintegrated Local GAAP Posting

Simple Nonintegrated Group Accounting Posting

Sequence of the Migration steps

1. Create prerequisites for the use of new Asset
2. Installation of SAP Simple Finance Add-on
3. Set up customizing for new Asset Accounting (Request)
4. Migrate the COD (Request)
5. Additional customizing in case this is missing in step 3 (Request)
6. Check prerequisites for Activating new Asset Accounting
7. Activate the customizing switch (Request) – Asset Accounting (New) is active
8. Migration data to SAP Simple Finance Add-on

Note:

• Pre-check of prerequisites for Asset Accounting (New) is very important before starting installing of the Add-on
• Periodic APC postings are deleted in Simple finance, you must have completed periodic postings in the system before installing the add-on
• Postings are not possible (including in FI-AA) after installation of add-on until migration has been finished.

​

16

�Migration of legacy data upload process�

​

• Earlier
• Through AS91 Asset Master data and Asset balances are uploading
• This results Balance update in Asset table
• OASV Transaction code is using to update Asset balance by GL wise
• Document type is an manual input
• This leads mismatching between GL and Asset Balance (ABST2)
• Legacy upload through LSMW
• Batch input, Business Object Method (BAPI) and Direct input recording
• In New Asset Accounting
• Asset Master data will created by using AS91 Transaction code
• Transaction balances will update through ABLDT
• This results Asset and GL initial balance upload
• Document type is part of configuration
• Legacy data during the FY will upload through T code AB01
• AUC/WIP Balance will upload through ABLDT_OI by line item wise.
• If wrong transfer values were posted, you must reverse the journal entry and then recreate it.
• ABST2 is obsolete
• Legacy upload through LSMW
• Only direct object method supports – BAPI (BAPI_FIXEDASSET_OVRTAKE_CREATE)
• Legacy data transfer using Microsoft Excel Transaction AS100 is still available
• This corresponds with choosing method CREATEINCLVALUES of business object BUS1022 in transaction LSMW.

​

​

​

​

​

​

​

​

​

​

17

Transaction changes

The following transactions are no longer available:

• ABST, ABST2, ABSTL , ABUB, AW01_AFAR,ABF1 and ABF1L, AJRW,OASV,AB02,ASKB and ASKBN,ABB1,ABMW,ABCO
• Programs

The following programs are no longer available:

RAALTD01, RAALTD11, RAALTD11_UNICODE

RAPERB2000, RAPOST2000

RAABST01, RAABST02, FAA_GL_RECON

RAJAWE00

​

SAP Notes