Skip to Content

This blog is focused on New Asset accounting for ledger approach in multiple currency environment. New Asset Accounting is the only Asset Accounting solution available in S/4 HANA, classic Asset Accounting is not available any more.

I have covered following key topics within S/4 HANA New Asset Accounting keeping in view various questions coming in from different customers/partners on this key innovation step taken within Finance as part of S/4 HANA simplification and we need to be very clear on this new requirement before starting the new or conversion S/4 HANA project.

1. Pre-requisite Business Functions

2. Data Structure Changes in Asset Accounting

3. New FI-AA-Integration with the Universal Journal Entry

4. Asset Accounting Parallel Valuation

5. Key Configuration Consideration in Ledger Approach

6. Why will use a technical clearing GL account

7. New Asset Accounting Posting Logic

8. FI-AA Legacy Data Transfer

9. Adjusting chart of Depreciation Prior to Conversion

10. Installing SFIN in Conversion/Migration Scenario

 

1. Pre-requisite Business Functions

Activate the following Business Functions

  • ENTERPRISE_EXTENSIONS – EA-FIN
  • ENTERPRISE_BUSINESS_FUNCTIONS – FIN_AA_PARALLEL_VAL

2. Data Structure Changes in Asset Accounting

  • Actual data of ANEK, ANEP, ANEA, ANLP, ANLC is now stored in table ACDOCA. ANEK data is stored in BKPF.
  • Compatibility views FAAV_<TABLENAME> (for example, FAAV_ANEK) are provided in order to reproduce the old structures.
  • Statistical data (for example, for tax purposes) previously stored in ANEP, ANEA, ANLP, ANLC is now stored in table FAAT_DOC_IT
  • Plan data previously stored in ANLP and ANLC is now stored in FAAT_PLAN_VALUES
  • Classic Asset Accounting is mostly transformed automatically into the New Asset Accounting by executing mandatory migration steps related to Asset Accounting.
  • Posting to different periods possible (restriction: beginning/end of FY needs to be equal) refer OSS note 1951069/ 2220152
  • Following table shows some redundant/new Asset accounting programme.

3. New FI-AA-Integration with the Universal Journal Entry

Asset Accounting is based on the universal journal entry. This means there is no longer any redundant data store, General Ledger Accounting and Asset Accounting are reconciled Key changes are listed below: –

  • There is no separate balance carry forward needed in asset accounting, the general balance carry forward transaction of FI (FAGLGVTR) transfers asset accounting balances by default.
  • The program Fixed Assets-Fiscal Year Change (RAJAWE00) transaction AJRW is no longer has to be performed at fiscal year change
  • Planned values are available in real time. Changes to master data and transaction data are constantly included
  • The most current planned depreciation values will be calculated automatically for the new year after performing the balance carry forward. The depreciation run posts the pre-calculated planned values.
  • The Selection screen is simplified as the “reasons for posting run” (planned depreciation run, repeat, restart, unplanned posting run) are no longer relevant.
  • 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.
  • All APC changes in Asset Accounting are posted to the general ledger in real time. Periodical APC postings are therefore no longer supported.
  • Transaction types with restriction to depreciation areas are removed in new Asset Accounting and you can set the obsolete indicator in the definition of the transaction that were restricted to depreciation areas in the classic asset accounting.

4. Asset Accounting Parallel Valuation

  • Very Important part of new Asset accounting is parallel valuation in multicurrency environment.
  • The leading valuation can be recorded in any depreciation area. It is no longer necessary to use depreciation area 01 for this. The system now posts both the actual values of the leading valuation and the values of parallel valuation in real time. This means the posting of delta values has been replaced; as a result, the delta depreciation areas are no longer required.
  • New Asset Accounting makes it possible to post in real time in all valuations (that is, for all accounting principles). You can track the postings of all valuations, without having to take into account the postings of the leading valuation, as was partly the case in classic Asset Accounting.

5. Key Configuration Consideration in Ledger Approach

We need to answer some basic question before configuring new asset accounting in S4 Hana environment as this would determine the required minimum depreciation areas to align the FI with Asset Accounting. i.e.

  • Required Valuation Approach

  • How Many Ledgers (Leading + Non Leading) exists or to be configured.

  • What all currencies are used in each of the ledgers.

For Example:-

In this Example we have one com code which has 2 ledgers 0L & N1 & these 2 ledgers having 3 currencies i.e 10,30 & 40 as shown below.

Above mapping is to ensure and establish link between depreciation area/accounting principal and Currency

