FI Asset Accounting Help

Prévia do material em texto

4/11/2024
1This is custom documentation. For more information, please visit the SAP Help Portal
Financial Accounting
Generated on: 2024-04-11 21:58:20 GMT+0000
Support Content | 1.0
PUBLIC
Original content: https://help.sap.com/docs/SUPPORT_CONTENT/�accounting?locale=en-US&state=PRODUCTION&version=1.0
Warning
This document has been generated from the SAP Help Portal and is an incomplete version of the official SAP product documentation. The
information included in custom documentation may not re�ect the arrangement of topics in the SAP Help Portal, and may be missing important
aspects and/or correlations to other topics. For this reason, it is not for productive use.
For more information, please visit the https://help.sap.com/docs/disclaimer.
Asset Accounting
WELCOME TO THE ASSET ACCOUNTING EXPERT CONTENT PAGE
What is ASSET ACCOUNTING?
https://help.sap.com/docs/disclaimer
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting?locale=en-US&state=PRODUCTION&version=1.0
https://help.sap.com/docs/disclaimer
4/11/2024
2This is custom documentation. For more information, please visit the SAP Help Portal
The Asset Accounting (FI-AA) component is used for managing and supervising �xed assets with the SAP System. In Financial Accounting it serves
as a subsidiary ledger to the General Ledger, providing detailed information on transactions involving �xed assets. 
The Asset Accounting component is intended for international use in many countries. You give this component its country-speci�c and company-
speci�c character with the settings you make in Customizing. The Implementation Guide (IMG) provides the necessary functions for this in Asset
Accounting. 
As a result of the integration in the SAP System, Asset Accounting (FI-AA) transfers data directly to and from other SAP components. For example,
it is possible to post from the Materials Management (MM) component directly to FI-AA. Also components like Financial Accounting (FI),
Controlling (CO) and Plant Maintenance (PM) components are directly involved.
Asset Accounting
Master Data & Organization Structure
Asset Master: WBS Element - Difference between PS_PSP_PNR and PS_PSP_PNR2
Asset Master Record Mass Changes
Basic Con�guration settings for implementing Asset Accounting in SAP 6.0
Basics of Asset Accounting – Creating Asset Master Record
Change log of asset master data
De�nition of Asset Class
FI-AA (Asset Accounting) and PM (Equipment) Synchronization
Flag ʻNegative val.allowed’ using in asset class level
How to do mass change for Negative value allowed
How we can verify Account assignment objects in Assets Accounting
Ignore memo value (ANLA-XERWRT) or OAAW
Logical Field Group Assignment in Validation and Substitution Rules
More Interval button not appearing in Depreciation Area tab
Parallel Ledger con�guration in classic Asset Accounting Vs New Asset Accounting
Pro�t center generation rules in Asset Accounting
Relationship between asset value date and depreciation start date
Scrap value, cutoff value and memo value
Synchronize Asset Accounting and Equipment which created individually
Where and how to allow negative values in Assets Accounting by customizing
Worklist Release and Troubleshooting
Legacy Data Transfer
Depreciation Areas in AS91 legacy data restricted to 50 Areas
Takeover Date
Technical Information
Depreciation
Asset Shutdown
Asset Value Date and Ordinary Depreciation Start Date
AW01N - The Effect on Planned Depreciation where 'Dep.below NBValue zero' is 'No' (Depreciation Key)
BASE VALUE for a RETIREMENT with Old Engine calculation
Depreciation Calculation for Shorten Fiscal Year
Depreciation Calculation for Subsequent Acquisition (where �rst acquis. is in last month of FY and period control is 11)
Depreciation calculation with base method Unit-of-production
Depreciation Smoothing and Catch Up
Interest Calculation for Capital Leased Asset
Methods to update table ANLBZW
Period control introduction(t-code: AFAMP) - depreciation key setting
https://help.sap.com/docs/disclaimer
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361881700.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880862.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880169.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880559.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361878501.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361878905.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361878946.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880335.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361878899.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880744.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361878924.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880950.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361878295.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880390.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361881423.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880599.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361878782.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361878671.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361878829.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880867.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361878710.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361881702.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880264.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361881690.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361881864.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361878575.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880952.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361878640.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880404.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880049.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361878816.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880387.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880408.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361878502.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361878949.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880858.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361878713.html
4/11/2024
3This is custom documentation. For more information, please visit the SAP Help Portal
Shift Factor usage in depreciation calculation
Start Depreciation One Month After Capitalization of Asset
Transaction Processing
Analysis of Error AA698
Analysis of Error message AA632
Asset Accounting - Period Control
Asset Acquisition via F110
Asset capitalization (or asset posting) by MIRO or MIGO
AUC settlement when one depreciation area exists in sender asset but not in target asset
AUC settlement when one depreciation area exists in the sender asset but not in the target asset
AW01N - Effect on Planned Depreciation where Dep.below NBValue zero is No (Example)
Basics of Asset Accounting - Asset Acquisition
Basics of Asset Accounting - Asset Retirement
Basics of Asset Accounting - Asset Transfer
Basics of Asset Accounting - Asset Transfer (Intercompany)
Basics of Asset Accounting - Asset Transfer Partial (Intercompany)
Basics of Asset Accounting - Post-Capitalization of an Asset and How Depreciation is Calculated and Distributed
Basics Postings
Cross system Depreciation Areas and Intercompany Asset transfer
De�ning posting rules for depreciation
Document type selection via F4 help in asset transaction
Japanese Impairment Posting
Settlement of an Internal Order or Investment Order - All Processes
Settlement ofAsset Under Construction using transaction codes AIAB and AIBU
Tables for Posting
Transaction type - current year and previous year
Periodic Processing
Asset Fiscal Year Change
Balance Carryforward: values no transfered into next year for some assets
Cross Company Code Depreciation Postings
How we can verify the asset posting logs
Recalculate Depreciation
Reconcile General Ledger and Subsidiary Ledger
Running Depreciation using RABUCH00
V2 update error handling
What the number means in document text �eld which generated in AFAB
Year-End Closing in Asset Accounting (NEW)
Year-End Closing procedure in FI-AA
Asset Reporting
Data Archiving in FI-AA
Directory of Asset Reports
Include own �elds in FI-AA standard ALV
SAP List Viewer Basics
Sort Variant de�nition in Asset Accounting reports
Trivia Incorrect Book Value in Asset Explorer and Asset History Sheet
Use of Archive Index in FI-AA
All Other Information
https://help.sap.com/docs/disclaimer
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361878862.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361878590.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361881695.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880825.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361878938.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361878923.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361878877.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880853.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880801.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361878751.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880697.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361878516.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361878513.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361878539.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361878536.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361878399.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880695.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361878366.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361878591.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880592.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880936.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361878951.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361878401.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361878677.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880915.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880640.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361881698.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361879077.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880885.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880208.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880621.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361881499.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880848.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361882073.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361878367.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880903.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361878095.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361878387.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361881699.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361878299.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361881887.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361878305.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361878297.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880795.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361878325.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361878298.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361881694.html
4/11/2024
4This is custom documentation. For more information, please visit the SAP Help Portal
Asset Accounting Transaction Codes
Automatic Opening of a New Depreciation Area - PGM: RAFABNEW
Basics of Asset Accounting – Asset Explorer
Fiscal Year Variants
Key Terms
Mapping transaction type de�nition and depreciation area speci�cation
Mass processing in Asset Accounting
Overview BW Delta Extraction
Reconciliation Program ABST2
Simulation Function in Asset Explorer
Substituation during asset master creation
Transaction type de�nition for asset accounting transaction posting
Useful Transaction Codes for FI
Validation and Substitution Call Points in Asset Management Accounting
Migration to S/4HANA
Additional line items in ACDOCA table
New Asset Accounting
Access SAP For Me Visit the SAP Community View Product Documentation
Useful Links
 For SAP official product information, you can visit the Support Portal 
Master Data & Organization Structure
This section covers all topics related to asset master data and organizational structure (Chart of Depreciation, Dereciation Area, etc.)
Asset Master Record Mass Changes
Asset Master Record - Mass Changes
https://help.sap.com/docs/disclaimer
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880826.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880288.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361878551.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880574.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361881678.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361878843.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880531.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880168.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361878702.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361878919.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880937.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361878940.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361881677.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880716.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361879265.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361879274.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361881515.html
https://me.sap.com/
https://community.sap.com/
https://help.sap.com/docs/
https://support.sap.com/home.html
4/11/2024
5This is custom documentation. For more information, please visit the SAP Help Portal
Author: D033258
GBU Financials, SAP AG 
Purpose
The Asset Accounting component provides a function for mass processing of freely de�nable changes to asset master data. The system carries out
these changes automatically to a large extent. This type of mass asset change might be necessary in the following cases:
When there is a change to the cost center plan, you have to change the cost center assignment of all assets affected.
As part of year-end closing, you have to change depreciation terms.
Following the legacy data transfer, you have to make entries in certain asset master data �elds that could not be copied from your legacy
system.
You made a change at the asset class level. Changes at this level affect only those assets that are created after the change was made.
Therefore, you have to make this change in the already existing assets.
....
Authorization
In order to carry out a mass change, you need
 ->the normal authorization for asset master data maintenance,
as well as
 ->authorization for authorization object A_PERI_BUK (authorization for periodic processing)with activity 40. This authorization is contained in the
standard pro�le A_ALL.
Process Flow
The mass change process has three levels:
1. De�ning the change rules
2. Selecting the assets, and entering them in a worklist
3. Checking and correcting the worklist, and releasing the worklist (= execution of the mass change)
De�ning the Change Rules I
You de�ne the change rules using Substitution. The change rules determine
under which circumstances
which master data �eld should
receive which new contents.
When you create a worklist for mass change, you have to enter a substitution rule. When the worklist is processed, all the assets in the worklist are
changed according to the de�ned rules.
For more information on substitution rules, see the documentation in the FI-AA Implementation Guide under Master Data. The procedure for
de�ning a substitution rule is described there.
De�ning the Change Rules II
https://help.sap.com/docs/disclaimer
4/11/2024
6This is custom documentation. For more information, please visit the SAP Help Portal
 
De�ning Substitutions
De�ning the Change Rules III
The following graphic shows the Customizing de�nition of a substitution rule. In all assets with cost center "MILA", the cost center should be replaced
by cost center "HOLIDAY".
De�ning the Change Rules IV
https://help.sap.com/docs/disclaimer
4/11/2024
7This is custom documentation. For more information, please visit the SAP Help Portal
De�ning the Change Rules V
De�ning the Change Rules VI
https://help.sap.com/docs/disclaimer
4/11/2024
8This is custom documentation. For more information, please visit the SAP Help Portal
De�ning the Change Rules VII
De�ning the Change Rules VIII
https://help.sap.com/docs/disclaimer
4/11/2024
9This is custom documentation. For more information, please visit the SAP Help Portal
De�ning the Change Rules IX
De�ning the Change Rules X
https://help.sap.com/docs/disclaimer
4/11/2024
10This is custom documentation. For more information, please visit the SAP Help Portal
De�ning the Change Rules XI
Process Flow - Carrying Out Mass Changes I
1. De�ne a substitution rule for the mass change (Tools -> Mass change rule).
2. Select the assets that are to be changed. Either start any standard FI-AA report, or use the function Tools -> Work list -> Generate. Start the
report with the appropriate limitations. Note that you can only select assets from a single company code.
3. Select the function Create worklist on the output list. Select the standard purpose "Change master record."
4. In the next dialog box, select the substitution rule that you want to use for the mass change.
Process Flow - Carrying Out Mass Changes II
https://help.sap.com/docs/disclaimer
4/11/2024
11This is custom documentation. For more information, please visit the SAP Help Portal
Process Flow - Carrying Out Mass Changes III
5. Choose Tools -> Worklist -> Edit. Enter the number of your worklist and choose Execute.
6. You can enter individual assets in the worklist or delete them under Edit. You can also include complete worklists in the worklist under Add to
worklist.
7. Under Change worklist header, you can change the substitution rule for the mass change.
8. Release the worklist (Release).
9. Check the status of the worklist (Refresh screen). The following statuses are possible:
Ready (was created, but not yet processed)
Accepted (being processed, but not yet released)
Ended (all assets were changed correctly)
With errors (the change could not be made for at least one asset because an error occurred)
Process Flow - Carrying Out Mass Changes IV
10. Check any errors that occurred during the mass change to master data (Edit ->? _Display error). Correct the errors. Use the long text of the
error message as a help.
11. Create and process a new worklist for the assets that had errors.
12. Check the results using the change document list (Infosystem -> Report selection -> Preparations for closing).
Further Information I
Validations are not needed for Asset Master Data Mass Changes, only a substitution rule is necessary.
The system documents the mass change to master data using change documents, just as it does for manual changes.
You can enter the number of the worklist as a selection criteria in the standard report for displaying master data changes. The report shows
all changes that were made using a mass change. It also shows the user who processed the mass change.
You can also include more than one person in carrying out a mass change to asset master data. Using this method provides you with an
opportunity for additional checks by other members of your enterprise. For more information, see "BC Work�ow Scenarios in the
Applications".
The work�ow scenario "Mass changes to asset master data" (including more than one person) is active as soon as a user is assigned to the
standard activity "Correct worklist" (FI-AA Customizing: Preparing for Production Startup -> Management of Authorizations). On the other
hand, you have to make sure that this activity is not assigned to a user, if you do not want to use work�ow and instead plan to use the
procedure described above.
https://help.sap.com/docs/disclaimer
http://help.sap.com/saphelp_470/helpdata/en/04/926f8546f311d189470000e829fbbd/frameset.htm
4/11/2024
12This is custom documentation. For more information, please visit the SAP Help Portal
Further Information II
You can add individual assets to a worklist
From within the asset master data transaction
During later processing of the worklist
From with the FI-AA standard reports
Important Consulting Notes
544703 -> FAQ Mass change / Mass retirement
543138 -> Mass change / mass retirement
383812 -> Bulk change asset description via user exits
317762 -> Mass change only changes �elds de�ned in substitution
210897 -> Substitution of time-dependent data
127887 -> Performance measures for large datasets
75976 -> Problems with mass changes / mass retirement
Asset Master: WBS Element - Difference between PS_PSP_PNR and PS_PSP_PNR2
Purpose
This document should help to identify the origin and purpose of a WBS Element (Work Breakdown Structure) posting, and explains the link
between the customizing in transaction ACSET and where it is represented in the Asset Master Record.
Overview
This document explains the difference between the two account assignments for WBS Elements (Work Breakdown Structure) PS_PSP_PNR and
PS_PSP_PNR2 (Costs) in Customizing Transaction ACSET and how it corresponds to the Asset Master Record �eld 'WBS Element' (of Investment
Project), table ANLA-POSNR respectively �eld 'WBS Element (Costs)', table ANLZ-PS_PSP_PNR2. 
Transaction ACSET:
There are two options for WBS Element Account Assignment Objects in Customizing: PS_PSP_PNR and PS_PSP_PNR2
Difference between the two WBS Element Account Assignments and where in the Asset Master
Record they are re�ected
Notice that there is a difference between Account Assignment PS_PSP_PNR2 and PS_PSP_PNR:
A) Account Assignment PS_PSP_PNR2 is the �eld in the asset master record on the tab 'Time-dependent' which is called 'WBS Element (Costs)'. It
is normally used to post gain/loss, depreciation and interest on it.
 
You can use this �eld and assign a WBS element to the asset in the case where you want to make an account assignment of depreciation and
interest, as well as gain/loss to a WBS element.
https://help.sap.com/docs/disclaimer
4/11/2024
13This is custom documentation. For more information, please visit the SAP Help Portal
B) In contrary, the Account Assignment PS_PSP_PNR (WBS Element of Investment Project) is displayed in the asset master data on tab 'Origin' and
is called 'WBS element'. It is used to be posted statistically for acquisition or retirement postings.
Important to note:
Please note that in the system standard behaviour, the WBS Element or Investment Order is automatically updated under the 'Account Assignment
for Investment' section in the "Origin"tab in the Asset Master Record (transaction AS03 to display) when creating the AUC (Investment Measure)
from transaction CJ01 or KO01. That is why the WBS element can be seen in the Asset under Construction (AuC) master date in tab "Origin".
Regarding the Final Asset (FXA) the Asset number in tab "Origin" is always updated with the source asset of a transfer, and �nal settlements are
transfers from the AuC to the Final Asset. In the Final Asset there is not an automatic way to update WBS element in the tab "Origin" in the Asset
Master Record!
Transaction SPRO: Customizing Requirements
Please refer to Customizing SAP Note 684659 FAQs about account assignment objects as of Release 4.70 .
Minimum customizing must be in place for the company code (and depreciation area) in order for the account assignment to work: The account
assignment object must be activated in Customizing, Transaction SPRO - SAP Reference IMG:
Menu Path: Financial Accounting - Asset Accounting - Integration with the General Ledger - Additional Account Assignment Objects:
Set up the assignment for posting of APC Transactions and/or Depreciation. For the system to post depreciation to a WBS element it is important
that the indicator for this is set in the Customizing de�nition of the depreciation posting run.
Use the Asterix * for transaction type if the assignment is meant for all kind of transactions.
Once in the customizing transactions, use the F1 Help option for �elds and indicators within the customizing to help to decide which are relevant to
your business requirements.
Related Transaction Codes:
ACSET
AACCOBJ
Related Documents
Activate PS_PSP_PNR as Account Assignment Object in FI-AA 
Related SAP Notes/KBAs
684659 FAQs about account assignment objects as of Release 4.70
548735 FQA note account assignment objects 
71079 Investment acct. assignment �elds for assets
__________________________________________________________________________________________________________
Use this structure to help you compose your contributions for WIKI and at the same time will ensure spelling and grammar.
https://help.sap.com/docs/disclaimer
https://me.sap.com/notes/684659
https://help.sap.com/docs/SUPPORT_CONTENT/plm/3363506183.html
https://me.sap.com/notes/684659
https://me.sap.com/notes/548735
https://me.sap.com/notes/71079
4/11/2024
14This is custom documentation. For more information, please visit the SAP Help Portal
Basic Con�guration settings for implementing Asset Accounting in SAP 6.0
Basic Con�guration settings for implementing Asset Accounting in SAP 6.0
INTRODUCTION:
The asset accounting module in SAP is one where the accounting pertaining to �xed assets is done. These include transactions like acquisition of
�xed assets, sale of �xed assets, in-house development of assets, settlement of WIP, and accounting for depreciation on �xed assets and so on.
A separate Asset Accounting Module is required for these transactions because there are some distinguishing characteristics of �xed assets as
compared to normal General Ledger accounts. Some of these characteristics of �xed assets which necessitate a separate Asset accounting module,
are given below :
- Fixed assets have a life span exceeding one year. But they are subject to wear and tear, and to provide for this we need to depreciate them.
The Asset Accounting Module enables such calculation of depreciation (we can create depreciation keys where we give the rate of depreciation).
Such feature is not there in the normal GL Accounting.
- Fixed assets must be shown as a separate head in the balance sheet of companies, and that too under broad categories. Example : Land, Plant
and Machinery etc. In the Asset Accounting Module, we can categorize individual �xed assets into asset classes, and thus we can meet this
requirement. In other words, classi�cation of �xed assets for balance sheet disclosure purposes becomes easy.
- Sometimes we may have self-constructed �xed assets which are categorized as WIP in construction stage. These must be settled from WIP to
normal GL accounts after construction. This facility of settlement is provided by the Asset accounting module.
- The management may require different reports pertaining to �xed assets like asset history report, report of �xed assets cost center wise etc,
which are readily available in the Asset Accounting Module.
- Apart from this some other features like assets planned values, calculation of insurance value, physical inventory data etc. are possible in
asset accounting.
In order to set up the asset accounting module in SAP, some con�guration needs to be done in IMG. This includes setting up the organization
structure, de�ning the depreciation areas, creating the different asset classes, account assignment, de�ning depreciation keys and so on. All these
con�guration settings has been discussed below:
1) Chart of Depreciation: A chart of depreciation is a directory of depreciation areas arranged according to business requirements. Each chart of
depreciation contains the rules for the evaluation of assets that are valid in a speci�c country or economic area.
Each company code de�ned in Asset Accounting must refer to a chart of depreciation.
Copy reference Chart of Depreciation: SAP provides country-speci�c charts of depreciation with prede�ned depreciation areas. These charts of
depreciation are only references for customer charts of depreciation and therefore, cannot be used directly. When you create your own chart of
depreciation, you must copy a reference chart of depreciation. Once the 
 same is copied, give the required description to the newly created Chart of Depreciation.
Transaction Code: EC08
IMG Menu Path: Financial Accounting (New) à Asset Accounting à Organizational Structures à Copy Reference Chart of
Depreciation/Depreciation Areas à Copy Reference Chart of Depreciation
2) De�ne Chart of Depreciation and depreciation areas: You can change the de�nition of the depreciation areas that were copied from the
standard depreciation plan, and add additional depreciation areas if required:
Transaction Code: OADB
IMG Menu Path: Financial Accounting (New) à Asset Accounting à Organizational Structures à Copy Reference Chart of
Depreciation/Depreciation Areas à Copy/Delete Depreciation Areas
3) Assign Chart of Depreciation to Company code: When you assign a Chart of Depreciation, you assign a Company code for asset accounting.
Transaction Code: OAOB
IMG Menu Path: Financial Accounting (New) à Asset Accounting à Organizational Structures à Assign Chart of Depreciation to Company Code
4) Asset Classes: Asset classes are the most important structuring elements for �xed assets. You can de�ne any number of asset classes in the
system. You can use them to structure your �xed assets according to different criteria. Asset class controls asset master data. Many values are
derived from asset class while creating the master data. Example : Asset number, GL accounts, screen layouts are derived from asset class. Further
it provides default depreciation keys while creating the master data.
 Individual assets must compulsorily be assigned to an asset class at time of creating them, e.g. A Table purchased may be booked as a individual
asset linked to an asset class "Furniture". As given earlier, companies are required to classify their assets in the balance sheet into different broad
heads, and asset classes may be created to suit these. Based on asset classes, we also assign the account assignment for various transactions
pertaining to that asset class.
 Transaction Code: OAOA
IMG Menu Path: Financial Accounting (New) à Asset Accounting à Organizational Structures à Asset Classes à De�ne Asset Classes
 5) Specify Account Determination: The most important function of an asset class is to link asset master records to their respective general
ledger accounts in Financial Accounting. This link is created by the account determination keyin each asset class. You can assign several asset
classes to the same account determination key.
Transaction Code: SPRO
IMG Menu Path: Financial Accounting (New) à Asset Accounting à Organizational Structures à Asset Classes à Specify Account Determination
 6) Create Screen Layout Rules: Screen Layout rules are created to make it easier to maintain the asset master data as the asset master
contains a large number of �elds which are used for different purposes.
Transaction Code: SPRO
IMG Menu Path: Financial Accounting (New) à Asset Accounting à Master Data à Screen Layout à De�ne Screen Layout for Asset Master Data à
Create Screen Layout Rules for Asset Master Record
7) Number Assignment Across Company Codes: In Asset Accounting you can assign the main asset number on the basis of cross-company codes.
Transaction Code: AO11
https://help.sap.com/docs/disclaimer
4/11/2024
15This is custom documentation. For more information, please visit the SAP Help Portal
IMG Menu Path: Financial Accounting (New) à Asset Accounting à Organizational Structures à Specify Number Assignment Across Company
Codes
8) De�ne how depreciation areas post to General Ledger: This setting will determine how the depreciation areas post their APC transactions
and/or depreciation to the GL. SAP can post the APC transactions of one depreciation area to the general ledger online automatically. Usually this is
the book depreciation area 01. For the rest, transactions to the general ledger can be posted automatically using periodic processing.
Transaction Code: OADX
9) Assign the General Ledger Accounts: Account determination is a set where GL accounts are assigned to post asset acquisition, retirement &
depreciation based on various business process scenario. These account determinations are then assigned to asset classes to derive & control GL
postings pertain to the asset class. Here we give the Chart of account wise General Ledger Account determination for various asset accounting
transactions, like acquisition, gain/loss on sale, ordinary depreciation etc.
Transaction Code: AO90
10) Specify the Financial Statement Version for Asset Reports: This de�nes which �nancial statement version should SAP use for each
depreciation area as a default. This default applies when the �nancial statement version is contained in the sort version used for a given report.
Transaction Code: OAYN
Specify Account Assignment Types for Account Assignment Objects: Here we can de�ne how the controlling area posting of cost required for
each asset transaction type. We con�gure the account assignment objects that can be posted based on :
- The transaction type, and
- Account assignment type
IMG Menu Path: Financial Accounting à Asset Accounting à Integration with the General Ledger à Additional Account Assignment objects ->
Specify account assignment types for account assignment objects
11) Assign Tax code for non-taxable transactions: Here we give the input/output tax code which is used when posting non-taxable
transactions to tax-relevant accounts from the Accounting interface. As an alternative, it is possible to set an indicator in the G/L account master
record which permits transactions "not relevant to tax" to be posted even without a tax code.
Transaction Code: OBCL
12) Assign settlement pro�le: The settlement pro�le includes settings on the allowed receivers of the settlement. We can give settlement pro�le 10
to enable settlement to all receivers. The settlement pro�le is applicable to assets under construction.
 Transaction Code: OAAZ
13) Maintain Depreciation keys & activate them: Depreciation keys contain the calculation methods for depreciation calculation and parameters
that control :
- Ordinary depreciation
- Special depreciation
- Scrap value (cutoff value)
 Transaction Code: AFAMA
14) Specify document type for posting depreciation: Here we give the accounting document type to be used in depreciation postings, for the
company code.
Transaction Code: AO71
 15) Specify Intervals & Posting Rules: Here we specify the depreciation areas for which the depreciation is posted to the general ledger during the
depreciation run. We specify if the period for depreciation posting in the run is monthly, bi-monthly, quarterly etc.
Transaction Code: OAYR
16) Determine Depreciation Areas in the Asset Class: Here, asset classes are assigned default values for the depreciation key and useful life. These
values are defaulted whenever postings to assets of these classes is done.
Transaction Code: OAYZ 
I hope this will help the readers with the basic settings required for con�guring Asset Accounting in SAP 6.0.
Basics of Asset Accounting – Creating Asset Master Record
Purpose
The purpose of this page is to clarify the understanding of the system logic and requirements in relation to the creation of asset master record.
Overview
The following paragraphs and pictures will describe an EXAMPLE in steps of the creation of an asset and the functionality of the main �elds and their
links between other components like FI-GL, CO, PM.
Creating Assets - Creating an asset master record
To create the asset go to Navigation: SAP Easy Access -> SAP Menu -> Accounting -> Financial accounting -> Fixed Asset -> Asset -> Create ->
Asset
Alternatively: Transaction code AS01
https://help.sap.com/docs/disclaimer
4/11/2024
16This is custom documentation. For more information, please visit the SAP Help Portal
1) Fill out the �elds Asset Class and Company Code with ZSAO (Press Enter)
2) Fill out �eld Description, as detailed in the image below:
https://help.sap.com/docs/disclaimer
4/11/2024
17This is custom documentation. For more information, please visit the SAP Help Portal
3) If you double click in Acct. Determination 20000, you will be forwarded to GL account master Data (transaction code FS00) as you can see in the
below picture. I.E.: to see the Accounts related to this account determination you may go to transaction code AO90. 
4) In Time - dependent tab Fill out the �eld Cost Center with ZSAO (Relevant to CO integration).
5) If you double click in Cost Center ZSAO, you will be forwarded Cost Center Master Date (transaction code KS03)
https://help.sap.com/docs/disclaimer
4/11/2024
18This is custom documentation. For more information, please visit the SAP Help Portal
6) In Allocation tab you will be able to see the integration of assets and equipment. However the equipment number will be automatically updated
only after you save the new asset.
7) In Depreciation Area Tab you can set the depreciation key for each depreciation area.
https://help.sap.com/docs/disclaimer
4/11/2024
19This is custom documentation. For more information, please visit the SAP Help Portal
Related Content
Related Documents
http://help.sap.com/saphelp_erp60_sp/helpdata/en/4f/71e040448011d189f00000e81ddfac/frameset.htm
Related Notes
Change log of asset master data
Purpose
This document describes how to check historical changes on asset master data.
Overview
Changes on asset master data could affect asset depreciation calculation as well as output results of asset reports. In standard system, we can
check if any change made on a single speci�c �eld of asset master data, or on whole asset master data. In addition, we could sort out changed assets
from mass asset by ʻDate of change’, ʻChanged by’ and ʻField changed’ and so on.
Section 1
To check changes on a solo �eld of asset master data, we need to follow below steps:
1, Use transaction code AS02 or AS03 to display asset master data
2, Place cursor on the �eld you want to check its historical changes
3, Go through menu: Environment -> Change documents -> On �eld
Here is an example to display the changes on �eld ʻDepreciation key’:
Section 2
To check changes on whole asset master data. We need to follow below steps: 
1, Use transaction code AS02 or AS03 to display asset master data
2, Go through menu: Environment-> Change documents -> On asset
Here is an example to display all changes on an asset since the asset is activated.
https://help.sap.com/docs/disclaimer
http://help.sap.com/saphelp_erp60_sp/helpdata/en/4f/71e040448011d189f00000e81ddfac/frameset.htm
4/11/2024
20This is custom documentation. For more information, please visit the SAP Help Portal
Section 3
To sort out assets from mass assets by one criteria or combined criteria of ʻDate of change’, ʻChanged by’ and ʻField changed’ and so on, you can use
report RAAEND01 or report RAAEND02 for this purpose. 
Here, if we specify below parameters and run report RAAEND01, then we could have same result of example 1. 
Parameter selection:
Output result:
De�nition of Asset Class
Purpose
This document describes how to de�ne an asset class. 
Overview
https://help.sap.com/docs/disclaimer
4/11/2024
21This is custom documentation. For more information, please visit the SAP Help Portal
Asset classes are the most important means of structuring �xed assets according to real business requirement. An asset class consists of two main
sections: asset master data section and depreciation area section.
Section 1
We use transaction code OAOA to de�ne with control data and default values for asset master data in an asset class. in this section, below main
con�guration contains: 
- Account determination 
to establish a link between the asset master records and their values and the general ledger accounts to which the related asset values and
depreciation are posted
- Screen layout rule 
determines which input �elds in the asset master records can be processed or whether these �elds are to be de�ned as required �elds or if the �elds
are not displayed at all
- The number range 
controls the assignment of the number of the asset master 
- Status of AUC record
Assets under construction (AuC) require a separate asset class and corresponding G/L account, because they have to be shown separately in the
�nancial statement.
Section 2
We use transaction codet OAYZ to de�ne with control parameters and default values for depreciation terms for each depreciation area in an asset
class. 
FI-AA (Asset Accounting) and PM (Equipment) Synchronization
Purpose
How to activate synchronization of master data in FI-AA (Asset Accounting) and PM (Equipment).
Overview
In Transaction SPRO go to the following customizing path.
Financial Accounting -> Asset Accounting -> Master Data -> Automatic creation for Synchronization of Master Data.
https://help.sap.com/docs/disclaimer
4/11/2024
22This is custom documentation. For more information, please visit the SAP Help Portal
Select an Asset Class and double click into the next screen.
Set the System to synchronize any changes made in the Equipment master data with Asset master data and vice versa as outlined in the screen
below.
https://help.sap.com/docs/disclaimer
4/11/2024
23This is custom documentation. For more information, please visit the SAP Help Portal
With the following settings, every time you create an Asset, via transaction code AS01, in this particular asset class an Equipment Master record is
created and like wise when you create an Equipment via Transaction IE01 a corresponding asset is created.
Transaction IE03:
https://help.sap.com/docs/disclaimer
4/11/2024
24This is custom documentation. For more information, please visit the SAP Help Portal
 
Also, anytime you make a change in either the master data (AS02) or equipment (IE02) the change is also automatically updated in both.
In the asset master data, via AS02, add a cost centre.
https://help.sap.com/docs/disclaimer
4/11/2024
25This is custom documentation. For more information, please visit the SAP Help Portal
https://help.sap.com/docs/disclaimer
4/11/2024
26This is custom documentation. For more information, please visit the SAP Help Portal
You can now see this update in the equipment Master Data via IE03:
https://help.sap.com/docs/disclaimer
4/11/2024
27This is custom documentation. For more information, please visit the SAP Help Portal
Related Content
Related SAP Notes/KBAs
 SAP Note 370884 - PM-AA 4.6C: Consulting on sync activation + corrections 
SAP Note 549929 - FAQ Note on AA-PM linkage
KBA 1877281 - Link between equipment and asset is broken
Flag ʻNegative val.allowed’ using in asset class level
Flag ʻnegative val.allowed’ using
Purpose
The purpose of this page is to clarify the understanding of ̒ negative val.allowed’ using.
Overview
About this indicator :
Set this indicator, if you want negative APC and positive depreciation to be allowed for the asset. 
This might be necessary, for example, for
-investment support, that is managed in the form of a negative asset
-assets under construction, if you need to post a subsequent credit memo 
 to the asset under construction after it has already been completely settled
The indicator is not required, if depreciation below-zero should be calculated for assets in this class.
NOTE:
https://help.sap.com/docs/disclaimer
https://launchpad.support.sap.com/#/notes/370884
https://launchpad.support.sap.com/#/notes/549929
https://launchpad.support.sap.com/#/notes/1877281
4/11/2024
28This is custom documentation. For more information, please visit the SAP Help Portal
You are not allowed to set this indicator for depreciation areas,
which are de�ned to manage negative values
(such as, depreciation areas for investment support shown on the liabilities side,
or areas for transferred reserves).
How to set the ʻnegative val.allowed’ in the class level
1. Go to T-code: OAYZ, select asset class you want to modify and double click “depreciation areas” in the dialog structure.
2. In the next screen, check the value of �eld “Layout”
https://help.sap.com/docs/disclaimer
4/11/2024
29This is custom documentation. For more information, please visit the SAP Help Portal
3. Go to T-code: AO21, select “ScrnLayout” which is con�rmed in step above, and double click “Field group rules” in the dialog structure.
4. In the next screen, �ag on the check box of “Class” for the �eld 17 (Field group name : Negative values) and SAVE
https://help.sap.com/docs/disclaimer
4/11/2024
30This is custom documentation. For more information, please visit the SAP Help Portal
5. Then check the �led in T-code: OAYZ again, “Negative val.allowed” is available.
How to do mass change for Negative value allowed
Purpose
In certain case, we have to set "Negative value allowed" for many assets. And it will take time to set the indicator one by one.
We could use substitution and work like to do the mass change.
 
Section
Before set the indicator:
https://help.sap.com/docs/disclaimer
4/11/2024
31This is custom documentation. For more information, please visit the SAP Help Portal
T-cd: OA02 to create a substitution
https://help.sap.com/docs/disclaimer
4/11/2024
32This is custom documentation. For more information, please visit the SAP Help Portal
T-cd AR01 select the assets which you want to set the �ag(in this example only one asset need to maintain)
Click work list button 
https://help.sap.com/docs/disclaimer
4/11/2024
33This is custom documentation. For more information, please visit the SAP Help Portal
Enter the substitution name here
T-cd AR31 Release the work list
https://help.sap.com/docs/disclaimer
4/11/2024
34This is custom documentation. For more information, please visit the SAP Help Portal
 
After release the change
https://help.sap.com/docs/disclaimer
4/11/2024
35This is custom documentation. For more information, please visit the SAP Help Portal
 
 
 
 
How we can verify Account assignment objects in Assets Accounting
Purpose
The purpose of this page is to illustrate where in the system, we can verify the con�guration of account assignment objects in the Assets Accounting
side.
Overview
There are many situations where we need to verify our Account assignment objects con�guration. Many of these situations are described in the SAP
note 684659.Where can we verify them in the system?
In note 684659 we are request to verify a few con�gurations. For example, in case we want to verify Account assignment objects Cost Center in the
system:
1. Activate the account assignment object required.
Go to Transaction code SPRO:
https://help.sap.com/docs/disclaimer
4/11/2024
36This is custom documentation. For more information, please visit the SAP Help Portal
2. De�ne which account assignment objects have to be assigned to an account for the
corresponding transactions. 
Go to Transaction code SPRO:
https://help.sap.com/docs/disclaimer
4/11/2024
37This is custom documentation. For more information, please visit the SAP Help Portal
3. Check whether the account (de�ned in the account determination) has �eld status group with
Cost element as Optional. 
Go to Transaction code FS03 to verify G/L Account in the affected Company Code:
https://help.sap.com/docs/disclaimer
4/11/2024
38This is custom documentation. For more information, please visit the SAP Help Portal
https://help.sap.com/docs/disclaimer
4/11/2024
39This is custom documentation. For more information, please visit the SAP Help Portal
4. Check whether the account has been created as a cost element in Controlling and if it in valid
date.
 Go to transaction code KA03 to check account element:
Go to transaction code OAK7 to create cost element:
https://help.sap.com/docs/disclaimer
4/11/2024
40This is custom documentation. For more information, please visit the SAP Help Portal
5. In case you want to assign APC values postings to a statistical cost element and cost center,
you also have to deactivate error message KI 098 in CO Customizing.
Go to transaction code OBA5:
Related Content
Related SAP Notes/KBAs
Sap Note 684659 FAQs about account assignment objects as of Release 4.70
https://help.sap.com/docs/disclaimer
https://service.sap.com/sap/support/notes/684659
4/11/2024
41This is custom documentation. For more information, please visit the SAP Help Portal
Sap Note 1732825 Error KI 235 in asset accounting transaction
 
Ignore memo value (ANLA-XERWRT) or OAAW
Purpose
The purpose of this page is to clarify the understanding of the setting for “Ignore memo value”.
Overview
Basing on business requirement or legal requirement, you can set memo value for a whole company code in t-code: OAYI. In case that some asset
classes do not need to care about memo value, 
for these asset classes, you can set ʻDo not take memo value into account’ in t-code: OAAW. However, this doesn’t work existing assets in the same
class.
Reason behind
In table ANLA, there’s a �eld XERWRT (Indicator: Ignore memo value) that controls whether memo value is taken into account or not. Changing in t-
code: OAAW only affects new assets created. For existing assets, this �eld remains unchanged even you change t-code: OAAW later.
Way to update this �eld on asset level
Unfortunately there’s no direct customizing transaction code to do this, but this can be done by writing a small program or by using asset master
record mass change. More information about mass change can be found in below "related documents".
Related Content
Related Documents
Asset Master Record Mass Changes
Related SAP Notes/KBAs
SAP Note 32901: - General information on the memo value
Logical Field Group Assignment in Validation and Substitution Rules
Purpose:
This document explains the importance of assigning and how to assign the correct logical �eld group to an asset master validation rule or
substitution rule.
Overview:
When creating a validation/substitution rule for asset master it is important to check the logical �eld group that is assign to the rule. It has to match
with the logical �eld group created in the screen layout for the asset master in transaction AO21. If the incorrect logical �eld group is assigned to a
validation/substitution rule the validation/substitution itself will not take effect as desired.
Transaction OACV – Validation and Validation Rule:
In this Example Validation we focus on �eld “WBS Element” (Technical �eld name ANLA-POSNR) in the Asset Master (Transaction AS01/AS02) in Tab
ʻOrigin’. The validation created in Transaction OAVC currently has assigned Logical Field Group 9 in the validation rule, as per we believe it is correct
and in line with Customizing in Transaction SPRO for Screen Layout for tab 'Origin': IMG Menu Path is Asset Accounting – Master Data – Screen
Layout – De�ne Screen Layout for Asset Master Data
https://help.sap.com/docs/disclaimer
https://service.sap.com/sap/support/notes/1732825
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880169.html
https://me.sap.com/notes/32901
4/11/2024
42This is custom documentation. For more information, please visit the SAP Help Portal
The current - Display View “Validation for Master Data” - looks as follows:
However, the validation does not work as expected -> see the test result for further details in section 'Transaction AS01 or AS02' below.
Let’s see in the validation what the Prerequisites and Check Rule are?
Go to Menu -> Goto – Validation
The validation stipulates for the system to issue the Error Message “Information of the WBS element is required” in case the �eld is not �lled
(ʻblank’) in the Asset Master transaction AS01/AS02:
Transaction AS01 or AS02:
Test the Validation in Create/Change Asset Master Data
https://help.sap.com/docs/disclaimer
4/11/2024
43This is custom documentation. For more information, please visit the SAP Help Portal
Go to Tab ʻOrigin’
1) Fill in the value in �eld “WBS Element”
2) Hit Enter
NOTE: The system ignores the validation rule and issues the error message despite the prerequisites of the validation rule are met: Error Message
“Information of the WBS element is required”
Transaction OAVC - Logical Field Group Assignment:
Check Logical Field Group assigned to the validation rule
https://help.sap.com/docs/disclaimer
4/11/2024
44This is custom documentation. For more information, please visit the SAP Help Portal
Transaction AS01 or AS02 - Tab 'Origin':
Field “WBS Element” is under tab ʻOrigin’ , BUT under Section A̒ccount assignment for investment’
IMG: Screen Layout for Asset Master - �eld “WBS Element” (ANAL-POSNR):
Where in the Screen Layout for Asset Master is �eld “WBS Element” (ANAL-POSNR) listed?
https://help.sap.com/docs/disclaimer
4/11/2024
45This is custom documentation. For more information, please visit the SAP Help Portal
Check Customizing Transaction SPRO - IMG:
Although we �nd the �eld “WBS Element” in Tab ʻOrigin’ in the Asset Master (AS01/AS02) as can be seen above, we have to take into accout in
which sub-section within a tab a �eld is assigned.
In our example, the screen layout shows �eld “WBS Element” in Logical Field Group 10 ʻInv.account assignment’, and not in Logical Field Group 9
ʻOrigin’ as may be expected when looking at the tab ʻOrigin’ in the Asset Master.
Double-click on the line: Field group name “Investment project” is �eld “WBS Element” (= ANLA-POSNR) in the Asset Master
https://help.sap.com/docs/disclaimer
4/11/2024
46This is custom documentation. For more information, please visit the SAP Help Portal
Transaction OACV- Adjust Validation Rule:
In order for the validation to work, the logical �eld group assigned in the validation rule must be the same logical �eld group to which �eld ANLA-
POSNR (= �eld ʻWBS element’) is assigned in the asset master customizing. It may not be the 'obvious' �eld group name as per the 'asset master
tab name' - it may be a sub-section within the asset master tab, and hence belongs to a different logical �eld group.
Logical Field Group 9 (Tab ʻOrigin’ in Transaction AS01/AS02) for �eld “WBS Element” is not correct. 
The correct Logical Field Group is 10 in our example (�eld group name ʻInv. account assignment’). In transaction AS01/AS02 this sub-section in tab
'Origin' is actually called ̒Account assignment for Investment’ .
Once the correct Logical Field Groupis assigned in the Validation Rule, the Validation will work when �lling a value in �eld “WBS Element” in
Transaction AS01/AS02. No error message will be triggered by the validation.
More Interval button not appearing in Depreciation Area tab
You have activated Business Function EA-FIN via T-code: SFW5 -> ENTERPRISE_EXTENSIONS and the table
TBE11 has also the application EA-FIN activated.
If you go to tab "Depreciation Area" via T-code: AS02 or T-code: AS03 and double click on any line of
depreciation key, you cannot �nd button "More Intervals" in order to add extra intervals of depreciation key.
https://help.sap.com/docs/disclaimer
4/11/2024
47This is custom documentation. For more information, please visit the SAP Help Portal
As of release ERP 6.0, if business function EA-FIN is activated, button "More Intervals" will be displayed in the
master data of depreciation area. However, if the switch on business function sets and business functions is not
performed successfullyowing to any reason, consequently button "More Intervals" cannot be displayed in the
master data of depreciation area as expected.
It can happens that there is an inconsistency with the switch and the business function in your system for EA-
FIN. Business Function EA-FIN was activated but switch is OFF. You can check these inconsistencies in
transaction SFW_BROWSER. 
You should �rst apply the note 1528533. Then go to transaction SFW5 menu System Settings-> Activate Restart.
Please refer to the following notes 2068227 and 965032.
 
 
 
 
 
Parallel Ledger con�guration in classic Asset Accounting Vs New Asset Accounting
 
To understand the system behavior, the most important thing is to understand how area 01 is posting its values:
As you will know, area 01 is the only area that is posting its values online (this means that APC values will be
updated in the G/L directly when posting to an asset). It is a technical matter that this "Online"- posting will
always be done to ALL(!) ledgers that are de�ned in the company code. So whatever Ledger group you assign to
depreciation area 01, this will not be considered by any APC value posting, APC transactions (as well as write-
ups) will always be posted in ANY ledger group in G/L with the values from area 01.
 If you then want to setup a scenario in Fixed Asset Accounting, where you post different valuations (local GAAP /
IFRS) to a different ledger group in G/L for parallel valuation, then you have to use (in total) 3 depreciation areas
in the following way. For each additional "valuation" for which you have additional ledgers de�ned in G/L, and for
which you want to get different values as those posted in area 01, you need also two additional depreciation
areas (1 real and 1 derived area) in asset accounting.
 
So a typical dep.area setting for a parallel ledger is like:
 Real Posting to G/L Ledger
Area 01 X 1 0L
Area XX X 3 XX (your ledger code) !!
Area YY 6 XX (your ledger code)
 
Acquisition/transf/retirement postings in area 01 go to all ledgers independently of your setting in OADB. And, if
any difference occurs between area 01 an area XX this is posted trough the derived area YY (posting indicator 6).
https://help.sap.com/docs/disclaimer
https://launchpad.support.sap.com/#/notes/1528533/E
https://launchpad.support.sap.com/#/notes/2255500/E
https://launchpad.support.sap.com/#/notes/965032/E
4/11/2024
48This is custom documentation. For more information, please visit the SAP Help Portal
 
This is the parallel ledger scenario logic and how the techincal solution to this requirement was developped.
Therefore please can you review your current parallel ledger scenario carefully once again and if necessary
contact your local SAP consultant for assistance to ensure your customizing is in place correctly.
 
SAP NOTE 1433535 - Parallel valuation: Ledger approach
DIFFERENCE WITH NEW ASSET ACCOUNTING:
In new FI-AA it is no longer possible to de�ne a ""Delta Area"", as we know it from classical FI-AA. These Delta
Areas where usually part of a so called Ledger Scenario, which was how parallel valuation with mutliple ledgers
had been realized in FI-AA.
The former Delta Area was necessary to post APC adjustments for the parallel ledger. This is why it was possible
to de�ne a derived area that posts to GL and which base areas belong to different ledger groups. It's also why the
�ag ""Derived area as real area"" was added to the setup (because otherwise the delta postings could not hit the
same accounts as in the base areas, because normally a derived area uses only a limited set of accounts).
In new FI-AA there is for each Ledger Group a depreciation area that posts ""realtime"". This area posts the
complete APC amount and delta postings are no longer necessary.
 
Pro�t center generation rules in Asset Accounting
Purpose
This document describes how the pro�t center will be generated if there are couple of CO objects available in asset master data and/or transaction
posting.
Overview
System always derive pro�t center based on pre-de�ned priotiry of CO object. In order to ensure that system works as desired, below customizing
described in SAP Note 684659 has to be con�gured completely for Cost Center (as well as for Pro�t Center as of release 605 with activation of BF
FIN_GL_REORG_1) 
1. First, activate the required account assignment objects (choose the activity Activate Account Assignment Objects). De�ne whether
the corresponding account assignment object is relevant to the balance sheet or whether the account assignment object must be
identical with the account assignment object from the master record while posting. For more detailed information, read the IMG
documentation.
 
2. In addition, de�ne the corresponding account assignment rules (choose the activity Specify Account Assignment Types for Account
Assignment Objects). De�ne which account assignment objects have to be assigned to an account for the corresponding transactions.
For more detailed information, read the IMG documentation. Note that all transactions are generically assigned to the respective
object if you enter transaction type '*'. Likewise, you can exclude individual transaction types by deselecting the indicator AcctAssgnt.
 
3. Make sure that the account assignment objects are ready for input in the �eld status of the account and the posting key. Hidden
objects are not copied to the line items.
 
(Example: If you grayed out the cost center in the �eld status, a pro�t center derivation cannot be performed for this line item).
 
https://help.sap.com/docs/disclaimer
https://launchpad.support.sap.com/#/notes/1433535/E
4/11/2024
49This is custom documentation. For more information, please visit the SAP Help Portal
4. Check whether the account has been created as a cost element in Controlling. You can do this with report RACKAR00 or transaction
OAK7.
 
5. If you want to assign APC values postings to a statistical cost element and cost center, you also have to deactivate error message KI 098 in
CO Customizing (transaction OBA5).
Section 1
 For assets that do not belong to any investment measure
The pro�t center is �rst derived from the following objects (if it is available and the pro�t center is not already �lled):
WBS element (ANLZ-PS_PSP_PNR2)
Internal order (ANLZ-CAUFN)s
Key for real estate (ANLZ-IMKEY)
Cost center (ANLZ-KOSTL)
If above objects are not available, then system will perform a derivation from the account assignments to investment measure for an initial
pro�t center:
Investment WBS element (ANLA-POSNR)
Investment order (ANLA-EAUFN)
Section 2
For assets that belong to an investment measure, the sequence mentioned above in used in reverse for pro�t center derivation
Section 3
BADI_FIAA_MASTERDATA with the method DERIVE_PRCTR provides the option to in�uence above rules
RelatedSAP Notes/KBAs
SAP Note 684659 - FAQs about account assignment objects as of Release 4.70
SAP Note 1628542 - Error AIST 009 for account assignments to investment measure
SAP Note 1796962 - Derivation of pro�t centre: BAdI for control
Relationship between asset value date and depreciation start date
Purpose
The purpose of this page is to clarify the relationship between asset value date and depreciation start date, and how they infulence the depreciation
calculation.
Overview
The asset value date is the value date for Asset Accounting. It can derivate from the posting and document date and be in posting periods already
closed for Financial Accounting. However, the posting year and asset value date year must be the same.
Depreciation start date is the key date for the begining of depreciation calculation. As a general rule, the system determines the depreciation start
date from the asset value date of the �rst acquisition posting. However, you can also manually enter a calendar date in the asset master record for
the start of depreciation. In that case, the system ignores the asset value date of the acquisition posting.
The asset value date can have a direct in�uence on the amount of depreciation. It determines the ordinary depreciation date with consideration of
transaction type on the �rst transaction happen in the asset. In the case of depreciation key use remaining useful life in multilevel method, if the
ordinary depreciation start date and asset value date was in the same �scal year, the ordinary depreciation start date will be considered and
depreciation calculation will be calculated from it. And if the ordinary depreciation start date is at the previous year of asset value date, the
depreciation calculation will take the asset value date as the begin of depreciation.
Example
https://help.sap.com/docs/disclaimer
4/11/2024
50This is custom documentation. For more information, please visit the SAP Help Portal
Create an asset with system standard depreciation Key LINS (remaining useful life is used in multilevel method), for example. Capitalize the asset
and set the asset value date to 2013.07.01.
1.Ordinary depreciation start date and asset value date was in the same �scal year, the ordinary depreciation start date will be considered and
depreciation calculation will be calculated from it.
 2.Ordinary depreciation start date is at the previous year of asset value date, the depreciation calculation will take the asset value date as the begin
of depreciation.
https://help.sap.com/docs/disclaimer
4/11/2024
51This is custom documentation. For more information, please visit the SAP Help Portal
Related SAP Notes/KBAs
SAP note 165036 : Period control of subsequent periods
Scrap value, cutoff value and memo value
Purpose 
This page is aimed to clarify the 3 values and their priority in the standard system.
Overview 
For certain types of valuation, it makes sense, or is legally required, that you stop depreciation when a certain value (NBV) is reached.
Scrap value can be set in depreciation area level. You can enter an absolute scrap value or percentage of APC in the asset master record. Or you can
enter a percentage scrap value (cut-off value) in the calculation key.
You can con�gure cut-off value key to realize the control of cut-off value, In this step, you de�ne the calculation key for automatically determining
scrap values. For each calculation key, you can specify the percentage of the depreciation base that should be used as the cut-off value percentage,
at what point in time the system should start calculating the validity period. You can enter several cut-off percentages for each scrap value key. You
can de�ne the cut-off percentages/levels per acquisition year, and the validity period can be of any length. Depending on how the cut-off value key is
de�ned, this amount is either deducted from the depreciation base value before the start of depreciation, or depreciation is stopped as soon as this
amount is reached.
The memo value function is provided in the system in order to allow for managing memo values from a previous system in FI-AA. In order to have a
memo posting for an asset, which has already exceeded its useful life. The system reduces the planned annual depreciation in the acquisition year
for the asset by the amount of the memo value. You can activate or deactivate the memo value by means of an indicator in the asset class, although
it has been de�ned on depreciation area/company code level (this is applies especially to asset classes for low value assets).
Scrap value has higher priority than cut-off value. If there is scrap value and cut-off value exist for one asset at the same time (or memo value is
smaller than both value), after you specify a scrap value, then the cut-off value which is calculated by percentage determined on the basis of the cut-
off value key will not be taken into account. Even if the cut-off value calculated is bigger than scrap value, depreciation will stop when scrap value is
reached.
https://help.sap.com/docs/disclaimer
https://me.sap.com/notes/165036
4/11/2024
52This is custom documentation. For more information, please visit the SAP Help Portal
Memo value is set in depreciation area level, normally, it is a small amount determined by company management requirement, the amount must be
never be violated. If all the three value exist, and memo value is not the smallest amount, system will consider the biggest amount and keep it as
residual value on the asset.
Related SAP Notes/KBAs
SAP note 145975 : Scrap value with negative assets
SAP note 32901 : General information on the memo value 
SAP note 935995 : Tolerance with the cutoff value 
 
Synchronize Asset Accounting and Equipment which created individually
 
Purpose
How to activate synchronization between Asset Accounting and Equipment via AS02 and IE02 when they are created individually.
Overview
Section 1
Transaction code AS02, active indicator "Synchronization" and save.
https://help.sap.com/docs/disclaimer
https://me.sap.com/notes/145975
https://me.sap.com/notes/320901
https://me.sap.com/notes/32901
https://me.sap.com/notes/935995
https://me.sap.com/notes/935995
4/11/2024
53This is custom documentation. For more information, please visit the SAP Help Portal
Section 2
Transaction code IE02
(1) Enter asset information then press "Enter" key.
https://help.sap.com/docs/disclaimer
4/11/2024
54This is custom documentation. For more information, please visit the SAP Help Portal
(2) Click "Change Attchme" button to set synchronization method then save.
https://help.sap.com/docs/disclaimer
4/11/2024
55This is custom documentation. For more information, please visit the SAP Help Portal
The following values are allowed for synchronization method:
' ' No synchronization
'1' Triggering a work�ow when saving
'2' Direct synchronization when saving
'3' Direct synchronization plus work�ow
Section 3 
Check asset master data via transaction code AS03, equipment number linked in asset master number and synchronization activated.
https://help.sap.com/docs/disclaimer
4/11/2024
56This is custom documentation. For more information, please visit the SAP Help Portal
 
Related Content
Related Documents
FI-AA (Asset Accounting) and PM (Equipment) Synchronization
Related SAP Notes/KBAs
 SAP Note 370884 - PM-AA 4.6C: Consulting on sync activation + corrections
 SAP Note 549929 - FAQ Note on AA-PM linkage
 SAP Note 417696 - AAPM AS02 incorrectly without synchronization
Where and how to allow negative values in Assets Accounting by customizing
https://help.sap.com/docs/disclaimer
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880335.html
https://service.sap.com/sap/support/notes/370884
https://service.sap.com/sap/support/notes/549929
https://service.sap.com/sap/support/notes/417696
4/11/2024
57This is custom documentation. For more information, please visit the SAP Help Portal
Purpose
There are some scenarios where it is necessaryto allow the system to post negative acquisition in the asset. Some of these scenarios are described
in the SAP notes 459688, 19048, 141656 and 1521151.
Overview
In this page we expect to be able to show you options and the step-by-step on how you can allow the negative values in the Assets Accounting by
customizing.
Where to customize the negative values?
There are 4 Areas to allow negative values in your customizing:
1. Chart of Depreciation via Transaction code OABN 
2. Depreciation Area via transaction code OADB
3. Asset Class via transaction code OAYZ 
4. Asset Master Data via transaction code AS02
How to customize the negative values (step-by-step)?
1. Chart of Depreciation via Transaction code OABN 
 1.1 Select Depreciation Area
 1.2 Double click over affected “Depreciation Area"
 1.3 Flag the Field "Only negative values and zero allowed"
 
https://help.sap.com/docs/disclaimer
http://service.sap.com/sap/support/notes/459688
http://service.sap.com/sap/support/notes/19048
http://service.sap.com/sap/support/notes/141656
http://service.sap.com/sap/support/notes/1521151
4/11/2024
58This is custom documentation. For more information, please visit the SAP Help Portal
2. Depreciation Area via transaction code OADB
 2.1 Select Depreciation Area
 2.2 Double click over affected “Depreciation Area”
 2.3 Flag the Field "Only negative values and zero allowed"
https://help.sap.com/docs/disclaimer
4/11/2024
59This is custom documentation. For more information, please visit the SAP Help Portal
3. Asset Class via transaction code OAYZ 
 3.1 Select Asset Class
 3.2 Select Folder “Depreciation area”
 3.3 Double click over affected “Asset Class”
 3.4 Double click over affected “Depreciation Area” 
 3.5 Flag the box "Negative val. allowed"
https://help.sap.com/docs/disclaimer
4/11/2024
60This is custom documentation. For more information, please visit the SAP Help Portal
https://help.sap.com/docs/disclaimer
4/11/2024
61This is custom documentation. For more information, please visit the SAP Help Portal
4. Asset Master Data via transaction code AS02
 4.1 Select "Deprec. Area" tab
 4.2 Double click over affected Depreciation Area
 4.3 Negative values allowed
https://help.sap.com/docs/disclaimer
4/11/2024
62This is custom documentation. For more information, please visit the SAP Help Portal
What to do if the 'Neg.Vals Allowed' �eld is not available in Transaction code AS02?
If this �eld is not available, you will need to adjust the screen layout rule to be able to check this box. In this case, please check the screen layout for
the related asset class via transaction code AS03:
Menu > Environment > Screen layout > Depreciation area
Then, go to transaction code AO21:
https://help.sap.com/docs/disclaimer
4/11/2024
63This is custom documentation. For more information, please visit the SAP Help Portal
1. Select needed screen layout rule (in example is 1000)
2. Go to �eld group 17 'Negative values'
3. Change status to optional
4. Check the maintain level as "Asset Class" and "MainNo" as well
Related Content
Related Notes
SAP Note 459688: AA641 after reverse posting in new settlement
SAP Note 19048: AA617 with credit memo on �xed asset / AuC settlement
SAP Note 141656: Negative net book value, neg. APC, below zero depreciation
SAP Note 1521151: Error message AA641 in Trx AIBU - Net book value negative in Depreciation area
Worklist Release and Troubleshooting
Purpose
This is a brief summary of common checks that can be performed in case of issues during worklist creation and release.
Overview
Following the information in this Wiki and the various SAP Notes, KBAs and Wikis referred to in this Wiki, this should help to resolve commonly known
issues arising in relation to creating and releasing worklists within the work�ow processing. These are typically used in Asset Accounting for mass
changes for asset master data and also mass transfers and retirements (common transactions used in this regard are AR01 and AR31).
Work�ow
https://help.sap.com/docs/disclaimer
http://service.sap.com/sap/support/notes/459688
http://service.sap.com/sap/support/notes/19048
http://service.sap.com/sap/support/notes/141656
http://service.sap.com/sap/support/notes/1521151
4/11/2024
64This is custom documentation. For more information, please visit the SAP Help Portal
Commonly known issues may be:
In the user inbox the worklist remains in status "In Process" or "Ready"
Message '5W141 - No administrator found for task' is issued in transaction AR31
The technology of the mass changes is based on work�ow. To be able to use this you need to have the minimum con�guration of the work�ow.
Errors and difficulties are often due to missing customizing, various SAP Notes and WIKI pages already exist to help in troubleshooting. Most are
mentioned and referred to in this Wiki. ,
The customizing of the work�ow is found in IMG (transaction SPRO) under menu path: SAP NetWeaver - Application Server - Business Management -
SAP Business Work�ow - Maintain Standard Settings (SWU3). Here is the possibility of an 'auto-customizing' (transaction SWU3) which will show
whether the customizing is incomplete or not. Process the automatic customizing for work�ow in transaction SWU3. For further information also
review SAP Note 75976.
1) Check in transaction OAWF (IMG: Asset Accounting - Preparing for Production Startup - Authorization Management - Assign Work�ow Tasks) if the
responsible users are assigned to the work�ow tasks:
 -> Menu path: Basic Functions
 Assign tasks to agent
 Correct worklist
 Release worklist
 Correct and release worklist
For further information also see SAP Note 544703 - FAQ Mass change / Mass retirement
2) In addition check if the users are assigned to the work�ow-tasks in the basis-component (transaction PFTC).
 -> Menu path: Task type: TS - Standard task
 Task: corresponding task (e.g.8010) 00008010 CORR. AM WL 
 Name: Correct worklist
 or e.g.: Task type: TS - Standard task
 Task: 00008011 Rel.AA WList 
 Name: Release worklist
The relevant logic is, if the system �nds that the agent or user is de�ned, it will go straight to transaction code SO01. And the user can edit
the work list there.
For further information also see SAP Note 543138 - Mass change / mass retirement 
Related Documents
Asset Master Record Mass Changes 
Related SAP Notes/KBAs
127931 - Work�ow for Mass change in FI-AA from 40B on
322526 - Analysis for work�ow problems
75976 - Problems with mass changes / mass retirement
210897 - Substitution of time-dependent data
653093 - Error 5 W 141 with work queues
Legacy Data Transfer
This section covers all topics dealing with Asset Legacy Data Transfer. 
https://help.sap.com/docs/disclaimer
https://css.wdf.sap.corp/sap(bD1lbiZjPTAwMQ==)/bc/bsp/sno/ui_entry/entry.htm?iv_language=E&param=69765F6D6F64653D3030312669765F7361706E6F7465735F6B65793D303131303030333538373030303039303333343332303031267361702D6C616E67756167653D452669765F6C616E67756167653D45
https://me.sap.com/notes/544703
https://me.sap.com/notes/543138
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880169.html
https://me.sap.com/notes/127931
https://me.sap.com/notes/322526
https://me.sap.com/notes/75976
https://me.sap.com/notes/210897
https://me.sap.com/notes/653093
4/11/2024
65This is custom documentation. For more information, please visit the SAP Help Portal
Depreciation Areas in AS91 legacy data restricted to 50 Areas
 
Purpose
Clarify the restriction of product SAP ERP 6.0in Asset Accounting Transaction Code AS91, AS92 and AS93 in depreciation area when
transfer asset legacy data from a legacy system. 
Overview
Typically, depreciation is posted by depreciation key assigned and depreciation area for the particular asset class, and depreciation
areas are grouped together into a chart of depreciation, there are up to 99 depreciation areas you can define, however, only 50 of them
you can use for transfering asset legacy data function.
Business Scenario
Usually, user can create a new depreciation area by transaction code AFBN, and then assign depreciation key and link it to its asset
classes, it needs to be activated in transaction code OAYZ, like the example bellow:
There are 52 activated depreciation areas assigned to an asset class in this example (please note area 70 and 80), but in general
speaking you may rare assign 52 areas in a production system, this is only for the purpose of testing.
In transaction AS91, user would like to create legacy asset and using the depreciation area assigned, the table only shows 50 areas
the area 70 and area 80 missing as example bellow:
https://help.sap.com/docs/disclaimer
4/11/2024
66This is custom documentation. For more information, please visit the SAP Help Portal
 
Reason
the depreciation areas in transaction code AS91 are limited to a total number of 50; this is because the structure to store legacy values
has only 50 value fields to use. 
 
Conclusion 
If user assigns more than 50 depreciation areas in an asset class, and the legacy depreciation posted base on those settings, it will
omit some information due to miss the depreciation areas. The alternative option is to create it by using
BAPI_FIXEDASSET_OVRTAKE_CREATE.
Related SAP Notes/KBAs
KBA 2061518
SAP note 360399 AA860 when creating legacy assets
Takeover Date
What is the Takeover Date used for?
The takeover date is best described as a "transfer date". It represents, mostly from a depreciation perspective, what values are loaded from the
legacy system. 
It does not represent the actual data entry date. For instance, you can specify a takeover date of Dec 31, 2007 but load the data before or after that
date. However, the values that you load need to re�ect the values that were in effect as of Dec 31 2007. This typically only affects the depreciation
values.
There are two types of takeovers dates:
1. At the end of the last closed FY, or
2. During the FY. This is referred to as a Mid Year Data Takeover.
Customizing path: SPRO→ Asset Accounting → Asset Data Transfer → Parameters for Data Transfer → Date Speci�cations → Specify Transfer
Date/Last Closed Fiscal Year
Technical Information
What transaction codes can be used?
https://help.sap.com/docs/disclaimer
https://me.sap.com/notes/360399
4/11/2024
67This is custom documentation. For more information, please visit the SAP Help Portal
There are a series of dedicated transaction codes that can be used to create legacy �xed asset records. These are separate from the normal
transaction codes that are used as part of the daily processing of �xed assets although the screens are very similar. 
AS91 - Create legacy main asset
AS92 - Change legacy main asset
AS93 - Display legacy main asset
AS94 - Create legacy sub-asset
AS81 - Create legacy Group Asset
AS82 - Change legacy Group Asset
AS83 - Display legacy Group Asset
AS84 - Create legacy Group Sub-Asset
What programs can be used to process legacy assets?
There are two programs that can be utilized to automatically process legacy assets. They are RAALTD01 and RAALTD11.
The main difference between the two is that RAALTD01 uses a dialog process whereas RAALTD11 uses a direct table update approach. As a result,
RAALTD01 is not as fast but will respond in a more predictable way... what you experience while using transaction AS91 is what will happen with
RAALTD01. This is true for custom validations, defaults, input formats (i.e., date values), etc. 
There are also a series of BAPIs that can be utilized as well.
SAP also offer a method to load directly from Excel using transaction code AS100. Read the documentation for information on it's limitations and
how to utilize it.
What other steps are required?
A reconciliation to the General Ledger is required. Look at the transaction OASV to start with.
Depreciation
.
AW01N - The Effect on Planned Depreciation where 'Dep.below NBValue zero' is 'No'
(Depreciation Key)
Purpose
This is to demonstrate one example of the effect on Planned Depreciation where 'Dep.below NBValue zero' is 'No' (Depreciation Key).
Symptoms that may be observed could be:
No depreciation has previously been posted on the asset: yet depreciation is planned to be posted on the asset despite the asset value
being zero already at the time of �rst planned deprecation run. This is not expected.
As per the depreciation key con�guration the expectation is that no depreciation should have been planned and hence posted since the
netbook value was zero already.
The asset value has become zero before the depreciation run was executed.
Asset Shutdown
Purpose
The purpose of this page is to clarify the understanding of asset shutdown.
Steps
In order to use asset shutdown, two elements will be needed.
(1) �eld 'asset shutdown' (ANLZ-XSTIL) must be �agged in the asset master data (T-code : AS02)
https://help.sap.com/docs/disclaimer
4/11/2024
68This is custom documentation. For more information, please visit the SAP Help Portal
 
 (2) need to allow 'shutdown' in the depreciation key used for a speci�c depreciation area(T-code : AFAMA)
 In AFAMA, select your depreciation key, click on "Assignment of calculation method", double click on the �rst line, there you will see �eld 'shutdown'
(T090-XSTILL). The online documentation (F1 help) says : "Speci�es that depreciation will be reduced or stopped if there are speci�cations for
shutdown periods in the asset master record. This applies only to ordinary depreciation, even if depreciation is split into a portion based on units of
production."
https://help.sap.com/docs/disclaimer
4/11/2024
69This is custom documentation. For more information, please visit the SAP Help Portal
 
Related SAP Notes/KBAs
SAP Note 454989 - Shutdown not considered with depreciation
SAP Note 160093 - Period weighting and shutdown in depreciation
Asset Value Date and Ordinary Depreciation Start Date
Purpose
The purpose of this page is to clarify the relationship between asset value date and depreciation start date, and how they infulence the depreciation calculation.
Overview
The asset value date is the value date for Asset Accounting. It can derivate from the posting and document date and be in posting periods already
closed for Financial Accounting. However, the posting year and asset value date year must be the same.
Depreciation start date is the key date for the beginning of depreciation calculation. As a general rule, the system determines the depreciation start
date from the asset value date of the �rst acquisition posting. However, you can also manually enter a calendar date in the asset master record for
the start of depreciation. In that case, the system ignores the asset value date of the acquisition posting.
The asset value date can have a direct in�uence on the amount of depreciation. It determines the ordinary depreciation date with consideration of
transaction type on the �rst transaction happen in the asset. In the case of depreciation key use remaining useful life in multilevel method, if the
ordinary depreciation start date and asset value date was in the same �scal year, the ordinary depreciation start date will be considered and
depreciation calculation will be calculated from it. And if the ordinary depreciation start date is at the previous year of asset value date, the
depreciation calculation will take the asset value date as the begin of depreciation.
Related SAP Notes/KBAs
SAP note 165036 : Period control of subsequent periods
https://help.sap.com/docs/disclaimerhttps://me.sap.com/notes/454989
https://me.sap.com/notes/160093
https://me.sap.com/notes/165036
4/11/2024
70This is custom documentation. For more information, please visit the SAP Help Portal
BASE VALUE for a RETIREMENT with Old Engine calculation
How does the system calculate BASE VALUE for a RETIREMENT with Old Engine
calculation?
The aim of this document is to explain the internal logic of the system to calculate the base value when
performing a partial retirement, considering that the depreciation key uses Base Value (24 = Net Book value).
As you might be aware of, the old depreciation engine calculates the depreciation by transactions, instead of
by segments of time, which is the logic followed by the new engine. For further details about the differences
between the 2 engines, please review Note 965032.
In this detailed example, we will analyze how the system calculates the Base Value (24 = Net Book value) for the
transaction: partial retirement of previous year acquisitions (Transaction Type 210).
In the below picture, you can �nd the retirement transaction for the asset, as well as the necessary value
adjustment made (proportional values).
300,20€ / 72.363,90€ (APC) = 0,004132 = 0,4132%
Value Adjustment:
Previous years: 0,4132% * 62.609,94 = 258,76€
Current year: 0,4132% * 911,54 (Dep. Posted in period 1) = 3,76€
Total: 262,53€
 
When you double click in the planned depreciation you can see 2 lines:
https://help.sap.com/docs/disclaimer
https://me.sap.com/notes/965032
4/11/2024
71This is custom documentation. For more information, please visit the SAP Help Portal
1. Depreciation with the Net Book Value at the beginning of the year: According to the depreciation key, it
should not be a problem to understand that Base Value is 10.026,96€ = Net Book Value at FY Start.
2. Depreciation correspondent to Retirement Transaction. Why is the NBV 41,44-?
As the transaction type used is retirement from previous years (210), the Base Value (Net Book Value) for the
transaction is:
Retirement(-) + proportional depreciation values of previous years = Base Value (Net Book Value Retirement)
300,20- + 258,76 = 41.44-
Depreciation Calculation for Shorten Fiscal Year
Purpose
After implementing Shorten Fiscal Year in a carter Fiscal Year, you may expect different ordinary depreciation amount calculated in the Shorten
Fiscal Year and following Fiscal Years. This article will guide you how to realize your expected deprecation calculation results. .
Overview
For example, we have an asset using straight line depreciation method with 5 years useful life and acquisition 60,000 at the beginning of Fiscal Year
2013, After we implemented Shorten Fiscal Year in 2013, in which total periods are shorten from 12 to 9, In general, there are 3 results of
depreciation calculation we can have in the Shorten Fiscal Year and Following Fiscal Years. 
Result 1:
The ordinary depreciation in Shorten Fiscal Year 2013 is not reduced, even ordinary depreciation is calculated over 5 year useful life. 
Result 2: 
The ordinary depreciation in Shorten Fiscal Year 2013 is reduced and the reduced amount of ordinary depreciation in 2013 is planned in the �scal
year after 5 year useful life. 
https://help.sap.com/docs/disclaimer
4/11/2024
72This is custom documentation. For more information, please visit the SAP Help Portal
Result 3:
The ordinary depreciation is Shorten Fiscal Year 2013 is reduced and the reduced part of ordinary depreciation in 2013 smooth over left 4 useful
years.
Business Scenario
Owing to various business scenarios, you may want asset depreciated in different way after Shorten Fiscal Year implementation. We can con�gure
depreciation key accordingly to reach the results we expect. 
Approach to deal with above expectation for Shorten Fiscal Year implementation
Section 2 
For result 2 – Use T-cd: AFAMA to con�gure depreciation key and use T-cd: AFAMS to customize Multi-Level Methods like below
Section 3
Section 1 
for result 1 – Use T-cd: AFAMA to configure depreciation key and use T-cd: AFAMS to customize Multi-Level Methods l
 
https://help.sap.com/docs/disclaimer
4/11/2024
73This is custom documentation. For more information, please visit the SAP Help Portal
For result 3 – Use T-cd: AFAMA to con�gure depreciation key and use T-cd: AFAMS to customize Multi-Level Methods like below
 
Depreciation Calculation for Subsequent Acquisition (where �rst acquis. is in last month of FY
and period control is 11)
Purpose
The Purpose of this Wiki is to show the effect of a �rst posting to an asset in the last period of the �scal year and where period control is "Next
Month" (11). But also what it means in regards to depreciation calculation in the event that a subsequent posting is made in the next �scal year
(but technically is still the �rst year of acquisition).
Overview
The First Year of Acquisition is always referred to as the Year in which the Ordinary Depreciation Start Date is set. Hence in a scenario where you
post your �rst acquisition in the last period of a �scal year (FY) but with a period control of "Next Month", the Ordinary Depreciation Start Date is
actually 01.01.FY+1. Any subsequent acquisition posted within this '�rst year of acquisition' will have the same depreciation start date of 01.01.FY+1
(in this example scenario below it will be 01.01.2012).
 Postings done in any subsequent year from which depreciation start date is set, will have depreciation calculated from the asset value date.
First Acquisition Posting to an Asset: an example scenario
1) An Asset is acquired and capitalized on 08.12.2012 ( = Acquisition year 2012 012). Fiscal year variant is from January to December as per a
normal calendar year.
Fiscal Year 2012
https://help.sap.com/docs/disclaimer
4/11/2024
74This is custom documentation. For more information, please visit the SAP Help Portal
2) According to the assigned depreciation key XYXY the period control method has period control 11 (next month) assigned for acquisition (Acq)
and subsequent acquisition (Add).
What does this mean in real depreciation calculation terms for year 2012, 2013, 2014 in this example?
First acquisition: 08.12.2012 -> Since the period control for �rst acquisition is "Next month", the system assigns correctly the Depreciation Start
Date 01.01.2013. Hence no depreciation is calculated in �scal year 2012.
This is also re�ected in the Asset Explorer in transaction AW01N: the system only starts calculation of depreciation in 2013, and correctly starts on
01.01.2013.
Second (Subsequent) Acquisition Posting to the Asset (in �rst year of acquisition)
1) Let's assume that on 07.06.2013 a subsequent acquisition is posted to the asset.
Fiscal Year 2013 
 
2) The system correctly recalculates depreciation for all 12 periods. This is so since in the year of the depreciation start date every subsequent
posting is being calculated form the depreciation start date (and not from the asset value date).
https://help.sap.com/docs/disclaimer
4/11/2024
75This is custom documentation. For more information, please visit the SAP Help Portal
This is also explained in SAP Note 165036 - Period control of subsequent periods.
A note on the side: since the subsequent posting is done in period 6, the system will make a catch-up posting for the 5 previous periods (period 1-5)
and includes of course the amount for period 6, too. If you have set the indictor for "Smoothing" in transaction OAYR (Posting Rules) the system will
apply and distribute the depreciation amount evenly for each period 1-12.
Third (Subsequent) Acquisition Posting to the Asset (in subsequent year of depreciation start
date)
1) Another subsequent transaction is posted. This time it is in the subsequent year (2014) from which depreciation start date is set (2013): Asset
Value Date is 19.09.2014
Fiscal Year 2014
 
2) Now the system calculates depreciation from the Asset Value Date taking into account Period Control 11 ("NextMonth") for
subsequent acquisition (as seen under �eld "Add" in the period control method - see above screen shot): hence depreciation is calculated from
01.10.2014 as seen in next screen shot. No catch-up is calculated for period 1-9 anymore.
https://help.sap.com/docs/disclaimer
https://service.sap.com/sap/support/notes/165036
4/11/2024
76This is custom documentation. For more information, please visit the SAP Help Portal
 
 
Depreciation Smoothing and Catch Up
Purpose
Explain the concept of smoothing and catch up functionality when de�ning depreciation posting rules via transaction OAYR. This write up also
explains the calculation of depreciation under smoothing and catch up methods of depreciation.
Overview
Typically, depreciation is posted by the system at the end of each posting period. The frequency of depreciation posting is de�ned via transaction
OAYR (i.e, Monthly posting, Bi-Monthly posting , quarterly posting etc..). Once the frequency for posting depreciation is de�ned, the speci�cations
are valid at the company code and depreciation area level.
In the same customizing step, there is an important option called Smoothing. This option determines how the system behaves if settings like the
depreciation key or useful life have changed in the Asset during the �scal year, resulting in changes in the value of depreciation ( either high or low).
If the smoothing option is activated, the difference is distributed equally among the remaining posting periods of the current �scal year.
If this option is not activated, the entire difference is posted to the current period which is known as catch up.
Business Scenario
Depreciation relevant parameters like depreciation key or useful life of an asset is changed in the asset master or in customizing. This results in
change in the depreciation amount.
Example
An asset is acquired for $12,000 on 01/01/2012 and its useful life is 10 years. Hence the yearly depreciation will be $12,000/10 years = $1,200 per
year and the monthly depreciation will be $1,200/12 months = $100 per month.
Depreciation is posted for period 1 to period 6.
Now the useful life of the above asset is changed from 10 years to 5 years in the asset master record in the mid of the year i.e on 01/07/2012. Then,
the revised (new) depreciation will be $12,000/5 years = $2,400 per year and the monthly depreciation will be $2,400/12 months = $200 per
month.
This resulted in increase of Depreciation from $ 1200 to $2400 for the �scal year 2012.
Original Depreciation: $ 100/ Month
Revised Depreciation: $ 200/Month
What happens with the difference between the original and new depreciation in periods 1- 6?
https://help.sap.com/docs/disclaimer
4/11/2024
77This is custom documentation. For more information, please visit the SAP Help Portal
There are 2 possibilities: Smoothing or Catch-Up
Smoothing
The difference will be equally distributed over the remaining planned periods:
Period Original Depreciation New Depreciation Difference Amount to be Posted
1 Posted -100 200 
2 Posted -100 200 
3 Posted -100 200 
4 Posted -100 200 
5 Posted -100 200 
6 Posted -100 200 
7 Planned 200 100 300
8 Planned 200 100 300
9 Planned 200 100 300
10 Planned 200 100 300
11 Planned 200 100 300
12 Planned 200 100 300
Catch up
The whole difference will be posted in the next planned period:
Period Original Depreciation New Depreciation Difference Amount to be Posted
1 Posted -100 200 
2 Posted -100 200 
3 Posted -100 200 
4 Posted -100 200 
5 Posted -100 200 
6 Posted -100 200 
7 Planned 200 600 800
8 Planned 200 200
9 Planned 200 200
10 Planned 200 200
11 Planned 200 200
12 Planned 200 200
Conclusion
If the depreciation parameters are changed after the transaction and depreciation are posted. The depreciation posting run executed with the
smoothing method divides the difference between planned annual depreciation and the depreciation amount posted to date among the remaining
posting periods in equal shares.
If the catch up method is used, the depreciation posting run posts this difference as one total in the current posting period. 
https://help.sap.com/docs/disclaimer
4/11/2024
78This is custom documentation. For more information, please visit the SAP Help Portal
Help Link
Depreciation calculation with base method Unit-of-production
Purpose
This page was created with the purpose to illustrate how the system calculates depreciation when depreciation key is de�ned with base method
Unit-of-production.
Overview
SAP documentation regarding base method with base method Unit-of-production is explained in details in ʻUnit-of-Production Method of
Depreciation ’. However, here you can �nd an asset example, where depreciation calculation is illustrated.
Asset example:
Please check below images with asset example and values, in tab 'Planned values' (transaction code AW01N).
Figure 1
If you change from 'Planned values' tab to 'Posted values' tab (still in transaction code AW01N), you can check depreciation amount values that were
already posted or/and planned values to be posted per period. 
https://help.sap.com/docs/disclaimer
http://help.sap.com/erp2005_ehp_05/helpdata/EN/4f/71dbdb448011d189f00000e81ddfac/frameset.htm
http://help.sap.com/saphelp_47x200/helpdata/en/4f/71de6f448011d189f00000e81ddfac/frameset.htm
4/11/2024
79This is custom documentation. For more information, please visit the SAP Help Portal
Figure 2
Why there are values only for period 01 to 05?
Because, the number of units for this asset is updated only for these periods in transaction code AO25. Check �gure below: 
https://help.sap.com/docs/disclaimer
4/11/2024
80This is custom documentation. For more information, please visit the SAP Help Portal
Figure 3
How is the Depreciation Calculation to periods 01 to 05? 
Depreciation with base method Unit-of-production is calculated as the following logic:
Acquisition value (net book value) / Total output (remaining output) * Period output
Based in this logic explained in SAP documentation, asset example with acquisition value of 4.098,35 (�gure 1) and values updated in transaction
code AO25 (�gure3), system calculates depreciation for the periods (�gure 2) as below:
Depreciation calculation to Period 1
4.098,35 / 998.400 * 20.000
 = 82,10 
Depreciation calculation to Period 2
(4.098,35 - 82,10) / 978.400 * 15.000 
 = 61,57 
Depreciation calculation to Period 3
[4.098,35 – (82,10 + 61,57)] / 963.400 * 10.000 
= 3.954,68 / 963.400 * 10.000 
= 41,05 
Depreciation calculation to Period 4
[4.098,35 – (82,10 + 61,57 + 41,05)] / 953.400 * 5.000 
= 3.913,63 / 953.400 * 5.000 
= 20,53 
https://help.sap.com/docs/disclaimer
4/11/2024
81This is custom documentation. For more information, please visit the SAP Help Portal
Depreciation calculation to Period 5
[4.098,35 – (82,10 + 61,57 + 41,05 + 20,53)] / 953.400 * 1.000 
= 3.893,10 / 948.400 * 1.000 
= 4,10 
System calculation for depreciation in the year (area 01):
Total depreciation for the year is calculated by the sum of values from all period in this year. In this example, total depreciation in 2012 is the sum of
depreciation values calculated for periods 01 to 05. The total depreciation calculated in the year 2012 is the following:
= Period 1 + Period 2 + Period 3 + Period 4 + Period 5
= 82,10 + 61,57 + 41,05 + 20,53 + 4,10
= 209,35
Related Content 
Related Documents 
Unit-of-Production Method of Depreciation
Interest Calculation for Capital Leased Asset
Purpose
This page describes how SAP system calculates interest for capital leased asset.
Overview
SAP note 458641 describes about how ʻPresent Value’ is calculated for leased asset. Consequently you may also want to know how the interest is
�gured out in each period. Below is an example for capital leased asset with payment in advance.
Leased Asset example:
Here is the master data of leased asset. The �scalyear variant is April – March. Present Value 5.820.723 is calculated out based on the formula of
SAP Note 458641.
https://help.sap.com/docs/disclaimer
http://help.sap.com/saphelp_47x200/helpdata/en/4f/71de6f448011d189f00000e81ddfac/frameset.htm
4/11/2024
82This is custom documentation. For more information, please visit the SAP Help Portal
If you go to the tab ʻPosted Values’ of AW01N, we will see the payment liability and interest are calculated for each period. 
How is the periodic interest calculated for each period? 
 
https://help.sap.com/docs/disclaimer
4/11/2024
83This is custom documentation. For more information, please visit the SAP Help Portal
Here is the formula for periodic interest calculation:
 
Periodic Interest = Periodic Lease Payment – Net Lease Cost
Parameters used in the calculation of present value / interest:
 Total number of lease payments (n) : 60
 Number of periods in �scal year (m) : 12
 Lease payment cycle (r) : 1
 Annual interest rate in percentage (i) : 1.2%
 Payment amount (g) : 100,000
 Period interest factor (q) = 1 + (i / 100) * (r / m )
 = 1 + (1.2 / 100) * (1 / 12)
 = 1.001
Based on the present value calculation formula in SAP Note 458641, the present value in each period could be �gured out as below: 
Present value before �rst payment :
N0= g * (q ^n - 1)/(q ^n *(q - 1))
 = 100,000 * (1.001^60 - 1)/(1.001^60*(1.001 - 1))
 = 100,000 * 0.06180471314696464039972579223441 / 0.00106180471314696464039972579223
 = 5,820,723
Present value before second payment: 
N1 = g * (q ^n - 1)/(q ^n *(q - 1))
 = 100,000 * (1.001^59 - 1)/(1.001^59*(1.001 - 1))
 = 100,000 * 0.06074396917778685354617961262179 / 0.00106074396917778685354617961262
 = 5,726,544
Payment Liability (Cost of leased asset) in period 1:
= Present value at the beginning of period 1 – Present value at the end of period 1
= N0 – N1 
= 5,820,723 - 5,726,544 
= 94179
Interest in period 1: 
= Monthly payment amount – Payment Liability in period 1 
= 100,000 – 94179 
= 5,821
 
Related Documents 
 
SAP Note 458641
 
https://help.sap.com/docs/disclaimer
http://help.sap.com/saphelp_47x200/helpdata/en/4f/71de6f448011d189f00000e81ddfac/frameset.htm
https://me.sap.com/notes/458641/E
4/11/2024
84This is custom documentation. For more information, please visit the SAP Help Portal
Methods to update table ANLBZW
Purpose
This document will show you how you can update table ANLBZW in case of base value key 28 is used in a depreciation key 
Overview
If based value 28 is used in a depreciation key, base value percentage is required in asset depreciation calculation in order to determine accurate
base value. Based on different business scenario, you can use below ways to update the base value percentage into table ANLBZW accordingly.
Case 1 
Single asset or few assets uses depreciation key with based value key 28
Solution: 
To use transaction code S_ALR_87009145 to update base value percentage to single asset or small number assets. .
Case 2 
Transfer the base value percentage of sending asset to target asset 
Solution: 
You need to follow below steps
1, To activate the copy function of �eld 'Scrap Value %' in transfer variant via IMG -> Financial Accounting -> Asset Accounting -> Transactions ->
Intercompany Asset Transfers -> Automatic Intercompany Asset Transfers -> De�ne Transfer Variants -> Specify Transfer of Fields (for New Asset in
Target CoCd) -> Depreciation Areas -> Field transfer or �eld groups -> Field group 23 (base value %)
2, To create new asset as target asset in transfer process
Case 3 
Base valu key 28 is assigned in the second phase of a depreciation key 
Solution:
To use BAdi FAA_DC_CUSTOMER to develop own logic to determine depreciation key changeover condition and calculate base value percentage at
the start of second phase of depreiciation key, then update the base value percentage into table ANLBZW.
Case 4 
Migration of ANLBZW for numbers of legacy assets
Solution:
To use batch input tools to update ANLBZW for mass process in background.
Related SAP Notes/KBAs 
 SAP Note 1117955 
 SAP Note 1057539
 
Period control introduction(t-code: AFAMP) - depreciation key setting
Purpose
The purpose of this page is to clarify the understanding of period control assigning to depreciation key.
Overview
Introduction of standard period control rule; Meaning of each �eld.
Field for different transactions
https://help.sap.com/docs/disclaimer
https://websmp130.sap-ag.de/sap/support/notes/1117955
https://websmp130.sap-ag.de/sap/support/notes/1057539
4/11/2024
85This is custom documentation. For more information, please visit the SAP Help Portal
 Period control rule is one of an important part in a depreciation key. You can maintain period control rules for below different kind of transactions
separately.
1. Acquisition
2. Subsequent acquisitions(acquisitions in the following year)
3. Retirement
4. Transfer
5. Revaluation(impairment)
6. Investment support
7. Unplanned depreciation
8. Write up to Reserves
Period control can be created and edited in T-code AFAMP.
Detail settings for each �eld
There are many kinds of period control provided in standard system. Here follwows some of the rules that used often.
01: Period start date 
 If you use 01 for one kind of transaction, the posting will be considered from the start date of the posting period.
02: Up to mid-period at period start date
 The posting happens in 1st half of the period is considered from current period start date, and the posting happens in 2nd half of
the period is considered from the start of next period.
06: At the start of the year 
 The posting is considered from the start of posting year, no matter what the posting date is. Please also refer to �scal year
setting(T-code OB29).
07: At mid-year 
 The posting is considered from the middle of the posting year, no matter what the posting date is. Please also refer to �scal year
setting(T-code OB29).
11: Next month 
 Using 11 means the posting will not be considered until the start of next period. 
Tips: You may need to reconsider using 06/07 for retirement, so that the retirement does not happen before acquisition when they
are in a same year.
The periods listed above can be checked in details in transaction code: OAVH
Tips
Some tips related to 1.Acquisition and 2. Subsequent acquisitions(acquisitions in the following year):
Rule 2 Subsequent acquisitions is for additional posting in year after depreciation start year, the additional acquisition postings happens in
depreciation start year does not consider this, it depreciation in depreciation start year will always be calculated based on depreciation start date.
Sample: �scal year is K4 ( calendar year)
1st acquisition posting ( capitalization): 01.07.2016 
Depreciation start date: 01.07.2016
2nd acquisition posting 01.08.2016 <<< Depreciation is calculated from depreciation start date, regardless of period control setting. 
3rd acquisition posting 01.11.2016 <<< Depreciation is calculated from depreciation start date, regardless of period control setting. 
4th acquisition posting 01.02.2017 <<< The system considers period control for Subsequent acquisitions(acquisitions in the following
year)
Some tips related to period control for 5/6/7/8:
https://help.sap.com/docs/disclaimer
4/11/2024
86This is custom documentation. For more information, please visit the SAP Help Portal
In new depreciation engine (EA-FIN ON), period control for revaluation / investment support / unplanned depreciation / write-upscan be separately
customized.
However, old transaction type groups could not recognise these new period control �elds, if you want to use these new period controls, please use
transaction types in new transaction type group.
New transaction type group are as below:
Name for the transaction type group
-----------------------------------------------------------------------
53 Allocation of Support (Pergrp Inv)
76 Write-Up Transfer of Reserves (Pergrp D)
78 Write-Up Unplanned Depreciation (Pergrp D)
A1 Gross Reval. w/ Dep. (Pergrp Revaluat.)
A2 Gross Reval. w/ Dep. (Pergrp Revaluat.)
A4 Unplanned Deprec. (Pergrp Unplanned Dep)
A5 Unplanned Dep. CYA(Pergrp Unplanned Dep)
For example, transaction type 892 is provided in standard system, it belongs to old transaction type group 82, so it could not recognise the period
setting for �eld 5. Revaluation(impairment).
If you need to use new period control group to control revaluation transaction separately, you need to create a new transaction type in group A2 and
use this transaction type to post revaluation.
Please refer to note 1138166 for more details.
Related Content
Related SAP Notes/KBAs
SAP Note 1634613- Unplanned depreciation in the current year (new depreciation engine)
SAP Note 1138166 - Enhanced period controls for new depreciation calculation
Shift Factor usage in depreciation calculation
Purpose
 
This document describes how Shift Factor works for depreciation calculation. 
Overview
In order to consider Shift Factor in depreciation calculation, We need to set Shift Factor in asset master data, specify ʻVariable depreciation portion’
in depreciation area and customize ʻMultiple Shift’ in depreciation key accordingly.
Section 1 – Set all relevant settings to make depreciation calculation considering shift factor.
1, Use T-Code: AS02 to set Shift Factor in asset master data 
https://help.sap.com/docs/disclaimer
https://launchpad.support.sap.com/#/notes/1138166
https://me.sap.com/notes/1634613/E
https://me.sap.com/notes/1138166
4/11/2024
87This is custom documentation. For more information, please visit the SAP Help Portal
2, Use T-Code: AS02 and double click on depreciation area to specify ʻVariable depreciation portion’ as below:
3, Use T-Code: AFAMA to customize ʻMultiple Shift’ in depreciation key
https://help.sap.com/docs/disclaimer
4/11/2024
88This is custom documentation. For more information, please visit the SAP Help Portal
 
Section 2 – Change of depreciation after shift factor setting
1, Before shift factor settings with depreciation term – UL=10, Straight line method, APC = 1,000,000 at year start 
 
 
2, After shift factor settings
https://help.sap.com/docs/disclaimer
4/11/2024
89This is custom documentation. For more information, please visit the SAP Help Portal
Note:
The percentage is calculated by below formula: 
percentage = Original percentage X Amount Factor
= 0,1 X (1 - Variable depreciation portion + Variable depreciation portion X Shift Factor)
= 0,1 X (1 – 3 + 3 X 1,5)
= 0,1 X 2,5
= 0,25
 
Start Depreciation One Month After Capitalization of Asset
Purpose
The Purpose of this wiki is to demonstrate the con�guration steps involved in creating a Depreciation key which can be used to calculate
depreciation one month after the Capitalization of Asset.
There are many different country speci�c regulations, particularly for asset acquisitions, that govern how the depreciation start date can be
determined from the date of acquisition of an asset.
Overview
Depreciation is a Periodic and a permanent decrease in the value of a Fixed asset over its economic life period because of its usage and associated
wear and tear.
SAP supports two kinds of Depreciation:
1. Planned Depreciation: Calculated automatically through depreciation keys that contain the value settings and calculation rules for arriving at
the depreciation amount.
2. Unplanned Depreciation: This is a manual reduction of APC values and transfer to reserves.
The entire framework of Depreciation calculation is based on depreciation keys that are used in the depreciation area.
A depreciation key also known as valuation key contains the necessary parameters for valuating an asset in the depreciation area. It contains the
calculation methods and control parameters for controlling ordinary depreciation, special depreciation, Scrap value and cut off value.
https://help.sap.com/docs/disclaimer
4/11/2024
90This is custom documentation. For more information, please visit the SAP Help Portal
Business Scenario
An asset is acquired by a company on 01 April 2012.This asset is capitalized on 01 April 2012.However as per the Country speci�c legislation; the
depreciation should not be calculated for the month of April. But the depreciation should be calculated for the month of May starting 01 May 2012.
Solution
To enable a company to calculate depreciation on asset from the month following the month of capitalization, we can use standard SAP period
control key 11.
Period Control is a function and a part of depreciation key that determines the start or the end of depreciation calculation at the time of a �xed
asset acquisition or retirement. 
Con�guration
Step 1: Create a Period Control method.
Menu Path: Financial Accounting -- Asset Accounting -- Depreciation -- Valuation Methods -- Depreciation Key -- Calculation Methods -- Maintain
Period Control Method
Transaction Code: AFAMP
Create a new period control method that consist of period control key “11” and save the customizing. 
Step 2: Con�gure a depreciation key. This Depreciation key needs to be created with period control method which is created in Step 1.
Menu Path: Financial Accounting -- Asset Accounting -- Depreciation -- Valuation Methods -- Depreciation Key -- Maintain Depreciation Key.
Transaction Code: AFAMA
Once the depreciation key is created it’s usually in an “Inactive” status. We would have to activate the depreciation key by clicking on the activate
button.
Step 3: Assign the depreciation key to the asset class.
Menu path: Financial Accounting -- Asset Accounting -- Valuation -- Determine Depreciation Areas in the Asset Class.
Transaction Code: OAYZ
Once we have the depreciation key created as per our requirement in the system, we would have to assign this to the Asset Class.
Generally, the assets in an asset class use the same depreciation terms (depreciation key, useful life). Therefore, you do not have to maintain the
depreciation terms in the asset master record. Instead, they can be default values from the asset class. 
Reference
SAP Help 
SAP Note
1143988
Transaction Processing
This section covers all topics for asset transactions such as acquisitions, retirements, and transfers.
AUC settlement when one depreciation area exists in sender asset but not in target asset
Purpose
The purpose of this page is to clarify the understanding of the system logic and requirements in relation to AUC settlement when AUC asset
(sender) manages less depreciation area than �nal asset (receiver).
st st
st
https://help.sap.com/docs/disclaimer
http://help.sap.com/saphelp_erp60_sp/helpdata/en/4f/71fd71448011d189f00000e81ddfac/frameset.htm
4/11/2024
91This is custom documentation. For more information, please visit the SAP Help Portal
Overview
For AUC settlement to �nal asset, it’s not always true that both assets manage exactly the same depreciation areas. For example, if the �nal asset is
from a Japanese company code and manages area 10 which is Japanese tax report area, but unfortunately there’s no such a depreciation area in
sender AUC asset. Here in this Wiki page you can �nd a way to handle this.
For new settlement
Please check customizing below from IMG path(t-code: SPRO).
https://help.sap.com/docs/disclaimer
4/11/2024
92This is custom documentation. For more information, please visit the SAP Help Portal
Here 'transfer method' of4 should be used in order to transfer value also into depreciation area 10.
As background, depreciation area 10 takes value from area 01 as customized in t-code: OABC.
After above setting, you can test for system behavior.
Sender asset only manages depreciation area 01, but in receiver asset it has both area 01 and 10.
Sender asset:
https://help.sap.com/docs/disclaimer
4/11/2024
93This is custom documentation. For more information, please visit the SAP Help Portal
Receiver Asset:
T-code: AIAB for settlement rule.
T-code: AIBU for settlement.
In receiver asset, depreciation area 10 also shows values.
https://help.sap.com/docs/disclaimer
4/11/2024
94This is custom documentation. For more information, please visit the SAP Help Portal
Related Content
Related Documents
Settlement of Asset Under Construction using transaction codes AIAB and AIBU
Related SAP Notes/KBAs
SAP Note 300273: Settlmt AuC: various errors due to transfer variant
AUC settlement when one depreciation area exists in the sender asset but not in the target asset
Purpose
The purpose of this page is to clarify the understanding of the system logic and requirements in relation to AUC settlement when AUC asset
(sender) manages less depreciation area than �nal asset (receiver).
Overview
For AUC settlement to �nal asset, it’s not always true that both assets manage exactly the same depreciation areas. For example, if the �nal asset is
from a Japanese company code and manages area 10 which is Japanese tax report area, but unfortunately there’s no such a depreciation area in
sender AUC asset. Here in this Wiki page you can �nd a way to handle this.
For new settlement
Please check customizing from IMG path(t-code: SPRO).
https://help.sap.com/docs/disclaimer
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361878677.html
https://me.sap.com/notes/300273
4/11/2024
95This is custom documentation. For more information, please visit the SAP Help Portal
 
 
Here 'transfer method' of 4 should be used in order to transfer value also into depreciation area 10.
https://help.sap.com/docs/disclaimer
4/11/2024
96This is custom documentation. For more information, please visit the SAP Help Portal
As background, depreciation area 10 takes value from area 01 as customized in t-code: OABC.
After above setting, you can test for system behavior.
In test sample below, the sender asset only manages depreciation area 01. In receiver asset it has both depreciation area 01 and 10.
Sender asset:
Receiver Asset:
https://help.sap.com/docs/disclaimer
4/11/2024
97This is custom documentation. For more information, please visit the SAP Help Portal
T-cd: AIAB settlement rule.
T-cd: AIBU settlement.
After settlement, check receiver asset and �nding in area 10 value is updated correctly.
https://help.sap.com/docs/disclaimer
4/11/2024
98This is custom documentation. For more information, please visit the SAP Help Portal
For existing settlement 
For existing settlement, you will need to reverse existing settlement re-settle it again after changing customizing of transfer variant as above.
Related Content
Related Documents
Settlement of Asset Under Construction using transaction codes AIAB and AIBU
Related SAP Notes/KBAs
SAP Note 300273: Settlmt AuC: various errors due to transfer variant
AW01N - Effect on Planned Depreciation where Dep.below NBValue zero is No (Example)
 
Purpose
This document helps to understand one of many different examples of the effect that the setting "Dep.below NBValue zero" = "No" can have in
planned depreciation as seen in the Asset Explorer when dispaying the asset (Tranasction AW01N) after the asset is transferred or retired.
Overview
The purpose of thispate is to clarify the understanding of the system logic and requirements in relation to depreciation adjustments posted when
the Netbook Value reaches Zero, yet outstanding depreciation is planned and still needs to be posted, however the setting in the depreciation key
does not allow NBV zero. The system will instead post a positive value adjustment which you don't expect maybe.
Here are the Symptoms:
No depreciation has previously been posted on the asset: yet depreciation is planned to be posted on the asset despite the asset value being
zero already at the time of �rst planned deprecation run. This is not expected.
As per the depreciation key con�guration the expectation is that no depreciation should have been planned and hence posted since the
netbook value was zero already.
The asset value has become zero before the depreciation run was executed.
This should be an executive summary of the content and argument being made in the document. Basically a summary (not repeat) of the
information you are explaining.
Section 1
This is the main body of your WIKI Page where you talk through the system logic or behavior you are explaining. Use pictures to emphasize the points
you are trying to make or to illustrate the transactions/selection screens/reports etc.
https://help.sap.com/docs/disclaimer
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361878677.html
https://me.sap.com/notes/300273
4/11/2024
99This is custom documentation. For more information, please visit the SAP Help Portal
1. First posting is a negative acquisition (e.g. via settlement) to the asset: note that in our example the settlement had no proportional
depreciation posted, hence no positive depreciation is being calculated to balance the negative proportional depreciation amount.
2. In the following period several other positive acquiring transfers are posted to the asset.
3. Until �nally in the same period equally as many retirements transfers are posted until the netbook value (NBV) reaches zero.
Note: For all these acquiring and retiring transfers the system calculated proportional depreciation. Hence, the planned depreciation amount
corresponds to all the proportional values received on the asset from all the transfers (1,236,042.44- / previous year) + (182,500.85- / current year).
The total of these proportional depreciation values is 1,418,543.29- therefore.
AW01N_Transactions 1.JPG
[....several more acquiring transfers are being posted in the same period as well as eventually many additional retirement transfers in the same
period bring the NBV to 0.00....]
AW01N_Transactions 1a.JPG
[....etc....]
AW01N_Transactions 2_NBV zero.JPG
The Question is: what depreciation posting or value adjustment can you expect the system to perform in October (in our case this is period 7) when
running Depreciation (RAPOST2000 / Transaction AFAB) in case of this scenario? Should there be any depreciation posted at all? How will the
system post and why?
Cause
The Answer is: this depends on the settings in the depreciation key, as in our case, the settings in the base method have a bearing. In order to
understand the system behaviour in our example in the 'Resolution' part in regards to the posting for (positive) depreciation (and value adjustment),
it is indeed very important to take into account the con�guration settings in the depreciation key: the system behaviour is due to the effect that the
settings in the Base method have where 'deprecation below NBValue zero' is not allowed (= 'No') and therefore a positive depreciation is calculated
to make NBV = 0,00 !
In any case, the system has to post a value adjustment for the planned depreciation, which in our example is done when the depreciation program
RAPOST2000 is executed at the end of period 7 (October 2013). Since the depreciation run has not been started before the asset reached NBV
zero, the system will therefore post the positive depreciation in the same period in which the NBV reached 0.00 for this asset and really, IN ORDER
TO to make NBV = 0.00!
F1 Help: see also for further documentation on this indicator using the F1 Help when in the customizing transaction: "Calculation of depreciation
below net book value zero"
Resolution
Note: please refer customer to the Wiki link attachedin case of similar enquiry.
1. Go to customizing transaction AFAMA.
2. Check the maintenance of the base method in the depreciation key which is assigned to the asset.
In this example scenario, when the base method has the setting "Depr.below NBValue zero = No" the system will have to post positive depreciation
to make the NBV 0.00. If the base method would allow depreciation below netbook value zero, then the asset would not reach netbook value 0.00 in
this example scenario (and therefore, if negative NBV was allowed in transaction OADB, the result would be a NBV of 1,418,543.29- in that case as
depreciation run would post 1,418,543.29-). This is not an error, this is expected system behaviour according to the postings on this asset in
combination with the depreciation key settings for the base method. The system will automatically plan and post a positive depreciation in this case
once the depreciation run is executed (transaction AFABN) and in order to be able to deactivate the asset upon all retirement postings lead to a
NBV 0.00.
P.S.: AW01N: Period 8 and 9 are missing (see above) because last depreciation has been posted in period 9 (see table TABA below) and this asset had
nothing to post in these periods after being deactivated. When period 10 will be run the planned line with amount 0,00 for period 10 as seen in
AW01N above will also “disappear” on this asset display. This is normal system behaviour.
See Also
https://help.sap.com/docs/disclaimer
4/11/2024
100This is custom documentation. For more information, please visit the SAP Help Portal
Menu paths in Customizing IMG, transaction SPRO:
Financial Accounting - Asset Accounting - Depreciation - Valuation Methods - Depreciation Key - Calculation Methods - De�ne Base Methods
Financial Accounting - Asset Accounting - Depreciation - Valuation Methods - Depreciation Key - Maintain Depreciation Key
Analysis of Error AA698
Purpose
This document should help you to �nd the root cause of Error AA698. From an Asset Accounting point of view the most common causes for Error
AA698 in various FI-AA transactions are the following: 
________________ 
Cause 1
*********************** 
In most cases the error message AA698 is caused by inconsistencies in table T082AVIEWB for view 0 (internal view generated automatically) where
there is no authorization for one or several depreciation area(s). 
The error is often raised when you go into transaction AS91/AS92 but also in transaction AW01N for example. 
Please check which depreciation areas you have activated in table ANLB and ANLC and then go to table T082AVIEWB and change the authority to
2. 
SE16: table T082AVIEWB 
FIAA_VIEW AFAPL AFABER AUTHORITY 
00 TRAN ** 0 ->>> should be 2 
This correction report is called "RACORR_VIEW0_SET" and it will set �eld “Authority” for View 0 (legacy takeover view) from 0 to 2. The report is
attached in SAP note 900767. This report must be implemented manually via transaction SE38, it is valid also for releases higher than 600. 
 
Once the problem is corrected and depending on your system release and support package you should ensure that SAP note 853754 is in your
system to avoid any inconsistencies of that kind in future.
________________ 
Cause 2
*********************** 
In a few cases is has been noticed that this error is caused due to newly created or deactivated depreciation areas which are not present in both
tables ANLC and ANLB. 
In order to resolve this error both tables ANLC and ANLB will have to match and show the same depreciation areas. 
For example:
Table ANLB has depreciation area XX that table ANLC does not have – this could be a depreciation area that was created with
RAFABNEW. 
This depreciation area will have to be added to ANLC. To manually install the depreciation area is a matter for consulting since there are tables which
could be affected (ANLB, ANLC, ANEP, ANEA, COEPBR). 
Please contact your SAP Consultant for the manual correction of the relevant
tables. 
________________ 
https://help.sap.com/docs/disclaimer
https://me.sap.com/notes/900676
4/11/2024
101This is custom documentation. For more information, please visit the SAP Help Portal
Cause 3 
*********************** 
Check the asset in ANLB and ANLC for any inconsistency between the two �elds: 
>> ANLB-LGJAN is not equal to ANLC-GJAHR : 
In this case you need to run report RACORR96 to correct the inconsistency. 
Run RACORR96 in TEST mode for your company code and it should pick up any asset in error. 
Go to transaction SE38: 
-> enter report name: RACORR96 
-> execute 
P_BUKRS "your company code" 
P_TEST X 
-> execute
"Comparison of ANLB-LGJAN and ANLC-GJAHR" 
Here you should see the asset number and the company code which will need corrections.
After running RACORR96 in REAL mode ANLB-LGJAN and ANLC-GJAHR show the same �scal year. 
 ________________ 
Cause 4 
*********************** 
The reason for the error is that the actual system date is for example in 2010 and the last opened �scal year in FI-AA for your company code is
e.g.2009. You can check this in transaction SE16 (T093C-LGJAHR = e.g. 2009). This situation leads to error AA698. 
Start the �scal year change report (RAJAWE00) to open �scal year 2010 and to avoid the error. 
Note: for error AA698not to appear you should close the �scal years for which ANLC records do not exist. 
________________ 
Cause 5 (in case of investment measure involvement)
***********************
It may be that there are missing entries in table COEPBR. It could be that certain depreciation areas have line items in FI-AA table ANEP but which
are not updated in CO table COEPBR.
For this you can go to table COEPBR, enter �eld KOKRS (CO Area) and OBJN (Object Number). 
Tip: in table PRPS enter WBS / Project number in �eld POSID, execute. Then check value in �eld OBJN, which you need in order to view table
COEPBR.
Compare the line items for each depreciation area in CO table COEPBR with the line items for each depreciation area in FI-AA table
ANEP. 
Please refer to SAP note 317806 and carefully read.
Run the correction report ZZAFANEW2 for the relevant asset and company code to update table COEPBR with the missing entries. 
________________ 
https://help.sap.com/docs/disclaimer
4/11/2024
102This is custom documentation. For more information, please visit the SAP Help Portal
Cause 6
*********************** 
The expired useful life in the asset master is not updated correctly.
In the Asset Master (AS02) tab ʻDepreciation Areas’ you notice that no expired useful life is shown although there should be. When you want to
return to another tab, you get AA698.
Check tables ANLB and ANLC for the affected asset. These tables should have the same �scal year as the current �scal year in T093C. If this
is not the case, then you may have to run �scal year change program RAJAWE00 or if the last closed �scal year in T093B shows a greater
year than ANLB and ANLC for the affected asset, then you may have to forward the values to the current �scal year via correction report
RACORR55.
 You will �nd these reports on the SAP Service Marketplace https://websmp203.sap-ag.de/�aa-faq -> in 'Frequently Asked Questions' 
Just in case you have differences in values in closed �scal years for the asset also, then run correction report RACORR110 before you run
RACORR55. It can be found via the same link above.
1. Report RACORR110 will align the values in tables ANEP and ANLC
2. Report RACORR55 carries forward the values in closed �scal year to the next �scal year. 
When the asset has the same current �scal year in ANLB and ANLC like in T093C, next step is to adjust the expired useful
life in the erroneous asset .
Go to AS02 tab ʻDepreciation Areas’: possibly there is now a value in �eld ʻExpired Useful Life’ but it may still be the incorrect expired useful
life. Although you might not get error AA698 in AS02 anymore, you most likely will still get it when you go to transaction AW01N: 
The reason for this is that in ANLC �elds NDABJ and NDABP are not updated with the correct expired useful life yet. 
Correct the expired useful life in the Asset Master via AS02 manually
 Go to tab ʻDepreciation Areas’ and remove the value in �eld ʻExpired Useful Life’ and hit ʻEnter’.
 The system will automatically calculate the correct expired useful life and �ll the �elds NDABJ and NDABP in ANLC once you SAVE the changes.
The expired useful life in the Asset Master for the affected asset is now correct. You may need to recalculate the asset (in AS02).
Tables ANLB and ANLC are now aligned with the same current �scal year as in table T093C and the error AA698 is resolved.
******************************************************************************************************************************************* 
NOTE:
Always test a correction report in a TEST SYSTEM �rst if the same problem also occurs in any other system but the Productive system.
Always run a correction report in TEST MODE �rst. Then check the report output, and only then run the report in REAL MODE when you are
satis�ed with the test result. Only when the report is started in REAL MODE will the affected tables be updated.
SAP Notes:
1531737 Error AA698 - Possible causes and resolutions
2430005 - Requested issue on Asset Accounting answered by SAP Community WIKI
In addition, some SAP notes are available that resolve known system errors or bugs causing error AA698 in various transactions. You should always
check and search for SAP notes in the SAP Service Marketplace for your Release and Support Package using search term “AA698” or AA 698”.
Analysis of Error message AA632
Purpose
The purpose of this page is to clarify the understanding of the system logic and solution in relation to the error message "AA632 — Line item causes
scrap value of XX.XX to be violated"
Overview
The message AA632 is a very frequent error when doing asset posting(acquisition: ABZON, transfer: ABUMN, retirement: ABAVN, unplanned
depreciation: ABAA... and so on). In a lot of case, it is hard to understand why this error happens.
https://help.sap.com/docs/disclaimer
https://websmp203.sap-ag.de/fiaa-faq
https://me.sap.com/notes/1531737
https://me.sap.com/notes/2430005
4/11/2024
103This is custom documentation. For more information, please visit the SAP Help Portal
Cause 1:
System bug. 
Solution: search SAP notes with the key word AA632 and the support package of your system(SAP_APPL and EA-APPL)
Cause 2:
Memo value have been maintained in OAYI, the net book value for the problem asset is is below the memo value.
Solution: Set the �ag "Negative values allowed" for the problem asset.
Cause 3:
You have set scrap value in the asset master data , the net book value for the problem asset is is below the scrap value.
Solution: delete scrap or adjust the amount which you want to post for the problem asset.
Cause 4:
You have set "cut-off value key" in the depreciation key, the net book value for the problem asset is is below the cut-off value.
Solution: adjust the amount which you want to post for the problem asset, or adjust the setting for the depreciation key.
Cause 5:
Rounding difference calculation.
Solution: adjust the rounding setting by t-cd: OAYO.
 
 
Asset Accounting - Period Control
Purpose
The purpose of this page is to clarify the understanding of the system logic and requirements about period control
 Overview
The period control is relevant to determine the depreciation start and end date for asset transactions.
You can set a period control for:
Acquisitions
Subsequent acquisitions/post-capitalization (Note 92260 relevant in old engine)
Intracompany transfers
Retirements
If new engine is active enhanced (note 1138166) period controls are available for:
Revaluation
Investment support
Unplanned depreciation, or
Write-ups
How is the period control determined?
This is the main body of your WIKI Page where you talk through the system logic or behavior you are explaining. Use pictures to emphasize the points
you are trying to make or to illustrate the transactions/selection screens/reports etc.
https://help.sap.com/docs/disclaimer
4/11/2024
104This is custom documentation. For more information, please visit the SAP Help Portal
1) Transaction Type 
To know to which group this transaction type belongs(i.e.acquistion, retirement, acquisition, revaluation) you have to check the following tables:
TABW and TABWG
2) Depreciation Key
https://help.sap.com/docs/disclaimer
4/11/2024
105This is custom documentation. For more information, please visit the SAP Help Portal
To know which period control you are using you can check transaction AFAMA and AFAMP.
AFAMA
AFAMP
https://help.sap.com/docs/disclaimer
4/11/2024
106This is custom documentation. For more information, please visit the SAP Help Portal
How the depreciation start andend date for the asset transactions are determined?
1) CALENDAR ASSIGMENT
For the calendar assigment 
2) FISCAL YEAR VARIANT + PERIOD CONTROL COMBINATION
Types of Fiscal Year Variant
· Standard Calendar Year Jan 1 - Dec 31 (K4) 
· Standard Fiscal Year Jul 1 - Jun 30 (K6) 
· Year Dependent Fiscal Year April - March 28 (L4) 
· 24 Periods year dependant Jan 1 - Dec 31 (24)
For “year dependant” variants it is necessary to make sure that all relevant calendar years exist in transaction OB29 (table T009B) .
FY variant
https://help.sap.com/docs/disclaimer
4/11/2024
107This is custom documentation. For more information, please visit the SAP Help Portal
n Fiscal Year Variant at Company Level ( T001).
n Fiscal Year Variant in Asset Accounting (T093C)
n Fiscal Year Variant in Depreciation Areas (T093B)
https://help.sap.com/docs/disclaimer
4/11/2024
108This is custom documentation. For more information, please visit the SAP Help Portal
IMPORTANT : The posting period for the depreciation run is always from the G/L variant on company code level 
Not possible to assign different �scal year variants to depreciation areas that post to the general ledger (error AA455).
What �scal year variant to consider?
Fiscal year variant check is done considering below sequence : 
 1 -Fiscal Year Variant In Depreciation Areas exists (T093B) ? IF NOTst
https://help.sap.com/docs/disclaimer
4/11/2024
109This is custom documentation. For more information, please visit the SAP Help Portal
2 Fiscal Year Variant in FI-AA for the company code exists(T093C) ? IF NOT
3 Fiscal Year Variant At Company Level FI-GL ( T001) -> It’s used
Once the FY variant is determined, we have to make sure that the calendar assignment for the relevant FY variant / period control exists.
nd
rd
https://help.sap.com/docs/disclaimer
4/11/2024
110This is custom documentation. For more information, please visit the SAP Help Portal
If not, the missing period controls must be generated (transaction OA84).
https://help.sap.com/docs/disclaimer
4/11/2024
111This is custom documentation. For more information, please visit the SAP Help Portal
Related Content
Related SAP Notes/KBAs 
SAP Note 988238: FAQ New depreciation calculation
Asset Acquisition via F110
Purpose
This document describes how to acquire asset via transaction code F110 (Down payment to vendor).
Overview
Follow below steps to acquire asset while post down payment to vendor via transaction code F100.
Asset Acquisition with transaction code F110
https://help.sap.com/docs/disclaimer
https://service.sap.com/sap/support/notes/988238
4/11/2024
112This is custom documentation. For more information, please visit the SAP Help Portal
1, To use T-cd:AS01 to create asset master data XXXX 
 
 
2, To use transaction code F-47 to create down payment request with Trg.sp.G/L ind. ʻM’ and payment method U to Vendor VENDER8801 and then
assign asset XXXX to the payment request as account assignment
https://help.sap.com/docs/disclaimer
4/11/2024
113This is custom documentation. For more information, please visit the SAP Help Portal
 
 
3, To execute transaction code F110 with below parameters 
https://help.sap.com/docs/disclaimer
4/11/2024
114This is custom documentation. For more information, please visit the SAP Help Portal
4, To check asset acquisition amount and acquisition document via T-cd:AW01N
https://help.sap.com/docs/disclaimer
4/11/2024
115This is custom documentation. For more information, please visit the SAP Help Portal
Related Content
Related Documents
 
Asset capitalization (or asset posting) by MIRO or MIGO
Purpose
The purpose of this page is to clarify the understanding of the system logic and requirements in
relation to asset values posted by purchase orders (PO). 
https://help.sap.com/docs/disclaimer
4/11/2024
116This is custom documentation. For more information, please visit the SAP Help Portal
Overview
Whenever a purchase order (PO) with category ʻA’ (assets) is created, it is possible chose if it will
update values in the asset when you post the ʻGoods Receipt’ (by transaction code MIGO) or
during the Invoice Receipt (by transaction code MIRO). The update work�ow is illustrated bellow,
when you choose if Purchase Orders (PO) will be (or not) valuated during the Goods receipts
posting.
 
 Figure 1: Goods receipt logic regarding assets.
How you chose when values will be posted in assets from a PO?
You can choose it during Purchase Orders (PO) creation by transaction code ME21N, tab delivery
in the Item. If box ʻGR Non-Valuated’ is not checked, than values will be Valuated and updated in
asset after you post Goods Receipt (MIGO). Example:
Figure 2: PO - Delivery tab with ʻGR Non-Valuated’ not checked.
https://help.sap.com/docs/disclaimer
4/11/2024
117This is custom documentation. For more information, please visit the SAP Help Portal
Figure 3: Values updated in asset by MIGO.
Otherwise, if you want only update values in asset after you post the Invoice receipt, than box
ʻGR Non-Valuated’ should be �agged during Purchase Orders (PO) creation. In this case, values
will be updated in the asset only after you post the Invoice (MIRO). Example:
Figure 4: PO - Delivery tab with ʻGR Non-Valuated’ checked.
https://help.sap.com/docs/disclaimer
4/11/2024
118This is custom documentation. For more information, please visit the SAP Help Portal
Figure 5: Values updated in asset by MIRO.
With the NEW ASSET ACCOUNTING (in EHP7):
Posting an integrated asset acquisition (via MM or FI) will always split the transaction in several
documents by the system:
- an operational document posted to all ledger groups; it debits the “technical clearing account
for integrated asset acquisition” (new account) and credits the vendor account (accounts
payable)
- and for each valuation a valuating document restricted to the corresponding ledger group; it
debits the asset account and credits the “technical clearing account for integrated asset
acquisition”
This “technical clearing account for integrated asset acquisition” can not be posted manually,
only the system posts to the account. We need to ensure that the “technical clearing account for
integrated asset acquisition” always balance to zero per ledger and account assignment.
Related Content
Related Documents
Entering Account Assignments
Related SAP Notes/ KBA
SAP Note 518368 : FAQ: Valuation for the purchase order
Basics Postings
https://help.sap.com/docs/disclaimer
http://help.sap.com/erp2005_ehp_06/helpdata/en/43/d00a0ce3f63ac3e10000000a422035/content.htm?frameset=/en/79/d98d38f3c49164e10000009b38f842/frameset.htm
https://service.sap.com/sap/support/notes/518368
4/11/2024
119This is custom documentation. For more information, please visit the SAP Help Portal
Basics on postings and the main database tables in asset accounting
Author: D021502
Tables For Postings
Postings in Asset Accounting create or modi�es entries in the following tables:
ANEK (Document Header Asset Posting)
ANEP (Asset Line Items)
ANEA (Proportional Values: mostly for retirements and retiring transfers)
ANLC (asset values summarized on area and year level)
ANLB (only for the very �rst posting on the asset; table is updated)
ANLA (aquisition date, deactivation date, origin)
Fields of Posting Tables
The most important �elds are explained in the following slides:
The following �elds belong to the tables ANEP, ANEA, ANEK:
BUKRS: company code
ANLN1: asset main number
ANLN2: asset sub number
GJAHR: �scal year
LNRAN: number of the asset line item
Table ANEK
The following important�elds belong to table ANEK:
CPUDT, CPUTM: System date of posting
TCODE: Transaction code, which was used for posting
ANLU1, ANLU2: Asset number of acquired/retired asset for transfer or intercompany transfers
BELNR: document number (FI or reference number)
AWTYP, AWORG, AWSYS: �elds which are the unique link to the corresponding FI document.
Table ANEP
Table ANEP consists of the following important �elds:
AFABE: depreciation area
BELNR: document number (or reference number)
BWASL: transaction type
ANBTR: APC amount of the posting
NAFAB, SAFAB, ZINSB: ordinary, special depreciation, interest on transaction (not valid anymore for the new depreciation engine!)
XANTW: indicator, that proportional values exists (XANTW = X, if there are entries in table ANEA)
LNSAN: line item number of the reversal document
AUGLN: number of the clearing line items (is set by the AuC settlement)
Table ANEA
Table ANEA is �lled if proportional values/value adjustments have to be considered, e.g. for retirements and transfers.
In table ANEP �eld XANTW is set to X
The following important �elds are part of table ANEA:
https://help.sap.com/docs/disclaimer
4/11/2024
120This is custom documentation. For more information, please visit the SAP Help Portal
AFABE: depreciation area
NAFAV, SAFAV, AAFAV: proportional value adjustments of previous �scal years
NAFAL, SAFAL, AAFAL: proportional value adjustments of current �scal year
Table ANLC
In table ANLC the sum of all asset values are listed per asset, depreciation area and �scal year :
BUKRS: company code
ANLN1, ANLN2 : asset number
GJAHR: �scal year
AFABE: depreciation area
KANSW: accumulated APC values
KNAFA, KSAFA, KAAFA: accumulated ordinary, special, unplanned depreciation
Further �elds of table ANLC per company code, asset, depreciation area, �scal year:
NAFAP, SAFAP, AAFAP: Planned ordinary, special, unplanned depreciation of the current �scal year
NAFAG, SAFAG, AAFAG: Posted ordinary, special, unplanned depreciation of the current �scal year
ANSWL: sum of all the changes of the APC value
NAFAV, SAFAV, AAFAV: Proportional depreciation of previous years
NAFAL, SAFAL, AAFAL: Proportional depreciation of the current �scal year
Example
Example: Posting of an acquisition of 1200 Euro for asset 4711 in company code 1000 on 1.1.2008.
A FI document is created that looks like:
BSCHL means posting key.Posting key 70 ist for debit postings to an asset reconciliation account.Posting key 50 is for credit postings to for
example clearing accounts.
The acquisition affects table ANEK in the following way:
An asset line item with the line item number 00001 is created, if it is the �rst posting to the asset. In all other cases a line item with the number of
the last line item + 1 is taken, regardless if the already existing line items are created in previous �scal years. This means that the line item number
is independent of the �scal year.
The transaction code of the posting is stored in �eld TCODE (e.g. ABZON or FB01)
The time and the date when the document was created is stored in the �elds CPUDT and CPUTM.
The acquisition affects table ANEK in the following way:
For postings triggered by FI �eld BELNR contains the FI document number, for postings with ABZON the internal asset document number is stored,
for example 0000000012.
The �elds AWORG, AWSYS and AWTYP combined with the document number BELNR are the link to the FI document.There is the following
relation:BKPF-AWKEY = ANEK-BELNR + ANEK-AWORGBKPF-AWSYS = ANEK-AWSYS BKPF-AWTYP = ANEK-AWTYPAWORG is for example BUKRS +
GJAHR (FI applications)
Example: Table ANEK
Effects on table ANEK:
https://help.sap.com/docs/disclaimer
4/11/2024
121This is custom documentation. For more information, please visit the SAP Help Portal
Example: Table ANEP
The acquisition affects table ANEP in the following way:
An asset line item with the line item number 00001 is created if it is the �rst posting to the asset.
Per depreciation area one entry is created. In our example there is only one depreciation area for the asset.
The document number is stored in �eld ANEK-BELNR.
The transaction type of the posting (in our example 100 for an acquisition) is stored in �eld BWASL.
The posting amount of 1200 Euro is stored in �eld ANBTR.
The depreciation value (for example 10 % of the APC amount for 10 years useful life) is stored in NAFAB. This �eld might be changed if the
depreciation parameters are changed.
Example table ANEP
Effects on table ANEP:
Old Depreciation Engine -120,00 / New Depreciation Engine 0,00
Example table ANLC
The posting affects table ANLC in the following way:
The acquisition of 1200,00 Euro provokes a change of the APC value (ANSWL) of 1200,00 Euro.
With for example 10% of depreciation per year considering a useful life of 10 years the planned depreciation for a year (NAFAP) results in 120,00
Euro.
Effects on table ANLC:
Example 2 (Reversal)
Example: Reversal of the acquisition of asset 4711 in company code 1000 on 1.1.2008.The following FI document is created:
https://help.sap.com/docs/disclaimer
4/11/2024
122This is custom documentation. For more information, please visit the SAP Help Portal
BSCHL is the posting key.
Posting key 75 is for credit postings to the asset reconciliation account (KTANSW).
Posting key 40 is for debit postings to for example a clearing account.
The reversal of the acquistion affects table ANEK in the following way:
An asset line item with number 00002 is created, because the last asset line item of this asset was 00001.
The transaction code of the posting is stored in �eld TCODE like for the acquisition, in our example AB08 or FB08.
The time and the date, when the document was created is stored in the �elds CPUDT and CPUTM.
Field BELNR is �lled like for the acquistion posting, for example 0000000013.
The �elds AWORG, AWSYS and AWTYP are �lled corresponding to the original acquisition posting.
Effects on table ANEK:
The reversal of the acquisition affects table ANEP in the following way:
An asset line item with number 00002 is created.
Per depreciation area one entry is created. In our example there is onle one depreciation area for the asset.The document number BELNR
corresponds to �eld ANEK-BELNR.
The transaction type of the posting (in our example 100 is stored for the acquisition) is stored in �eld BWASL.
The amount of the original posting is posted with reversed sign. In our example -1200 Euro is stored in �eld ANBTR.
The amount of the depreciation (10% of the amount for 10 years useful life in the example) is posted with reversed sign in �eld NAFAB.
Effects of the reversal in table ANEP:
In order to mark a line item as reversed, the number of the line item of the original posting is �lled in �eld LNSAN of the reversal posting and vice
versus.
Reversed line items are no more considered by the depreciation recalculation, e.g. the depreciation of the transaction NAFAB of a line item is no
more changed for line items with non initial values in �eld LNSAN.Apart from this, the APC amounts of reversed line items are no more considered in
rebuilding the value ANSWL.
Effects on table ANEP:
Example 2
The posting effects table ANLC in the following way:
The reversal of the acquisition changes the APC value with the value -1200,00 Euro.
The planned depreciation (NAFAP) for the whole �scal year results in 0 Euro with the reversal.
Example 2 (Reversal)
Effects on table ANLC:
https://help.sap.com/docs/disclaimer
4/11/2024
123This is custom documentation. For more information, please visit the SAP Help Portal
Example 3
1. Acquisition posting on 1.7.2007 (previous year) to asset 4712 in company code 1000 with the amount of 2400 Euro. The depreciation is
calculated with the APC value as base value and the method is depreciation according to the useful life.
2. Posting of a complete retirement on 1.4.2000.
3. Reversal of the complete retirement.
4. Posting of a partial retirement with the amount of 600 Euro.
Example 3: Acquisition
Acquisition to asset4712 in company code 1000 on 1.7.2007. A FI document is created which looks like:
Depreciation on the transaction:
With period rule 01 pro rata depreciation is calculated as of 1.7. (i.e. for half of the year).
With 10 years useful life the depreciation is 240 Euro per year. For a half year the depreciation is 120 Euro.
1. Acquisition to asset 4712 in company code
Example 3: Fiscal Year Change
Fiscal year change (RAJAWE00 or automatically when a posting is done for previous years)
Effects on table ANLC: A new entry for the new �scal year 2008 is created.
The cumulated values are calculated as:
previous �scal year = PY
KANSW = KANSW(PY) + ANSWL(PY)
KNAFA = KNAFA (PY) + NAFAP(PY) + NAFAL(PY) + NAFAV(PY)
https://help.sap.com/docs/disclaimer
4/11/2024
124This is custom documentation. For more information, please visit the SAP Help Portal
Example 3: Complete Retirement
Complete Retirement
For a retirement, value adjustments have to be considered.
Proportional values or value adjustments for a retirement:
A retirement means, that an asset is retired with its net book value.But the system stores only the APC value on the database.
The netbook value of asset 4712 on 1.4. is calculated as the APC value minus the depreciation that was considered up to 1.4. This depreciation
is called value adjustments.
The system makes differences between the value adjustments of previous �scal years and of those of the current �scal year: 
NAFAV : Value adjustments of the previous �scal years.
NAFAL : Value adjustments of the current �scal year.
Both �elds are also called „Proportional Values".
Example 3: Complete Retirement
Value Adjustments for a complete retirement of asset 4712
Value adjustments of previous �scal years NAFAV:The whole depreciation of previous �scal years is - 120 Euro.
Value adjustment of the current �scal year NAFAL: On 1.4. the retirement is posted. Thus 1/4 of the depreciation planned for the whole year is
depreciated considering period rule pro rata. E.g. NAFAL is 1/4 * (- 240) Euro = - 60 Euro.The sum of the value adjustments is thus - 180 Euro.
For the complete retirement without revenue the FI documentlooks like:
Thus we get 3 lines:
https://help.sap.com/docs/disclaimer
4/11/2024
125This is custom documentation. For more information, please visit the SAP Help Portal
1. Credit posting to the APC account (KTANSW) with the APC value.
2. Debit posting to the value adjustment account KTNAFB with the value of the value adjustments.
3. Debit posting to the account Loss of Scrapping.
A new entry is created in table ANEP for �scal year 2008
with the line item number (LNRAN) = 00002 (last LNRAN + 1)
transaction type BWASL for retirement 200
retiring APC amount -2400 Euro
ordinary depreciation on the transaction NAFABSince the system always plans the depreciation for a whole �scal year, regardless if an asset is
retired in the current �scal year, the depreciation has to be corrected. Retirement on 1.4., e.g. 3/4 of the deprecation of the whole �scal year has to
be corrected: 3/4 * (- 240) = - 180.
The indicator for proportional values XANTW = X, because there exist entries in table ANEA. This is always valid for retirements and for the retiring
part of a transfer.
Please note: The amount of NAFAB does normally not correspond to the amount of the value adjustments. This is only accidentally!
Effects on table ANLC
Effects on table ANEA
Example 3: Reversal of the Retirement
The reversal of the complete retirement results in the following FI document:
https://help.sap.com/docs/disclaimer
4/11/2024
126This is custom documentation. For more information, please visit the SAP Help Portal
The reversal document consists naturally of the same values than the orignal documents but uses reversed signs.
Therefore, the reversed debit/credit posting keys are used.
A new entry for the reversal posting in table ANEP is created for the �scal year 2008. The number of the line item is 00003 (last LNRAN + 1).
The amounts are the same as for the original document, but the signs are reversed. Since the document is reversed, the �eld LNSAN is �lled with
the line item number of LNRAN of the original document, thus with 00002.
All other �elds, especially �eld XANTW = X is taken from the original document. Only �elds for the posting periods or for a date need not to
correspond to the orignal document.
Effects on table ANEP
Effects on table ANLC
The APC value of the current �scal year (ANSWL and the proportional values (NAFAV, NAFAL) get to 0. NAFAP gets back the orignal value.
A second entry for a new LNRAN is created. The proportional value are the same like for the original documents but with reversed signs.
https://help.sap.com/docs/disclaimer
4/11/2024
127This is custom documentation. For more information, please visit the SAP Help Portal
Example 3: Partial Retirement
4. Partial retirement with the amount of 1200 Euro on 1.4.2008.Since only half of the total sum is retired, the value adjustments are also half of the
complete retirement.
NAFAV = 60
NAFAL = 30
For a partial retirement of n % the value adjustments are calculated as NAFAV (part. retiremt) = NAFAV(compl. retiremt) * n % and NAFAL
accordingly.The same is valid for the depreciation on the transaction NAFAB.
Also, the retiring APC amount is calculated internally as the percentage of the whole amount.
The partial retirement results in the following FI document:
The �elds ANSWL, NAFAV, NAFAL are �lled again.
https://help.sap.com/docs/disclaimer
4/11/2024
128This is custom documentation. For more information, please visit the SAP Help Portal
A new entry for LNRAN 00004 is created with half of the proportional values of the complete retirement.
Retirement with Revenue
Retirement with RevenueAsset 4713 with
a cumulated APC value of 2400 Euro,
cumulated ordinary depreciation of 120 Euro and
10% depreciation, e.g. the planned depreciation for the whole �scal year will be 240 Euro.
Retirement Gain/Retirement Loss
Dependent on the revenue amount entered , the FI document contains an additional line in the document for the Retirement Gain/Retirement Loss.
Retirement Gain:
The revenue is higher than the net book value of the asset when retired. Example: Asset 4713,
net book value = APC - value adjustments = 2400 - 180 = 2220.
The revenue of 3220 Euro results in a Retirement Gain of 1000 Euro. The retirment gain is posted to the account KTMEHR.
Retirement Loss:
The revenue is lower than the net book value.
Example: Asset 4713, revenue of 1220 Euro.
The revenue of 1220 Euro results in a Retirement Loss of 1000 Euro. Retirement Loss is posted to the account KTMIND.
Retirement Gain/Retirement Loss
No retirment gain/loss:
The revenue corresponds exactly to the net book value of the asset when retired.
Example: Asset 4713, revenue is 2220 Euro.
There is neither retirement gain nor loss.
The FI document consists of only three lines for this situation.
Complete retirement with revenue of 3220 Euro results in the following FI document:
Complete retirment with the revenue of 1220 Euro results in th following FI document:
https://help.sap.com/docs/disclaimer
4/11/2024
129This is custom documentation. For more information, please visit the SAP Help Portal
Complete retirement with the revenue of 2220 Euro results in the following FI document:
New Acquisition and Acquisition of Previous Fiscal Years
New Acquisition and Acquisition of Previous Fiscal Years when retiring
The transaction type indicates, if new acquisition of previous �scal year acquisitions are retired.
When posting a complete retirement new acquisition as well as acquisition of previous �scal years is retired, because after a complete retirement
APC and net book value has to be zero.Therefore, two entries in table ANEP and ANEA will be created for an asset with acquisition of previous �scal
years and with new acquisition. Two table entries belong then to one transaction.
Basics of Asset Accounting - Asset Acquisition
Purpose
The purpose of this page is to clarifythe understanding of the system logic and requirements in relation to the asset acquisitions through
transaction code ABZON.
Overview
The following paragraphs and pictures will describe an EXAMPLE in steps of an asset acquisition and the functionality of the main �elds and buttons.
Asset Acquisition with transaction code ABZON
To acquire an asset go to navigation: SAP Easy Access -> SAP Menu -> Accounting -> Financial accounting -> Fixed Asset -> Posting -> Acquisition ->
External Acquisition -> Acquis. w/Autom. Offsetting Entry.
https://help.sap.com/docs/disclaimer
4/11/2024
130This is custom documentation. For more information, please visit the SAP Help Portal
Alternatively: transaction code ABZON 
1) Fill out Field Existing asset with an asset number already created. (Press enter)
2) Fill out Fields Document Date, Posting date and Asset Values Date.
3) Fill out Field Amount Posted with any amount.
https://help.sap.com/docs/disclaimer
4/11/2024
131This is custom documentation. For more information, please visit the SAP Help Portal
4) If you press Line items button, you will see the values generated for each depreciation area
5) If you press Simulate button you will see the accounts that will be credited and debited. In this case 11000 and 199990.
6) Double clicking on each line item you can see all details of these transactions.
https://help.sap.com/docs/disclaimer
4/11/2024
132This is custom documentation. For more information, please visit the SAP Help Portal
 
Related Content
Related Documents
http://help.sap.com/saphelp_erp60_sp/helpdata/en/4f/71e695448011d189f00000e81ddfac/frameset.htm
Basics of Asset Accounting - Asset Retirement
Purpose
The purpose of this page is to clarify the understanding of the system logic and requirements in relation to the asset retirement through transaction
code ABAVN
Overview
The following paragraphs and pictures will describe an EXAMPLE in steps of an asset retirement and the functionality of the main �elds and buttons.
Asset Retirement with transaction code ABAVN
To retire an asset go to Navigation: SAP Easy Access -> SAP Menu -> Accounting -> Financial accounting -> Fixed Asset -> Posting -> Retirement ->
Asset Retirement by Scrapping
https://help.sap.com/docs/disclaimer
http://help.sap.com/saphelp_erp60_sp/helpdata/en/4f/71e695448011d189f00000e81ddfac/frameset.htm
4/11/2024
133This is custom documentation. For more information, please visit the SAP Help Portal
Alternatively: Transaction code ABAVN
 1) Fill out Field Asset with your asset number already created and with postings (press enter)
2) Fill out Fields Document Date, Posting date and Asset Values (it cannot be a date prior to this asset capitalization date.
https://help.sap.com/docs/disclaimer
4/11/2024
134This is custom documentation. For more information, please visit the SAP Help Portal
3) If you press Line items , you will see the values generated for each depreciation area.
4) If you press Simulate button you will see the accounts that will be credited and debited. In this case 11000, 11010 and 200010.
https://help.sap.com/docs/disclaimer
4/11/2024
135This is custom documentation. For more information, please visit the SAP Help Portal
5) Double clicking on each line item you can see all details of these transactions.
https://help.sap.com/docs/disclaimer
4/11/2024
136This is custom documentation. For more information, please visit the SAP Help Portal
 
Basics of Asset Accounting - Asset Transfer
Purpose
The purpose of this page is to clarify the understanding of the system logic and requirements in relation to the asset transfer through transaction
code ABUMN.
Overview
The following paragraphs and screen shots will describe an EXAMPLE in steps of an asset transfer and the functionality of the main �elds and
buttons.
Asset Transfer with transaction code ABUMN
To transfer an asset go to Navigation: SAP Easy Access -> SAP Menu -> Accounting -> Financial accounting -> Fixed Asset -> Posting -> Transfer ->
Transfer within Company code
https://help.sap.com/docs/disclaimer
4/11/2024
137This is custom documentation. For more information, please visit the SAP Help Portal
Alternatively: Transaction code ABUMN.
1) Fill out Field Asset with an asset number already created (press enter)
2) Fill out Fields Document Date, Posting date and Asset Values Date .
3) In transfer to select the option New Asset and �ll out Asset Class with ZSAO and Cost Center with ZSAO.
https://help.sap.com/docs/disclaimer
4/11/2024
138This is custom documentation. For more information, please visit the SAP Help Portal
4) If you press Line items, you will see the values generated for each depreciation area. Also, you can see both assets that will be posted after the
transfer, in this case 2036 and 2037.
5) If you press Simulate button you will see the accounts that will be credited and debited. In this case 11000 and 11010. 
https://help.sap.com/docs/disclaimer
4/11/2024
139This is custom documentation. For more information, please visit the SAP Help Portal
How to update a Transfer Variant
Purpose
The purpose of this content is to help SAP users correct their transfer variants as described in SAP notes below:
-> SAP Note327088:De�nition of the delivered transfer variants
-> SAP Note 300273: Settlmt AuC: various errors due to transfer variant
Overview
During some Asset Transfer or Assets Under Construction (AuC) / projects / orders settlements to Fixed Assets, system may display error
messages or incorrect values in the Fixed Asset depreciation areas due to some incorrect or incomplete transfer variant de�nition. SAP provides
some notes with transfer variants standard de�nition and recommendations.
The following section and pictures will describe an example in steps of transfer variant where the transfer method is updated.
How to do the update
Example:
To update transfer variant 4 as per SAP note 327088 , go to transaction code SPRO (IMG) and double click 'De�ne Transfer Variant' as indicated
below:
https://help.sap.com/docs/disclaimer
https://service.sap..com/sap/support/notes/327088
https://service.sap.com/sap/support/notes/300273
https://service.sap.com/sap/support/notes/327088
4/11/2024
140This is custom documentation. For more information, please visit the SAP Help Portal
Select Transfer Variant that you want to change by double click:
Correct the transfer method and transaction type as it is indicated in the SAP Note327088 and SAP Note 300273.
https://help.sap.com/docs/disclaimer
https://service.sap.com/sap/support/notes/327088
https://service.sap.com/sap/support/notes/300273
4/11/2024
141This is custom documentation. For more information, please visit the SAP Help Portal
Related Content
Related SAP Notes/ KBA
SAP Note 327088: De�nition of the delivered transfer variants
SAP Note 300273: Settlmt AuC: various errors due to transfer variant
Basics of Asset Accounting - Asset Transfer (Intercompany)
Purpose
The purpose of this page is to clarify the understanding of the system logic and requirements in relation to Intercompany asset transfer through
transaction code ABT1N.
Overview
The following paragraphs and screen shots will describe an EXAMPLE in steps of an Intercompany asset transfer and the functionality of the main
�elds and buttons.
Asset Transfer with transaction code ABT1N
To transfer an asset go to Navigation: SAP Easy Access -> SAP Menu -> Accounting -> Financial accounting -> Fixed Asset -> Posting -> Transfer ->
Intercompany Asset Transfer
Alternatively: Transaction code ABT1N. 
 
 
1) Fill out Field Company Code and Sending Asset (press enter).
2) Fill out Fields Document Date, Posting date and Asset Values Date.
3) In topic Interco. transfer to select the option New Asset and �ll out the receiving Company Code. 
https://help.sap.com/docs/disclaimer
https://service.sap.com/sap/support/notes/327088
https://service.sap.com/sap/support/notes/300273
4/11/2024
142This is custom documentation.For more information, please visit the SAP Help Portal
 
 
4) Review parameters in the tab “Additional Details”
 *Regarding transfer variant, review page How to update a 'Transfer variant' ?
5) If it is not a complete transfer from sending asset to the receiving asset, set parameters in tab “Partial Transfer”.
6) Click over Line Items to open popup with depreciation areas values.
7) Double click over sending asset number to check values in sending asset depreciation areas.
8) Double click over receiving asset number to check values in receiving asset depreciation areas. 
https://help.sap.com/docs/disclaimer
http://wiki.sdn.sap.com/wiki/x/HBNaDw
4/11/2024
143This is custom documentation. For more information, please visit the SAP Help Portal
 
9) Press “Simulation” button to simulate transfer document creation. 
https://help.sap.com/docs/disclaimer
4/11/2024
144This is custom documentation. For more information, please visit the SAP Help Portal
10) Press “Additional account assignment” button to complete missing information (if necessary). 
11) If it is everything ok after that, you may execute the transfer by saving it. Otherwise, you may repeat steps above and simulate it different
transfer parameters.
Related Content
Related Documents
https://help.sap.com/docs/disclaimer
4/11/2024
145This is custom documentation. For more information, please visit the SAP Help Portal
How to update a Transfer Variant
Related Notes
SAP Note 444797 : Separ.SET-/GET parametrs for trnsfr and intracompany trnsfr
SAP Note 310346 : ABT1 De�ning transfer variant gross
SAP Note 339528 : Transfer gross: depreciation to target asset
Basics of Asset Accounting - Asset Transfer Partial (Intercompany)
Purpose
This document helps to understand how to post a partial intercompany transfer and how it affects the values on the sending as well as the
receiving asset. It shows how the calculation and distribution of values is affecting both assets based on previous and current year acquisition. 
Overview
Depending on the values initially posted on the source asset, the system calculates and takes the transferring amount from the source asset based
on the indicated percentage or indicated amount entered in the transactino ABT1N as well as based on the indicator whether the amount is to be
retired from the previous year or current year acquired amount. The distribution therefore is not as may be extected equally from both prior and
current year acquisition - instead it is either or and so it is transferred to the target asset. This document will illustrate an example of both, a
partial intercompany transfer of prior-year acquisition as well as current-year acquisition.
IMPORTANT INFORMATION to note: in this example the current �scal year is 2014, the last closed �scal year is 2012.
Create Source Asset with prior-year acquisition and current year acquisition in Transaction AS01
and e.g. ABZON respectively: display view in Transaction AW01N
1) Acquisition (2.600,00 EUR) posted in previous �scal year:
2) Acquisition (1.500,00 EUR) posted in current �scal year:
https://help.sap.com/docs/disclaimer
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361878303.html
http://service.sap.com/sap/support/notes/444797
http://service.sap.com/sap/support/notes/310346
http://service.sap.com/sap/support/notes/339528
4/11/2024
146This is custom documentation. For more information, please visit the SAP Help Portal
A) Post a Partial Transfer (e.g. 50 percent) from the Source Asset from prior-year acquisition to
the Target Asset with Transaction ABT1N: display view in Transaction AW01N
1) Enter source asset and company code A and target asset and company code B in transaction ABT1N (Intercompany transfer): asset value date is
in the current year.
2) Enter the percentage rate (or amount) and indicate from which APC you want to partially transfer: in this case we want to transfer acquisition
acquired in the previous (prior) year.
https://help.sap.com/docs/disclaimer
4/11/2024
147This is custom documentation. For more information, please visit the SAP Help Portal
3) Simulate and review line items, and then save the transaction.
4) Dispaly the values in the source and target asset.
https://help.sap.com/docs/disclaimer
4/11/2024
148This is custom documentation. For more information, please visit the SAP Help Portal
B) Post a Partial Transfer (e.g. 50 percent) from the Source Asset from current-year acquisition
to the Target Asset with Transaction ABT1N: display view in Transaction AW01N
1) Enter source asset and company code A and target asset and company code B in transaction ABT1N (Intercompany transfer): asset value date is
in the current year.
https://help.sap.com/docs/disclaimer
4/11/2024
149This is custom documentation. For more information, please visit the SAP Help Portal
2) Enter the percentage rate (or amount) and indicate from which APC you want to partially transfer: in this case we want to transfer acquisition
acquired in the current year.
3) Simulate and review line items, and then save the transaction.
https://help.sap.com/docs/disclaimer
4/11/2024
150This is custom documentation. For more information, please visit the SAP Help Portal
4) Dispaly the values in the source and target asset.
https://help.sap.com/docs/disclaimer
4/11/2024
151This is custom documentation. For more information, please visit the SAP Help Portal
 
 
 
 
 
Basics of Asset Accounting - Post-Capitalization of an Asset and How Depreciation is Calculated
and Distributed
Purpose
This document helps to understand how to post-capitalize an asset and how post-capitalization affects the values on the asset. It shows how the
calculation and distribution of depreciation is affecting the asset. This is a simple example using a straight line depreciation key in the asset and
which has a useful life of 10 years. 
Overview
For a full documentation on what a post-capitalization of an asset is, please refer for detailed information in the SAP Help Portal under following link:
http://help.sap.com/erp2005_ehp_06/helpdata/EN/4f/71e835448011d189f00000e81ddfac/frameset.htm
Depending on the depreciation key settings in the post-capitalized asset, the system calculates the full depreciation and distributes it over the
remaining useful life or beyond even. This document will show how to create an asset for post-capitalization, how to post value to the post-
capitalized asset and how the system calculates and distributes the depreciation value over the useful life and/or beyond.
The depreciation key settings determines how the system behaviour may vary in each case: in the example asset shown below you can observe a
different distribution of the depreciation value in depreciation area 01 and 02, depending on the depreciation key assigned in each area. Area 01 has
standard depreciation key LINR (Str.-line frm rem.life to book value zero) assigned whereas Area 02 has standard depreciation key LINA (Str.-line
frm acq.value pro rata w/curb) assigned. Since these are standard depreciation keys, you can check their full customizing in transaction AFAMA.
Note, this document does not go into the customizing of the used depreciation keys LINR and LINA. However, the different system behaviour in
regards to how depreciation is calculated over the useful life and/or after the useful life is depending on the customizing of the depreciation key
itself. For example the settings in the depreciation key determines whether or not depreciation is planned and posted after planned useful life end.
 IMPORTANT INFORMATION to note: in this example the current �scal year is 2013, the last closed �scal year is 2011.
https://help.sap.com/docs/disclaimer
http://help.sap.com/erp2005_ehp_06/helpdata/EN/4f/71e835448011d189f00000e81ddfac/frameset.htm
4/11/2024
152This is custom documentation. For more information, please visit the SAP Help Portal
Creating an Asset for a Post-Capitalization in Transaction AS01Press "Enter"
 Fill in all required �elds and parameters.
 
Note: the system requires �eld 'Capitalization on' to be �lled.
 
Note: when you hit "Enter" also �elds First acquisition on' and 'Acquisition Year' are now �lled automatically to complete
the Posting Information.
In 'Deprec.Areas' tab: enter or change the depreciation key and useful life as required. The ordinary depreciation start date is being �lled
automatically according to your capitalization date that you entered (see above) and taking into account the period control in the depreciation key.
https://help.sap.com/docs/disclaimer
4/11/2024
153This is custom documentation. For more information, please visit the SAP Help Portal
 Note, since the last closed �scal year is 2011, and the current �scal year is 2013, the expired useful life for this asset is 4 years. It is calculated and
�lled automatically by the system.
Once all parameter settings in the asset master are completed, you can "SAVE" the asset master. 
Display Asset Master in Transaction AS03 
Post an acquisition value to the post-capitalized asset via (for example) transaction ABZON
Enter the asset number, company code, document date, posting date, asset value date, amount and any other relevant parameters.
https://help.sap.com/docs/disclaimer
4/11/2024
154This is custom documentation. For more information, please visit the SAP Help Portal
 
"SAVE" transaction ABZON to post the value to the asset. Then check in the Asset Explorer the values and depreciation calculated and distributed on
the Asset.
Values in the Asset Exporer: transaction AW01N
1) Display of all values and parameters in Depreciation Area 01, with depreciation key LINR
Planned values: depreciation value is calculated for 10 years (from 01.01.2008), but is distributed now over the remaining useful life of 5 years.
Hence, 2.400,00 EUR per �scal year.
Posted values:
https://help.sap.com/docs/disclaimer
4/11/2024
155This is custom documentation. For more information, please visit the SAP Help Portal
 
 
Comparison:
 
Parameters:
 
https://help.sap.com/docs/disclaimer
4/11/2024
156This is custom documentation. For more information, please visit the SAP Help Portal
 Display Dereciation key: LINR
 
 
 
 
https://help.sap.com/docs/disclaimer
4/11/2024
157This is custom documentation. For more information, please visit the SAP Help Portal
2) Display of all values and parameters in Depreciation Area 01, with depreciation key LINA
Planned values: depreciation value is calculated for 10 years useful life (starting on 01.01.2008), but is spread beyond the 5 years of remaining
life according to the customizing of the depreciation key LINA. It is therefore a very different distribution of depreciation over the years compared to
example depreciation key LINR in previous example. The depreciation planned in FY 2013 (acquisition) is in case of depreciation key LINA amounting
to 1.200,00 EUR, and remains same value for the 5 remaining years of useful life, until the effect of the 'Curb' customizing in the depreciation key
kicks in - see below under 'Comparison' for more information.
 
 
Posted values:
 
https://help.sap.com/docs/disclaimer
4/11/2024
158This is custom documentation. For more information, please visit the SAP Help Portal
 
Comparison: 
 
https://help.sap.com/docs/disclaimer
4/11/2024
159This is custom documentation. For more information, please visit the SAP Help Portal
For more information on depreciation key LINA and the effect the speci�c settings "with curb" has on depreciation after the useful life ends, please
read SAP Library Documentation under Link:
http://help.sap.com/saphelp_470/helpdata/en/4f/71ddc6448011d189f00000e81ddfac/content.htm
Parameters:
 
 
Display Dereciation key: LINR
 
 
https://help.sap.com/docs/disclaimer
http://help.sap.com/saphelp_470/helpdata/en/4f/71ddc6448011d189f00000e81ddfac/content.htm
4/11/2024
160This is custom documentation. For more information, please visit the SAP Help Portal
 
 
 
 
Cross system Depreciation Areas and Intercompany Asset transfer
Purpose
The purpose of this page is to clarify the understanding of the system logic and requirements when make transfer between two company code using
Cross system depreciation areas.
Overview
Cross System Depreciation Area can be used to set depreciation areas from different Chart of Depreciation to a single key (Called Cross-System
Depreciation Area) and than giving these areas same meaning across the system.
De�ning Cross System Depreciation Area
To de�ne the Cross System Depreciation Area go to navigation: SPRO -> Financial Accounting-> Asset Accounting -> Transactions -> Intercompany
asset transfer -> Automatic Intercompany Asset Transfers -> De�ne Cross-System Depreciation Areas.
https://help.sap.com/docs/disclaimer
4/11/2024
161This is custom documentation. For more information, please visit the SAP Help Portal
1) Click on De�ne Cross-System Depreciation Areas.
2) In this phase you will de�ne the cross-system depreciation areas. 
3) To have a better understanding how it works, please �nd the below images and steps:
3.1) In the next steps of con�guration you will de�ne which depreciation areas corresponds to the cross system depreciation areas.
https://help.sap.com/docs/disclaimer
4/11/2024
162This is custom documentation. For more information, please visit the SAP Help Portal
3.2) In the example above we exemplify the links between the areas. When executing transaction code ABT1N (for example: moving values from
Company code A to Company code B) , area 1 of Chart of depreciation B will receive values from area 1 of Chart of depreciation A. But for
depreciation areas 11 and 26 the values, they will receive values of 25 and 10 respectively.
4) Returning to the system, now you have to create the links for the relevant chart of depreciation. For this go to navigation: SPRO -> Financial
Accounting-> Asset Accounting -> Transactions -> Intercompany asset transfer -> Automatic Intercompany Asset Transfers -> De�ne Cross-System
Depreciation Areas. In the poupup window please double click on Assign Local to Cross-System Depreciation Areas.
5) As in example of point 3.2 here we are making the links between Chart of depreciation ZFRI and ZTHA using the Cross-system Depreciation Areas.
6) As you could notice this link will correspond to:
Depreciation areas 1, 41 and 50 in Chart of depreciation ZTHA will receive values from depreciation area 1, 20 and 15 respectively of Chart of
depreciation ZFRI when executing intercompany asset transfer (ABT1N).
Intercompany Asset transfer
As already discussed in Intercompany Asset transfer , please go to transaction code ABT1N.
1) As you see in the below picture we will transfer values from asset 20084 which has 12,000 as APC in company code ZFRI to a new asset in
company code ZTHA.
https://help.sap.com/docs/disclaimer
http://wiki.sdn.sap.com/wiki/x/CQaYDw
http://wiki.sdn.sap.com/wiki/x/CQaYDw)
4/11/2024
163This is custom documentation. For more information, please visit the SAP Help Portal
2) Press the “line items” button to simulate the transfer and check the transfer values between the both company codes.
In the image above you can see the values of the sending asset 20084 in company code ZFRI.
In the image above you can see the values of the Receiving asset in company code ZTHA.
3) In the above pictures you can see that the values are transferred from area 1, 15 and 20 in ZFRI to depreciation areas 1, 20 and 41 respectively in
ZTHA.
4) If it is everything ok after that, you may execute the transfer by saving it. Otherwise, you may repeat steps above and simulate it different transfer
parameters. 
Related Content 
Related SAP Notes/KBAs
https://help.sap.com/docs/disclaimer
4/11/2024
164This is custom documentation. For more information, please visit the SAP Help Portal
2022044 - Transaction ABT1N: Intercompany transfer with cross-system depreciation areas (book and group/parallelarea)
De�ning posting rules for depreciation
Purpose
The purpose of this page is to clarify the understanding of the system logic and requirements in relation on how to de�ne the postings rules in
depreciation.
Overview
There are few ways when to post the depreciation, normally the depreciation is posted at the end to the period. The other ways you can �nd at
transaction code OAYR.
De�ning posting rules
To de�ne posting rules in depreciation go to navigation SPRO -> Financial Accounting -> Asset Accounting -> Integration with the General Ledger ->
Post Depreciation to the General Ledger -> Specify Intervals and Posting Rules
Alternatively: Transaction code OAYR
To maintain the posting rules for a certain company code, select it in the right column and double click at posting rules in the left column as you can
see in the image below.
https://help.sap.com/docs/disclaimer
https://me.sap.com/notes/2022044
4/11/2024
165This is custom documentation. For more information, please visit the SAP Help Portal
As you can see in the below image, now you can choose between the used depreciation areas in the selected company code. 
Choosing one of them you will now be able to select how often you will post the depreciation. Please check it in the follow image.
Selecting Monthly posting the depreciation will take place every period;
Selecting Bi-monthly posting the depreciation will take place every two periods;
Selecting Quarterly posting the depreciation will take place every three periods;
Selecting Semi-annual postings the depreciation will take place every 6 periods;
At least, if you select annual posting the depreciation will take place only in the last period.
https://help.sap.com/docs/disclaimer
4/11/2024
166This is custom documentation. For more information, please visit the SAP Help Portal
You also have the option - Enter in expert mode . This option is used in case your �scal year variant has more than 12 periods, for example 20 periods
and you want that the depreciation take place 4 times in the year. In this select 5 at the period interval.
20 period / 5 as period interval = will give you 4 times of depreciation in a year.
Regarding the smoothing indicator you can refer to the link below:
Depreciation smothing and catch up
Other settings
You also have other posting settings as you can see in the below image:
 
If setting post interest the interest is posted in addition to the depreciation during the depreciation posting run
If setting post revaluation the revaluation of APC and the accumulated ordinary depreciation will post to the general ledger during the depreciation
posting run.
If below-zero option is set the system will the depreciation even the useful life ends to the account speci�ed in the account determination.
Related Content 
Related Documents 
Depreciation Smoothing and Catch Up
System Settings for Posting Depreciation
Related SAP Notes/KBAs
Document type selection via F4 help in asset transaction
Title
Document type selection via F4 help in asset transaction
Purpose
Explain the necessary customizing for the document types which could be selected via F4 help when execute asset transaction like ABZON, ABUMN,
ABAVN...
Overview
Via customizing IMG->Asset accounting->Integration with the general ledger->Post depreciation to the general ledger->Specify document type for
posting of depreciation(Choose de�ne document type), we could �nd many document types but not all document types could be selected in F4 help
when doing asset transaction.
For example, we have following document types in above customizing:
https://help.sap.com/docs/disclaimer
http://wiki.sdn.sap.com/wiki/x/2QPGE
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361878502.html
http://help.sap.com/saphelp_46c/helpdata/en/4f/71dbce448011d189f00000e81ddfac/content.htm
4/11/2024
167This is custom documentation. For more information, please visit the SAP Help Portal
Take document DA for example, in the F4 help of ABZON, we could �nd the document type is not in the F4 help list
https://help.sap.com/docs/disclaimer
4/11/2024
168This is custom documentation. For more information, please visit the SAP Help Portal
Section 1
 In order to make document type could be selected in F4 help,, we need to make sure the document type contains the same number range with the
asset class which used for the asset and the document type need to allow asset in "Account types allowed".
For the example document DA, current customizing is below:
https://help.sap.com/docs/disclaimer
4/11/2024
169This is custom documentation. For more information, please visit the SAP Help Portal
After change "Number range" to 02(example asset uses asset class 2000 which uses number 02) and allow asset in "Account types allowed":
https://help.sap.com/docs/disclaimer
4/11/2024
170This is custom documentation. For more information, please visit the SAP Help Portal
After save the change, we could �nd document DA in the F4 help list:
https://help.sap.com/docs/disclaimer
4/11/2024
171This is custom documentation. For more information, please visit the SAP Help Portal
This change could be found in other transaction like ABUMN,ABAVN...
Section 2
 Via customizing IMG->Asset accounting->Organization structures->Asset classes->De�ne asset classes(T-code OAOA), we could check which
number range used in asset class.
For in example in this WIKI, example asset uses asset class 2000 and asset class uses number range 02
Japanese Impairment Posting
https://help.sap.com/docs/disclaimer
4/11/2024
172This is custom documentation. For more information, please visit the SAP Help Portal
Purpose 
The purpose of this page is to clarify the Japanese impairment posting steps.
Overview
The following paragraphs and picture will describe an example in steps of a Japanese impairment posting.
There are 3 steps for Japanese impairment posting.
 1) Creation of new time-dependent interval in depreciation area of asset with new depreciation parameters.
 2) Posting of impairment amount to asset.
 3) Execute depreciation recalculation
1. Go to transaction AS02 to change asset.
2. Go to the depreciation area tab, double click the depreciation area line.
 
3. Press more interval button.
4. Press the add Interval button, enter the “from date” of impairment, the date should be the �rst date of period.
https://help.sap.com/docs/disclaimer
4/11/2024
173This is custom documentation. For more information, please visit the SAP Help Portal
5. Enter the impairment key and period information, then save the change.
Note:
SAP provide standard Japanese impairment key, IDB, IDM, ILI, ILT in sap note 951312.
6. Go to transaction ABAW
 Note:
 use standard transaction type SA1 for assets acquired in previous year
 use standard transaction type SA2 for assets acquired in current year
https://help.sap.com/docs/disclaimer
4/11/2024
174This is custom documentation. For more information, please visit the SAP Help Portal
7. Asset value date should be the last date of previous period (30.06.2015)
8. When save, following popup appear, then press yes.
9. Back to transaction AS02 to recalculate depreciation
10. Check the result
Transaction AW01N
https://help.sap.com/docs/disclaimer
4/11/2024
175This is custom documentation. For more information, please visit the SAP Help Portal
11. Transaction AS03, Asset master
Related Content
Related Documents
http://help.sap.com/saphelp_erp2005/helpdata/en/44/3323f8eb773f0ae10000000a114a6b/frameset.htm
Related SAP Notes/KBAs
SAP note: 951312, 986616, 1095424
__________________________________________________________________________________________________________
Use this structure to help you compose your contributions for WIKI and at the same time will ensure spelling and grammar.
Settlement of Asset Under Construction using transaction codes AIAB and AIBU
Purpose
The purpose of this page is to clarify the understanding of the system logic and requirementsin relation to the settlement of asset under
construction through transaction codes AIAB and AIBU.
Overview
The following paragraphs and screen shots will describe an EXAMPLE in steps of a settlement of asset under construction using transaction codes
AIAB and AIBU and provide an explanation of the functionality of the main �elds and buttons.
Preparing scenario
Creating the Assets:
https://help.sap.com/docs/disclaimer
http://help.sap.com/saphelp_erp2005/helpdata/en/44/3323f8eb773f0ae10000000a114a6b/frameset.htm
https://service.sap.com/sap/support/notes/951312
https://service.sap.com/sap/support/notes/986616
https://service.sap.com/sap/support/notes/1095424
4/11/2024
176This is custom documentation. For more information, please visit the SAP Help Portal
1.1) Create an asset under construction using asset class that refers to AUC. and post two acquisitions to this asset with different posting date,
please refer to the following link how to post acquisitions: Asset acquistion.
1.2) After creating and posting to this asset, AW01N should appears like the following picture:
1.3) Create another asset with a non-asset under construction class without any posting.
Setting distribution rules through transaction code AIAB
2.1) To set distribution rules to an asset under construction go to Navigation: SAP Easy Access -> SAP Menu -> Accounting -> Financial accounting ->
Fixed Asset -> Posting -> Capitalize Asset u. Const. -> Distribute.
Alternatively: Transaction code AIAB.
2.2) Fill out Field Asset with your asset number already created and with postings (press F8)
https://help.sap.com/docs/disclaimer
http://wiki.sdn.sap.com/wiki/x/igVXDw
4/11/2024
177This is custom documentation. For more information, please visit the SAP Help Portal
2.3) Select the �rst of the two line items as per the picture above, then press button -Enter- or shift+f6 
2.4) Fill out Field settlement Receiver with the �rst asset created in the section 1.3 and �ll out �led % percentage with 100. Them press button to
check or Shift+f2. 
2.5) After that, return to line items screen pressing return button or F3. Select the second line item and press button --Enter- or shift+f6.
2.6) Fill out Field settlement Receiver with the second asset created in the section 1.3 and �ll out �led % percentage with 50. Them press button to
check or Shift+f2. 
https://help.sap.com/docs/disclaimer
4/11/2024
178This is custom documentation. For more information, please visit the SAP Help Portal
2.7) After that, return to line items screen pressing return button or F3 and save. Now the distribution rules are created.
Settlement AUC through transaction code AIBU
3.1) To settle an asset under construction go to Navigation: SAP Easy Access -> SAP Menu -> Accounting -> Financial accounting -> Fixed Asset ->
Posting -> Capitalize Asset u. Const. ->Settle.
Alternatively: Transaction code AIAB
https://help.sap.com/docs/disclaimer
4/11/2024
179This is custom documentation. For more information, please visit the SAP Help Portal
3.2) Fill out Field Asset with your asset under construction number already created with postings, same that you used in section 2.2.Fill out Fields
Document Date, Posting date and Asset Values (it cannot be a date prior to this asset capitalization date). Press “Simulation” button to simulate
settlement document creation.
3.4) For means of check you can go to asset explorer and check the values posted to the asset under construction and the receivers assets.
Settlement of an Internal Order or Investment Order - All Processes
Purpose
This document explains the various steps how an Internal Order or Investment Order is settled. The steps will also include some of useful steps on
the Controlling and Material Managment side that will help in the investigation of settlement issues.
Overview
When settling an order to an Asset under Construction or Fixed asset it is generally one of the last steps in a long chain of other steps that need to
be completed �rst, and which are not related to Asset Accounting. However, this overview should help to give a more rounded insight of what is or
can be involved before we settle an order (or project or WBS element for that matter) in CO tranasctions such as CJ88 or KO88 for example. 
What is an Internal Order or Investment Order?
Internal Orders or Investment Orders are “cost collectors”, they can receive postings from MM, FI, down payments etc.
Internal Orders:
They settle to a cost center (e.g. Marketing). These can be costs for example for an event or marketing etc.
Investment Orders:
You receive a budget and buy and asset. Then settle to an asset or an Investment Order created in CO. This could be for example for
PC/Laptops, furniture etc.
What makes an investment order? The Investment Pro�le! When you enter an investment pro�le () it will create an Asset und Construction
(AuC) once you save.
The investment pro�le (transaction OITA) is linked to the asset class.
Tables for Posting
Postings in Asset Accounting creates or modi�es in the following tables.
ANEK (Document Header Asset Posting)
ANEP (Asset Line Items)
ANEA (Proportional Values: mostly for retirements and retiring transfers)
ANLC (Asset values summarized on area and year level)
ANLB (Only for the very �rst posting on the asset; table is updated)
ANLA (Aquisition date, deactivation date, origin)
The most important �elds in table ANEK:
CPUDT, CPUTM: system date of postin
TCODE: transaction code, which was used for postin
ANLU1, ANLU2: asset number of acquired/retired asset for transfer or intercompany transfers
BELNR: document number (FI or reference number)
AWTYP, AWORG, AWSYS: �elds which are the unique link to the corresponding FI document. 
The most important �elds in table ANEP:
FABE: depreciation area
BELNR: document number (or reference number)
https://help.sap.com/docs/disclaimer
4/11/2024
180This is custom documentation. For more information, please visit the SAP Help Portal
BWASL: transaction type
ANBTR: APC amount of the posting
NAFAB, SAFAB, ZINSB: ordinary, special depreciation, interest on transaction (not valid anymore for the new depreciation engine!)
XANTW: indicator, that proportional values exists (XANTW = X, if there are entries in table ANEA)
LNSAN: line item number of the reversal document
AUGLN: number of the clearing line items (is set by the AuC settlement)
The most important �elds in table ANEA:
AFABE: depreciation area
NAFAV, SAFAV, AAFAV: proportional value adjustments of previous �scal years
NAFAL, SAFAL, AAFAL: proportional value adjustments of current �scal year
 
Transaction type - current year and previous year
Purpose
The purpose of this page is to clarify the understanding of the system logic and requirements in relation to transaction type for current year and
previous year.
Overview
In asset accounting, different transaction types are used during posting. 
As a basic rule, transaction types can be considered as previous year transaction type or current year transaction type, and it's very important to
use a correct one based on the asset value.
How to check if it's previous year or current year
For each transaction type, it's assigned to a transaction type group. You can check this in table TABW.
Then you can check the transaction type group in table TABWG whether �eld XZUGNE is �agged with X.
XZUGNE X current year transaction
XZUGNE blank previous year transaction
For example, if an asset only have current year APC amount, and you want to post revaluation to it, only current year transaction type for revaluation
could be used.
Besides, the amount posted with current year transaction type is considered as current year value.
The value carried forwarded from last year and also the amount posted with previous year transaction type is considered as previous year value.
Periodic Processing
Periodic Processing
This section will coverall topics for Periodic Processing such as running depreciation and year end closing activities.
Asset Fiscal Year Change
Generally speaking, a Fiscal Year change is the opening of a new Fiscal Year for a Company Code. During a Fiscal Year change process, the asset
values from previous Fiscal Year are carried forward cumulatively into the new Fiscal Year. Once the Fiscal Year change takes place, one can start
posting to assets using value dates in the new Fiscal Year. Simultaneously, one can continue to post in the previous Fiscal Year. You �nd the Fiscal
Year change program under Periodic processing. SAP Easy Access Menu: Accounting → Financial Accounting → Fixed Assets → Periodic
Processing → Fiscal Year Change (AJRW) - Refer screenshot below:
https://help.sap.com/docs/disclaimer
4/11/2024
181This is custom documentation. For more information, please visit the SAP Help Portal
https://help.sap.com/docs/disclaimer
4/11/2024
182This is custom documentation. For more information, please visit the SAP Help Portal
Process �ow
The Fiscal Year change can only be carried out (even in test mode) for the new Fiscal Year. The earliest that one can carry out a Fiscal Year change is
in the last month of the old Fiscal Year. One can choose any point in the new Fiscal Year for carrying out the Fiscal Year change. One can have a
maximum of two Fiscal years open for postings at any given point in time. Before one changes to Fiscal Year 9999, it is important and must to close
Fiscal Year 9999 - 2 (Reference: Year-end Closing → Transaction AJAB). 
https://help.sap.com/docs/disclaimer
4/11/2024
183This is custom documentation. For more information, please visit the SAP Help Portal
One should not post any business transactions in a new Fiscal Year before the Fiscal Year change is taken up. Posting in the old Fiscal Year can be
continued, even after the Fiscal year Change, as already mentioned above. The system automatically corrects any values which are affected by
postings in the past
Let's see an example here. Let's take a scenario where there are two open Fiscal Yea(s) for Assets are 2016 and 2017. Now, if Fiscal Year 2018 need
to be opened, then one should consider closing Fiscal Year 2016. To congurate this situation, one need to access Transaction Code OAAQ (Change
View "Remove Year-End Closing for Company Code": Overview). 
https://help.sap.com/docs/disclaimer
4/11/2024
184This is custom documentation. For more information, please visit the SAP Help Portal
Now, consider closing Fiscal Year in Asset Accounting with Transaction Code AJAB (Refer Screenshot above).
As a next step, consider opening a Fiscal Year in Asset Accounting with Transaction Code: AJRW (Refer Screenshot Above)
Later, consider copying a Document Number Range Interval for the next Fiscal Year with Transaction OBH2. 
Later open posting periods for the next Fiscal Year with Transaction Code OB52.
 
 
 
Balance Carryforward: values no transfered into next year for some assets
What to check:
 
1) Execute SCMO transaction to check the log when the Balance Carryforward was executed. Use the following
parameters:
 
Application: FI-AA 
Company Code: (your Company Code) 
Fiscal Year: (current Fiscal Year) 
Program Name: RAJAWE00
 
Check whether error message is shown in the log.
If error message is: “Asset xxxxx CoCd xxxx: Error in �scal year change” (AA707). This is a generic error
message and in order to investigate the real issue in the asset, you have to execute the steps in the
following note where you can �nd the real error in the asset: 1560041 - Error message AA707 in transaction
AJRW
If not error message is found in the log:
https://help.sap.com/docs/disclaimer
4/11/2024
185This is custom documentation. For more information, please visit the SAP Help Portal
1. Check the master data in the asset: 
Are all �elds �lled correctly? 
Is there a value in the “Adquisition Year” �eld? 
If any �eld is missing, try to �ll it up and try the Balance Carryforward again. 
The following note could be useful here: 118233 - Table SAP Note 1531737 - Error AA698 - Possible
causes and resolutions.
 
2) Repeat the Balance Carryforward and check whether the previous error messages are triggered.
 
3) You are in a S/4 HANA system, then the following note should be applied in your system: SAP Note 2255500 -
New Asset Accounting: relevant notes for year-end closing.
 
4) You are in SAP_APPL 616 without SP on a SAP HANA database, then the following SAP Note 1794781 should
be applied.- RAJAWE00: Performance problems on HDB
 
 
Cross Company Code Depreciation Postings
Cross-Company Code Depreciation Postings with RAPOST2000
Author: D033258
IMS Financials, SAP AG 
Common Abbreviations
CoD = Chart of Depreciation
CC = Company Code
TCODE = Transaction Code
G/L = General Ledger
Occuring Issues
Customer upgrades from release prior to R/3 Enterprise (4.70) and detects differences between cross-company postings done by the old
depreciation program (RABUCH00) vs. the new depreciation program (RAPOST2000).
Often the Cost Center has a different company code assigned, RABUCH00 did not post the depreciation to this foreign company code (=
cross-company), but RAPOST2000 ends with error message KI 223 (Cost center &/& can only be assigned to in company code &).
In some cases customer complains that other G/L transactions (FB01, etc.) allow posting to TCODE used in this transaction without errors,
even if the cost center has a different company code assigned, but RAPOST2000 ends with error message KI 223 (Cost center &/& can only
be assigned to in company code &).
In seldom cases the customer does not know the document number determination for these postings, because it changed also from
RABUCH00 to RAPOST2000
Basic Functionality
IMG
Asset Accounting
Master Data
Specify Cost Center Check Across Company Codes
https://help.sap.com/docs/disclaimer
https://launchpad.support.sap.com/#/notes/1531737/E
https://launchpad.support.sap.com/#/notes/2255500/E
https://launchpad.support.sap.com/#/notes/1794781/E
4/11/2024
186This is custom documentation. For more information, please visit the SAP Help Portal
IMG Documentation Specify Cost Center Check Across Company Codes
Activate this functionality if
cost accounting extends across company codes (several company codes belong to one controlling area) and
account assignment of cost accounting depreciation from Asset Accounting to cost centers that are in different company codes than the
asset.
When you enter a cost center in the asset master record, the standard system checks if this cost center exists in the same company code as the
asset. You are not allowed to enter a cost center in a different company code.
In this step, you can make this check less strict. The system then only checks whether the cost center exists in the given controlling area.
Example
Asset: 30051 -> Company code of the asset: 0001 -> Cost center in the asset: SAP-DUMMY -> Company code of cost center SAP-DUMMY: 1000
Excursus CO
Company Code Maintenance in Cost Center Master Record only when Cross-Company Code Cost Accounting is active in Controlling Area (OX06)
https://help.sap.com/docs/disclaimer
4/11/2024
187This is custom documentation. For more information, please visit the SAP Help Portal
Excursus RABUCH00 vs. RAPOST2000
Old depreciation run RABUCH00 did not check the cost center initially. RABUCH00 interpreted IMG activation �ag in FI-AA customizing (T093C-
BKRAKT). If not set to active, only sending CC was posted - even if cost center had different CC assigned.
This is the �rst pitfall when upgrading to RAPOST2000. New depreciation report initially uses cost center information. As additional check T093C-
BKRAKT is checked. If inconsistent information is determined, RAPOST2000 will end with errors
Asset Master Record Maintenance
IMG Setting not active, trying to assign Cost Center with different company code:
Exception
If the company code check is deactivatedfor 'Activate components' in the Controlling IMG under 'Controlling -> General Controlling -> Organization -
> Maintain Controlling Area', then a cost center can be assigned to the asset master record without having activated it in IMG FI-AA!
Second Pitfall: these cases will lead to KI 223 in RAPOST2000!!!
Important note:
Deactivating the company code check has an effect on all postings in external FI since CO objects from other company codes can
generally be assigned to an account as a result. A reconciliation between G/L and cost accounting is no longer possible.
https://help.sap.com/docs/disclaimer
4/11/2024
188This is custom documentation. For more information, please visit the SAP Help Portal
Deactivate the company code check is only possible if the reconciliation ledger is not active (Deactivate Reconciliation Ledger:
Transaction KALB).
Basic Intention
If depreciation is posted in company code X for the cost-accounting depreciation area "�xed assets" that points at a cost center K in another
company code Y, two documents are created (one for each account assignment): 
 
Document 1 (relevant for CO): 
============================= 
Debits/credits Account Company code Cost center 
 D depr. account Y K 
 C clearing acc. Y - 
 
Document 2: 
============================ 
Debits/credits Account Company code Cost center 
 D clearing acc. X - 
 C depr. clearing acc. X - 
Cross-Company Code Document Type Customizing with RABUCH00
Described in note 51860
All company codes "X1, X2 ..." with �xed assets use same doc type for depreciation posting (e.g. AF). Corresponding number ranges over company
codes "X1, X2 ..." may have no overlaps. In addition, the number range for document type AF must be maintained in company code Y of the cost
centers and all number ranges for document type AF must be across company codes "X1, X2 ..." or chosen internally. 
 
Example: company code X1: number range for AF = (10000, 19999) 
 company code X2: number range for AF = (20000, 29999) 
 company code Y: number range for AF = (10000, 29999)
 or other internal number range 
 
If �xed assets are also contained in company code Y, then in Y a document type other than the AF document type for the "X1, X2, ..." company codes
(e.g. AG) must be chosen as document type for the depreciation posting runs. The number range of document type AG across company code Y may
not overlap with the number ranges of document type AF across company codes "X1, X2, ...". 
 
Example: company code X1: number range for AF = (10000, 19999) 
 company code X2: number range for AF = (20000, 29999) 
 company code Y: number range for AF = (10000, 29999) 
 or other internal number range 
 number range for AG = (50000, 59999) 
Cross-Company Code Document Type Customizing with RAPOST2000
Assumption: standard document type AF is used for depreciation posting
IMG Asset Accounting -> Integration with G/L -> Post Depreciation to G/L -> Document Type for Cross-Company Code Cost Accounting in External
Company Code
Logic before release ECC 6.0:
AF must have external number range assignment
Document type for cross-company code depreciation posting must meet the following conditions:
It must be a document type different from AF (e.g. AZ)
It must be de�ned with internal document number assignment.
Enhancement: only 2 document types needed, AF used for depreciation postings in all company codes, AZ will always be used for cross-
company postings!
Logic as of release ECC 6.0:
AF must have internal number range assignment
https://help.sap.com/docs/disclaimer
http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=DISPL_TXT&_NNUM=51860
4/11/2024
189This is custom documentation. For more information, please visit the SAP Help Portal
Document type for cross-company code depreciation posting must meet the following conditions:
It needs not to be different from AF, can be the same as the regular depr. document type
It must be de�ned with internal document number assignment.
Enhancement : only 1 document types needed for any number determination
Depreciation document without cross-company code posting
G/L Depreciation Document
Depreciation document without cross-company code posting
https://help.sap.com/docs/disclaimer
4/11/2024
190This is custom documentation. For more information, please visit the SAP Help Portal
G/L Depreciation documents
->Offset Accounts balance to zero!!!
Maintenance of clearing accounts - standard functionality
IMG Financial Accounting -> General Ledger Accounting -> Business Transactions -> Prepare Cross-Company Code transactions
https://help.sap.com/docs/disclaimer
4/11/2024
191This is custom documentation. For more information, please visit the SAP Help Portal
If no clearing accounts are maintained, error message is given out.
Maintenance of clearing accounts - individual functionality
As the standard functionality is used mainly for cross-company code functionality for component accounts payable and accounts receivable, these
accounts are regularly open item managed accounts.
Many customers do not want to use open item managed accounts in their local GAAP for postings from the CO-only depreciation area (e.g. area 20)
... this is a con�ict, because is only one IMG step for any purposes
Assumption: Accounting Interface creates automated cross-company postings only if balance per document per company code is not balancing.
Solution: Asset Accounting line item generator enriches created document, so that in each affected company code balance zero is given before
passing the document to Accounting Interface.
Use of method ADD_DOC_LINES in Business Add-In BADI_FIAA_DOCLINES for Asset Accounting line item generator.
Coding Template released in note 723611 (RAPOST2000: Cross-company code postings in calc. Area)
Functionality: take depreciation line item for sending company code (offset account) and
Duplicate entry with twisted posting indicator and twisted posting amount in sending company code to identical account
Duplicate entry with an identical posting in receiving company code to identical account
-> G/L document balances in all company codes before passing the document to Accounting Interface
Schedule Monitor Assistance
With the change from external to internal document number usage, Schedule Monitor integration was enhanced. Internal AA document numbers are
stored as well as all generated G/L document numbers
https://help.sap.com/docs/disclaimer
http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=DISPL_TXT&_NNUM=723611
4/11/2024
192This is custom documentation. For more information, please visit the SAP Help Portal
Useful Notes
1079708 RAPOST2000: Deactivate cross-company code postings
723611 RAPOST2000: Cross-company code postings in calc. area
702210RAPOST2000: Unwanted cross-company code postings
683313 Diffs in depreciation runs RAPOST2000 vs RABUCH00
666225 RAPOST2000: Incorrect cross-company-code clearings
648606 RAPOST2000: Cross-company code cost accounting
51860 Cross company code depreciat. posting runs > F5152 (> for RABUCH00)
How we can verify the asset posting logs
Purpose
The purpose of this page is to help users to verify system log after run periodic posting or depreciation posting in test mode.
Overview
When we run periodic posting or depreciation posting, as best practice, we should run them as test mode �rst and verify the system log to ensure
that posting will occur without errors.
The most used transaction codes to verify periodic and depreciation posting logs are SCMO and ARMO.
Transaction codes to verify log:
The most used transaction codes to verify periodic and depreciation posting logs are SCMO and ARMO.
Go to transaction code SCMO:
https://help.sap.com/docs/disclaimer
http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=DISPL_TXT&_NNUM=1079708
http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=DISPL_TXT&_NNUM=723611
http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=DISPL_TXT&_NNUM=702210
http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=DISPL_TXT&_NNUM=683313
http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=DISPL_TXT&_NNUM=666225
http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=DISPL_TXT&_NNUM=648606
http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=DISPL_TXT&_NNUM=51860
4/11/2024
193This is custom documentation. For more information, please visit the SAP Help Portal
Or go to transaction code ARMO directly:
By both transaction codes you will able to verify monitor below:
https://help.sap.com/docs/disclaimer
4/11/2024
194This is custom documentation. For more information, please visit the SAP Help Portal
Also, if you want to know if there have been errors in the "direct posting", you can check it by transaction code ARAL:
Related Content
Related SAP Notes/KBAs
SAP Note 625204: RAPOST2000: Displaying errors, spool lists
https://help.sap.com/docs/disclaimer
https://service.sap.com/sap/support/notes/625204
4/11/2024
195This is custom documentation. For more information, please visit the SAP Help Portal
Recalculate Depreciation
Purpose
As the �rst step of Monthly/Quarterly/Yearly end closing, you need to execute depreciation recalculation via transaction code AFAR. In case of any
error occurred in test run and/or real run of depreciation recalculation, the error has to be eliminated �rst before you move to further steps of
closing process.This article describes detailed steps for general depreciation recalculation process.
Overview
To ensure depreciation is recalculated correctly for all assets, usually we execute depreciation recalculation in background �rst and remove all errors
occurred in test run of depreciation recalculation. afterwards, we execute real run of depreciation recalculation in background.
Section 1: Test Run of Depreciation Recalculation
1, Execute transaction code AFAR and specify parameters only for �eld ʻCompany code’ and ʻTest run’
 
2, Go to menu: Program -> Execute in background to execute depreciation calculation in background mode.
 
3, Specify printer and push button 'Con�rm'
https://help.sap.com/docs/disclaimer
4/11/2024
196This is custom documentation. For more information, please visit the SAP Help Portal
 
 4, Push button 'Con�rm'
 
 5, Push button 'Immediate' and button 'Save'
 
6, Execute transaction code SE37 to check the job has �nished 
 
https://help.sap.com/docs/disclaimer
4/11/2024
197This is custom documentation. For more information, please visit the SAP Help Portal
7, Execute transaction code ARMO then input below parameters → F8 to Execute
 
 
 8, Check the status of Test Run. if the status is red light, then go to next step to check the details of error messages
 
 
 9, Push button 'Spool'
 
 10, Go to the bottom of Spool to check if there is any error message recorded
https://help.sap.com/docs/disclaimer
4/11/2024
198This is custom documentation. For more information, please visit the SAP Help Portal
 
11, Check error messages one by one and correct those errors completely
12, After all errors are solved, you need to repeat all of above steps again to check if there is still any error message recorded in the spool of test run
of depreciation recalculation
13, If the status for test run of depreciation recalculation in step 8 is green light like below screen, you can move to section 2 to execute real run of
depreciation recalculation
 
Section 2: Update Run of Depreciation Recalculation
 1, Execute transaction code AFAR and input parameter ʻcompany code’ only
 
 
2, Go to menu: Program -> Execute in background to execute depreciation calculation in background mode.
 
 3, Specify printer and push button 'Con�rm'
https://help.sap.com/docs/disclaimer
4/11/2024
199This is custom documentation. For more information, please visit the SAP Help Portal
 
 4, Push button 'Con�rm'
 
 5, Push button 'Immediate' and button 'Save'
 
 6, Execute transaction code SE37 to check the job has �nished 
 
https://help.sap.com/docs/disclaimer
4/11/2024
200This is custom documentation. For more information, please visit the SAP Help Portal
7, Execute transaction code ARMO then input below parameters → F8 to Execute
 
 8, Check the status for update run is green light. 
 
 9, In below screen, click on button 'Spool' to check there is no error message recorded in the bottom of the spool
 
Section 3: Scenarios for Depreciation Recalculation
1. Before Month / Year end closing
2. After customizing change in Asset Accounting
3. After support package upgrade
https://help.sap.com/docs/disclaimer
4/11/2024
201This is custom documentation. For more information, please visit the SAP Help Portal
 
Reconcile General Ledger and Subsidiary Ledger
Steps for analyzing ABST2 differences:
 
1) For the account concerned, compare the last two �scal years using the account display transaction (FS10N or
FAGLB03 in New G/L) in the General Ledger. If the closing balance and opening balance differ, you have to start
the balance carryforward program again for the current year. 
 
2) Create two asset history sheets for the accounts involved using the following parameters:
Limiting the account assignment or the asset class in the dynamic selections
Sort version 0020
Group totals
Report date – �scal year end of prior year and current year
Setting “Depreciation posted” If the starting and �nal value of the asset history sheets are different, you
should repeat the �scal year change in asset accounting ( transaction AJRW).
 
If the starting and �nal values are still different after you repeat the �scal year change, then check to see if
there is an asset with a capitalization date but without acquisition data. Follow the procedure outlined in
SAP Note 194635.
 
3) The asset history sheet for the previous year does not agree within itself when you cross-foot. In this case:
Start RAABST01 for accounts with line item management.
Start RAABST02 for reports without line item management.
If the balance carryforward is affected, you now have to reset the year-end closing, perform depreciation
recalculation, possibly carry out a depreciation posting run, and then run the year-end closing again.
 
4) The starting balance values of the current year do not agree with the value of the balance display. There are
various possible causes, that then also require different actions on your part.
The difference arose already during the legacy data transfer. In this case, contact SAP Remote Consulting.
Missing line items. To see which line items are involved, see the log of RAABST01 or RAABST02. There are
two possible scenarios:
1. Missing line items during asset acquisition.These can be created easily using report RACORR05. In
the case of multiple account assignments, use report RACORR05A
2. Missing line items during asset retirement. These can not be created using report RACORR05. In this
case, contact SAP R/3 Support, describing the exact parameters of the asset concerned.
Line items with incorrect acquisition year. This situation is found at times with postings from invoice
veri�cation (transactions MRHR or MIGO). For correcting this problem, there are a number of correction
reports that are listed in SAP Note 366848. If you are unsure of how to proceed, contact SAP Support.
Account determinations that have errors or are incomplete can also cause differences, which cause errors
during the euro conversion, if not before. For these errors, you should now, at the latest, consider your
results from point 2.
Manual postings to asset balance sheet accounts. In this case, contact SAP Remote Consulting, with the
document numbers involved.
https://help.sap.com/docs/disclaimer
https://launchpad.support.sap.com/#/notes/194635/E
https://launchpad.support.sap.com/#/notes/366848/E
4/11/2024
202This is custom documentation. For more information, please visit the SAP Help Portal
 
 
For further Background information and hints on the reports that can be used for reconciliation, refer to SAP
Note 382548.
The procedure for reconciling the subsidiary ledger and general ledger is described in SAP Note 104567, point 3.
 
Running Depreciation using RABUCH00
Running Depreciation using RABUCH00
Background
There are two major programs used to run depreciation in SAP.
All R/3 releases prior to R/3 Enterprise used program RABUCH00. As of R/3 Enterprise, SAP released a new version of the depreciation
program called RAPOST2000 although the older program RABUCH00 is still available and can be used. This page of the Wiki will discuss RABUCH00
only.
Process Description 
Every asset transaction immediately causes a change of the forecasted depreciation. However, it does not immediately cause an update of the
depreciation and value adjustment accounts for the balance sheet and pro�t and loss statements. The planned depreciation is posted to the general
ledger when you run the periodic depreciation posting run. This posting run uses a batch-input session to post the planned depreciation for each
posting level for each individual asset as a lump sum amount.
Keys automatically control the calculation and scheduling of depreciation, interest and revaluation in the system, or you can control them manually
using a special posting transaction. In both cases, planned depreciation from Asset Accounting must be periodically posted to the corresponding
asset and expense accounts of the general ledger. You carry out this posting using a batch-input session. In addition to the various depreciation
types, interest and revaluation, this batch input session also posts the allocation and writing off of special reserves.
When the system posts depreciation, it creates collective documents. It does not create separate documents for each asset.
Technical Information
Program: RABUCH00
Transaction Code: AFAB
The program creates batch-input sessions for posting depreciation and interest to the G/L accounts in Financial Accounting and/or to Controlling.
Steps for Running Depreciation: 
At the initial screen of the program there are several �elds that can be input.
Company code: Enter in the company code that you want to run depreciation for
Fiscal Year: Your �scal year
Posting period: This is the depreciation period that has to be posted to the G/L
Reason for posting run:
Planned: This is used for all normal depreciation runs and is the default for the program.
Repeat: This can be used to make an additional posting run for a period that has already been run.
Restart: This can be used to restart a depreciation run that has failed for some reason.
Unplanned: Unplanned depreciation runs can be executed without evaluating the Posting Period. This lets you deviate from SAP's
standard requirement to always post for the next available posting period
List assets: You can activate this parameter so that the report output will list individual asset records. 
Test run: activate this indicator if you want to run it in test mode
Main asset number: During a test run you can specify certain asset numbers 
https://help.sap.com/docs/disclaimer
https://launchpad.support.sap.com/#/notes/382548/E
https://launchpad.support.sap.com/#/notes/104567/E
4/11/2024
203This is custom documentation. For more information, please visit the SAP Help Portal
After populating these values, goto the menu path Program --> Execute in Background. For test run purposes, the program can be executed in the
foreground but will be limited to only evaluating approximately 1000 assets. You should get this message "Background job was scheduled for
program RABUCH00".
To process the depreciation session, goto transaction code SM35. Double click on the BDC session that was created (most likely RABUCH). Choose
the options to [Display Errors Only] and [Dynpro Standard Size]. The session will then run in the background but will pop into the foreground if it
encounters an error.
Steps for Recreating the Depreciation Log: 
Using transaction code AFBD or program RABUCH30, you can create recreate the depreciation posting session in case there are errors that stop
the documents from posting.
Available Fields at AFBD:
Company code: Enter your company code
Fiscal year: Enter your �scal year
Posting period: Enter your posting period
List assets: (tick if you want to see the detail)
Test run: (tick if you run in test mode else Un-tick for production run)
Click the execute button if this is a test run. If this is a productive run, goto the menu path Program --> Execute in Background. You should get this
message "Background job was scheduled for program RABUCH00 and print out the output".
V2 update error handling
Parallel scenario in investment orders / WBS settlements
Due to new legal requirements a parallel valuation is necessary in some scenarios.
One common scenario is the capitalization of cost with different criteria depending on the legislation (Local vs. IAS).
The use of capitalization keys applies to this scenario and provides a solution to automatically update parallel valuation.
In some cases parallel areas are not updated as expected so a periodic process has to be executed to "catch up" missing On-line (V2)
postings.
Customizing
Customizing -Investment pro�le
https://help.sap.com/docs/disclaimer
4/11/2024
204This is custom documentation. For more information, please visit the SAP Help Portal
Customizing - Capitalization key
https://help.sap.com/docs/disclaimer
4/11/2024
205This is custom documentation. For more information, please visit the SAP Help Portal
The calculation of depreciation is based on period intervals instead of calculating depreciation on each single movement. From this follows that the
�elds „NAFAB" and „SAFAB" of the table „ANEP" are not updated anymore. This applies also to already posted movements.
Depreciation parameters in the asset master record can be maintained time-dependent. Dependency on time is considered when depreciation is
calculated.
A method change over is now possible on a period level - during the �scal year.
The new functionality is available if the Add-On „EA-FIN" is active.
https://help.sap.com/docs/disclaimer
4/11/2024
206This is custom documentation. For more information, please visit the SAP Help Portal
Error handling
When settlement takes place it could be that the parallel area is not updated on-line (V2 update) however no errors are encountered in the
settling transaction (KO88/CJ88).
Log of erroneous V2 update are displayed in transaction ARAL :
Object FIAA
Subobject 006
Errors displayed in the log have to be corrected.
Periodic posting program RAPERB2000 has to be executed to "catch-up" missing postings.
https://help.sap.com/docs/disclaimer4/11/2024
207This is custom documentation. For more information, please visit the SAP Help Portal
APERB_ITEMS table contains records of all V2 postings correctly updated. In case of an error in the "direct posting" the record will not be
updated in the table.
RAPERB2000 compares ANEP records with APERB_ITEMS records and if there is something missing it will post it.
APERB_ITEMS contains all records between two RAPERB2000 runs. After RAPERB2000 is correctly executed this table is cleared.
Table APERB_PROT - This table will be updated in case errors have not been completely corrected and RAPERB2000 is executed in real mode.
Related SAP Notes/KBAs
KBA 1626675 - V2-postings in relation to tables APERB_ITEMS & APERB_PROT and transaction ARAL 
What the number means in document text �eld which generated in AFAB
Purpose
Understand the numbers which shows in document text �eld which generated in AFAB after change to use internal document number. 
Overview
There is a system behavior change that depreciation posting use internal number due to note 890976.
Due to the behavior change, text �eld will not show document number directly but change to use reference document number.
Section
For example, if the text shows “AFB15201300104-0000000006”:
 
AFB->Hard coding.
15->area
2013->�scal year->T093D-AFBLGJ
001->Period in which last depreciation was posted->T093D-AFBLPE
04->Number of depreciation posting runs in the period->T093D-AFBANZ
“-”->Hard coding
0000000006->reference document number
Related SAP Notes/KBAs
 SAP Note 890976 - Converting closing report to internal doc number assgnmnt
 
 
Year-End Closing in Asset Accounting (NEW)
Purpose
Year-end closing in Asset Accounting: The process described in this document assists you in keeping on top of critical factors, such as data
consistency, which can involve a considerable amount of time and work during the year-end closing phase in Asset Accounting.
Overview
The following changes, among others, apply to New Asset Accounting. They are mostly valid as of SAP Simple Finance 1503 powered by SAP HANA
and SAP S/4HANA 1511.
https://help.sap.com/docs/disclaimer
https://me.sap.com/notes/1626675
https://service.sap.com/sap/support/notes/890976
4/11/2024
208This is custom documentation. For more information, please visit the SAP Help Portal
The �scal year change program RAJAWE00 is obsolete. It has been replaced with transaction FAGLGVTR ("G/L: Balance Carried Forward").
Program RAJAWE00 and transaction AJRW have been deleted and are no longer available.
All APC changes in Asset Accounting are posted to the general ledger in real time. Periodical APC postings are therefore super�uous and are
no longer supported (program RAPERBxxxx / transaction ASKB).
It is no longer necessary to reconcile the general ledger with the subledger of Asset Accounting as from now on Asset Accounting postings
are integrated in the general ledger (program RAABSTxxxx is obsolete).
Planned depreciation amounts per period and value type are stored in database table FAAT_PLAN_VALUES. Asset reports (e.g. Asset
Balances, Asset History Sheet, etc.) and the depreciation run do not calculate depreciation amounts at runtime anymore, but use the
information in this table to determine deprecation amounts to be reported/posted.
Program RAAFARxx to recalculate depreciation values has been replaced by program FAA_DEPRECIATION_CALCULATE.
Program RAPOSTxxxx to post depreciation has been replaced by program FAA_DEPRECIATION_POST.
The year-end closing in Asset Accounting consists of the following three parts which will be explained in detail in the following paragraphs:
Part 1: Preparation of the New Fiscal Year: Execute Fiscal Year Change Program
Part 2: Preparation for Year-End Closing in Asset Accounting
 1. Check Last Closed Fiscal Year in FI and FI-A
 2. Check Customizing Using Report RACHECK0
 3. Check Incomplete Assets
 4. Check Indexes
 5. Recalculate Depreciation
 6. Execute Depreciation Posting Run
 7. Reconcile General Ledger and Subsidiary Ledger
Part 3: Execute Year-End Closing Program
Part 1: Preparation for the New Fiscal Year: Execute Fiscal Year Change Program
The �scal year change program is an activity that you must execute within the scope of a �scal year change.
It is a necessary step in order to be able to post to the new �scal year. It should be carried out as soon as the new �scal year is reached at the latest.
Due to the fact that there is a journal entry, the balance carryforward of Asset Accounting is integrated with the balance carryforward of General
Ledger Accounting. The balance carryforward carries the general ledger values and the statistical �xed asset values forward to the new year.
Critical Factor
Posting transactions to a �scal year is only possible in Asset Accounting when carry-forward segments have been created for this �scal year. These
are created by the carryforward program FAGLGVTR.
Recommendation and Troubleshooting
We recommend carrying out the �scal year change in Asset Accounting near the time of year-end closing. From the viewpoint of SAP, no more than
two �scal years are allowed to be open at the same time.
Background
The system carries forward all general ledger-relevant values and statistical �xed asset values with a balance carryforward. The system writes
values carried forward on accounts and ledger level for each �xed asset.
The balance carryforward must be executed for all representative ledgers. It can only perform the balance carryforward in Asset Accounting
automatically when this was successfully performed in General Ledger Accounting.
In order to determine the planned depreciation values for the depreciation run, the system automatically triggers a recalculation of values for all
�xed assets in the new year. If errors occurred, you should start the recalculation again manually.
Part 2: Preparation for Year-End Closing in Asset Accounting
https://help.sap.com/docs/disclaimer
4/11/2024
209This is custom documentation. For more information, please visit the SAP Help Portal
The year-end closing in Asset Accounting is a required step before you can close the �scal year in Financial Accounting (FI). If you omit this step, or
do not carry it out until after closing the �scal year in FI, serious problems can result. This could include problems in changing master data. In order
to prevent these problems from happening, you should follow the steps below in the sequence they are listed.
1. Check Last Closed Fiscal Year in FI and FI-AA
Critical Factor
The closed �scal year in FI cannot be larger than the last closed �scal year in Asset Accounting. If you do not adhere to this guideline, the following
problems can result: It is no longer possible to recalculate depreciation, but this is nonetheless required, and error messages are therefore issued.
The recalculation of depreciation is also triggered, for example, when changes are made to the asset master record (for example, to the cost center
or even to texts). These changes are then sometimes no longer possible since, in certain cases, the depreciation recalculation is triggered. The
system is unable to automatically perform the depreciation recalculation if the �scal year is already closed in FI but not in Asset Accounting.
Recommendation and Troubleshooting
It is strongly recommended to close the �scal year in Asset Accounting before you close the �scal year in FI. Make sure that, at the most, two years
are open for posting in FI-AA. If you have problems because the �scal year is closed in FI but not in FI-AA, and in addition the years are far in the past,
contact your SAP consultant.
Background
For more detailed information, refer to the online documentation for Asset Accounting.
2. Check Customizing Using Report RACHECK0
Critical Factor
Errors in Customizing of depreciation areas, transaction types and periodrules. These can cause the following problems:
Inexplicable error messages are issued when adjustment postings are made, although nothing was changed in Customizing. 
A typical example of these error messages is AAPO176 (AAPO 176) "Transaction type XY cannot be used for activity Z."
Transfer postings cannot be carried out.
Differences occur due to missing account assignments.
When depreciation is recalculated, there are inexplicable error messages, such as AA641 (AA 641).
Recommendation and Troubleshooting
Customizing report RACHECK0 should be started at least once before the go-live date by asset accounting specialists, and corrections made in
Customizing accordingly.
3. Check Incomplete Assets
Critical Factor
Incomplete assets prevent the year-end closing from being made. The system lists these assets in an error log, with the request for them to be
processed.
Recommendation and Troubleshooting
You can �nd and process incomplete assets before the year-end closing using report RAUNVA00. There are two different types of incomplete assets:
The asset is incomplete, but can be posted.
The asset is incomplete and cannot be posted.
You need to correct both types.
Background
Incomplete assets can be created, for example, when the user lacks authorization for master data �elds that are required entry �elds, but these are
not so critical that the asset cannot be created at all. The system sets an indicator showing that assets are incomplete. Another reason could be
that the screen layout rule of the asset has changed, so a �eld that has no entry is now designated as a required entry �eld. When changes are made
to assets so that they are no longer incomplete, the system does not automatically reset this indicator. However, the indicator can be removed by
the report. For assets that are still incomplete when the report is run, you can go directly from the report to their asset master records and correct
them, as long as this is allowed by your authorization pro�le.
4. Check Indexes
https://help.sap.com/docs/disclaimer
4/11/2024
210This is custom documentation. For more information, please visit the SAP Help Portal
Critical Factor
Missing indexes can lead to the following errors:
If entries are missing, it may not be possible to carry out the �scal year change.
If entries are missing, it may not be possible to carry out the recalculation of depreciation, and the assets affected are �agged.
Recommendation and Troubleshooting
You should enter the indexes (e.g. for determining replacement values) as part of the preparations for closing. You use transaction OAV5 for this
task. It is important to carry out a recalculation of depreciation after the index series have been maintained. Refer also to SAP Note 35721. For
assistance with indexing in �scal years that are already closed, contact your consultant.
5. Recalculate Depreciation
The determination of the depreciation of an asset and the posting of depreciation expense takes place in the system at different points in time.
Calculate depreciation (transaction AFAR): the depreciation is determined with each master record change on the asset and updated in the
database accordingly (database table FAAT_PLAN_VALUES). In addition to this, the determination of accumulated depreciation is performed
automatically when performing the �scal year change for the prospective �scal year.
Critical Factor
Not recalculating depreciation can lead to the following errors:
Values are not calculated correctly. This results in an incorrect display in the asset value display transaction.
In the new �scal year, there are assets with the message "Depreciation values not completely calculated for this asset" (error
message AA510). Recalculation at this point often does not correct the error.
Assets with indexed depreciation areas are possibly not deactivated in the case of a complete retirement, if the calculation of
replacement values was not up-to-date.
Recommendation and Troubleshooting
Start the depreciation recalculation program for the whole company code, for which the year-end closing is to be carried out. Execute report
FAA_DEPRECIATION_CALCULATE (transaction AFAR) in test mode with the List Assets and Execute in Background options. When you run
FAA_DEPRECIATION_CALCULATE, a statistical log is issued containing any error messages that occurred. Correct the errors leading to any error
messages you receive, and start an update run of report FAA_DEPRECIATION_CALCULATE for these assets.
Background
Under certain circumstances, such as those listed below, depreciation values are not updated in the depreciation areas of some assets:
You have changed depreciation keys. This is especially important in the case of unit-of-production depreciation, where it is essential
that you recalculate depreciation after maintaining the current parameters.
You have made mass changes that you programmed yourself, and these changes affected data relevant to depreciation.
You still want to calculate subsequent revaluation (after the legacy data transfer is closed) using current index �gures. In order to
correctly calculate replacement values, however, you can only use index series that calculate historically.
 
IMPORTANT: Up to and including this step, you can repeat all activities as often as necessary to ensure that the system is up-to-date. However, in
the case of the following steps, you have to consider more carefully the individual planning and regulations within your enterprise, for example,
whether you post depreciation once a year or once a month, and so on.
6. Execute Depreciation Posting Run
Starting with this step, you begin preparing directly for the year-end closing. You can only carry out the processes and activities described below
when the year-end closing is imminent and is about to be carried out. Nonetheless, we recommend carrying out the depreciation posting run
FAA_DEPRECIATION_POST in test mode beforehand, to catch possible errors.
The determination of the depreciation of an asset and the posting of depreciation expense takes place in the system at different points in time. 
Post depreciation (transaction AFAB): The depreciation run adopts the planned asset values and posts them in Financial Accounting. The journal
entry is updated in Financial Accounting at asset level and the entry also contains the asset number.
Errors with individual assets do not necessarily need to be corrected before period-end closing during the �scal year; period-end closing can still be
performed during the �scal year.
But you have to make sure that all assets are corrected by the end of the year so that depreciation can be posted completely.
https://help.sap.com/docs/disclaimer
4/11/2024
211This is custom documentation. For more information, please visit the SAP Help Portal
Critical Factor
It is not possible to carry out the year-end closing without �rst performing the depreciation posting run for the last period of the �scal year without
any errors with individual assets.
Recommendation and Troubleshooting
Perform the depreciation posting run for the last period of the year (usually period 12 of the �scal year being closed). We strongly recommend that
you start report FAA_DEPRECIATION_POST �rst in the background and in test mode, and then carefully check the log. If error messages are issued in
the test run, then correct the errors (usually these are in account determination or the customizing of cost centers), before starting
FAA_DEPRECIATION_POST in update mode. The posting logic in the area of cost center postings is explained in SAP Notes, such as 684659.
Background
FAA_DEPRECIATION_POST adopts the planned asset values and posts them in Financial Accounting at single asset level. It is important to stress
that there is no reversal function for the depreciation postings. If depreciation terms are changed retroactively, this can often be corrected by
starting FAA_DEPRECIATION_POST in the period for which depreciation was last posted.
Reportingby Posting Period of Depreciation (�eld DEPR_PERIOD in ACDOCA) will allow you to summarize the depreciation amount which was posted
to a speci�c period.
In �eld DEPR_PERIOD in ACDOCA the system stores for which period the depreciation is valid. An error with an individual asset took place in the
previous period, so depreciation could not be posted for this single asset. As soon as the error is corrected in the actual period and depreciation
posting run is performed in the actual period, the system will adopt the planned asset values for the previous and actual period and will post them in
Financial Accounting. This journal entry is posted with posting period "actual period" and
one line item is posted for the depreciation being valid for the previous period (DEPR_PERIOD) and
one line item is posted for the depreciation being valid for the actual period (DEPR_PERIOD).
Example:
The cost center assigned to a single asset is locked. Therefore, it is not possible to post depreciation for this single asset in period 001. The cost
center will be unlocked in period 002. The depreciation run is performed during period-end processing activities of period 002. The system will adopt
the planned asset values for period 001 and period 002 for this single asset. A journal entry is posted to Financial Accounting with posting period
002.
KTNAFB = Accumulated Depreciation Account
KTNAFG = Expense Account for Depreciation
7. Reconcile General Ledger and Subsidiary 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 due to the universal journal entry.
We recommend that you run reports on the current asset values, for example, the asset history sheet, account balances, and �nancial statement.
Part 3: Execute Year-End Closing Program
Once these preparatory tasks have been completed, you can then carry out the year-end closing in Asset Accounting.
Critical Factor
Closing the general ledger before closing Asset Accounting violates generally accepted accounting principles. Not only that, but a missing year-end
closing in Asset Accounting, when the �scal year is already closed in FI, leads to no longer being able to change asset master records, among other
problems.
Recommendation and Troubleshooting
https://help.sap.com/docs/disclaimer
4/11/2024
212This is custom documentation. For more information, please visit the SAP Help Portal
Perform year-end closing in Asset Accounting. First execute report RAJABS00 in test mode, and check the log for error messages. If you carried out
the steps listed above in the correct order, you should not see any error messages.
However, the following errors could show up and need to be corrected:
There are errors in the calculation of depreciation: Recalculate the depreciation in the master data of the affected asset. It is possible that
the planned depreciation values have been changed. Therefore, the depreciation posting run needs to be performed again in the last period
of the �scal year of a special period.
Planned depreciation was not posted completely to the general ledger. Therefore, the depreciation posting run needs to be performed again
in the last period of the �scal year of a special period.
The capitalization date was not set.
o The assets listed are not assets under construction. Set the capitalization date manually in the asset master record.
o The assets listed are assets under construction. Re-run the report and make sure that all asset classes for assets under construction have
been entered correctly on the initial screen.
There are incomplete assets. Any incomplete asset master data have to be completed before year-end-closing. Re-run report RAUNVA00.
Background
As part of a sequence of postings and master record changes, a depreciation recalculation is triggered and checks are performed on the last �scal
year that is still open in Asset Accounting. If the system then determines that it is no longer possible to post depreciation to the general ledger, all
further processing is terminated and the system issues an error message.
Related SAP Notes/KBAs
KBA 2527328 - Year-End-Closing in Asset Accounting (NEW): Best Practice
Year-End Closing procedure in FI-AA
Preparation for Year-End Closing in Asset Accounting
 The year-end closing in Asset Accounting is a required step before you can close the �scal year in Financial Accounting (FI). You should follow the
steps below in the sequence they are listed.
 
 
1 Check Last Closed Fiscal Year in FI and FI-AA
First close the �scal year in Asset Accounting and then in FI. Make sure that, at the most, two years are open for posting in FI-AA.
 2 Check Incomplete Assets
You can �nd and process incomplete assets before the year-end closing using report RAUNVA00. There are two different types of incomplete assets:
• The asset is incomplete, but can be posted.
• The asset is incomplete and cannot be posted.
You need to correct both types.
 3 Check Indexes
You should enter the indexes for determining replacement values, or for updating the base insurable value, as part of the preparations for closing. It
is important to carry out a recalculation of depreciation after the index series have been maintained.
Calculation and carry forward of indexed values, above all insurable values, takes place solely during the �scal year change. If the indexes are not up-
to-date at that point, the �scal year can still be closed. But calculations from that point on can only be made using a special report.
 4 Recalculate Depreciation
Start the depreciation recalculation program for the whole company code, for which the year-end closing is to be carried out.
 5 Execute Depreciation Posting Run
Starting with this step, you begin preparing directly for the year-end closing. You can only carry out the processes and activities described below
when the year-end closing is imminent and is about to really be carried out.
 6 Execute Periodic Posting Program
Unless the periodic posting of balance sheet values is current, it is not possible to carry out the year-end closing. It is important to keep in mind here
that the year-end closing report checks the date of the last periodic posting program run using the system date as a reference. As a result, the year-
end closing can only be carried out at a time close to the end of the year.
 7 Reconcile General Ledger and Subsidiary Ledger
Perform a reconciliation of the values of Asset Accounting with the balances of the general ledger accounts.
 8 Execute Fiscal Year Change Program
Executing the �scal year change program is an optional step in the course of the year-end closing. It is not necessary in order to carry out the year-
end closing.
 Once these preparatory tasks have been completed, you can then carry out the year-end closing in Asset Accounting.
https://help.sap.com/docs/disclaimer
https://launchpad.support.sap.com/#/notes/2527328
4/11/2024
213This is custom documentation. For more information, please visit the SAP Help Portal
Additional documentation:
https://blogs.sap.com/2008/07/09/year-end-closing-in-asset-accounting-best-practices/
Decision Tree:
KBA 2532921 - Asset Accounting Year-end Closing Procedure and Common Issues
Asset Reporting
This page will be used to provide information on the reporting capabilities within Asset Accounting.
Data Archiving in FI-AA
Data Archiving in Asset Accounting
 
Introduction - Reasons for archiving
Data Archiving removes mass data that the system no longer needs online, but which must still be accessible at a later date if required, from the
database.
Resolves memory space and performance problems caused by large volumesof transaction data
Ensures that data growth remains moderate so that the database remains manageable in the long term
Ensures that companies can meet the legal requirements for data storage in a cost-efficient manner
Ensures that data can be reused at a later date, for example, in new product development
Archiving Procedure - steps
Creation of archive �les
In the write phase the data to be archived is written sequentially into newly created archive �les.
Delete from the database
The delete program reads the data from the archive �les and then deletes it from the database.
Storage of archive �les (optional)
The newly created archive �les can then be moved to a storage system or copied to a tape. The removal to an external storage system can be
triggered manually or automatically. It is also possible to store the data before the delete phase.
Data Reload (Optional)
Date can be read from Archive and inserted into DB again
Archiving Procedure - Illustration
https://help.sap.com/docs/disclaimer
https://blogs.sap.com/2008/07/09/year-end-closing-in-asset-accounting-best-practices/
https://me.sap.com/notes/2532921
https://me.sap.com/notes/2532921
4/11/2024
214This is custom documentation. For more information, please visit the SAP Help Portal
Archiving Features
Data Security During Archiving 
Data archiving is carried out in two steps (storage is optional). Step 1: data for archiving is copied to archive �les. Step 2: data is
deleted from DB.
Advantage: if problems occur during the archiving process. (e.g. network data transfer errors between DB and archive �le), restart of
archiving process possible at any - because data is still either in DB or in an archive �le.
increase data security by storing the archive �les in an external storage system before deletion of data from DB. Data will will only be
deleted from DB after it has been securely stored in an external storage system.
Data Compression
During archiving, data is automatically compressed by up to a factor of 5. Data is compressed before it is written to the archive �le.
Storage Space Gained by Archiving 
Increased storage space in the DB and the resulting performance gains in the application programs are the most important bene�ts
of data archiving.
Archiving Without Database Backup 
Data can be archived independently from general backup operations on the database.
Accessing Archived Data 
Because archived data has only been removed from the database and not from the application component itself, the data is always available.
Others (Converting Old Archive Files, Link to External Storage Systems)
Archiving Procedure
Creation of archive �les
In the write phase the data to be archived is written sequentially into newly created archive �les.
Delete from the database
The delete program reads the data from the archive �les and then deletes it from the database.
Storage of archive �les (optional)
The newly created archive �les can then be moved to a storage system or copied to a tape.
Data Reload (Optional)
Date can be read from Archive and inserted into DB again
Creation of Archive File
https://help.sap.com/docs/disclaimer
4/11/2024
215This is custom documentation. For more information, please visit the SAP Help Portal
Data to be archived is read from DB and written to archive �le. Process continues until one of following three events occurs:
1. All the data is written to an archive �le
2. Archiving is not complete, but the archive �le reaches the maximum size speci�ed in archiving object-speci�c Customizing
3. The archiving is not yet �nished, but the archive �le contains the maximum number of data objects speci�ed in Customizing.
If in cases 2 and 3 there is still data to be archived, the system will create another archiving �le.
Archiving Procedure
Creation of archive �les
In the write phase the data to be archived is written sequentially into newly created archive �les.
Delete from the database
The delete program reads the data from the archive �les and then deletes it from the database.
Storage of archive �les (optional)
The newly created archive �les can then be moved to a storage system or copied to a tape.
Data Reload (Optional)
Date can be read from Archive and inserted into DB again
Storing Archive Files
Once write program has �nished creating archive �les, these can be stored. Several ways of storing archive �les:
Storage Systems
HSM Systems
Existing Storage Media (tape)
Storage can be started automatically or by manual trigger
Archiving Procedure
Creation of archive �les
In the write phase the data to be archived is written sequentially into newly created archive �les.
Delete from the database
The delete program reads the data from the archive �les and then deletes it from the database.
https://help.sap.com/docs/disclaimer
4/11/2024
216This is custom documentation. For more information, please visit the SAP Help Portal
Storage of archive �les (optional)
The newly created archive �les can then be moved to a storage system or copied to a tape.
Data Reload (Optional)
Date can be read from Archive and inserted into DB again
Delete from Database
After closing the �rst archive �le, Archive Administration creates a new archive �le and continues with the write process. Depending on settings, a
delete program is started automatically in parallel for the previously created archive �le.
Several delete processes run simultaneously, because write program create new archive �les faster than they can be processed by the delete
program
Archiving Procedure
Creation of archive �les
In the write phase the data to be archived is written sequentially into newly created archive �les.
Delete from the database
The delete program reads the data from the archive �les and then deletes it from the database.
Storage of archive �les (optional)
The newly created archive �les can then be moved to a storage system or copied to a tape.
Data Reload (Optional)
Date can be read from Archive and inserted into DB again
Data Reload
The reloading function is only meant for emergency cases, e.g. in which the wrong data was archived due to errors in Customizing or during
document selection.
If you reload the data later you may end up with inconsistencies in your database.
Archiving Objects (AM_ASSET and AM_STEUER)
Archiving Objects
The archiving object is a central component of SAP Data Archiving.
speci�es precisely which data is archived and how
describes which database objects must be handled together as a single business object
interprets data irrespective of the technical speci�cations at the time of archiving (such as release and hardware)
Data in the database can only be archived using archiving objects, which describe the data structure and context.
Data Object
A data object is the application-speci�c instance of an archiving object, that is, an archiving object �lled with concrete application data.
https://help.sap.com/docs/disclaimer
4/11/2024
217This is custom documentation. For more information, please visit the SAP Help Portal
The archiving object only describes the data structure, that is, it determines which data belong logically together, whereas the data object contains
real data from the database (e.g. all table entries belonging to a Financial Accounting document).
A data object incorporates all application data that is necessary to archive a business object (master data or transaction data) completely and
consistently.
A typical data object is composed of a:
Header containing general information for identifying the data object, and a
Individual items that contain the actual application data
Archiving Objects AM_ASSET & AM_STEUER
Archivin object for archiving asset data is AM_ASSET.
This object contains all
master data
transactions
values
that are associated with an asset in the database.
It does not include any control tables (Customizing).
Structure of AM_ASSET
AM_ASSET has (basically) the following table structure:
AM_ASSET also contains asset long texts andchange documents.
Sub Objects to AM_ASSET
AM_ASSET tables are grouped together into sub-objects. The archiving program checks these sub-objects to see if they should be archived and
reorganized according to the de�ned retention period. If a sub-object is to be deleted, the program deletes all the data records in the tables that
belong to the sub-object in a second step.
Depreciation Posting Values (ANLP)
The ANLP sub-object contains information on one depreciation posting run for each asset and depreciation area. (ANLP becomes
meaningless once the next depreciation posting run is carried out)
The archiving program archives the ANLA, ANLH, ANLB, ANLC, ANLT and ANLZ table entries for each ANLP record.
Transactions, Annual Values, and Change Documents (ANLC, ANEK, ANEP, ANEA)
Because it logically belongs together, the system considers this information as a single sub-object for reorganization. Archiving program
always archives the complete asset object (all tables except ANLP) here.
https://help.sap.com/docs/disclaimer
4/11/2024
218This is custom documentation. For more information, please visit the SAP Help Portal
Complete Asset
The complete asset object contains all the tables of the AM_ASSET archiving object, including master data. All the archiving object tables are
archived and deleted. All change documents and long texts are also cleared along with the asset.
Note: The archiving program does not allow you to archive only selected sub-objects. You can't for instance, archive only depreciation posting values.
The program always archives all sub-objects that are eligible for archiving according to their de�ned minimum retention period.
Dependent Objects
Archiving object AM_ASSET is always archived together with AM_STEUER.
AM_STEUER contains customizing tables that can be made available for a possible later further development of asset archiving.
You must, therefore, also maintain the technical settings for the archiving object AM_STEUER (such as the logical �le path) in asset archiving.
Preparing to Archive
Before you start archiving Asset Accounting, basic settings for archiving - such as �le names, storage location, system, etc. - for Objects AM_ASSET
and AM_STEUER must be maintained.
Archive Administration (transaction SARA).
Data Retention Periods
Standard Retention Period
Depreciation posting values
is only relevant in current FY -> system reorganizes or archives this data during the �rst reorganization run after the �scal year has been
closed
Transactions, annual values, and change documents
It may be necessary to reverse the year-end closing more than once in order to be able to correct postings. Therefore, the minimum retention
period of these objects is extended to a year beyond the year-end closing. This means that these objects can only be cleared after the close of
the following �scal year
Complete asset
The earliest that a complete asset can be cleared is when it is deactivated and none of its depreciation areas contain values. The minimum
retention period is extended to a year beyond the close of the year in which the asset is deactivated
Customer-Speci�c Retention Periods
In addition to standard retention periods, customer can specify own retention periods for transactions or values. (SARA or IMG FI-AA ->
Master Data -> Archiving ? Specify retention periods for archiving). The actual retention period is the sum of this retention period and the
standard system retention period of one year.
Example:
 Deactivated asset: 3/1/YYYY
 System retention period: 1 year
 Customer retention period: 1 year
 The earliest that an asset can be reorganized is in the �scal year YYYY plus three years. The number three comes from adding a year each for the
year following the deactivation year, the system retention period, and the customer retention period.
https://help.sap.com/docs/disclaimer
4/11/2024
219This is custom documentation. For more information, please visit the SAP Help Portal
Retention Period for Assets Under Construction with Line Item Management
Assets under construction with open item management are handled somewhat differently than other assets during archiving. You can delete
transactions and annual values for these assets only when the asset under construction is deactivated.
Retention Period for Assets with History Management
Assets with history management (indicator in the asset master record) are handled like assets under construction with open-item
management.
Retention Period for Capital Investment Measures
Assets under construction for capital investment measures can only be deleted when the accompanying Controlling (CO) object (internal
order, WBS element) is deleted.
Archiving Authorizations
To archive data in Asset Accounting, user must have the following authorizations:
Archiving in general
 For more information, see User Authorization Checks.
Authorization object S_ARCHIVE with
Activity: 01 (creating, reloading, deleting, and reading archive �les)
Application area: FI
Archiving object: AM_ASSET, AM_STEUER
Authorization object A_PERI_BUK with
Activity 37 (archiving)
Activity 38 (reloading)
Archiving Data
Create Variant for Write Program
1. Test run without archive �le (simulation of archiving). Result is a statistic using the table entries which would be archived during a program
run.
2. Test run with archive �le (Create archive without database changes). Note: No removal of data from archives created this way from database
using the delete program.
3. Update run (Create archive with database changes). Archive File will be created
Write Data
https://help.sap.com/docs/disclaimer
4/11/2024
220This is custom documentation. For more information, please visit the SAP Help Portal
Select Variant
Output
Only containing summarized information
https://help.sap.com/docs/disclaimer
4/11/2024
221This is custom documentation. For more information, please visit the SAP Help Portal
Special Logic FI-AA
Asset Accounting archiving only archives entire �scal years.
A feature of this is that not all data that is archived is necessarily deleted from the database. Asset master records, for example, are not deleted.
They are archived but table entries for master records are only deleted from the database if the �xed asset is deactivated and the prede�ned
retention period has been exceeded for this subobject.
Reason: accessing data later on by standard reports only have to consider one data source. Either database or archive �le.
Advantage: improves runtime in reporting
Disadvantage: partially double storage of data in both sources
Store Data
If no automatic storage is activated.
It is con�guration if storage is done before or after deletion. Recommended: before!
Delete Data
If no automatic deletion is activated.
It is con�guration if storage is done before or after deletion. Recommended: before!
https://help.sap.com/docs/disclaimer
4/11/2024
222This is custom documentation. For more information, please visit the SAP Help Portal
note:
If you want to save archive �les for the AM_STEUER archiving object in an external �ling system, you must set either 'Delete before storing' or
'Storage before delete phase' together with 'Delete Program reads from storage system' in the archiving object-speci�c Customizing under
"File storage in storage system". Otherwise the archive �les will not be deleted from the exchange directory after storage.
Managing Archiving Sessions
https://help.sap.com/docs/disclaimer
4/11/2024
223This is custom documentation. For more information, please visit the SAP Help Portal
Error Messages
Common Problems and Error Messages
a. Nametab for Structure T092O does not exist (BA 123)
You tried to determine the nametab for structure T092O. The system could not �nd any nametab for structure T0920. To correct this, execute
program RAARCH00 (see Note 36712).
b. After an error, an operation was performed on a handle (BA 235).
To correct this, execute program RAARCH00 (see Note 665043).
c. Selectan active archive �le key (BA 018)
You want to run an asset report for a given �scal year. This error occurs if asset accounting for the relevant company code was not yet active.
Meanwhile, because of the retention period set for annual values and transactions, this �scal year should have been included in the archiving
sessions the system has already performed. In this case the archiving session does not create an archive �le. Only run archive evaluations in
Asset Accounting if the company code is already active in the appropriate �scal year.
Access to archived data
Standard FI-AA reports
Depreciation Log
Archive Explorer in Archive Information System (SARI) (see note 385694)
Archive File Browser (AS_AFB)
Adminsitrative FI-AA Archive Information
All Fixed Asset Reports using the logical database ADA can read data from Archive.
Archive run information stored in T093R:
https://help.sap.com/docs/disclaimer
4/11/2024
224This is custom documentation. For more information, please visit the SAP Help Portal
Logic
Dynamic Selections in Reports
As described in Note 372445, dynamic selections in the archive reports are ignored by the standard reports.
This problem is eliminated as of Release MySAPERP2007 as part of an enhancement of the archive reports for access using an archive index (Note
954189). As of this release, dynamic selections are no longer ignored in archive reports in the SAP standard system.
Depreciation Log
After successfully archiving and deleting the data from the application tables, ?old" report "Restore log for a depreciation run" (RABUCH30) can no
longer be used for the archived years.
This because the application data for the posted depreciation (table ANLP) is immediately deleted for all closed �scal years. Depreciation Log
RABUCH30 can not read data from the archive but needs the ANLP data from the �scal year evaluation period to create the log.
As of Release R/3 Enterprise (4.70), a the ?new" report (RAPOST2001) has been developed which can display the log for archived years. This report
is able to read data from Archive.
https://help.sap.com/docs/disclaimer
4/11/2024
225This is custom documentation. For more information, please visit the SAP Help Portal
Archive Explorer - SARI
Archive File Browser - AS_AFB
https://help.sap.com/docs/disclaimer
4/11/2024
226This is custom documentation. For more information, please visit the SAP Help Portal
Additional Information
You can also �nd a detailed description of archiving within Asset Accounting in the SAP Library under Cross-Application (CA) Components ->
Archiving Application Data -> Financial Accounting (FI) -> Archiving FI Asset Data.
Important notes:
954189 Archiving: Usage of Archive Index in standard reports
389920 Overview of Asset Accounting archiving
385694 Archive information system in Asset Accounting
Directory of Asset Reports
Directory of Asset Reports
The table below lists the main reports used in Asset Accounting
Report
Name
Transaction
Code
Program Name Description and Comments
Asset
Balances
AR01 RABEST_ALV01 Lists out asset records with their cumulative APC, depreciation and NBV.
Asset
History
Sheet
AR02 RAGITT_ALV01
Displays asset records and their associated balances based on a con�gurable layout. This allows you to gain
visibility into any type of asset transaction such as Write-Ups or Special Depreciation.
Total
Depreciation
AR03 RAHAFA_ALV01 Displays asset records with a breakdown of all available depreciation values such as Ordinary, Special, and
Unplanned depreciation.
 
Include own �elds in FI-AA standard ALV
Include additional �elds in Standard Fixed Asset ALV reports
Author: D033258, SAP AG 
How to include additional �elds in standard reports.
Every Fixed Asset ALV report has a prede�ned Field catalogue structure with the naming convention
https://help.sap.com/docs/disclaimer
4/11/2024
227This is custom documentation. For more information, please visit the SAP Help Portal
 FIAA_SALVTAB_xxxxxx *
Examples:
Asset Balances -> FIAA_SALVTAB_RABEST (out of RABEST_ALV01)
Asset History Sheet -> FIAA_SALVTAB_RAGITT (out of RAGITT_ALV01)
Asset Transaction List -> FIAA_SALVTAB_RABEWG (out of RABEWG_ALV01)
Planned depreciation List -> FIAA_SALVTAB_RAHAFA (out of RAHAFA_ALV01)
Customer owned structures
Every prede�ned Field catalogue FIAA_SALVTAB_XXXXXX includes a customer owned structure
 CI_REPxxxxxx *
Examples:
FIAA_SALVTAB_RABEST includes CI_REPRAZUGA (out of RABEST_ALV01)
FIAA_SALVTAB_RAGITT includes CI_REPRAGITT (out of RAGITT_ALV01)
FIAA_SALVTAB_RABEWG includes CI_REPRABEWG (out of RABEWG_ALV01)
FIAA_SALVTAB_RAHAFA includes CI_REPRAHAFA (out of RAHAFA_ALV01)
Procedure to include additional �elds
Procedure in the example of program RABEST_ALV01 (out of note 335065):
1. Call up the ABAP Dictionary (Transaction SE11) and enter 'Data type' FIAA_SALVTAB_RABEST.
2. Select Include CI_REPRABEST (double-click).
3. In the table, enter the �elds which you want the system to include additionally in the report.
4. Activate the change.
5. When you next start the program, change the layout.Copy the new �eld from the column set to the column selection.
->Result: the system displays the �eld in the output list.
Restrictions and Recommendations
Restrictions
-> You can always only include �elds that are transferred to the report by the logical database. These are typically �elds of structures
ANLAV [containing ANLA (Asset Master), ANLZ (time-dependent data) and ANLU (user-de�ned �elds)] and
ANLB.
->This method is not available for report RASIMU02. Read Note 427827 for an enhancement of RASIMU02.
Recommendations
-> Transfer only the �elds actually required since every added �eld impairs the performance.
-> The �elds that are additionally included are supplied with values within the program by a MOVE-CORRESPONDING statement. That is why it is
necessary to designate the added �elds to the exact corresponding �elds of the original tables or original structures.
-> The component type also has to agree to ensure a correct format. Therefore, always check the names of the �elds in the initial structures
(ANLAV, ANLB) and which type they are. Then copy the entries to the CI_REPRA... structure identically.
-> For �elds that contain either currency amounts or quantity speci�cations, you have to specify reference tables and reference �elds. You can assign
the reference �elds on the Currency/quantity �elds tab page.
-> Activating CI_REPRA...-structure usually leads to warning messages, because you insert �elds in SAP namespace in a customer owned structure.
You can ignore these warnings here and activate the structure even so.
Ordinary �elds
a) Asset description long text (in structure ANLAV) and
b) Depreciation key (in structure ANLB)
https://help.sap.com/docs/disclaimer
4/11/2024
228This is custom documentation. For more information, please visit the SAP Help Portal
Warning Message during activation
Date Fields
a) Deactivation date (in structure ANLAV) and
b) Acquisition date (in structure ANLAV)
https://help.sap.com/docs/disclaimer
4/11/2024
229This is custom documentation. For more information, please visit the SAP Help Portal
Quantity Fields I
Quantity and unit of measure (in structure ANLAV)
Quantity Fields II
In addition, you also have to enter 'ANLA' as reference table and 'MEINS' as reference �eld for the quantity �eld on the Currency/quantity �elds tab
page.
https://help.sap.com/docs/disclaimer
4/11/2024
230This is custom documentation. For more information, please visit the SAP Help Portal
Currency Fields I
Asset scrap value (in structure ANLB)
Currency Fields II
In addition, you also have to enter 'T093B' as reference table and 'WAERS' as reference �eld for the quantity �eld on the Currency/quantity �elds tab
page.
https://help.sap.com/docs/disclaimer
4/11/2024
231This is custom documentation. For more information, please visit the SAP Help Portal
Changing Layout I
Changing Layout II
https://help.sap.com/docs/disclaimer4/11/2024
232This is custom documentation. For more information, please visit the SAP Help Portal
Changing Layout III
Changing Layout IV
https://help.sap.com/docs/disclaimer
4/11/2024
233This is custom documentation. For more information, please visit the SAP Help Portal
SAP List Viewer Basics
Abbreviations
Important Abbreviations
- ALV = SAP List Viewer (originally ABAP List Viewer)
Types of ALV Lists - ALV Classic
The SAP List Viewer uni�es and simpli�es the use of lists in the R/3 System. A uniform user interface and list format is available for all lists. This
prevents redundant functions. The SAP List Viewer can be used to view both single-level lists and multilevel sequential lists.
Single-level lists contain any number of lines that have no hierarchical relationship to each other (e.g. Asset Balances RABEST_ALV01).
Multilevel sequential lists consist of any number of lines that have two hierarchical levels. Multilevel lists have header rows and item rows;
the item rows are subordinate to the header rows. For each header row there can be any number of subordinate item rows (e.g. Asset
Transaction List RABEWG_ALV01).
The list layout can be chosen as ALV Classic display or ALV Grid display. Restrictions:
The ALV Grid Control does not allow you to display block or hierarchical lists (Problem for transaction lists, e.g. RABEWG_ALV01).
Currently, simple lists can be displayed in single-line format only (problem for Asset History Sheet RAGITT_ALV01). However, users can de�ne
multiple-line format in the print preview and print the list as such.
Examples:
Single-level lists
- Asset History Sheet Classic
- Asset History Sheet Grid
Multilevel lists
- Asset Transaction List Classic
Features Overview
1. Navigate within the List
2. Choose Details
3. Sort in Ascending/Descending Order
4. Select and Deselect Rows
5. De�ne Exceptions
6. Set and Delete Filters
https://help.sap.com/docs/disclaimer
4/11/2024
234This is custom documentation. For more information, please visit the SAP Help Portal
7. Display and Delete Sums
8. Create Subtotals
9. Choose Summation Levels
10. De�ne the Breakdown of the Summation Levels
11. Display the List Status
12. Optimize the Column Width
13. Freeze to Columns and Unfreeze Columns
14. ABC Analysis
15. Spreadsheet
16. Text Processing
17. Use Layouts
18. Find Terms
19. Print Lists
20. Send the List as a Document
21. Transfer a List to a Local File
Navigate within the list
When you call up a list with the List Viewer, the columns are displayed from left to right if they �t within the window. In large lists in which not all the
columns can be displayed initially, you can do the following:
Display the columns on the left or right side of the list (First column or Last column)
Scroll horizontally through the columns (Column left or Column right)
First Column/Last Column
1. (Choose Last Column) to go to the column on the right side of the list.
2. (Choose First Column) to go back to the column on the left side of the list.
Column Left/Column Right
3. (Choose Column Right) to shift the display one column to the right.
The column on the left side is hidden, and a new column is displayed on the right side. This enables you to scroll from left to right through the
columns of the report.
4. (Choose Column Left) to shift the display one column to the left.
The column on the right side is hidden, and a new column is displayed on the left side. This enables you to scroll from right to left through the
columns of the report.
The lead columns, together with any other columns you specify with Freeze to column, are always displayed independently of the First Column / Last
Column / Column Left / Column Right functions. (See: Freezing to Columns and Unfreezing Columns).
Choose Detail
1. To obtain detailed information about a line, position the cursor on the appropriate line and choose Choose detail . You obtain further
information about the line, including information which is not in the current list.
2. You cannot use the Choose Detail function on subtotals.
3. Depending on the list, you can also execute this function with a single or double click on the row.
Sort in Ascending/Descending Order
Sorting Single Rows in a Column in the List
1. Select a column by clicking on the column header.
2. Choose Sort in Ascending Order or Sort in Descending Order .
If you use this procedure in a multilevel sequential list, you can sort by a maximum of one header column and one subordinate row.
https://help.sap.com/docs/disclaimer
4/11/2024
235This is custom documentation. For more information, please visit the SAP Help Portal
Sorting According to Multiple Columns or Fields Not Displayed
1. Choose Sort in Ascending Order or Sort in Descending Order .
2. The dialog box De�ne Sort Order appears. It shows the �elds you can sort. Fields are also available that are not shown in the list.
3. To select �elds for sorting, select the relevant rows and choose Show Selected Fields (arrow key ). The selected �elds then appear in the dialog
box as sorting �elds.
4. You select the sorting �elds in multilevel sequential lists separately for header and item.
5. The sequence in which the sort �elds are shown determines the sequence in which the columns are sorted. To change the sequence of the �elds,
use the functions Cut and Paste.
6. Use the radio buttons to specify whether the report rows are to be sorted in ascending or descending order within the column.
7. Exit the dialog box with Copy.
8. You can also use the List Status (Settings->List Status) function for an overview of the selected sort criteria.
De�ning Exceptions
Some lists contain rows that are highlighted by red, yellow, or green traffic lights. The signi�cance of the row indicators depends on the list (example
report BCALV_GRID_04).
You can sort, create subtotals, or set �lters with reference to these exceptions.
With totals rows , exceptions can be passed on.
Set and Delete Filters
The Set Filter function enables you to display only those rows that ful�l certain criteria in one or more columns.
Setting Filters
1. To set a �lter, select one or more columns by clicking on the column header and by choosing Set Filter .
2. In the Set Filter dialog box, enter the From/To values for each column selected. Only rows with data within the intervals speci�ed are shown.
3. Use Multiple Selection to enter more than one interval for a column. Use tabs to include values or tabs to exclude values from the
Selection.
Deleting Filters
1. To delete entries for a �lter criterium, position the cursor on the appropriate line and choose Delete Selection .
2. To delete all the entries for the �lter, choose Delete All Selections .
3. Choose Execute to copy the �lter criteria and exit the dialog box.
4. To go back to the pre�ltered list display, choose Edit -> Delete Filter on the Basic List.
Display and Delete Sums
You can sum one or more columns in the list. The sums can be for value columns and for quantity columns. If you sum incompatible units such as
kilograms and liters, a separate sum is shown for each unit. You can display sums in multilevel sequential lists via column headers or via their
subordinate rows.
Displaying Sums
1. Select the desired columns in the list by clicking on the respective column headers.
2. Choose Display Sum 
Note that the system can only sum columns containing values or quantities.
https://help.sap.com/docs/disclaimer
4/11/2024
236This is custom documentation. For more information, please visit the SAP Help Portal
Deleting Sums
1. Select the desired columns by clicking on the respective column headers.
2. Choose Display Sum 
Depending on the list, the totals row may contain information in addition to that of the summation level, if a number of asterisks are shown.
 
Depending on the list, the subtotals can also be shown above the totaled rows. This is only possible with single-level lists.
Create Subtotals
You can create subtotals in oneor more columns in the list that are not value columns. This function is also available for �elds that are not in the list.
You can create subtotals in sequential lists for column headers but not, however, for their subordinate rows.
Prerequisites
Before you can create a subtotal, you must have created a total for at least one column (see Display and Delete Sums).
Creating Subtotals for One Column
1. Select the columns for which you require subtotals by clicking on the column header.
2. Choose Subtotal 
Creating and Deleting Subtotals for More Than One Column
1. Choose Subtotal . The dialog box De�ne Sort Order appears.
2. The dialog box De�ne Sort Order shows the �elds you can create subtotals on. Fields are also available that are not shown in the list.
3. To select �elds for subtotaling, select the relevant rows and choose Show selected �elds (arrow key ). The selected �elds then appear in the
dialog box as sorting �elds.
4. To delete the calculation of subtotals for individual �elds, select the corresponding rows in Sorting Fields in the dialog box, and choose Hide
Selected Fields (arrow key ). The selected �elds then appear in the dialog box under Field List.
5. The sequence in which the selected �elds are shown in the dialog box determines the sequence in which subtotals are created. To change the
sequence of the �elds, use the functions Cut and Paste.
6. Specify whether the rows on which a subtotal is calculated are to be sorted ascending or descending. Also set the indicator for subtotals and the
control break (page change or underline) .
7. Exit the dialog box with Copy.
Depending on the list, the subtotals rows may contain information in addition to that of the summation level, if a number of stars ("*") are shown.
Depending on the list, the subtotals can also be shown above the subtotaled rows. This is only possible with single-level lists.
Choose Summation Levels
You can create subtotals in one or more columns in the list provided you have already totalled at least one column.
Procedure
1. Choose Settings -> Summation Levels -> Choose.
2. A list appears in a dialog box showing the columns for which the subtotals were created, together with the summation level.
3. To sort the list, choose Sort in Ascending Order or Sort in Descending Order.
4. To carry out a search in the list for certain terms, choose Find.
5. Select the subtotals to be displayed. Select All displays all the subtotals; Deselect All suppresses them.
6. Exit the dialog box with Copy.
De�ne Breakdown of Summation Levels
https://help.sap.com/docs/disclaimer
4/11/2024
237This is custom documentation. For more information, please visit the SAP Help Portal
If you have created subtotals in one or more columns, you can restrict the list to certain subtotals rows.
Procedure
1. Choose Settings -> Summation Levels -> De�ne Breakdown. A list appears in a dialog box showing the subtotals together with the
summation level.
2. To sort the list, choose Sort in Ascending Order or Sort in Descending Order.
3. To search in the list for certain terms, choose Find.
4. In the dialog box, choose the summation level from which the sutotals should be displayed in the list by clicking on the appropriate row in the
Level column.
Example
You have created subtotals in two columns of the list. In the dialog box, summation levels 0 to 2 are proposed. If you choose summation level 2, the
subtotals of level 2 only will be displayed. If you choose summation level 1, the subtotals of both levels 1 and 2 will be displayed.
Display List Status
To display the list status, choose Settings -> List Status.
Result
The list status provides the following information:
The columns for which the current list was sorted in ascending or descending order
The columns for which subtotals were created
Which �lter criteria were set
How many records were passed
How many records were hidden by the �lter
How many total records were calculated
- To carry out a search in the columns displayed for certain terms, choose Find.
- To print the list choose Print.
Optimize Column Width
To adapt the column width to the entries in the columns regardless of the settings in the layout (see Changing Layouts), choose Settings -> Columns
-> Optimize Width.
Result
After optimizing the column width, the columns are displayed as narrowly as possible in order to include the maximum amount of information in the
display screen.
If a list is already displayed with optimized column width in the standard system, you can alter the column width according to your requirements
using Change layout . To revert to the optimized column width, choose Settings -> Columns -> Optimize Width.
Optimizing the column width can result in the text for a totals row or subtotals row not being output in the full length. To achieve full output of the
text, you must increase the width of the column with Change layout .
Freeze to Columns and Unfreeze Columns
Fixed columns are always displayed independently of the First Column, Last Column, Column Left and Column Right functions (see Navigating
Within the List). In the standard system, all the lead columns of the list are �xed. However, you can �x further columns via the lead columns.
Freezing to Columns
1. Select the column to which you want to freeze the table by klicking on the column header.
2. Choose Settings -> Columns -> Freeze to Column. The columns of the table are frozen from the left to the column selected.
Unfreezing Columns
If the table was frozen to a non-lead column, you can undo this by choosing Settings -> Columns -> Unfreeze Columns.
https://help.sap.com/docs/disclaimer
4/11/2024
238This is custom documentation. For more information, please visit the SAP Help Portal
ABC Analysis I
ABC analysis groups objects within a list according to their signi�cance in regard to a particular numerical key �gure. ABC analysis is available with
single-level lists if the list has at least one key �gure.
Features
ABC analysis allows the grouping of objects in three segments:
A segment = important objects
B segment = less important objects
C segment = relatively unimportant objects
The object to be grouped must have a value for at least one key �gure. In ABC analysis the objects are �rst sorted in ascending or descending order
with reference to a preselected key �gure. Then the list is subdivided using a prede�ned strategy. The following strategies can be used for grouping:
Key �gure -> percentage
Key �gure -> absolute
Characteristics -> percentage
Characteristics -> absolute
The number of objects to be assigned to the A and B segments is speci�ed by the user. The remaining objects are assigned to the C segment.
ABC Analysis II
Activities
To perform ABC analysis:
1. Select a key �gure column in the list to be used as the criteria for ABC analysis by positioning the cursor on the column header.
2. Choose ABC analysis . A dialog box appears showing the key �gure you selected that is used as the basis for ABC analysis. The
characteristics of the columns that are in the list to the left of the selected key �gure column.
3. Choose the type of sorting (ascending or descending) and the strategy for grouping. Specify values for the grouping within the selected
strategy.
Result
A list is displayed with the segment (A, B, or C) in the �rst column. This is followed by the object and further characteristics (such as the order type)
and the selected key �gure. After each key �gure the percentage share of that key �gure on the total is shown, along with the cumulative
percentage share. In addition, the list contains the total and the subtotals for the segments and for the totals of the A and B segment and for the B
and C segment.
A number of functions are available in the results list of ABC analysis:
Hide columns -> This functions allows you to remove selected characteristic columns from the visible display. The cursor must be positioned in
the column and then the function accessed.
Show columns-> This function allows you to display the columns you previously hid with the Hide columns function.
All characteristics -> If the characteristic columns in the list are to the right next to the selected key �gure column when ABC analysis is
accessed, these characteristics are not shown in the results list at �rst. Choosing All characteristics displays these characteristics in the
results list.
Print -> This function prints the results list of ABC analysis. The printout corresponds to the screen display - hidden columns are not shown in
the printout.
New analysis -> This function initiates a new ABC analysis on the same objects.
End / back -> This function returns you to the initial list.
Spreadsheet
This function passes data across the XXL interface. If you want to do this, you must �rst decide what you want to do with the data. You can:
Save the data as a SAPoffice document
Save the data as a PC �le
Transfer the data to Excel
https://help.sap.com/docs/disclaimer
4/11/2024
239This is custom documentation. For more information, please visit the SAP Help Portal
This function is available in single-level lists.
Prerequisites
Before you can transfer data into a spreadsheet program, you must install this program.
If you perform a download in Excel without �rst installing Excel, a �le is saved in the proper format but is not downloaded.
Activities
Perform the function !i20.gif!when you want to transfer data to the XXL interface.
When you transfer data to Excel, the columns may be resorted so that they are shown in Excel sorted according to characteristics and key �gures.
Note that totals rows are not included when data are transferred to the XXL interface.
Also note that the list formatting functions of the SAP List Viewer are not available when data are transferred to the XXL interface into Excel. For
example, there are no �lter functions in the Excel list, nor is it possible to show exceptions or row markings in Excel.
Text processing
Text processing offers two different functions:
Form letters with MS Word
Creating a document
This function transfers the currently displayed list to the presentation server as an RTF �le. The format allows the use of the �le as a Word
document. You can specify whether colors are included in the list and whether MS Word is started immediately. You specify the full path for the �le.
Text processing is available in single-level lists.
Prerequisites
The form letter function and the immediate start of Word when a document is created are only available if MS Word is installed on the PC.
Activities
Start text processing from the list display and choose whether you want form letter processing or creation of a document.
Note that wide lists may be cut off at the margin.
All settings that you have on the list are transferred into the Word document. For example, hidden rows and columns are not transferred into the
Word document.
Use Layouts
You change the display of your list using layouts.
The layouts that you can use vary according to the type of list: In all lists, you can do the following:
Choose one of the standard layouts supplied with the standard system.
Change the current layout of the list.
In lists that use only the standard layouts in the standard system, you cannot save your changes to the current layout. When you choose the
layouts, only the standard layouts will be proposed.
In some lists, you can also save the layouts that you have de�ned as your own layouts.
User-de�ned layouts are generally saved for all users. They can then be used by all users. All users will be able to choose from the user-
de�ned layouts as well as the standard layouts.
In some lists, you can also save user-speci�c layouts that you have de�ned. When you choose the current layout, only these layouts are
available to you.
You can delete or transport layouts, or de�ne them as initial layouts.
Choose Layout
To choose an existing layout for the display of the list, choose Select Layout . A list of the existing layouts is displayed. In the standard setting, an
entry is made for each layout specifying whether this layout was saved as follows:
With sorting
With subtotals
With �lter conditions
As a user layout
https://help.sap.com/docs/disclaimer
4/11/2024
240This is custom documentation. For more information, please visit the SAP Help Portal
You can manipulate the layout list using the following SAP List Viewer functions:
Choose Detail
Sort in Ascending Order or Sort in Descending Order
Set Filter or Delete Filter
Change layout
Find
In the dialog box, choose a layout either by clicking the layout name or by positioning the cursor on the relevant layout and choosing Copy.
Change Layout
To change the layout, choose Change layout . The Change Layout dialog box shows you which columns are currently displayed and which
additional columns can be displayed. Multilevel sequential lists also distinguish between the �elds in the header rows and those in the item rows. You
change the layout in multilevel sequential lists separately for header rows and item rows.
1. To show or hide columns in the list, the following functions are available:
With Hide All Fields , you can hide all �elds with the exception of the key �elds. The �elds appear under Hidden �elds, while the only �elds
displayed are the key �elds.
To show all the hidden �elds, choose Show All Fields . The �elds appear as display �elds, while the list of hidden �elds is empty.
To show separate �elds, select the relevant rows of the hidden �elds and choose Show Selected Fields . The �elds are transferred from the
hidden �elds to the displayed �elds.
To hide separate �elds, select the relevant rows of the display �elds and choose Hide Selected Fields . The �elds are transferred from the
display �elds to the hidden �elds.
2. The sequence of columns in the list is determined by the item number in the Item �eld. You cannot change the item numbers of key �elds.
3. In the Length of display �eld column, enter the required length, if this is to be different to the standard setting. If you have changed the length of
the display �eld and you now want to return this to the standard length, select the column and choose Get Standard Length .
4. If it is possible to create totals for a column (only for value and quantity columns), you can use the Total column in the display �elds to specify
whether they can be created in the layout for this column.
5. Using a clipboard, you can cut a �eld from the display �elds or hidden �elds and insert them in the required position. Only one �eld can be placed in
the clipboard. As soon as you cut another �eld, the �eld in the clipboard is assigned to the hidden �eld .
If you exit the SAP List Viewer without saving the layout, your settings will not be saved. When you next call up the list, the standard settings will
appear. You can no longer call up your layout.
Save Layouts
1. Choose Save Layout .
2. In the dialog box, enter a name and a description for your layout.
In general, layouts are available for all users as client-speci�c standard layouts.
The standard SAP layouts begin with a number.
Non-user-speci�c layouts (customer-speci�c standard layouts) begin with "/".
User-speci�c layouts begin with a letter from "A" to "Z".
-> If you have entered sort criteria, subtotals criteria or �lter conditions, you can save the layout with these criteria by selecting the checkbox.
-> Specify the summation level to which the list should be broken down when calling the layout. With the entry 0, all the non-totals rows are
displayed in addition to the totals rows and subtotals rows.
-> If a layout with the same name already exists, the system will inform you of this and you can either overwrite the existing layout (Continue) or
enter another name (New entry).
Display Basic List
You can revert to the standard settings of a list, if you have done the following:
Created your own layout
https://help.sap.com/docs/disclaimer
4/11/2024
241This is custom documentation.For more information, please visit the SAP Help Portal
Selected your own layout
Created totals or subtotals
Hidden totals or subtotals
Optimized the column width
Frozen columns
Procedure
To go back to the pre�ltered list display, choose Settings -> Basic List.
Print Preview
If you start a report with option "Use ALV Grid", you can change the output list to ALV Classic by choosing (only available on the ALV Grid output
list).
Procedure
To go back to the pre�ltered list display, choose Settings -> Basic List.
Find Terms
1. To carry out a search in the list for certain terms, choose .
2. In the dialog box, enter a name to be searched for in the list.
3. Specify whether the search should be carried out from the current line or in the current page.
4. Restrict the search to a maximum number of hits.
5. Choose Find.
The positions found are displayed in a dialog box. If you click on a line, the cursor is positioned on the relevant position in the list.
To continue searching terms with the same search criteria, choose .
Sending the List as a document
To send the list as a mail, choose .
In the initial screen Create Document and Send, the document name, description, and send date are preset. They can be overwritten.
Create a note for the list if you so desire.
Enter the name of the recipient and specify the name with the Type indicator.
Under Recipient, enter the name and distribution list or address or organizational unit.
To send the mail, choose Choose Send.
Transfer List to a local �le
1. Choose Local File .
2. Choose the �le format.
3. Choose Continue.
4. Enter the path and name of the �le in which you want to write the data.
5. Choose Transfer.
If you want to transfer data into a spreadsheet program, set the �le format to DAT.
Important Notes
598621 -> Page number not displayed in asset history sheet
381972 -> ALV totals list: problems when downloading to Excel
333257 -> Sort versions and additional display variants
324612 -> Problems with ALV lists in assets reporting
311846 -> No sort levels in ALV lists without value �elds
214763 -> Asset Accounting reports: 'or main numbers only' option
205095 -> No offset and length speci�cations with ALV
Asset Balances Classic Screenshot
https://help.sap.com/docs/disclaimer
4/11/2024
242This is custom documentation. For more information, please visit the SAP Help Portal
Asset Balances Grid Screenshot
Asset Transaction List Classic Screenshot
https://help.sap.com/docs/disclaimer
4/11/2024
243This is custom documentation. For more information, please visit the SAP Help Portal
Navigate within the List Screenshot
De�ne Sort Order Screenshot
https://help.sap.com/docs/disclaimer
4/11/2024
244This is custom documentation. For more information, please visit the SAP Help Portal
Set and Delete Filters Screenshot
Create Subtotals Screenshot
https://help.sap.com/docs/disclaimer
4/11/2024
245This is custom documentation. For more information, please visit the SAP Help Portal
Choose Summation Levels Screenshot
De�ne Breakdown of Summation Screenshot
https://help.sap.com/docs/disclaimer
4/11/2024
246This is custom documentation. For more information, please visit the SAP Help Portal
List Status Screenshot
ABC Analysis Screenshot
https://help.sap.com/docs/disclaimer
4/11/2024
247This is custom documentation. For more information, please visit the SAP Help Portal
Change Layout Screenshot
Select Layout Screenshot
Save Layout Screenshot
https://help.sap.com/docs/disclaimer
4/11/2024
248This is custom documentation. For more information, please visit the SAP Help Portal
Find Terms Screenshot
Print Preview Screenshot
Send the list as a document Screenshot
https://help.sap.com/docs/disclaimer
4/11/2024
249This is custom documentation. For more information, please visit the SAP Help Portal
Sort Variant de�nition in Asset Accounting reports
Purpose
As one selection parameter, 'Sort Variant' (sort version) can be used to highlight variable information in reports. e.g. Asset Balances, Asset History
Sheet and so on. Sort versions determine the sort keys and summation criteria for your asset reports. we can de�ne sort variant based on owe
business requests.
Overview
This document describes how to de�ne a sort variant and the meanings for the main settings of sort version.
Section 1
SAP delivers numbers of sort versions which you can take over or use as a reference for further versions:
1. Execute transaction OAVI to Adapt the standard versions to your requirements or create new sort versions according to your requirements using
Edit --> New entries
2. The key should begin with X, Y or Z.
3. Specify the sort hierarchy of the sort version via the sequence of �eld names in the �eld string proposed by the system (from top to bottom). You
can also specify length and offset for the individual �elds.
4. When you set the total indicator, the system subtotals at the speci�ed sort level.
5. Additional indicators allow for 
 - displaying totals per main asset number (with accumulated values of all sub-numbers)
 - sorting the sub-numbers per main asset number in descending order. In this way, the system displays the most recently created sub-number �rst
Related SAP Notes/KBAs
 
37755 - Reporting: missing texts for control levels
169755 - Texts for control levels, example of user exits
Trivia Incorrect Book Value in Asset Explorer and Asset History Sheet
Module: FI-AA (Financial Accounting - Asset Accounting)
https://help.sap.com/docs/disclaimer
https://me.sap.com/notes/37755
https://me.sap.com/notes/169755
4/11/2024
250This is custom documentation. For more information, please visit the SAP Help Portal
Issue: Incorrect book value in Asset Explorer and Asset History Sheet
Asset explorer: shows incorrect Fiscal year-end value
Retirement transaction of 594173,13 is not included in change
In the asset history sheet as on 31-12-2008 transfer using Transaction Type 340 is not subtracted from the book value at FY start to calculate the
current book value 
In the asset history sheet as on 30-11-2008 value of retirement transfer using Transaction Type 340 is subtracted from FY start book value to arrive
at the currency book value 
Table ANEP(Asset Line items) shows the correct net book value
Table ANLC (Asset Value Fields) displays incorrect values
Solution : Execute t-Code AS02, Open the asset master data and click the menu option Edit > Recalculate Values.
 
After Recalculation
Asset Explorer (Aw01n) shows the correct year end and change values 
Asset history sheet as on 31.12.2008 also stands corrected
Table ANLC is Updated
Use of Archive Index in FI-AA
Use of Archive Index in Fixed Asset Reporting
Archiving Procedure
Administrative Archive Information Fixed Assets
All Fixed Asset Reports using the logical database ADA can read data from Archive.
Archive run information stored in T093R:
https://help.sap.com/docs/disclaimer
4/11/2024
251This is custom documentation. For more information, please visit the SAP Help Portal
Logic
Database Select vs. Sequential Archive Read
https://help.sap.com/docs/disclaimer
4/11/2024
252This is custom documentation. For more information, please visit the SAP Help Portal
Database SELECT
Via the SELECT statement the limitation of result data is passed to DB and interpreted by DB. Database will return data records �tting to selection
criteria
Archive Read - Sequential read
As Archive data lies unstructured in �at �les, no limitation is possible. Archive �le has to be read sequential (record by record) and result will be
interpreted and checked
https://help.sap.com/docs/disclaimer
4/11/2024
253This is custom documentation. For more information, please visit the SAP Help Portal
Alternative: Archive Index
To solve the basic problem of necessary sequential read, ADK provides the possibility to create Archive Index Data. Archive Index is a database table
according to a certain Field Catalogue, which stores per each data object in an archive �lethe corresponding OFFSET start position.
If Archive Index is used, the reading program can directly navigate inside the Archive File to the position where the selected archive object begins.
Example: Archive Index
Archive Read - Index based read
https://help.sap.com/docs/disclaimer
4/11/2024
254This is custom documentation. For more information, please visit the SAP Help Portal
Archive Index is created during creation of archive automatically. 
Activating the Archive Index for AM_ASSET
1. Start the Archive Retrieval Con�gurator (SARJ)
2. Environment -> Fill Structure for info structure ?SAP_FIAA_ABRA"
3. Choose the archive Sessions for which Index should be created
4. Check created Index in SARE
Structure of SAP_FIAA_ABRA
- Company Code
- Asset Main Number
- Asset Sub Number
- Asset Class
- Asset Super Number
- Cost Center
- Plant
- Business Area
- Location
-> Runtime Improvement - compared to sequential read - estimated always if one of these �elds is limited in selection criteria
Use of sequential vs. index based read
If no Archive Index exists, sequential read is used.
If Archive Index exists, and limitation on at least one �eld from Info Structure is done, then Index is used.
If Archive Index exists, but no limitation on at least one �eld from Info Structure is done, then
a) if Archive File is used for only 1 company code (one occurency in T093R)
-> sequential read (complete �le has to be processed due to no narrowing limitation, less overhead with sequential read (e.g. no read from archive
index database table)
b) if Archive File is used for more then 1 company code (one occurency in T093R)
-> index based read
Miscellaneous
If Archive Index is not created, the complete archiving functionality is as all releases before. There will be no change in logic.
https://help.sap.com/docs/disclaimer
4/11/2024
255This is custom documentation. For more information, please visit the SAP Help Portal
No action to be done by the customer during upgrade. Use of Archive Index is an optional feature which can be activated and deactivated isolated
after the upgrade.
Archiving procedure itself is as before, there is no change due to use of Archive Index.
Additional Information
You can also �nd a detailed description of archiving within Asset Accounting in the SAP Library under Cross-Application (CA) Components ->
Archiving Application Data -> Financial Accounting (FI) -> Archiving FI Asset Data.
Important notes:
-> 954189 Archiving: Usage of Archive Index in standard reports
-> 389920 Overview of Asset Accounting archiving
-> 385694 Archive information system in Asset Accounting
All Other Information
All Other Information
This section covers all other topics within Asset Accounting. 
Asset Accounting Transaction Codes
AACCOBJ Display Active Acct Assgnmt Elements
AARC Archiving Asset Accounting
AART Reading of Archive Data
AATENV1 Create Data Collection
AATENV2 Create Test Cases
AATENV3 Execute Test Cases
AAVN Recalculate base insurable value
AB01 Create asset transactions
AB02 Change asset document
AB03 Display Asset Document
AB08 Reverse Line Items
ABAA Unplanned depreciation
ABAD Asset Retire. frm Sale w/ Customer
ABAD_OLD Asset Retire. frm Sale w/ Customer
ABAKN Last Retirement on Group Asset
ABAO Asset Sale Without Customer
ABAON Asset Sale Without Customer
ABAV Asset Retirement by Scrapping
ABAVN Asset Retirement by Scrapping
ABAW Balance sheet revaluation
ABAWN New value method
ABB1 Correction of Asset Accounts
ABCO Adjustment Posting to Areas
ABF1 Post Document
ABF1L Post Document in Ledger Group
https://help.sap.com/docs/disclaimer
4/11/2024
256This is custom documentation. For more information, please visit the SAP Help Portal
ABGF Credit Memo in Year after Invoice
ABGL Enter Credit Memo in Year of Invoice
ABIF Investment support
ABMA Manual depreciation
ABMR Manual transfer of reserves
ABMW Reverse asset trans. using doc. no.
ABNA Post-capitalization
ABNAN Post-Capitalization
ABNC Enter post-capitalization
ABNE Subsequent Revenue
ABNK Subsequent Costs
ABSO Miscellaneous Transactions
ABSO_OLD Miscellaneous Transactions
ABST Reconciliation Analysis FI-AA
ABST2 Reconciliation Analysis FI-AA
ABT1 Intercompany Asset Transfer
ABT1N Intercompany Asset Transfer
ABUB Transfer between areas
ABUM Transfer From
ABUMN Transfer within Company Code
ABUZSM Maintain Line Item Schema
ABZE Acquisition from in-house production
ABZK Acquisition from purchase w. vendor
ABZO Asset acquis. autom. offset. posting
ABZON Acquis. w/Autom. Offsetting Entry
ABZP Acquistion from affiliated company
ABZS Enter write-up
ABZU Write-up
ABZV Asset Acquis. Posted w/Clearing Acct
ACC01 Account Maintenance FI-AA
ACCMAP Convert Depreciation Areas
ACSET Maint.Acct Types for Acct Asgmt Obj.
AFAB Post depreciation
AFABN Post Depreciation
AFAF Assets with errors
AFAM_093B View Default Values for Valuation
AFAM_093C Company Code Default Values
AFAMA View Maint. for Deprec. Key Method
AFAMD View Maint. Declining-Bal. Method
AFAMH Maintain Maximum Amount Method
AFAMP View Maint. Period Control Method
https://help.sap.com/docs/disclaimer
4/11/2024
257This is custom documentation. For more information, please visit the SAP Help Portal
AFAMR View Maintenance Base Method
AFAMS View Maint. Multi-Level Method
AFAMSK Method: Levels in Calendar Years
AFAR Recalculate Depreciation
AFBN Include New Depreciation Area
AFBP Create depreciation posting log
AIAB AuC Assignment of Dist. Rule
AIAO C AM Maint. list vers. gen. line itm
AIAZ Display Dist. Rule Allocation
AIBU Transfer Asset under Const.
AIIO C AM Maintain List Version AuC
AIST Reverse Settlement of AuC
AJAB Year-End Closing
AJRW Fiscal Year Change
AM04 Changes to Asset Classes
AM05 Lock Asset Class
ANHAL Maintain Cutoff Value Key
ANK0 Ch.-of-Depr.-Dep. Asset Class Data
ANK1 Ch.-of-Depr.-Dep. Control Specif.
ANK2 Ch.-of-Depr.-Dep. Allocations
ANK3 Ch.-of-Depr.-Dep. Net Worth Valuat.
ANK4 Ch.-of-Depr.-Dep. Insurance Data
ANKA Directory of asset classes
ANKL Generate Asset Classes
ANKL_OLD Create Asset Classes from Accounts
ANSICHT Maintain Asset Views
ANSICHT00 Assignment Trans.Group - Asset View
ANVEST Maintain Investment Support Measures
AO11 Assign number range
AO21 Screen layout for deprec. areas
AO25 Unit-of-prod. depreciation
AO31 Specify Depreciation Area
AO32 Assign net worth tax area
AO33 Net worth tax �eld selection
AO41 Add to insurance speci�cations
AO42 Insurance �eld selection
AO51 Leasing �eld selection
AO52 Add to leasing entries
AO61 Assign user �elds
AO67 De�ne Transaction Type
https://help.sap.com/docs/disclaimer
4/11/2024
258This is custom documentation. For more information, please visit the SAP Help Portal
AO68 De�ne Transaction Type
AO69 Account assignmt. KTNAIB
AO71 Document type for posting deprec.
AO72 Specify posting procedure
AO73 De�ne Transaction Type
AO73_INV De�ne Transaction Type
AO74 De�ne Transaction Type
AO75 De�ne Transaction Type
AO76 De�ne Transaction Type
AO77 De�ne Transaction Type
AO78 De�ne Transaction Type
AO79 De�ne Transaction Type
AO80 De�ne Transaction Type
AO81 De�ne Transaction Type
AO82 De�ne Transaction Type
AO83 De�ne Transaction Type
AO84 De�ne Transaction Type
AO85 Account assignmt Acquisitions
AO86 Account assingmt. Retirements
AO87 Acct. Assignmt Revaluation on APC
AO88 Acct.Assignmt for Investment Support
AO89 Acct.assmt. not to curr ac.as.share
AO90 Account assignmt Acquisitions
AO90_OLD Account assignmt Acquisitions
AO91 Specify �eld group authorization
AO92 Logical �eld groups
AO93 Ord. Depreciation Acct Assignment
AO94 Special Depreciation Acct Assignment
AO95 Acct. assgnmt. Unplanned deprec.
AO96 Acct. assgnmt. Transfer of reserves
AO97 Acct. assgnmt. Reval. of deprec.
AO98 Acct. assignment Interest
AO99 Acct. assgnmt. Derived dep. areas
AO99_OLD Acct. assgnmt. Derived dep. areas
AOBK Depreciation areas/Reduction rules
AOBV Maint. of rules for delivery costsAOCO Cost center check (across co.codes)
AOLA Master Data Tab
AOLAPOST Tabstrip Posting Transactions
AOLK Tab Layout for Asset Master Data
APER_RESET Reset Periodic Posting Run
https://help.sap.com/docs/disclaimer
4/11/2024
259This is custom documentation. For more information, please visit the SAP Help Portal
AR01 Call Asset List
AR02 Call Up Asset History Sheet
AR03 Call Up Depreciation List
AR04 Call Up Depreciation + Interest List
AR05 Call Up Asset Acquisition List
AR06 Call Up Asset Retirement List
AR07 Call Up Asset Transfer List
AR08 Call Up Depreciation Compare List
AR09 Call Up Property List
AR10 Call Up Insurance List
AR11 Investment Grants
AR11N Investment Grants
AR12 Call Up Asset Directory
AR13 Call Up Prim. Cost Plan. Dep./Int.
AR14 Call Up Manual Depreciation List
AR15 Changes to Master Record
AR16 Changes to Asset Classes
AR17 Call Up Leasing Liability List
AR18 Call Up Depr.Simulation
AR19 Call Up List of Origins
AR20 Retirement comparison
AR21 Mid-quarter Alert Report
AR22 Analysis of retirment revenue
AR23 Italy: Asset register
AR24 Italy: Assets at 3rd party
AR25 Depreciation posted
AR26 Call up special reserve list
AR27 Call up: Group asset list
AR28 Call up asset history
AR29 Re- and New Valuation of Assets
AR29N Re- and New Valuation of Assets
AR30 Display Worklist
AR31 Edit Worklist
AR32 Call Create Worklist
AR32N Call Create Worklist
ARAL Display Application Log
ARMO Schedule Monitor: Asset Accounting
ARQ0 FIAA - Ad hoc reports
ART0 FIAA - Information System
AS01 Create Asset Master Record
https://help.sap.com/docs/disclaimer
4/11/2024
260This is custom documentation. For more information, please visit the SAP Help Portal
AS02 Change Asset Master Record
AS03 Display Asset Master Record
AS04 Asset Changes
AS05 Block Asset Master Record
AS06 Delete Asset Record/Mark for Delet.
AS08 Number Ranges:Asset Number
AS100 Legacy Data Transfer using Excel
AS11 Create Asset Subnumber
AS11_FMIM Create AuC Subnumber
AS21 Create Group Asset
AS22 Change Group Asset
AS23 Display Group Asset
AS24 Create Group Asset Subnumber
AS25 Block group asset
AS26 Mark group asset for deletion
AS81 Create Old Group Assets Data
AS82 Change old group asset
AS83 Display old group asset
AS84 Create legacy group asset subnumber
AS91 Create Old Asset
AS92 Change Old Asset
AS93 Display Old Asset
AS94 Create Legacy Asset Subnumber
ASCC Assets on My Cost Center - GUI Vers.
ASCC_GUI Assets on My Cost Center
ASEM My assets
ASEM_GUI My Assets - GUI Version
ASIM Simulation of asset posting
ASKB Periodic Asset Postings
ASKBN Periodic APC Posting Run
AT01 Create Asset Master Record (old)
AT02 Change Asset Master Record (old)
AT03 Display Asset Master Record (old)
AT11 Create Asset Subnumber (Old)
AT21 Create Group Asset (old)
AT22 Change Group Asset (old)
AT23 Display Group Asset (old)
AT24 Create Group Asset Sub-Number (old)
AT81 Create Old Group Asset (old)
AT82 Change Old Group Asset (old)
AT83 Display Old Group Asset (old)
https://help.sap.com/docs/disclaimer
4/11/2024
261This is custom documentation. For more information, please visit the SAP Help Portal
AT84 Display Old Group Asset Sub-No.(old)
AT91 Create Old Asset (old)
AT92 Change Old Asset (old)
AT93 Display Old Asset (old)
AT94 Create Old Asset Sub-Number (old)
AUFW Maintain Revaluation Measures
AUN0 FI-AA Asset Summary - Analysis of an asset and its environment
AUN1 FI-AA Asset Summary - Analysis of an asset and its environment: Postings
AUN10 FI-AA Asset Summary - Analysis of an asset and its environment: Fiscal Year Variant
AUN11 FI-AA Asset Summary - Analysis of an asset and its environment: Transfer/Line Item Schema
AUN2 FI-AA Asset Summary - Analysis of an asset and its environment: Value Determination
AUN3 FI-AA Asset Summary - Analysis of an asset and its environment: Posted Values
AUN4 FI-AA Asset Summary - Analysis of an asset and its environment: Legacy Data
AUN5 FI-AA Asset Summary - Analysis of an asset and its environment: Account Assignment
AUN6 FI-AA Asset Summary - Analysis of an asset and its environment: Insurance
AUN7 FI-AA Asset Summary - Analysis of an asset and its environment: Leasing
AUN8 FI-AA Asset Summary - Analysis of an asset and its environment: Investment Support
AUN9 FI-AA Asset Summary - Analysis of an asset and its environment: Screen Layout
AUVA FI-AA Incomplete Assets
AW01 Asset Explorer
AW01_AFAR Asset Explorer (old engine)
AW01_OLD Asset Master Rec: Display Val.Fields
AW01N Asset Explorer
F-90 Acquisition from purchase w. vendor
F-91 Asset Acquis. Posted w/Clearing Acct
F-92 Asset Retire. frm Sale w/ Customer
FAA_GENMAP Generate Mapping Methods
FB05_OLD Post with clearing
FBA7_OLD Post Vendor Down Payment
FBA8_OLD Clear Vendor Down Payment
FIAAHELP FI-AA Utility Programs
FIAAHELP_DARK FI-AA Utility Programs Dispatcher
J1AH Creating Way Bills
J1AI Asset Revaluation (In�ation)
J1AJ Print Way Bill Document
OA01 Gain/loss substitution -Fixed assets
OA02 Substitution: Mass Changes to Assets
OA03 C AM Asset Class Index
OA05 C AM Maintain Table T499S
OA07 Generate C AM BALTD Record Layout
https://help.sap.com/docs/disclaimer
4/11/2024
262This is custom documentation. For more information, please visit the SAP Help Portal
OA08 FI-AA: Maintain Country Table
OA11 C AM Asset Master Matchcode
OA13 FI-AA Legacy Data Transfer
OA14 Direct import of data
OA15 C AM Maintenance Table T094P
OA1X Asset Data Transfer
OA50 Maint. of rules for delivery costs
OA79 C AM Maintain Ast.Hist.Sheet De�n.
OA80 C AM Maint. Asset.Hist.Sheet De�n.
OA81 Maintain Transaction Types - Expert
OA84 Generate Period Control
OA85 C FI-AA: Weighting periods
OA90 AM: Asset Register
OAAQ Take back FI-AA year-end closing
OAAR C AM Year-end closing by area
OAAW FI-AA: Memo value for asset class
OAAX FI-AA: Asst class for grp asset only
OAAY FI-AA: Hist. layout set-asset class
OAAZ FI-AA: Settlement pro�le
OABC Depreciation areas/value transfer
OABD Depreciation areas/param. transfer
OABE Deprec. areas/gross transfer
OABK Delete asset class
OABL C AM Reset Company Code
OABM Depreciation areas/Transfer of resvs
OABN Depreciation areas/ordinary deprec.
OABR Maint. of rules for delivery costs
OABS Depreciation areas/Special deprec.
OABT Set Up Parallel Currencies
OABT_OLD Deprec. areas/parallel currencies
OABU Depreciation areas/Unplanned deprec.
OABW Depreciation areas/Replacement vals
OABX Deppreciation areas/Investmt support
OABY C AM Maintain Table T093Y
OABZ Depreciation areas / Interest
OAC1 C AM Leasing Types
OACB Customer name for evaluation group 1
OACC Customer name for evaluation group 1
OACD Customer name for evaluation group 1
OACE Customer name for evaluation group 1
OACF Customer name for evaluation group 1
https://help.sap.com/docs/disclaimer
4/11/2024
263This is custom documentation. For more information, please visit the SAP Help Portal
OACS C FI-AA View maint. substitutions
OACV C FI-AA View maint. validations
OADB De�ne Depreciation Area
OADB_WZ Set Up Parallel Valuation
OADC Depreciation Areas: Area type
OAGL Reset posted depreciation
OAI5 C FIAA Time-dependent inv. support
OAK1 C AM Consist. Chart of Depreciation
OAK2 C AM Consist. Company Code
OAK3 C AM Consist. Depreciation Area
OAK4 C AM Consist. G/L Accounts
OAK5 C AM Customizng reconc. acct. contrl
OAK6 C AM Consist. G/L accounts
OAK7 Reconc. acct. as stat. cost element
OAKA Standart texts in asset class
OAKB De�ne asset for gain/loss
OALX De�ne Long Text Templates
OAMK Change Reconciliation Accounts
OAOA FI-AA: De�ne asset classes
OAOB FI-AA: Assign company codes
OAP4 FI-AA: Description of chart of dep.
OAPL C FI-AA: Set Chart of Depreciation
OARC Maint. of retention periods FI-AA
OARK Archive Settings
OARP Call up of AM report overview
OASI FI-AA Implementation Guide (smart)
OASV Enter G/L Account Postings
OATB Asgmt of dep.area to cross-sys.area
OATR De�ne Report SelectionOAV5 Index �gures
OAV7 C AM Change Simulation Versions
OAV8 FI-AA C Def. Eval. Group, 8 places
OAV9 C AM Asset hist. group view maint.
OAVA C AM Eval. Group View Maintenance
OAVB C AM View Maintenance Prop.Indicator
OAVC C AM Manual Valuat. View Maintenance
OAVD C AM Insurance Data View Maintenance
OAVE C AM View Maintenance Classif.NWTax
OAVF C AM View Maint. Insurance Companies
OAVG C AM View Maint. Report Simul.(Dep)
https://help.sap.com/docs/disclaimer
4/11/2024
264This is custom documentation. For more information, please visit the SAP Help Portal
OAVH C AM View Maint. Period Control
OAVI C AM View Maint. Sort Versions
OAVJ C AM View Maint. Trans.Type Group
OAVL C AM View Maint. Locations
OAVM C AM View Maint. Field Groups
OAVN C AM View Maint. Fld.Grp. Asset Data
OAVO C AM View Maint. Screen Control
OAVP C AM View Maint. Deprec.Trace Texts
OAVR C AM View Maint. Dep.Check Rules
OAVS C AM View Maint. Period Rule
OAVT C AM View Maint. Insurance Premium
OAVX C AM view maint no.periods shtd f.yr
OAVZ C AM Call up report
OAW1 Reason for investment
OAW2 Maximum base value
OAW3 Translation method
OAWF Assign Work�ow Tasks
OAWT AW01- de�ne value �eld texts
OAXB Deprec. areas for transaction types
OAXC Deprec. areas for transaction types
OAXD Deprec. areas for transaction types
OAXE Deprec. areas for transaction types
OAXF De�ne Transaction Type
OAXG De�ne Transaction Type
OAXH Deprec. areas for transaction types
OAXI Deprec. areas for transaction types
OAXJ Deprec. areas for transaction types
OAY1 Special handling of transfer posting
OAY2 Asset class: Low value asset check
OAYA Deprec. areas for transaction types
OAYB Limiting transaction type groups
OAYC Legacy data transfer: Depr. terms
OAYD Legacy data transfer: Man. entry FC
OAYE Legacy data transfer: Sequence
OAYF Legacy Data Transfer: Accumul. Depr.
OAYG Legacy data transfer: Calc.repl.val.
OAYH Depreciation area currency
OAYI Memo value of area
OAYJ Net book value is changeover amount
OAYK Low-value assets
OAYL Individual period weighting
https://help.sap.com/docs/disclaimer
4/11/2024
265This is custom documentation. For more information, please visit the SAP Help Portal
OAYM Permit group asset for area
OAYN Assign bal.sheet/inc.stmt to area
OAYO Rounding speci�c. for deprec. area
OAYP Shortening rules for shortened FY
OAYQ Gross/net resrvs.for special deprec.
OAYR Posting rules for depreciation
OAYS Special treatment of retirement
OAYT Transact.type for proportional vals
OAYU Capitaliztn of dwn-paymnts (transfr)
OAYZ Asset class: Depreciation areas
OAZ1 Validation Rules for Trans.Typ.Grp.
OAZ2 Substitution for trans.type group
OB03 C FI Maintain Table T003 (Change View "Document Types")
OKGL Versions for capitalization val.calc
ORFA Asset Accounting Customizing: Display IMG
SPRO Customizing: Execute Project - SAP Reference IMG
Automatic Opening of a New Depreciation Area - PGM: RAFABNEW
Purpose
This document describes basic steps to open a new depreciation area.
Overview
We can use program RAFABNEW or transaction code AFBN to open a new depreciation area to all of existing active assets. Owing to the variety of
business scenarios, it is also necessary to make proper adjustment in newly added area after opening a new depreciation area in order to meet your
business requirement.
Section 1 
Pre-customizing 
1, Create a new depreciation area 06 by coping area 01 via T-cd: OADB
2, in T-cd: OABC, to specify source area 01 for area 06 to take over values and depreciation parameters during opening of depreciation area 06
https://help.sap.com/docs/disclaimer
4/11/2024
266This is custom documentation. For more information, please visit the SAP Help Portal
3, To use T-cd: OAYZ to activate area 06 in relevant asset class and set default depreciation key / UL at asset class level
Section 2
Execute T-cd: AFBN (PGM: RAFABNEW) to open depreciation area 06 in all active assets which belongs asset class activating area 06
1, Input parameters which meets your business requirement
Notes for �eld ʻDep. Terms from asset class’
- If you leave this �eld BLANK, then dep. Terms of area 06 will take over from source area 01 as you de�ned in T-cd:OABC
- if you set this �eld FLAGGED, then ONLY for assets without posting, the dep. Terms of area 06 will take over from the setting of T-cd: OAYZ. For assets with posting, the terms in area 06 will take over from area 01 by
default
Notes for �eld ʻLeave values initial’
- if you �ag this �eld to open area 06, then there will be NO value copied from reference depreciation area 01 to new area 06.
2, Check result and see if there is any error during depreciation area opening process
https://help.sap.com/docs/disclaimer
4/11/2024
267This is custom documentation. For more information, please visit the SAP Help Portal
3, In AS03, we can see that the depreciation terms of area 06 was copied from area 01
4, in AW01N, we can see that transactions and value have been copied from area 01 to area 06 
Section 3
https://help.sap.com/docs/disclaimer
4/11/2024
268This is custom documentation. For more information, please visit the SAP Help Portal
Post-process of depreciation area opening 
1, To use T-cd:AS02 to change the depreciation key of area 06 
2, If necessary, to use T-Code: OAAR to open previous �scal year for area 06 
3, To execute depreciation re-calculation via T-Code: AFAR as per SAP note 646691 
4, Use program Z_T093B_UPDATE of note 646691 to close the �scal year for area 06 
Related SAP Notes/KBAs
SAP Note 301113 - Restrictions of RAFABNE
SAP Note 430618 - Procedure for setting up new depreciation area 
SAP Note 449325 - RAFABNEW apparently incorrect depreciation parameters
Basics of Asset Accounting – Asset Explorer
Purpose
The purpose of this page is to clarify the understanding of the system logic and requirements in relation to the asset Explorer through transaction
code AW01N.
Overview
The following paragraphs and �gures will describe with EXAMPLE the steps of how to explore an asset and the functionality of the main buttons.
In Asset Explorer by transaction code AW01N, we are able to display depreciation calculation. However, if system uses New depreciation calculation,
to be able to simulate Old depreciation calculation, you need to use transaction code AW01_AFAR. 
Exploring an asset with Transaction Code AW01n
Navigation: SAP Easy Access -> SAP Menu -> Accounting -> Financial accounting -> Fixed Asset -> Asset -> Asset Explorer
Alternatively: AW01N
1) Fill out �elds with asset number/Company Code.
https://help.sap.com/docs/disclaimer
https://me.sap.com/notes/646691
https://me.sap.com/notes/646691
https://me.sap.com/notes/301113
https://me.sap.com/notes/430618
https://me.sap.com/notes/449325
4/11/2024
269This is custom documentation. For more information, please visit the SAP Help Portal
2) In Planned values tab, you can check all values related to this asset. APC, Acquisition value, Ordinary depreciation, net book value.
3) If you select transaction line and click on “hat” button, you can check all details related to each transaction.
4) And if you double click in the acquisition / retirement / transfer transaction, you will be able to display the document generated in FI after the
acquisition / retirement / transfer.
https://help.sap.com/docs/disclaimer
4/11/2024
270This is custom documentation. For more information, please visit the SAP Help Portal
5) If you click on (display depreciation calculation) button or double click over Ordinary deprec. Value in the ʻPlanned values’ tab, you will be able
to see the parameter used by the system to calculate the asset depreciation in that depreciation area.
New depreciation calculation displays:
https://help.sap.com/docs/disclaimer
4/11/2024
271This is custom documentation. For more information, please visit the SAP Help Portal
Old depreciation calculation displays:6) In the Posted Values tab you will be able to see how the depreciation will be posted during the year for each period.
PS. In the example below period 1 is missing because it was already posted in time of creation and acquisition posting in this asset.
https://help.sap.com/docs/disclaimer
4/11/2024
272This is custom documentation. For more information, please visit the SAP Help Portal
Related Content
Related Documents
http://help.sap.com/saphelp_erp60_sp/helpdata/en/4f/71e695448011d189f00000e81ddfac/frameset.htm
Related Notes
Fiscal Year Variants
De�nition
The �scal year version de�nes the number and relation to the calendar of the depreciation periods in the �scal year in Asset Accounting. Asset
Accounting generally uses the same �scal year version as Financial Accounting (general ledger). In this case, the depreciation periods of Asset
Accounting correspond to the posting periods of Financial Accounting (without special periods). The system therefore automatically defaults the
�scal year version of FI-GL when you de�ne the FI-AA system settings for a company code. You do not need to make any system settings in this
section if your depreciation periods and G/L posting periods are identical.
In some cases, however, the G/L posting periods are not suitable for determining depreciation in Asset Accounting. In this step, you de�ne the FI-AA-
speci�c �scal year versions when this is the case.
You can specify your own �scal year version in the following implementation activities in the FI-AA de�nition of the company code below the company
code for each FI-AA depreciation area
Note
https://help.sap.com/docs/disclaimer
http://help.sap.com/saphelp_erp60_sp/helpdata/en/4f/71e695448011d189f00000e81ddfac/frameset.htm
4/11/2024
273This is custom documentation. For more information, please visit the SAP Help Portal
You cannot de�ne �scal year versions in this step. You enter the actual de�nitions of the �scal year versions and their relationship to the calendar in
the general section of FI Customizing.
Caution
However, a different �scal year version can only be used in Asset Accounting if the start and end dates of the versions in Asset Accounting and
Financial Accounting are the same. This also applies to depreciation areas that do not post automatically to the general ledger (when you have �scal
year versions that are speci�cally for given depreciation areas).
You can only change the �scal year version in Asset Accounting as long as the company code does not have production status.
Example
If a �scal year version with 13 (normal) posting periods is used in the general ledger, then you normally need a different �scal year version to
represent a number of FI-AA period controls (for example, �rst-year convention). The reason is that the depreciation calculation only works with full
periods, but the middle of the year in this example is 6.5 posting periods.
You can �nd the Fiscal Year Variant customzing under the following IMG / Transaction SPRO: 
 
 
It is NOT recommend to change a Fiscal Year Variant that has already been assigned to a
company code and already has some postings. This may create database inconsistencies in your
system.
SAP System Landscape Optimization (SLO) provides a service for"Prolonged �scal year
consulting".
For details about the scope and proceeding of this service you can usethe service desciption for "Shortened �scal year consulting". You �nd our
service description on the SAP Service Marketplace (link: http://service.sap.com/slo -> SAP Conversion Services/Data Harmonization Consulting ->
Detailed Information -> Shortened �scal year consulting.
https://help.sap.com/docs/disclaimer
http://service.sap.com/slo
4/11/2024
274This is custom documentation. For more information, please visit the SAP Help Portal
Useful notes / adverse effects :
672255 Shortened �scal year/changing �scal periods
10945 F4554: Entry for 12/31 is missing
427920 Analysis program for �scal year conversion
210861 Changing �scal year variant in production system
193713 SAPF070: Change of �scal year variant
123026 Shortened �scal year is not recognized/AA653
Please notice that as mentioned in the notes, if you decide to change the Fiscal Year variant, and any inconsistencies arise, it will be considered as
consulting issue, see note 83020 for more information. 
Key Terms
Key Terms
APC - Acquisition Production Costs. This refers to the total capitalized amount of the asset. Usually this is the purchase prices plus any other
costs associated with getting the asset up and running such as installation, callibration, delivery fees, etc.
NBV - Net Book Value
UL - Useful Life
RUL - Remaining Useful Life
TDDP - time-dependent depreciation parameters
COD - Chart of Depreciation
AUC - Asset Under Construction
LVA - Low Value Assets
WDV - Written Down Value
SLM - Straight Line Method
Mapping transaction type de�nition and depreciation area speci�cation
Purpose
In real business scenario, we need to use transaction type to distinguish transactions. owing to variant requirement of accounting standard, we also
need to decide a certain transactions can only be posted into one or several depreciation areas among all of depreciation areas on an
asset. Therefore, we need to de�ne transaction type properly and specify those transaction type to certain depreciation areas based on own
business requirement.
Overview
In below table, you can �nd the list of transaction code to de�ne transaction types and transaction code to specify depreciation areas
for each category of transaction type. 
Contents
Transactions Transaction code to de�ne transation type Depreciation areas speci�cation of transaction type
Acquisition AO73 OAYA
Retiement AO74 OAXB
Acquisition transfer AO75 OAXC
Acquisition retirement AO76 OAXC
Post-capitalization AO77 OAXD
Manual depreciation and unplanned depreciation AO78 OAXE
Settlement OAXG OAXF
Transfer reverse AO80 OAXH
Investment support AO83 / AO73_INV OAXI
Mass processing in Asset Accounting
https://help.sap.com/docs/disclaimer
4/11/2024
275This is custom documentation. For more information, please visit the SAP Help Portal
Purpose
This document lists approaches of masse process you can use in Asset Accounting.
Overview
In many business requirements, we need to register asset master data or process some transaction for a number of assets. In such cases, mass
process tools can improve the efficiency and save project time signi�cantly. Here, Let’s have at some asset accounting speci�c tools and some
across application tools for different general business scenarios.
Sections:
1, Mass process for legacy asset migration, we can use data transfer tool – T-cd: SXDA_TOOLS or SXDA.
2, Mass process for creation of new asset master, To use T-cd:AS01 with �eld ʻNumber of similar assets’. You can specify different asset master data
during asset creation if you customize relevant settings in IMG: Asset Accounting -> Master Data -> Screen Layout -> De�ne Screen Layout for
Asset Master Data -> Con�gurable Entry Screen for Creating Multiple Assets
3, Mass process for asset master data change, To follow below steps: 
1) Use T-cd:OA02 to de�ne a substitution for mass changes
2) Use AR01 to display target asset by using �exible selection parameters
3) Use worklist function via going through the menu: Edit -> Worklist -> Create -> Change asset w/o dialog (bulk change) and specify the substitution
in the result display list of AR01
4) Use AR31 to execute the worklist you created in step 3
4, Mass process for asset acquisition, Use the function ʻMultiple assets’ of T-cd: ABZON. Alternatively, you can create a batch input session via T-cd:
SHDB and then execute the session via T-cd:SM35
5, Mass process for asset retirement, we can utilize the standard mass retirement worklist provided in standard report AR01. Please refer the above
scenario 3 – step 3) to go through the menu of output list: Edit -> Worklist -> Create -> Select ʻRetirementwithout revenue’ or ʻRetirement with
revenue’. 
6, Mass process for asset transfer, Same with scenario 5, we can use the worklist function of AR01 by going through the menu of output list: Edit ->
Worklist -> Create -> Select ʻIntercompany Asset Transfer’.
7, Mass process for the simulation of the development of asset values, we can follow below steps:
1) De�ne simulation version via IMG: Asset Accounting -> Information System -> De�ne Simulation Variants for Depreciation Reports
2) De�ne a �xed simulation rule or use substitution during depreciation simulation
3) Execute a report that refers to the asset balance, e.g. AR18 and set parameter ʻSimulation version’ in section ʻFurther settings’ to simulate the
valuation of assets on the basis of different rules for valuation.
Overview BW Delta Extraction
Overview BW Delta logic for data extraction
Author: D033258
IMS Financials, SAP AG
BW Architecture
https://help.sap.com/docs/disclaimer
4/11/2024
276This is custom documentation. For more information, please visit the SAP Help Portal
Why BW?
BW as an OLAP system improves the reporting functionality.
performance
efficiency
�exibility
multiple system landscape
Main Extraction Methods
Full Update
DeltaInit Update (Initialization of Delta Process)
Delta
Delta Logic
Delta extraction loads only new and changed data into BW from the point of the last extraction.
Data transferred already into BW remains and does not have to be loaded again.
Advantage: Performance Improvement by decreasing the extraction time and data volume --compared to the FULL Update logic
Disadvantage: very complex logic necessary in OLTP to extract the data and determine which data has been changed.
Delta enabled DataSources in FI-AA
0ASSET_ATTR_TEXT Texts and attributes for asset master data (ANLA, ANLZ, ANLU)
0ASSET_AFAB_ATTR Asset depreciation parameters (ANLB)
0FI_AA_11 Transactions and annual values (ANLC, ANEK, ANEP, ANEA)
0FI_AA_12 Period depreciation planned and simulated (ANLP)
This extractor has no dedicated �elds for legacy values in ANLC, instead it just uses ANLC data to calculate the takeover values and
then create some kind of a "virtual" ANLP from it. So actually 0FI_AA_12 does not really load ANLC. ANLC is just part of the calculation,
which is necessary because the information of the legacy values does not directly exist in any database table.
Asset Master Data
https://help.sap.com/docs/disclaimer
4/11/2024
277This is custom documentation. For more information, please visit the SAP Help Portal
1. Asset Subnumber (Flexible Update) 
InfoObject 0ASSET
InfoSource 0ASSET_ATTR_TEXT
2. Asset Depreciation Area
InfoObject 0ASSET_AFAB
InfoSource 0ASSET_AFAB_ATTR
Asset Master Data : Data sources and targets (today)
Asset values
1. Transactions (Delta) 
InfoProvider 0FIA_DS11
InfoSource 0FI_AA_11
2. Annual Values (Delta) 
InfoProvider 0FIA_DS12
InfoSource 0FIA_DS11 (DataMart Scenario)
3. Period Values (Delta)
InfoProvider 0FIA_DS13
InfoSource 0FI_AA_12 and InfoSource 0FIA_DS11 (DataMart Scenario)
Asset values: Data sources and targets (before)
https://help.sap.com/docs/disclaimer
4/11/2024
278This is custom documentation. For more information, please visit the SAP Help Portal
Asset values: Data sources and targets (today)
SAP BW 3.2 Content: New Data Model
https://help.sap.com/docs/disclaimer
4/11/2024
279This is custom documentation. For more information, please visit the SAP Help Portal
DataSource de�nition (RSA2)
The de�nition of DataSources can be checked in transaction RSA2. Be aware that this transaction is only available in SAP owned systems. In
customer systems, this transaction is not available!
https://help.sap.com/docs/disclaimer
4/11/2024
280This is custom documentation. For more information, please visit the SAP Help Portal
Change pointers I
As there is no reliable timestamp information in most of the Asset tables, we had to implement change pointer tables which protocol changes to
asset and asset values.
BWFIAA_AEDAT_AS -> Asset Master record changes
BWFIAA_AEDAT_AB -> Asset depreciation parameter changes
BWFIAA_AEDAT_TR -> all changes to asset values, such as transactions, depreciation changes, depreciation postings
Change pointers II
Change pointers are stored by Business Add-In (BADI) FIAA_BW_DELTA_UPDATE. This BADI is called from every voucher function in FI-AA and
contains 3 methods:
UPDATE_POSTING
UPDATE_MASTERDATA
UPDATE_DEPRECIATIONS
FIAA_BW_DELTA_UPDATE is delivered inactive. So originally no change pointers are stored in change tables. If the customer wants to use FI-AA
Business Content, he has to activate this BADI. First when this is done, change pointers are created for the Delta Extractors.
Important: Leading Source FI-AA (0ASSET_ATTR_TEXT) checks on every Delta or DeltaInit extraction if the BADI is active. If it is not acitve,
extraction is stopped and errors are raised.
Example change pointers (BWFIAA_AEDAT_TR)
https://help.sap.com/docs/disclaimer
4/11/2024
281This is custom documentation. For more information, please visit the SAP Help Portal
Sequence for data requests
The aggregation of line items according to master data attributes (e.g. cost center) during the update of Info Cubes from the ODS objects makes it
necessary that master data is available in BW before transactions are loaded. Out of this necessity, the following load sequence must be executed:
0FI_GL_4
 General Ledger: Line items (only if used)
0ASSET_ATTR_TEXT
 Asset master data
0ASSET_AFAB
 Asset depreciation parameters
And then the transaction data
0FI_AA_11
 Transactions and annual values
0FI_AA_12
 Posted depreciation (period values)
The correct load sequence is checked by the extraction routines!
Extraction Routines
Central Routine for extraction is Function Module BWFIAA_EXTRACT_DELTA
DataSource De�nition in RSA2
https://help.sap.com/docs/disclaimer
4/11/2024
282This is custom documentation. For more information, please visit the SAP Help Portal
Extraction Phases
The extraction can be split at least into 3 phases. Extractor is called at least three times from the BW API.
1. INITIALIZATION PHASE
2. EXTRACTION PHASE
3. FINISHING PHASE
Initialization Phase
Prerequisite: Importing Parameter I_INITFLAG is not initial.
Checks:
Get selection data, build and convert internal selection tables
Get timestamps of the leading source (0FI_GL_4 or when this is not used 0ASSET_ATTR_TEXT)
Get timestamp of the extraction source
Build Selection Ranges for the extractor
Extraction Phase
Prerequisite: I_INITFLAG is initial.
Depending on extraction source call single extractors
BWFIAA_GET_MASTER for 0ASSET_ATTR_TEXT and 0ASSET_AFAB_ATTR
BWFIAA_GET_TRANS for 0FI_AA_11
BWFIAA_GET_DEPR for 0FI_AA_12
When all data is extracted set NO_MORE_DATA_FLAG -> the next call from API will be the FINISHING PHASE then
Finishing Phase
Prerequisite: I_INITFLAG is intial AND
 NO_MORE_DATA_FLAG is NOT initial
Two steps are remaining
Update Timestamps for extraction source
Delete "old" timestamps to keep extraction pointer tables as small as possible
Extraction Phase 0ASSET_ATTR_TEXT and 0ASSET_AFAB_ATTR
Done in Function BWFIAA_GET_MASTER
IF Delta Logic (DeltaInit, Delta) is chosen, active BADI Implementation for BADI FIAA_BW_DELTA_UPDATE is checked. If BADI is inactive,
extraction is stopped!
DeltaInit Extraction calls old extraction module
 ARBW_BIW_GET_MASTER_DATA
for both extractors.
Delta Extraction 0ASSET_ATTR_TEXT uses Function
 BWFIAA_GET_ASSET_DELTA.
Delta timestamps are read from BWFIAA_AEDAT_AS.
Delta Extraction 0ASSET_AFAB_ATTR uses Function
 BWFIAA_GET_ASSET_AFAB_DELTA.
Delta timestamps are read from BWFIAA_AEDAT_AB.
Extraction Phase 0FI_AA_11 and 0FI_AA_12
0FI_AA_11 with Function BWFIAA_GET_TRANS
DeltaInit Extraction uses Function BWFIAA_GET_TRANS_INIT
Delta Extraction uses Function
BWFIAA_GET_TRANS_DELTA.
Delta timestamps are read from BWFIAA_AEDAT_TR.
0FI_AA_12 with Function BWFIAA_GET_DEPRhttps://help.sap.com/docs/disclaimer
4/11/2024
283This is custom documentation. For more information, please visit the SAP Help Portal
DeltaInit Extraction uses Function BWFIAA_GET_DEPR_INIT
Delta Extraction uses Function BWFIAA_GET_DEPR_DELTA.
Delta timestamps are read from table BWFIAA_AEDAT_TR or Schedule Monitor logs.
Extraction Phase 0FI_AA_11 - special logic
Source data of this extractor is ANEK, ANEP, ANEA and ANLC. To extract ANLC data in one extraction with transactions (ANEK, ANEP, ANEA), the
ANLC data is split into 2 records and masked as transactions with special transaction types.
One ANLC record is split as follows:
Cumulative values with transaction type CUM
Planned annual values with transaction type PLN
ANLC values are converted to extract structure in Function BWFIAA_FILL_ANLC_TO_TRAN.
ANEK, ANEP and ANEA data is converted to extract structure BWFIAA_FILL_ANEPV_TO_TRAN.
Extraction Phase 0FI_AA_12 - special logic I
Extraction is split in 2 phases.
Phase 1: posted depreciation
-> ANLP is read and extracted for all posted periods
Phase 2: simulated depreciation
-> All periods not posted yet in all open �scal years are simulated and extracted.
-> Simulated depreciation is marked by �eld SIM in extract structure.
If simulated periods are posted then and extracted to BW, the simulated depreciation records are overwritten with the posted depreciation in ODS.
So step by step the annual period depreciation is extracted to BW.
Extraction Phase 0FI_AA_12 - special logic II
Delta Extraction uses 2 different methods to determine DELTA data, depending on the processed phase.
Phase 1: posted depreciation
-> Schedule Monitor monitors all executions for a productive depreciation run. To get the periods posted from the last extraction, Schedule
Monitor tables are read. With this method, periods can be determined
-> ANLP for these periods is read and passed to BW as real depreciation
Phase 2: simulated depreciation
-> assets changed since the last extraction determined by change pointer table BWFIAA_AEDAT_TR
Extraction Phase 0FI_AA_12 - Depreciation Simulation
Simulation Methods set up in table BWOM_SETTINGS, parameter BWFIAASIM
NO simulation (BWFIAASIM = 2)
FAST simulation (simpli�ed RAPOST00-method,
 BWFIAASIM = 0 )
EXACT simulation (exact RAPOST2000-method,
 BWFIAASIM = 1 )
Further information in note 614804.
How can I test the extraction in R/3?
Transaction RSA3 - Extractor Checker:
https://help.sap.com/docs/disclaimer
4/11/2024
284This is custom documentation. For more information, please visit the SAP Help Portal
Tips and Tricks I
1) Restrict data selection 0FI_AA_11 and 0FI_AA_12 to limited range of assets:
1. Breakpoint in Function Module ANLC_READ_RANGE_TRIGGER
2. Insert selection criteria in selection table t_dopt
https://help.sap.com/docs/disclaimer
4/11/2024
285This is custom documentation. For more information, please visit the SAP Help Portal
Sample content of T_DOPT:
- ( ANLN1 = '000000003370' )
- ( ANLN1 = '000300000000' )
- ( ANLN1 = '000200565799' AND
 ANLN2 = '0002' )
- ( ANLN1 GE '000000003021' )
 AND ( ANLN1 LE '000000003024' )
Tips and Tricks II
2) Timestamp conversion
1. Select extraction in table BWOM2_TIMEST
2. Fill Function Module RKE_TIMESTAMP_CONVERT_OUTPUT with parameters from BWOM2_TIMEST
Data exploration in BW
https://help.sap.com/docs/disclaimer
4/11/2024
286This is custom documentation. For more information, please visit the SAP Help Portal
Data exploration in BW - step by step
How do I start the extraction from BW?
Transaction RSA1 - Administrator Workbench:
https://help.sap.com/docs/disclaimer
4/11/2024
287This is custom documentation. For more information, please visit the SAP Help Portal
InfoPackage
Request Monitor
https://help.sap.com/docs/disclaimer
4/11/2024
288This is custom documentation. For more information, please visit the SAP Help Portal
Status of extraction requests - Error I
Status of extraction requests - Error II
https://help.sap.com/docs/disclaimer
4/11/2024
289This is custom documentation. For more information, please visit the SAP Help Portal
Status of extraction requests - Success
Content of InfoProviders - technical
https://help.sap.com/docs/disclaimer
4/11/2024
290This is custom documentation. For more information, please visit the SAP Help Portal
Content of InfoProviders - in BEx Analyzer
Reconciliation Program ABST2
Purpose
The document here is aimed to explain the function of reconciliation program ABST2 and how to distinguish the difference between GL/AA from it's
result
Overview
The program selects the asset records (ANLC), summarizes the values on G/L account and business area levels, and writes the summarized values
to table EWUFIAASUM.
The following accounts are reconciled:
https://help.sap.com/docs/disclaimer
4/11/2024
291This is custom documentation. For more information, please visit the SAP Help Portal
Balance sheet account APC
Balance sheet account down payments
Balance sheet account revaluation
Balance sheet account special items
Value adjustments ordinary depreciation
Value adjustments special depreciation
Value adjustments unplanned depreciation
Value adjustments transfer of reserves
Value adjustments revaluation of ordinary depreciation
You should start the report before year-end closing.
Example
Call transaction ABST2 to �nd the difference between GL and AA.
The difference column ʻ1st LC Delta GL/AA’ is the result of balance at AA minus balance at GL.
https://help.sap.com/docs/disclaimer
4/11/2024
292This is custom documentation. For more information, please visit the SAP Help Portal
For the period �eld, is used to distinguish last year and current year, if it is blank, this means the inconsistency is appeared in previous years; while if
it shows 999, this means the inconsistency is happened in current year.
Take account 213900 for example, here I will introduce the general method to distinguish the inconsistency between GL and AA.
Firstly, the G/L balance can be checked via FS10N or FAGLB03 by specify account number/�scal year/business area/ ledger.
You can check the balance from AA side as below:
1. According to the account re�ected, �nd the corresponding account determination.
You can check table T095B or T095, it depends on the account is an accumulated depreciation account or accumulated acquisition
account.
For account 213900, it is used for revaluation of acquisition for area 01 in account determination 20000, JP20000, JP30000 & JPTEST.
Then you can �nd the relationship between account determination and asset class in table ANKA, and �nally the assets in asset class in table ANLA.
For this case, the company code BM01 has 185 assets and belongs to asset class 2000 & 4000.
https://help.sap.com/docs/disclaimer
4/11/2024
293This is custom documentation. For more information, please visit the SAP Help Portal
 2. Run report RAGITT_ALV01 or RABEST_ALV01 to check the balance from Asset accounting with the parameter you check from the previous
table T095B/T095.
 
 3. Compare with FS10N results, you can see it is just the data displayed in ABST2.
Then, you need to go through the assets and �nd out the possible reason for the difference. For example, if the legacy asset has post a document via
OASV when take over the values. If there is any errors exits in the assets, you can try to check via AFAR run.
https://help.sap.com/docs/disclaimer
4/11/2024
294This is custom documentation. For more information, please visit the SAP Help Portal
https://help.sap.com/docs/disclaimer
4/11/2024
295This is custom documentation. For more information, please visit the SAP Help Portal
Please note sometimes the inconsistency is caused by G/L balance not been carry forward successfully. For such a case, please use F.16 or GLGVTR
(for new GL) to carry forward to do the balance carry forward again.
https://help.sap.com/docs/disclaimer4/11/2024
296This is custom documentation. For more information, please visit the SAP Help Portal
https://help.sap.com/docs/disclaimer
4/11/2024
297This is custom documentation. For more information, please visit the SAP Help Portal
If you need to post an adjustment document to make the AA consistent with GL, you can refer to note 69225 and use transaction code ABF1 to post
to reconciliation account. If the difference is caused by missing entry in AA, you can use correction program RACORR05 (it uses the FI document to
create the AA entries).
Related SAP Notes/KBAs 
104567 Collective note Euro FI-AA: Analysis phase
124509 Analysis of errors listed by reconciliation program
364878 Reconciliation with FI-GL during the �scal year
2032547 Reconciliation FI and FI-AA
1909833 Reconciliation issue between AA and GL by T-code: FS10N
69225 Reconciliation difference �nancial/asset accounting
Simulation Function in Asset Explorer
Purpose
The purpose of this page is to clarify the use of the simulation function in the Asset Explorer through transaction code AW01N.
Overview
The simulation function in asset explorer transaction AW01N is a very helpful function when you want to �gure out what is the effect to the depreciation calculation if you change any parameters or do transactions on
the asset. There are 2 kinds of simulation can be performed here.
 
Asset explorer simulation
https://help.sap.com/docs/disclaimer
https://me.sap.com/notes/364878/E
https://me.sap.com/notes/2032547/E
https://me.sap.com/notes/1909833/E
https://me.sap.com/notes/69225/E
4/11/2024
298This is custom documentation. For more information, please visit the SAP Help Portal
 
If you click on the “Switch on simulation” button on the top of the screen, you will �nd the screen has several �elds is ok for modify, these are parameters which may in�uence the depreciation calculation result.
https://help.sap.com/docs/disclaimer
4/11/2024
299This is custom documentation. For more information, please visit the SAP Help Portal
 
Here, you can modify these parameters and see what is the effect will be in the depreciation calculation. For example, if you change the useful life from 5 to 10 years, the depreciation is also got changed too. This
change will not be saved in asset master, just for simulation purpose.
https://help.sap.com/docs/disclaimer
4/11/2024
300This is custom documentation. For more information, please visit the SAP Help Portal
 
After you turn off the simulation, the asset is as the same as before the simulation take place.
https://help.sap.com/docs/disclaimer
4/11/2024
301This is custom documentation. For more information, please visit the SAP Help Portal
Transaction simulation
https://help.sap.com/docs/disclaimer
4/11/2024
302This is custom documentation. For more information, please visit the SAP Help Portal
Once the asset explorer simulation is turn on, there will be another simulation button shown in the transaction tab. You can use the function to see how the transactions like acquisition/post-
capitalization/retirement/transfer will impact the asset depreciation. This is especially useful when you trying to adjust the asset amount but you are not sure if there will be unexpected in�uence on depreciation.
https://help.sap.com/docs/disclaimer
4/11/2024
303This is custom documentation. For more information, please visit the SAP Help Portal
After click on the green tick, you will see the result of this transaction.
https://help.sap.com/docs/disclaimer
4/11/2024
304This is custom documentation. For more information, please visit the SAP Help Portal
Also, the transaction here will not be saved for the asset in any tables. The entry will disappear when you turn off the simulation for the asset explorer.
 
 
 
 
Substituation during asset master creation
Purpose
This page describes how to create substitution which can be triggered during asset master creation.
Overview
During asset master data register, if a �xed value in a certain �eld needs to be inputted based on the input value of other corresponding �eld, then
we can consider substitution to realize this mapping. E.g. for cost center XXXX, plant 1000 is required in asset master data, for cost center YYYY,
plant 2000 is required in asset master data and so on.
https://help.sap.com/docs/disclaimer
4/11/2024
305This is custom documentation. For more information, please visit the SAP Help Portal
Section 1
1, Execute transaction code OACS or go through IMG: Asset Accounting -> Master Data -> De�ne Substitution -> De�ne substitution for creating
assets to create new entry for your company code with Field Group Tab A̒’, Logical Field Group ʻ3’
2, Click on Button ʻSubstitution’ to create substitution ʻGR66_PL’ with below prerequisite condition and substitution contents:
 
 
 
3, Ensure the substitution is activated with status ʻ1 Active’ in the above �rst screen shot. 
 
4, To use T-Code: AS01 to create a new asset master in asset class AA66 of company code GR66, then input ʻCC001’ in �eld ʻCost Center’ of Tab
ʻTime-dependent’. 
https://help.sap.com/docs/disclaimer
4/11/2024
306This is custom documentation. For more information, please visit the SAP Help Portal
 Here when you push ʻEnter’ key, �eld ʻPlant’ will be substituted with value ʻ1000’ automatically
Section 2
The substitution works only once during creating asset master data. It doesn’t work in case of you change asset master data via T-cd:AS02 or you
want to trigger substitution again in AS01 by changing cost center after the substitution worked once before. For the reason of this standard
behavior, Please refer to the description of SAP Note 44882
Related SAP Notes/KBAs
SAP Note 44882 Substitution for master data
Transaction type de�nition for asset accounting transaction posting
Purpose
The transaction type in Asset Accounting classi�es the business transaction. The transaction type controls various system activities when business
transactions are posted.
https://help.sap.com/docs/disclaimer
https://me.sap.com/notes/44882
4/11/2024
307This is custom documentation. For more information, please visit the SAP Help Portal
Overview
The object that classi�es the business transaction (for example, acquisition, retirement, or transfer), and determines how the transaction is
processed in the SAP system.
The transaction type is the basis for the assignment of the business transaction to a column in the asset history sheet. Every transaction type
belongs to a speci�c transaction type group.
.
Section 1
A transaction type consists of 4 parts in general: 
1, Transaction type name and which transaction type group the transaction type is assigned 
2, Account assignment, where to de�ne transaction type is Debit or Credit
3, Posting type that de�nes if a transaction can be post to an affiliated company code on Gross value or Net value
4, Other features including consolidation transaction type, Asset history sheet group and so on 
Section 2
General procedure to create a transaction type, for example, to create a retirement transaction type and restrict the transaction type to area 01
only
1, User transaction code AO74 to create and de�ne a retirement transaction type 299 by referring transaction type 200
2, Use transaction type OAXB to restrict transaction type 299 to depreciation area 01 only
Section 3
Relationship between transaction type de�nition and depreciation area restriction for different transactions can be found out in below link: 
Mapping transaction type de�nition and depreciation area speci�cation
 
https://help.sap.com/docs/disclaimer
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361878843.html
4/11/2024
308This is custom documentation. For more information, please visit the SAP Help Portal
Useful Transaction Codes for FI
List of useful FI-AA Transactions
ORFA - Directly references the Asset Accounting section of the IMG
ARxx - Directly access key asset reports. These are much easierto goto rather than typing in the transaction code that is viewable from the
initial SAP Easy Acces menu (such as S_ALR_8437387). Examples are AR01 (Asset Balances), AR02 (Asset History Sheet), AR03
(Depreciation), AR18 (Depreciation Simulation). You can view them at transaction [SE93].
Validation and Substitution Call Points in Asset Management Accounting
Purpose
This document describes the call points of validation / substitution and relevant transaction codes / IMG menu path in Asset Accounting.
Overview
According to different business processes, we need to de�ne own validation / substitution in corresponding call points. When we de�ne a validation /
substitution, the call point is set by default based on what transaction code you use or which IMG menu path you go through.
Content:
Below are the list of call points of validation / substitution in Asset Accounting and the usage purpose as well as corresponding transaction codes /
IMG menu path. 
 
Call point 0001 for Master data => OACS / OACV
Call point 0002 for Postings => OAZ1
Call point 0003 for AM - Fixed Asset Retirement Postings => OA01
Call point 0004 for AM - Master data mass change => OA02
Call point 0005 for Simulation version => IMG: Asset Accounting -> Information System -> De�ne Simulation Variants for Depreciation
Reports
Call point 0006 for Transfer organizational units => IMG: Asset Accounting -> Master Data -> De�ne Substitution -> De�ne substitution for
automatic transfers
Migration to S/4HANA
Migration to S/4HANA
Are you planning a conversion into SAP S/4HANA?
The following information will help you in the Asset Accounting area:
 • KBA 2741967 - How to plan and execute the �nancial data migration during conversion of SAP ERP solution to SAP S/4HANA
 • SAP Note 2332030 - Conversion of accounting to SAP S/4HANA
 • SAP Note 2270333 - S4TWL - Data Model Changes in FIN
 • SAP Note 2618023 - Migration Preparatory Checks for FI-AA: Error Messages and Possible Solutions
 • KBA 2714344 - Financial data migration to SAP S/4HANA: Most frequent Error Messages – Information and Recommendations
General Documentation:
Migration to SAP S/4 HANA Finance 
https://help.sap.com/docs/disclaimer
https://launchpad.support.sap.com/#/notes/2741967
https://launchpad.support.sap.com/#/notes/2332030
https://launchpad.support.sap.com/#/notes/2270333
https://launchpad.support.sap.com/#/notes/2618023
https://launchpad.support.sap.com/#/notes/2714344
https://uacp2.hana.ondemand.com/doc/d7bf6052e7d1ea5fe10000000a423f68/3.6/en-US/frameset.htm
4/11/2024
309This is custom documentation. For more information, please visit the SAP Help Portal
Additional line items in ACDOCA table
Additional line items in ACDOCA table 
The asset line items normally refer to a FI document, but – e.g. for settlement postings,
retirements etc. – are not referenced to a single line of this FI document.
Thus we are not able to split an existing FI document line into N document lines with asset
information (1:N). Instead we use the M:N migration schema in general for all FI-AA line items :
All FIAA line items will be added to the document with migration source type ʻA’ additionally to
the FI-lines of migration source type ʻF’ or ʻG’ (FI respectively GL). To correct the duplicate
balance of the document, these lines will get reversal lines (migration source type ʻR’).
Therefore there are additional line items.
If the migration-status is green, everything is ok.
 
New Asset Accounting
Links to Online Documentation:
New Asset Accounting
New Asset Accounting in S/4HANA and Migration Guide
https://help.sap.com/docs/disclaimer
https://help.sap.com/erp2005_ehp_07/helpdata/en/78/51ec9a16b04ee9926e2487da804f31/frameset.htm
https://help.sap.com/viewer/67e323b7117e4c91869c258933f47182/1709%20001/en-US
https://uacp2.hana.ondemand.com/doc/d7bf6052e7d1ea5fe10000000a423f68/3.6/en-US/frameset.htm