Imp S - 4 HANA - New Asset Accounting - Considering Key Aspects - SAP Blogs

23/01/2018 S/4 HANA- New Asset Accounting – Considering Key Aspects | SAP Blogs
Products
Products Industries
Industries Support
Support Training
Training Community
Community Developer
Developer Partner
Partner About
About  
Home / Community / Blogs + Actions
S/4 HANA- New Asset Accounting – Considering Key

Aspects
March 25, 2017 | 17,747 Views |
Ajeet Kumar Agarwal

more by this author
FIN Asset Accounting
FIN (Finance) | SAP S/4HANA | SAP S/4HANA Finance | asset accounting | asset accounting documents | new asset accounting | S/4HANA
RIG | sap asset accounting;
share
0 share
17 tweet share
131
Follow
https://blogs.sap.com/2017/03/25/s4-hana-new-asset-accounting-considering-key-aspects/ 1/39
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
Fixed Asset Accounting currently only supports the FI relevant (BSEG-) Currencies.
For additional currency types, which are not BSEG relevant, you do not need to create dep area; these
currencies are converted during posting. This means, the sum of all depreciations does not balance with
the activation value for the additional currencies.
It is on roadmap for later releases, that Fixed Asset Accoun ng calculates the deprecia on with the
historic (ac va on) values in all currencies, but currently Fixed Asset Accoun ng does this only in
the BSEG Currencies.
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.
Brought to you by the S/4HANA RIG
Thanks
Ajeet Agarwal
SAP S/4HANA Regional Implementation Group- APJ
Alert Moderator
32 Comments
You must be Logged on to comment or reply to a post.
Umesh Chettiar
March 27, 2017 at 4:37 am
Very good article Ajeet, well articulated and informative.
Ajeet Kumar Agarwal Post author
March 27, 2017 at 5:07 am
Thanks a lot Umesh !!!
Milind Sonalkar
March 27, 2017 at 8:07 pm
Very good blog Ajeet.
Viswanatha Reddy Singamala
March 28, 2017 at 6:41 am
Collectively you have given all in one place for new asset accounting.
Nice document Ajit.
Regards,
Viswa.S
Shashank Agarwal
March 28, 2017 at 3:35 pm
As usual ..again a tremendous job.!
Keep it up!
Irala Damodara reddy
April 1, 2017 at 12:41 pm
Very good and clearly mentioned all steps.
Thank you Ajeet Agarwal.
Shinas Hamsa
April 2, 2017 at 7:04 am
Perfect and Well Clarified all Scenario…
Thanks for your time and valuable inputs..
Shinas
Theuns Pienaar
April 11, 2017 at 2:34 pm
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
April 12, 2017 at 8:35 am
Hi Thenus,
Thanks for pointing this and I should have make it more clear.
In S4 HANA carry forward activity would be taken care by FAGLGVTR itself not through AJRW. The fiscal year
close in Asset Accounting with AJAB is still the same
Thanks
Ajeet
Ramky Prabhakar
April 13, 2017 at 1:02 pm
Good blod Ajeet. All in one place for AA. Thanks for your post.
Prabhakar
Srinivasa Rao Nallamothu
June 11, 2017 at 9:54 pm
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?
Srinivasa Rao Nallamothu
June 11, 2017 at 10:23 pm
Got it. Thank you. I can see values in all the dep areas.
Shyam Vadlamani
July 1, 2017 at 9:19 pm
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
Functional S4HANA
July 5, 2017 at 9:23 pm
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!
Anant Malvankar
July 10, 2017 at 9:19 am
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
Prasad Neelisetty
July 26, 2017 at 2:13 pm
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.
Vikash Kumar Tulsyan
July 27, 2017 at 12:15 am
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.
Shiela Pailan
August 30, 2017 at 5:46 am
Hi Ajeet,
We are implementing S4 Hana and we have completed the configuration for asset. However we failed the activation and we
followed the necessary steps indicated in Prepare Asset Accounting (New) document. However, when I checked the New
Asset Activation Status it is set to “Active (Posting not possible in Client). Is there additional steps needed to activate the new
asset accounting? With this status, some transactions has errors during posting.
Thanks in advance.
Regards,
Shiela
September 4, 2017 at 12:47 am
Hi Shiela
If pre-requisite of new asset accounting is configured then it should not be a problem, you try transaction
FAA_DO_ACTIVATION in the client in which you see this status.
Regards
Ajeet
Elaine Pan
Hi Ajeet,
Thanks for sharing.
We are implementing S4 Hana and we have completed the configuration for asset. However, I cannot create a legacy asset
master data via AS91, the transfer date is set as below:
Transfer date: Dec.31.2016

Lasted period posted in previous sys.: Dec.31.2016
When I user AS91 to create a asset master data with capitalization date on June.01.2016 and click save, then I got an error
message.
Transaction.. AS91
Update key… 68A2C311EFC20070E00599A6415E08C0
Created…… 11.09.2017, 11:43:11