Explaining with ledger approach example. From release 1503 i.e initial version of SAP Finance add on version in S4 Hana a new table ACDOCA is introduced which stores the asset values also per ledger /per currency on real time basis & no need to have any reconciliation between Finance and Asset accounting and to do so it is must to follow the guidelines while setting up depreciation areas & respective currencies, which I have tried to explain with an example as given below: –

Ledger & currency setting has to be done in New GL in the following SPRO node.

Financial Accounting (New)–> Financial Accounting Global Settings (New)–> Ledgers–> Ledger –> Define Settings for Ledgers and Currency Types

Define Depreciation Areas

Depreciation Areas defined as per new FI-GL & FI-AA requirement so here at least 6 depreciation areas are must so that ledger wise each currency can be represented in separate depreciation area & these depreciation area is assigned to Accounting principal.

Specify Depreciation Area Type

Specify Transfer of APC Values

In this activity, you define transfer rules for the posting values of depreciation areas. These transfer rules let you ensure that certain depreciation areas have identical asset values

Specify Transfer of Depreciation Terms

In this activity, you specify how the depreciation terms for a depreciation area are adopted from another depreciation area. You can specify if the adoption of values is optional or mandatory. If you specify an optional transfer, then you can change the proposed depreciation terms in the dependent areas in the asset master record. In the case of a mandatory transfer, you cannot maintain any depreciation terms in the asset master record. In this way, you can ensure that depreciation is uniform in certain depreciation areas.

Define Depreciation Areas for Foreign Currencies

For every additional currency type defined on the company code a corresponding depreciation area needs to be set up.

As explained in previous step here we need to define the currency for each dep area so for example if a company code has 2 ledgers i.e 0L and N1 with 3 currencies then at least 6 depreciation areas should be setup & currencies should be assigned for each depreciation area ( Here leading valuation depreciation area will derive currency from com code currency)

Specify the Use of Parallel Currencies

Here we need to specify the Currency type for each for the Depreciation area which will align FI Currency type with Asset Depreciation areas & accordingly will be updated in ACDOCA.

With this setting its ensured that all currency types are aligned with respective depreciation area and asset values are getting updated parallel to Financial accounting per currency.

6. Why will use a technical clearing GL account

Architecture has been changed in the way that we now post in asset accounting for each valuation a separate document. So we perform on the asset part accounting principle specific postings. Technically we perform ledger-groups specific postings.

On the operational part (accounts receivable, accounts payable) the value is always the same for each accounting principle. So for the operational part we have to perform postings which are valid for all accounting principles. Technically we perform postings without specifying the ledger-group.

To split the business process in an operational and a valuating document there was a need to establish the “technical clearing account” for integrated asset acquisition.

  • For the operational part (vendor invoice/GRIR), the system posts a document valid for all accounting principles against the technical clearing account for integrated asset acquisitions. From a technical perspective, the system generates a ledger-group-independent document.

 

  • For each valuating part (asset posting with capitalization of the asset), the system generates a separate document that is valid only for the given accounting principle. This document is also posted against the technical clearing account for integrated asset acquisitions. From a technical perspective, the system generates ledger-group-specific documents.

Define account “Technical clearing account” for integrated asset acquisition.

Specify Alternative Document Type for Accounting Principle-Specific Documents

Here Operational document type will have original document used during entry & while generating accounting principal wise separate document it would be document type AA.

7. New Asset Accounting Posting Logic

The Operational Entry Document posts to a technical clearing account. The Operational Entry Document does not update the asset values; the asset data is only used to perform checks.

Accounting principle specific documents (1 to n). The accounting principle specific documents post to: – the technical clearing account in each view (balancing to zero) and the asset reconciliation account (and update the asset line items).

Asset Acquisitions Operational Document

Asset Acquisitions Accounting Principal (IFRS) specific Document

Asset Acquisitions Accounting Principal (LOCA) specific Document

Universal Table updated with respective ledger (0L & N1) and currencies.

Correction Asset Acquisition value in specific GAAP

Use Transaction code AB01L

 

8. FI-AA Legacy Data Transfer

  • You create asset master records for the legacy data transfer using transaction AS91.
  • You post the transfer values using transaction ABLDT; in doing so, a universal journal entry is posted for the fixed asset.
  • 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 sub numbers for the Asset master record.

Time of Legacy Asset Transfer

The transfer date is the cut-off date for the transfer of legacy data. The transfer will only include data up to this point in time. There are two possible scenarios.

  • The transfer date can be the end of the last closed fiscal year.

  • The transfer date can be in the fiscal year. This is called “transfer during the fiscal year.

Scenario 1: Transfer Date is the End of the Last Closed Fiscal Year:

In this case, you do not need to include any posted depreciation or transactions in the transfer of legacy data. You only need to transfer master data and the cumulative values as of the end of the last closed fiscal year.

Scenario 2: Transfer During the Fiscal Year

Along with the general master data, and the cumulative values from the start of the fiscal year (time period A), you must also transfer the following values.

  • Depreciation during the transfer year and Transactions during the transfer year
  • Include the depreciation posted in the legacy system since the end of the last closed fiscal year up to the date of transfer (time period B).
  • Any asset transactions in your legacy system that have a value date after the transfer date, but before the date of the physical transfer of data (time period C), need to be posted separately in the Asset Accounting component in any case.

Example of scenario 2 Legacy Data Transfer During the Fiscal year:-

Case: Legacy asset is acquired in previous year 01.01.2015 and taken over into simple finance system in mid-year of current year (30.04.2017)

Specify Transfer Date/Last Closed Fiscal Year (V_T093C_08)

Specify Last Period Posted in Prv. System (Transf. During FY) (OAYC)

Step 1:- AS91 to create Legacy asset master data

Step 2:- ABLDT to update Legacy Original Acquisition Value/ Accumulated Depreciation and current year Depreciation Posted.

Step 3: Verify Legacy Asset Planned Value

Step 4: Verify Legacy posted Value

9. Adjusting Chart of Depreciation prior to Conversion

  • For the leading valuation of the ledger approach and accounts approach and for parallel valuations of the ledger approach its must that the parallel currencies in the leading ledger in General Ledger Accounting and in the depreciation areas in Asset Accounting must be the same as explained one example above with ledger approach scenario.
  • Using the migration program available under Migration Tools, you can automatically adjust the parameters in your charts of depreciation. If error messages appear stating that automatic adjustment is not possible, you have to adjust the charts of depreciation manually.
  • If until now you have been using parallel currencies in General Ledger Accounting, but you have not implemented the corresponding parallel currency areas in Asset Accounting for all depreciation areas, you must implement these areas in a separate project before you install SAP Simple Finance. In such a project, you must first perform the preparatory steps for creating depreciation areas in Customizing; you must then determine the new values for each fixed asset for a newly created depreciation area.
  • For company codes that are assigned to the same chart of depreciation, these company codes are not allowed to differ in number and type from the parallel currencies used in General Ledger Accounting.
  • Even if you migrate to SAP Accounting powered by SAP HANA from a system (e.g. EHP7) having FI-AA (new) already active, you still must migrate every active chart of depreciation.

10. Installing SFIN in Conversion/Migration Scenario

From the viewpoint of Asset Accounting, it is not necessary that you install SAP Simple Finance at the end of the year or period. However, it is required that you perform a complete period-end closing directly before you install SAP Simple Finance and some of the important point you must consider w.r.t New Asset Accounting. (for detail you may refer conversion guide)

  • To check if the prerequisites outlined are met, you have to check using the program for preliminary checks RASFIN_MIGR_PRECHECK. You import the current version of this program using SAP Note 1939592, before you install SAP Simple Finance in your system. Perform this check in all of your systems – in the Customizing system as well as in the downstream systems (test system and production system).
  • If until now you updated transactions in parallel valuations with different fiscal year variants and want to continue using this update, then you must implement a new representative ledger using the SAP General Ledger Migration Service before you install SAP Simple Finance. For more information about alternative fiscal year variants with parallel valuation, see SAP Note 2220152 Information published on SAP site.
  • You must have performed periodic APC posting (RAPERB2000) completely; the timestamp must be current.
  • Execute the periodic depreciation posting run (RAPOST2000).
  • Run the program for recalculating depreciation (transaction AFAR).
  • Reconcile your general ledger with the Asset Accounting subsidiary ledger, both for your leading valuation and for parallel valuations.
  • The migration must take place at a time when only one fiscal year is open in Asset Accounting.
  • You can check which fiscal year is closed in your company code in Customizing for Asset Accounting (New) under Preparations for Going Live à Tools à Reset Year-End Closing.
  • Ensure that no further postings are made in your system after running period end transactions before installing S4 Hana Simple Finance hence lock the users.
  • Perform a backup before installing SFIN
  • As soon as you have installed SAP Simple Finance, you can no longer post in Asset Accounting. To ensure that migration is successful, it is essential that you make sure that the prerequisites are met and a complete period-end closing was performed before you install SAP Simple Finance. Posting for new Asset Accounting is only possible again after you have completed the migration fully and successfully.
  • After completing the migration, make sure that no fiscal year that is before the migration is reopened in Asset Accounting.

 

