10.2 S4TWL – Asset Accounting: Parallel valuation and journal entry – 2270388

From classic Asset Accounting to —> using new Asset Accounting in SAP S/4HANA

  • In S/4HANA, NEW Asset-Accounting is mendatory
  • In S/4HANA, NEW GL is mendatory
  • This blog thus focuses on Switching from “Classic Asset-Accounting” to using new Asset Accounting in SAP S/4HANA, with new General Ledger Accounting.
    • If you were using classic General Ledger Accounting before the conversion to SAP S/4HANA, new General Ledger Accounting is activated automatically with the conversion.
  • Other scenarios (such as the switch from SAP ERP 6.0, EhP7 with new Asset Accounting to SAP S/4HANA) are not considered here.

Key-Business Changes : Highlights

  • Usage of TECHNICAL Clearing-account.
  • 10.2.1 Parallel Valuation and Journal Entry, in REAL-TIME
    • In new Asset Accounting you can map parallel valuations with the ledger approach or accounts approach. (A mixture of the two is not supported)
    • System records the leading valuation of Asset Accounting in any depreciation area of new Asset Accounting. It is no longer necessary to use depreciation area 01 for this.
    • system now posts both the actual values of the leading valuation and the values of parallel valuation in real time. ( Delta-Depriciation Areas , posting of Delta-values is NO-longer required nor supported) .
    • New Asset Accounting makes it possible to post in real time in all valuations (that is, for all accounting principles)
    • Asset Accounting is based on the universal journal entry. No Recon required.
  • 10.2.2 Separate Document for each Valuation
    • Different accounting principles or valuations are represented – as in new General Ledger Accounting – in separate ledgers (for the ledger approach) or in a separate set of accounts (for the accounts approach)
    • The depreciation areas have equal status. Separate accounting-principle-specific documents are posted for each accounting principle or valuation
    • A business transaction created using integration is split by the system into the operational part and the valuating part.
      • A posting is made in each case against a technical clearing account.
      • For the asset acquisition using integration you require a new technical clearing account for integrated asset acquisition; however,
      • for the asset retirement using integration the existing clearing accounts asset retirement with revenue and asset retirement clearing are used.
      • The operational part is posted across accounting principles, the valuating part is posted accounting-principle-specifically
  • Entry of Value Differences for Each Depreciation Area or Accounting Principle (Ledger Group).
    • Value differences for each accounting principle or depreciation area can be entered in a separate transaction (AB01L) for an asset acquisition, a post-capitalization, and a manual depreciation or write up, with following consiquences
      • 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
  • 10.2.4 Entering a Business Transaction
    • Using the appropriate fields, you can restrict the posting to an accounting principle and depreciation areas, or limit it to certain areas using the selection of a depreciation area.
    • A business transaction is always entered in local currency. If you limit the posting to one or more depreciation areas in the same foreign currency, then the entry (and posting) is made in this foreign currency (see Conversion-Considerations : Statistical posting)
  • 10.2.5 Updating Journal Entries
    • The journal entries are updated in Financial Accounting at asset level. The entry also contains the asset number
  • 10.2.6 Change in Holdings in Real-time in All Valuations
    • In SAP S/4HANA, all changes in holdings are posted in real-time or simultaneously to the general ledger.
    • Periodical APC postings are therefore superfluous and are no longer supported.
    • This also applies for the processing of reserves for special depreciation.
    • This also affects the Customizing settings for the depreciation area
  • 10.2.7 Reconciliation Between Asset Accounting and the General Ledger
    • Asset Accounting is permanently reconciled with the general ledger automatically. [ i.e. no longer necessary to reconcile the general ledger with the subledger of Asset Accounting]. Recon-programs no-longer available in S/4HANA
  • 10.2.8 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. You can map these differing capitalization rules in new Asset Accounting using ‘unilateral’ assets.
  • 10.2.9 Transaction Types
    • In new Asset Accounting, it is not possible and also not necessary to restrict transaction types to depreciation areas.
    • In a posting transaction, you can select the depreciation areas to be posted to. This can significantly reduce the number of transaction types that need to be defined in the system
    • Investment support and also revaluation and new valuation are an exception:
      • • The transaction types for investment support and revaluation are automatically generated by the system when you create a corresponding measure, and therefore are restricted to the depreciation area to be posted to.
      • • The transaction types for revaluation and new valuation that relate to transaction type group 81/82/89 must continue to be restricted to depreciation areas
  • 10.2.10 Default Transaction Types for Down Payments
    • Default transaction types for down payments are NOW defined in in Customizing activity Specify Default Transaction Types (table TABWD). The system moves existing entries (in Classical Asset-accounting, Customizing activity Determine Transaction Types for Internal Transactions (table TABWV)
    • The same applies for the default transaction type Gain/loss on retirement for internal posting of write-ups from gain/loss from asset retirement (the EVL rule).
  • TBC …. till 10.2.30 ( To be Continued)

Technical-Changes

  • a NEW Technical-Clearing Account for Integrated asset acquisition is required
  • The user exit APCF_DIFFERENT_AMOUNTS_GET is no longer supported
  • Config-Changes : As periodic APC posting are no-longer required/supported, Customizing settings for the depreciation area need to contain following-INDICATOR
    • 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
  • Config-Migration-Confideration : Changes for Foreign Currency Depriciation Area
  • Recon-Programs, no longer required, hence not available in S/4HANA
    • RAABST01, RAABST02 and FAA_GL_RECON
  • Config-Changes : Transaction-Type : IMG structure for Asset Accounting does not have Customizing for restricting transaction types to depreciation areas
  • Config-Changes : Default transaction types for down payments are NOW defined in in Customizing activity Specify Default Transaction Types (table TABWD) & also for Gain/loss on retirement

Migration Considerations

  • In classic Asset Accounting you may have one depreciation area in a foreign currency that posts periodically to the general ledger, in new Asset Accounting it is no longer possible that a foreign currency area posts to the general ledger.
    • in Customizing for the depreciation area, you have selected the option “Area posts holdings and depreciation periodically” [Classic Asset Accounting]
    • In NEW-Asset-Accounting, recommendation is to set / choose the option Area does not post for postings to the general ledger. As a consequence, this foreign currency area of Asset Accounting is then managed as a statistical area

SAP-NOTES

  • 2332030 – Specification for the Conversion/Migration in Accounting
  • 2220152 –
  • 2270387 – Compatibility Views
  • 2257555 –
  • 2270392 – For Joint Venture Accounting (JVA)
  • 2270391 – For Lease Accounting Engine (LAE)
  • 2419194 – Not all transaction data is deleted in Asset Accounting when you reset a company code (using transaction OABL).
  • 2344012 – currencies in the universal journal. As of release SAP S/4HANA 1610, user-defined currencies are available in General Ledger Accounting (FI-GL). These are not available in Asset Accounting, but they are translated with the document life. The parallel local currencies used until now are translated in the meantime historically in the fixed assets, provided that depreciation areas are set up for parallel currencies.
  • 2297425 – Exception, The accumulated depreciation accounts are managed as a statistical cost element. Other 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.
  • 2403248 – availability of a tool to subsequently create new depreciation areas for assets already in use
  • 1069166 – The restriction of posting logic to certain depreciation areas is done in classic Asset Accounting using area types

Leave a Reply

Please log in using one of these methods to post your comment:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.