Completed…. 11.09.2017, 11:43:11
Error Info… ANLC not updated : ? ? ?
Would you please advice me am I doing something wrong? Thank you very much.
Elaine
Pradeep Menocha
Very nice and informative blog Ajeet!
Alexander Karpov
Hi, all.
When we activate New Asset Accounting in EPH7 we get Error Message “Parallel currency depreciation area xx is not defined
correctly” –> Message no. AC559, or error message “Parallel crcy area (crcy type xx) missing for area xx ch.of deprec.
xxxx”(from note 2307443).
But we can’t use this note and set flag IdntTrm, because, we have different sums in other depr areas.
How can we resolve that problem and activate New Asset Accounting?
SAP Training
October 10, 2017 at 9:12 am
Very nice document. I was looking for this document. Can you Please write one more blog on ‘Define Settings for Ledgers and
Currency Types’ in S/4 HANA finance. Example like multiple ledgers, multiple currency’s and multiple accounting principle.
October 10, 2017 at 1:14 pm
Thanks for the feedback , I would try to incorporate this requirement in a separate blog.
Regards
Ajeet
SAP Training
October 12, 2017 at 2:13 pm
Thanks
Sekhar Babu Thallam
November 4, 2017 at 10:28 am
Hello Ajeet ,
Detailed explanation with clear screen prints and examples.
Good Article.
Regards,
Sekhar Thallam
Arvind Pereira
November 6, 2017 at 10:23 am
Hi Ajeet,
SAP note for pre-check 2129306 has been discussed at length, this is a good ar cle.
thanks
Arvind Leo Pereira
Sandu Rakesh
November 28, 2017 at 12:08 pm
Hello Ajeet,
Thank you so much for documenting all the information related to AA, this could be a reference document who are
implementing and learning S4.
I have one doubt In posting logics:
Accounting principle LOCA why it is hitting to posting key 40 with GL code199990 instead 70 asset code.and what is could be
the other impact if it is posting to 70 Asset code.
Thanks in Advance.
January 8, 2018 at 9:53 am
Hi Rakesh
I agree with your comments the posting key should be used here 70 , however this may be one off case as I am
not getting the same case in my other test cases.
Thanks
Rajiv Singh
January 9, 2018 at 10:03 pm
Hi Ajeet,
Thanks for this posting. I have additional questions, how to get your contact please veere.
January 15, 2018 at 4:28 am
Hi Rajiv
Thanks a lot , I would encourage you to post your query here.
Maria Defago
January 22, 2018 at 2:43 pm
Hi Ajeet,
Thanks for your posting.
I have an error whit the 2nd step LTMC transfer. Don’t appears the asset class´s mapping, Do you know about this?
Thank in advancce.
“Asset class not entered
Message no. BAPI1022001
Diagnosis
You want to create a main asset number (the CREATESUBNUMBER parameter was not set), but you did not enter an asset
class.
System Response
The asset is not created.
Procedure
Transfer an asset class in the interface field GENERALDATA-ASSETCLASS.”
Share & Follow Privacy Terms of Use Legal Disclosure Copyright Trademark Sitemap Newsletter

Imp S - 4 HANA - New Asset Accounting - Considering Key Aspects - SAP Blogs

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Imp S - 4 HANA - New Asset Accounting - Considering Key Aspects - SAP Blogs

Uploaded by

Copyright:

Available Formats

23/01/2018 S/4 HANA- New Asset Accounting – Considering Key Aspects | SAP Blogs

S/4 HANA- New Asset Accounting – Considering Key

Ajeet Kumar Agarwal

FIN Asset Accounting

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

2. Data Structure Changes in Asset Accounting

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

4. Asset Accounting Parallel Valuation

Very Important part of new Asset accounting is parallel valuation in multicurrency

5. Key Configuration Consideration in Ledger Approach

Required Valuation Approach

Define Depreciation Areas

Specify Depreciation Area Type

Specify Transfer of APC Values

Specify Transfer of Depreciation Terms

Define Depreciation Areas for Foreign Currencies

Specify the Use of Parallel Currencies

6. Why will use a technical clearing GL account

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

Specify Alternative Document Type for Accounting Principle-Specific Documents

7. New Asset Accounting Posting Logic

Asset Acquisitions Operational Document

Asset Acquisitions Accounting Principal (IFRS) specific Document

Asset Acquisitions Accounting Principal (LOCA) specific Document

Correction Asset Acquisition value in specific GAAP

8. FI-AA Legacy Data Transfer

Time of Legacy Asset Transfer

Scenario 2: Transfer During the Fiscal Year

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

Specify Transfer Date/Last Closed Fiscal Year (V_T093C_08)

Step 1:- AS91 to create Legacy asset master data

Step 2:- ABLDT to update Legacy Original Acquisition Value/ Accumulated

Step 3: Verify Legacy Asset Planned Value

Step 4: Verify Legacy posted Value

9. Adjusting Chart of Depreciation prior to Conversion

10. Installing SFIN in Conversion/Migration Scenario

Execute the periodic depreciation posting run (RAPOST2000).

Run the program for recalculating depreciation (transaction AFAR).

Perform a backup before installing SFIN

Brought to you by the S/4HANA RIG

March 27, 2017 at 4:37 am

Very good article Ajeet, well articulated and informative.

Ajeet Kumar Agarwal Post author

March 27, 2017 at 5:07 am

Thanks a lot Umesh !!!

March 27, 2017 at 8:07 pm

Very good blog Ajeet.

Viswanatha Reddy Singamala

March 28, 2017 at 6:41 am

Nice document Ajit.

March 28, 2017 at 3:35 pm

As usual ..again a tremendous job.!

Irala Damodara reddy