Thanks a lot

Ajeet Agarwal

To report this post you need to login first.

17 Comments

You must be Logged on to comment or reply to a post.

  1. Theuns Pienaar

    Thanks Ajeet, very useful and comprehensive.

    Just a question on the following:

    Under your section 3 New FI-AA-Integration with the Universal Journal Entry, second bulletpoint, the fact that transaction AJRW is no longer required. How is this picked up in the asset reports, because I still get an error the moment the system date is in a new ‘fiscal’ year.

    Eg. today’s date being 11.04.2017, the fiscal year-end was 31.03.2017, ie. we are now in 2018 fiscal year. When I try to run report S_ALR_87011994 “Asset Balances” via Fiori tile or gui, doesn’t matter which, the following error appears, as we’re used to in the past when a fiscal year change hasn’t been carried out:

    Fiscal year change not yet made for company code XXXX

    Message no. AB059

    Diagnosis

    You have not yet carried out a fiscal year change for company code XXXX, although the current system date is in the new fiscal year.

    Procedure

    Carry out the fiscal year change for company code XXXX.

     

    Am I doing something wrong? Please let me know if you require additional information in order to assist.

     

    Thanks,

    Theuns Pienaar

    (0) 
    1. Ajeet Kumar Agarwal Post author

       

      Hi Thenus,

      Thanks for pointing this and I should have make it more clear.

      You still need to run AJRW as from the system point of view of, a fiscal year change is the opening of a new fiscal year for a company code and also at the fiscal year change, the asset values from the previous fiscal year are carried forward cumulatively into the new fiscal year. Once the fiscal year change takes place, you can post to assets using value dates in the new fiscal year. At the same time, you can continue to post in the previous fiscal year

      for detail on AJRW

      However in S4 HANA  carry forward activity would be taken care by FAGLGVTR itself not through AJRW

      https://help.sap.com/saphelp_pserv464/helpdata/en/6e/1223cb9f0411d189b80000e829fbbd/content.htm

      Please go ahead and run the AJRW .

      Thanks

      Ajeet

       

       

       

      (0) 
  2. Srinivasa Rao Nallamothu

    Thanks Ajeet.

    I have loaded the data through ABLDT, but it has updated APC/AccDep values only in depreciation area ’01’ and rest all are ‘zero’! Is this expected behavior for legacy asset upload or am i doing something wrong?

    (0) 
  3. Shyam Vadlamani

    Thanks for the detailed explanations, Ajeeth.

     

    Question on the number of depreciation areas for parallel currencies: Since the asset master data is also updated in ACDOCA table is there any reason why we need to create a separate dep area for each currency type?  In other words, when we post any asset related transaction all the currencies defined in FI are updated along with the asset master record. In such a case, wouldn’t ACDOCA itself would suffice for parallel currency reporting for fixed assets?  Please help to clarify. Thanks, Shyam

    (0) 
  4. Functional S4HANA

    Great article Ajeet.

     

    There is one concept I have been struggling with. As you know, S/4 has changed functionality of AS91/92 Takeover Values with the new T-code ABLDT. This transaction does not allow repetitive corrections to takeover values, which was previously allowed in ECC. SAP now requires that you reverse the transfer documents, before you make any subsequent updates to takeover values for existing assets.

    I have a requirement where the client makes updates to Ord. Depr and Special Depr. in ECC directly in AS92 for only the Tax Depreciation Areas. ABLDT does not allow changes to existing values for even the tax depreciation areas. Is there another workaround to make this possible in S/4 where the system will allow you to update Ord. Depr. directly via ABLDT for Tax Areas?

    Thanks for any details that you are able to share!

    (0) 
  5. Anant Malvankar

    Hi Ajeet,

    Thanks for the detail explanation.

    Ajeet, can you provide some explanation for below points along with the example in New Asset Accounting S/4 HANA.

    1. New feature in Asset accounting to have the option to select the Quantity update at Depreciation level.
    2. Revenue Distribution at the time of Retirement of An Asset

    Regards

    Anant

    (0) 
  6. Prasad Neelisetty

    Execution of AJRW is dependent on Support Pack.  Once system is upgraded to 1610/FPS-0002, AJRW is no longer available and FAGLGVTR is the only transaction that needs to be executed.

     

    (0) 
  7. Vikash Kumar Tulsyan

    I was able to complete the Fiscal Year change without AJRW and there is a specific note from SAP which says we should not execute AJRW tcode in S/4 as we need to execute FAGLGVTR and this is available since 1503.

    (0) 

Leave a Reply