Basic Configuration settings for implementing Asset Accounting in SAP 6.

0
INTRODUCTION:
The asset accounting module in SAP is one where the accounting pertaining to fixed assets is
done. These include transactions like acquisition of fixed assets, sale of fixed assets, in-house
development of assets, settlement of WIP, and accounting for depreciation on fixed assets and so
on.
A separate Asset Accounting Module is required for these transactions because there are some
distinguishing characteristics of fixed assets as compared to normal General Ledger accounts.
Some of these characteristics of fixed 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 fixed assets into asset classes, and thus we can meet this
requirement. In other words, classification of fixed assets for balance sheet disclosure purposes
becomes easy.
Sometimes we may have self-constructed fixed 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 fixed assets like asset history
report, report of fixed 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 configuration needs to be done in
IMG. This includes setting up the organization structure, defining the depreciation areas, creating
the different asset classes, account assignment, defining depreciation keys and so on. All these
configuration 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 specific country or economic area.
Each company code defined in Asset Accounting must refer to a chart of depreciation.
Copy reference Chart of Depreciation: SAP provides country-specific charts of depreciation with
predefined 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) Define Chart of Depreciation and depreciation areas: You can change the definition 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 fixed assets.
You can define any number of asset classes in the system. You can use them to structure your
fixed 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 Define 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 key in 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 fields which are used for
different purposes.
Transaction Code: SPRO
IMG Menu Path: Financial Accounting (New) Asset Accounting Master Data Screen
Layout Define 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
IMG Menu Path: Financial Accounting (New) Asset Accounting Organizational
Structures Specify Number Assignment across Company Codes
8) Define 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 scenarios. 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 defines which financial
statement version should SAP use for each depreciation area as a default. This default applies
when the financial 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 define
how the controlling area posting of cost required for each asset transaction type. We configure
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 profile: The settlement profile includes settings on the allowed receivers
of the settlement. We can give settlement profile 10 to enable settlement to all receivers. The
settlement profile 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

Symptom

When posting an intercompany asset transfer (asset transfer between two company codes)
the line items for the second local currency (LC2) is not populated correctly.

The line items for the second local currency show value 0.00 instead of the real and
actual value when simulating or posting the document.

Instead, additional line items are created in the FI document for the second local
currency. This is not expected and therefore incorrect system behavior

Environment

SAP_APPL 4.6C, 470, 500, 600, 602, 603, 604, 605

SAP Financials - Asset Accounting

Reproducing the Issue

1. Go to transaction ABT1N.
2. Enter all relevant posting parameters such as asset number, company code,
document/posting/asset value date, amount to transfer etc. to prepare for the transfer
posting.
3. Simulate the FI document by pressing the "Simulate" button (or F9) or save and post the
transaction.
When you review the document line items, you observe the unexpected system behavior as
described under section 'Symptom'.
Cause
The problem could be due to the settings in transaction OABE - Change View "Depreciation
areas": Gross transfer (between affiliated companies).
Firstly, please refer to the online F1 Help for the indicator "Gross Transfer", field T093AXUMHIS:
"Gross Transfer - T093A-XUMHIS

Indicator: Transfer with historical values

This indicator controls how the system treats transfers between affiliated companies. If this
indicator is set, transfers in this depreciation area are not identified as acquisitions or retirements.
Instead they are identified as transfers (particularly in the asset history sheet). In addition,
posting of the transfer is gross (that is, with historical acquisition costs and depreciation).
Note: This indicator has the affect described above only if it is used in combination with these
two indicators in the definition of the transaction type: 'post to affiliated company' and 'gross'."
The currently observed unexpected line item layout for your transfer posting with a parallel
currency involved (group currency) is most likely due to an inconsistency in your customizing.
Resolution
1. Go to transaction OABE. You find it in IMG transaction SPRO under path: Asset
Accounting -> Special Valuation -> Preparations for Consolidation -> Specify Group
Depreciation Area (OABE).
2. Enter the relevant Chart of Depreciation.
3. Check if the setting for flag "Gross Trnsf" (long text "Indicator: Transfer with
historical values", field name T093A-XUMHIS, Gross Transfer) is set for the parallel
area but not for the base area (e.g. area 01) or vice versa. The settings for both areas must
be identical.
4. If this is not the case, either remove the flag from the parallel currency area (LC2) or set
the indicator for base area (LC1).
Keywords
Financial Accounting, 46C, 4.7, ECC 6.0, wrong, inconsistent, zero, LCur2
Problem Details: Imbalance between ANEP and ANLC tables in Closed AA Year

If I am understanding correctly: is the difference in values is in already closed fiscal years? Also
I understand the upper part in AW01N shows an APC of 163,181,045.00, which
is the value shown in the summary table ANLC. Whereas the lower part in AW01N Transactions - shows an accumulated sum of values that does not match the total APC seen in
upper part of AW01N (table ANLC). The transactions are shown in line item table ANEP.
It can happen that the line items are not fully updated in the summary table. Therefore they may
need aligning. This can be done in closed fiscal years with a correction report that you find also
on the on the Service Marketplace:
https://websmp203.sap-ag.de/fiaa-faq
go to:

==> Find Support Tools

Correction and Maintenance Reports -> click on this and you will find both reports and its
coding
1) RACORR110 aligns the values in tables ANEP and ANLC (ANSWL)
2) RACORR55 carries forward these accum. values to the next fiscal year in ANLC (KANSW /
ANSWL). You can also try a fiscal year change again if the next fiscal year is e.g. the current
year 2013. Else, run the carry forward report from one closed fiscal year to the next.
Important: run the programs in 'TEST' mode first. Check the result and then run it in 'REAL'
mode. Only then will the update actually reflect in the tables.
See if this information helps you to resolve the problem.
Kind regards,
Brigitte
What do you think about this ? have you ever had a similar problem ?
Dear Customer,
The procedure to solve error MQ555 is the following:
Using program RFEWSBAL, select the accounts for which differences occur. To do this, proceed
as follows:
1. Changeover package: Active package
Phase: ANALYZE
Origin of change: AS
Proceed
2. Analyze the accounts containing errors using note 104567.
If the document number field contains the entry "W004", this means that although a difference
exists in the balance carried forward, this difference was charged off at the key date. Following
local currency changeover, the system adjusts the currency differences at the key date only, but
not in the balance carried forward. If the entry "W004" exists for all affected accounts, the status
is set to warning instead of error. If the correction at key date described above proves sufficient,
you can continue changing over the local currency without additional adjustments in the previous
year. However, SAP does recommend that you make corrections in the previous year in line with
note 104567 since this ensures that the balance carried forward is also reconciled."
For your information, I also attached the following two notes for completeness as they may be of
relevance to you also:
364878 Reconciliation with FI-GL during the fiscal year
113670 Reconciliation report: Incorrectly listing errors
69225 Reconciliation difference financial/asset accounting

ABST2 can only show the difference between GL and FI-AA on an accounting level, you will
see no asset numbers or document numbers. It'll show the difference in amount in total for the
account. So if you see difference in ABST2, you can run ABST (RAABST01) that then shows
the details of the differences detected via ABST2 (RAABST02).In order for the report to pick up
the details of these differences, you will have to make sure that the G/L account is line item
managed.
(FS03 -> 'Line item display' must be set).
If the account is not line item managed, but you want to see the details by running RAABST01,
then you have the option to set the indicator for this account by running report RFSEPA01. This
report will build up the information that was absent due to the indicator not having been on in the
G/L account master data. Once this information is available in your G/L account you can run
RAABST01 which will then show you the differences lined out for all assets affected and the
corresponding G/L account. Basically there should be an entry in your BSEG table with a
document number for each transaction that has been done on the asset IF and only IF the area is
set up to post to G/L obviously. With this two reports plus the G/L report FS10N you should be
able to work out where the differences come from. I'm a member of the Primary Support team,
which means that I can only help with problems caused by licensed SAP product errors or
missing documentation and this is not the case after reading the original description of this
incident.
1054121 The SAP Ecosystem in a Nutshell
However, I can tell you that SAP offers a wide range of free resources to help you, like the SAP
Help and Support Portals or the SAP Community Network which are gateways to thousands of
knowledge base articles, SAP software experts, including SAP engineers, consultants and
experienced users from our vast Ecosystem. They are by far the fastest and easiest way to find
solutions to most problems SAP users # experience.
Solution:
12.09.2013 - 01:06:01 CET - Reply by SAP
Dear Customer
The message has arrived to FI-AA development support level for further
processing.
I have checked asset 600089-0 (4010) in your system and it is
in fact inconsistent.
Since year 2013 is already closed, in order to get values
of asset 600089-0 (4010) corrected, please, implement and run
attached correction tools:
1. ZRACORR110
The report will total up the value for the asset selected
in FY 2013.

If you want to perform the report in update mode, you need

to remove the 'x' in test run.
Once the values in FY 2013 are corrected, these values need to
be carried forward into FY 2014 with correction tool ZRACORR55.
2. ZRACORR55
For the update mode you need to remove the X for TEST. Then
the values will be updated and carried forward into 2014.
In case you face such an issue again and you know more about
the circumstances and how the data are processed in
MIRO please let us know.
Thanks for your kind attention,
Best Regards,
Javier Reviriego
Development Support
SAP Asset Accounting

How to view depreciation simulation for future number of years

SAP Path

SAP
Code

SAP Easy Access -> SAP Menu -> Accounting -> Financial
Accounting->Fixed Assets -> Information System ->
Depreciation Forecast Depreciation on Capitalized Assets
(Depreciation Simulation)
Transaction S_ALR_87012936

Introduction
This report gives the depreciation simulation for future years by asset wise. There
are also options in order to get the depreciation on monthly, quarterly and yearly
basis. The is very useful report for the teams working in Fixed Assets area in order
to report the simulated depreciation figures for future number of years.
Enter Selection Parameters

Field Name

Company
Code

Description

Company in which the report is required to be executed

Report Date Last working day of the future year

Display
Variant

Select 1_SAP_1_LINE (which is more convenient for output display)

Summary
Report

Optional Select this box only if intend to display the balances for
Summary per asset class

Click on Explode" button in order to expand the selection screen details.

Field Name

Description

List Assets

This will show the list of details by asset

Evaluation Period

This will evaluation the simulation by period

Click on Execute Button

However, the above report showing the output data without columns optimized and limited up to few years.

The above report is now showing with column with optimized. However, still the
depreciation simulation up to 2020 is not included in the report.
Now, we need to change our layout in order to bring those fields into the report.
Change the Layout (Ctrl+F8)

Move the Additional Depreciation years

Now the proposed depreciation values for the future years are available in the
report. Please note that this report not only brings the depreciation values, it can
also bring the APC values and Net Book Values for the future years. However, the
layout needs to be accordingly changed and include the fields that required to be
shown in the output for reporting purpose.
I had created a Layout for our use in KRQ

We can use Transaction Code AR18 as well for this purpose.

Asset Transactions - Accounting Entries:

Asset Acquisition:
Dr.
Cr.

F-90 - With Vendor

Fixed Asset Acquisition Cost

Vendor (Accounts payable)

Posting date of the document will be copied into the asset master as the capitalization date.
The depreciation start date of each depreciation area will also be determined and updated in
the depreciation area data tab page.
Asset acquisition posting could also be done without PO from the MM module.
Posting could be done in FI posting only.
Asset Disposal Sales to a Customer:

F-92 - With Customer

Supposed an asset with historical cost $1,000 and accumulated depreciation of $100 is being sold to a
customer at a price of $1,100, the posting entries will be as follows:
Dr. Customer account (A/R)
Cr. Revenue for asset disposal
Cr. Fixed asset acquisition cost
Dr. Accumulated depreciation
Dr. Clearing account for asset disposal
Cr. Gain/loss of fixed asset disposal

1,100
1,1001,000100
1,100
200-

The posting date of the retirement posting will also be updated into the field "deactivation date" in the
asset master as the retirement date.

However, the sale revenue credit of 1100 is not to be treated as your current operating revenue since
the said revenue arises from out of the sale of a fixed asset. Such Entries do not form part of your
regular sales and therefore has to appear below the bottom line. But this is possible if and only if there
is an equal and corresponding debit of 1100 and therefore the system creates the offsetting clearing
account debit (this account is pre-defined in the account determination key of the asset class). This
clearing account also has to appear below the bottom line and therefore the sales revenue credit and
the clearing account debit for 1100 units each appear below the bottom line as notes to the financial
statement.
Asset Disposal Scrap without Revenue

ABAVN - Asset Retirement by Scrapping

Instead of selling, an asset could be disposed as a scrap. In this case, no revenue is expected and a loss
will be realized in the P&L if the fixed asset being scrapped still carries a net book value.
For the same asset with historical cost $1,000 and accumulated depreciation of $100, the posting of
the scrapping will be as follows:
Cr. Fixed asset acquisition cost
Dr. Accumulated depreciation
Cr. Gain/loss of fixed asset disposal

1,000100
900

Asset Transfer within a Company Reclassification

The NBV of an existing asset master record could be transferred to another asset within the same
company. The transaction could be used in the following scenarios:
Reclassify an existing asset to a new class or to correct an error
Transfer an asset to a new one with the same class. This may be necessary to execute the
change of the remaining useful life of an asset but still spread the net book value evenly throughout
the remaining life without allowing the system to catch up the postings of the missing or extra
depreciation of the past periods
For an asset with historical cost $1,000 and accumulated depreciation of $100, the posting of the intracompany transfer posting will be follows:
Cr. Fix asset acquisition cost (old asset)
Dr. Accumulated depreciation (old asset)
Dr. Fix asset acquisition cost (new asset)
Cr. Accumulated depreciation (new asset)

1,000100
1,000
100-

The old asset being transferred will become a retired asset and the transfer posting date will be
updated as the retirement date in the asset master record.
For the new receiving asset, the transfer will be the same as if it is being acquired.
The transfer posting date will be used as the capitalization date.
Month End Processing Depreciation Run
Dr. Depreciation expense
Cr. Accumulated depreciation

AFAB-Depreciation Run

Note that the above posting to G/L will be done in a summary level by G/L accounts and cost center
levels because the depreciation expense has to be charged to cost center in CO. However, the detailed
depreciation amount of each asset will also be stored in Asset Accounting such that each unique asset
master record will also have its unique posted depreciation amount. Besides, after each depreciation
run, the system will issue a report which list out the depreciation posting amount of each individual
assets as a record. This is advised that this report should be kept as an additional audit trail.
Asset under Construction (AUC) Config & Process Steps:
Internal Order as Investment Measure:

1. Define the AuC Asset Class (with investment measure) - OAOA

2. Define the Asset Class for Main Asset - OAOA
3. Define Investment Profile - OITA
a. Assign the AuC Asset Class (Step-1) in the investment profile
4. Assign Investment Profile to Model Order - OITA
5. Define Order Type (Investment) - KOT2
a. Settlement Profile - OKO7
b. Maintain Allocation Structures - OKO6
c. Planning Profile - OKOS
d. Budget Profile - OKOB
6. Create an Internal Order - KO01
a. With the Investment Profile (Step-2)
b. AuC automatically created by the system using Asset Class given in the Investment Profile
7. Post the amounts to IO - FB01
Dr. Material supplied to Asset (Expenditure)
Cr. Cash account
8. Settle the amounts to AuC from IO (Prcg type: Automatic) - KO88
Dr. Asset Under Construction account
Cr. Contra Capitalized
9. Create the Main Asset - AS01
10. Settle the amounts to Main Asset from AuC (Prcg type: Full) - KO88
Dr. Final Asset account
Cr. Asset Under Construction account
AuC using Line Item Settlement:
1. Define the AuC Asset Class (with Line Item Settlement) - OAOA
2. Define the Asset Class for Main Asset - OAOA
3. Define Order Type (Overhead) - KOT2

4. Create an AuC-Asset (using Step-1 Asset Class) - AS01

5. Create an Internal Order - KO01
a. Assign the AuC Asset in Settlement Rule in IO
6. Post the amounts to IO - FB01
7. Settle the amounts to AuC from IO - KO88
8. Create Main Asset (using Step-2 Asset Class) - AS01
9. Assign the Main Asset in IO (Step-5) - KO02
10. Settlement AuC Line Item List - AIAB
11. Settlement AuC - Receiver AIBU

Issue No.: 28
During data migration, the client forgot to transfer two assets whose book values are zero. Now
the client wants to bring those assets to the asset portfolio for reporting purposes. The client
needs both acquisition cost and accumulated depreciation in FI, including information from the
AM module. As the data migration is already done and the company code in question is already
in the Go-live stage, how can you bring these two assets to FIincluding the Asset module?
The solution for this ticket would be:
Set the company code status to "1" Asset data transfer not yet completed.
Update legacy data using T-code AS91.
Enter the acquisition cost and accumulated depreciation using T-code OASV
Issue No.: 29
The user wants to transfer an asset from one asset class to another asset class. A depreciation
expense of the new asset class is assigned to another account determination. The user wants to
transfer APC, accumulated depreciation, and depreciation expenses to G/L accounts that are
assigned to the new asset class. Transaction code ABUMN has fields for ACP and accumulated
depreciation. The user is wondering how depreciation expenses will be transferred from the old
accounts to the new account.
Through transaction code ABUMN, you can reclassify assets. In the reclassification process, you
can only transfer APC and accumulated costs to a new asset class with immediate effect.
Depreciation expenses will be transferred to the new G/L when you run depreciation. However,
during the depreciation run, you can't transfer previous depreciation expenses that were already
charged to the cost center. But you can transfer current-year depreciation to the new depreciation
expenses account. While entering the transaction in transaction code ABUMN, enter in the value
date field the date on which you want to transfer your expenses to the new account.
Issue No.: 30
After the depreciation run, the user changed the capitalized date and the depreciation start date in
the asset master. After making changes in the asset master, the user once again ran depreciation

in "repeat run" mode. But changes made to the asset master did not hit depreciation, and the
difference value is appearing as a planned value when checked in T-code AW01N
If you are making any changes in the asset master that affect depreciation that is already posted,
you must follow this procedure:
Recalculate depreciation using T-code AFAR.
Repeat the depreciation run using T-code AFAB.
Issue No.: 31
While running the year-end closing process through transaction code AJAB, the system gives the
following errors:
"Asset is incomplete and has to be completed. Message no. AU083"
Diagnosis:
The asset 000000100001-0000 is marked as incomplete. The asset was created by someone who
did not have the asset accountant asset view. When this is the case, the system expects that
certain required fields are not maintained.
Procedure:
You can add the necessary specifications using the master data change transaction and the needed
asset view.
The system gives this type of error when the asset master was not properly maintained. You can
execute transaction code AUVA to get the list of incomplete assets. After getting the list of
incomplete assets, maintain the necessary data for the asset master and rerun transaction code
AFAB.
Issue No.: 32
The user wants to post a transaction in the year 2008 through transaction code F-90. While
posting the transaction, the system returns the following error:
"You cannot post to asset in company code 9999 fiscal year 2008 Message no. AA347."
Diagnosis:
"A fiscal year change has not yet been performed in Asset accounting for company code 9999."
Procedure:
Check the asset value date
It looks like the user entered an asset acquisition in fiscal year 2008 for company code 9999, for
which the assets accounting (AA) fiscal year change has not been carried out.
For AA, it is required that the user carry out the fiscal year change before entering a transaction
in the New Year.
Run transaction code AJRW to change the fiscal year. The latest date you can run this transaction
code is the last business day of a financial year.
Issue No.: 33
The user wants to move assets to another class because the assets were created under the wrong
asset class. The old asset is capitalized on 08/01/2008. Since the depreciation key is 000, there is
no depreciation running for that asset.
Now the user wants to transfer the asset to another class, so the old asset is removed (or may be
retired) with an acquisition date of 08/01/2008, so that the depreciation expenses can be
calculated from 08/01/2008.

This is a case of reclassification of assets. In transaction code ABUMN, = enter the APC and the
accumulated cost along with an asset value date of 08/01/2008. In the receiver asset master
screen, enter the desired depreciation key and the depreciation start date.
Issue No.: 34
Is it possible to integrate the sale of assets with the SD module? It will involve some sales tax
and also the client wants to generate an invoice in the SAP solution. Can the SD module be used
for this?
Follow these steps for selling assets with integration with the SD module:
Retire the asset without customer (T-code ABAON). This will credit the APC and debit the
clearing account (which is a P&L account).
Then take a non-valuated material for asset sale purpose, and sell the same using SD. Make sure
you have a separate pricing procedure/SD document type, etc., where the account key ERL will
post to the clearing account mentioned in step 1. You can collect sales tax/excise, etc., as usual.
No.: 35
While capitalizing assets, the user capitalized $10,000. During the year-end process, the user
realized he has wrongly capitalized $10,000 instead of $7,000. Now the user wants to rectify this
by posting a credit transaction through transaction code F-90. While crediting, SAP R/3 returns
the following message: "acquisition value negative in the area 15." What does this mean? How
can you solve this issue and correctly post the document? Is there any other way to decapitalize
an asset?
To see the negative book value check box, you will have to first activate it in the screen layout.
To do this, go to Master Data Screen layout for Asset depreciation areas, select the screen
layout attached to the asset class to which the asset in question belongs, and click on Field group
rules. Here you can make negative values optional.
If you want to allow the negative book value for all of the assets created in that particular asset
class, follow the menu path: Valuation depreciation areas Determine depreciation areas in
the asset class. Select the asset class, click on the depreciation area, and check the negative book
value check box.
If you want to allow negative book values only for a particular asset, you can use transaction
code AS02. Go to the Depreciation tab, double-click on depreciation area 15, and then check the
negative values allowed check box.
Issue No.: 36
While creating assets under asset class XXXX, the user is getting default depreciation terms and
the system does not allow changing depreciation terms. The user does not want the default
depreciation key. How can you resolve this situation?
It sounds as if the depreciation key has been set as the default for the asset class. Check this in
the IMG by doing the following:
Go to the Depreciation Areas screen layout using T-code OA21. This transaction determines how
fields of depreciation areas in the asset master behave. This transaction code controls whether or
not fields are editable.
Determine depreciation areas in an asset class using T-code OAYZ. This transaction code
determines screen layout of the asset class and depreciation keys assigned to that asset class.

Issue No.: 37
In AA the client has not closed the year 2005, and so 2006 cannot be closed. For 2005, there are
errors and recalculations required for depreciation. However, if this is done, it will hit the FI and
figures submitted for 2005 will change in the SAP solution. From an audit perspective, this
cannot be permitted. How can the user remedy this?
The corrections must be made to enable you to close FI-AA for 2005 and carry forward into
2006. If these corrections will significantly change your balance sheet, you can "neutralize" them
by posting manual entries to bring your overall balance sheet back to what has already been
reported, and then reverse these in 2006. And convince your auditor accordingly.
Issue No.: 38
The user is trying to post unplanned depreciation for an asset for depreciation area 33, i.e., the
depreciation area for group currency, using the transaction type 643 and T-code ABAA. While
posting, the following message pops up: "In Dep. Area 01, you can post manual depreciation up
to the amount 0.00 only." The assets explorer shows the net book value as $1800.
This error generally appears after posting the unplanned depreciation when the net book value of
those assets after considering the planned depreciation becomes negative. Depreciation does not
allow negative book values.
Issue No.: 39
When you retire an asset, you only want the depreciation that has been posted to be reversed, i.e.,
accumulated depreciation up to the last month has to be reversed. However, the system is also
taking the current month's unplanned depreciation into consideration when reversing
accumulated depreciation and hence the profit and loss is calculated incorrectly. How can this be
changed?
You assign the period control method in the depreciation key. The period control method controls
how depreciation will be calculated during acquisition, retirement, etc. Check the period control
method assigned to your depreciation key, which in turn is assigned to the asset master.
Issue No.: 40
The user is trying to create an asset master using transaction code AS01. He is able to see fields
in the General, Time dependent, and Allocations tabs, but is not finding fields in the Depreciation
Area tab. As a result, the user is unable to specify the depreciation key and life of an asset.
Check your screen layout for depreciation areas (transaction code AO21).
In T-code OAYZ, make sure that the depreciation areas are activated and a depreciation key is
assigned. Also, check the screen layout rule for the depreciation area. It is the last column in the
table after useful life and index. This is where you enter the depreciation screen layout.
Issue No.: 41
Suppose that during year end, the period for both March and April are open and the depreciation
run for April is also executed. The asset year closing for the previous year is not done. Now an
adjustment in depreciation is to be made in the previous year (for the March period) and the user
has to run depreciation once again for March. Is this possible?
Run a depreciation recalculation (transaction code AFAR) before you execute another
depreciation run.

Issue No.: 42
Assume the following scenario in AA:
Life of the asset: 3 years
Original Cost: 60,000; Scrap Value: 15,000.
The configuration was done in such a way that the SAP solution was taking the original cost as
the basis for calculating depreciation. Thus, it is calculating depreciation as follows:
1st Year: 20,000
2nd Year: 20,000
3rd Year: 5,000
However, the user requirement is that depreciation should be calculated based on original cost
net of scrap value. That is, depreciation should be as follows:
1st Year: 15,000
2nd Year: 15,000
3rd Year: 15,000
This could be achieved by using T-code AFAMA in SPRO by resetting (for each depreciation
key) the scrap value field as "Base Value is reduced by the Scrap Value Amount."
Issue No.: 43
The user acquired his first set of assets in the month of February 2008 and is trying to run
depreciation starting from February. While running depreciation, the system returns the
following message: "According to the posting cycle, you should post period 001 next. Either
enter period 001, which corresponds to the posting cycle, or request an unplanned posting run
explicitly for this parameter."
If your posting cycle is monthly, then your SAP solution expects depreciation to run for every
period in sequential order. So, you can't run February until you have completed the January
depreciation run. Since you have acquired assets in the month of February, you are not running
depreciation for the month of January. However, SAP R/3 is expecting you to run depreciation
for January also. To overcome this, you have to do one of the following: (1) run depreciation for
the month of January and then the month of February or (2) select the unplanned posting run for
February. The unplanned run lets you skip over periods (in instances like this).
Issue No.: 44
The user wants to attach JPG pictures of assets to the asset master record. How can he do this?
You can attach JPG pictures to an asset master. From the asset master record menu, choose
System Services for Object Create Attachment.
Issue No.: 45
In January 2008, a user noticed that assets purchased in 2007 were not recorded in the books of
account. In the meantime, the user closed the books of account for 2007. Now the user wants to
disclose this asset in his books of account from January 2008.
This issue can be handled in two different ways, depending upon user requirements, i.e., from
which date the user wants to calculate depreciation expenses.
If the user wants to calculate depreciation from January 2008, then post the asset acquisition
using transaction code F-90 with reference to a vendor or using transaction code F-91 through a
clearing account.

If the user wants to charge depreciation starting from the original purchase date, then post the
acquisition through transaction code ABNAN. Then enter that date, 07/01/2007 in this example,
in the Orig. val.dat field as shown in Figure 3.10.

Issue No.: 46
The user is configuring the depreciation key. He has a unique requirement for calculating
depreciation for the month of acquisition as well as retirement. Here is the requirement:
If the asset is purchased from the 1st to the 15th of a month, the depreciation should be
calculated for the full month. If the assets are purchased after the 15th of a month, then no
depreciation for the month of purchase is calculated. However, depreciation should be calculated
for the full month for subsequent months.
The start date and end date of depreciation are controlled through the period control method. You
are assigning a calendar here to control how depreciation will be calculated for the acquisition
month.
See your configuration by using transaction code OAVH (menu path: IMG Financial
Accounting Asset Accounting Depreciation Valuation Methods Period Control
Define Calendar Assignments).
Issue No.: 47
When the user is processing asset impairment through transaction code ABMR, the system pops
up with the Depreciation Areas screen. The user does not want this pop-up screen. Is there any
way of turning off this pop-up and defaulting to the appropriate areas?

It is ideally advisable not to change this configuration. This pop-up window lets you select your
desired depreciation areas for asset impairment. If you want to avoid this, you have to change the

configuration through transaction code OA81. In this transaction code, you are setting automatic
posting.
Issue No.: 48
How can the user change the screen layout for equipment masters in order to add warranty
information?
If you are trying to put the warranty information on the equipment master data record itself, you
can configure this in the IMG within the PM module.
Follow the menu path: IMG Plant Maintenance and Customer Service Master Data in
Plant Maintenance and Customer Service Technical Objects General Data Set View
Profiles for Technical Objects.
The transaction code for Set View Profiles for Technical Objects controls various field layouts of
the equipment master.
Issue No.: 49
A user needs help with the following situation:
Some assets will be purchased for $50 million. Then, after using them for 12 years, they can be
sold for $5 million. So, the depreciable basis needs to be $45 million instead of $50 million over
12 years, or $3.750 million per year. The method will be straight line. So at the end of the 12
years, the net book value should be $5 million.
The SAP R/3 system comes with two options to handle the scrap: (1) by defining an absolute
percentage or (2) by entering an absolute value.
You can define an absolute percentage in the scrap key and then assign the key to the asset
master. To define the scrap key, use transaction code ANHAL (menu path: IMG Financial
Accounting Asset Accounting Depreciation Valuation Methods Further Settings
Define the Cutoff Value Key).

Issue No.: 50
The user posts an acquisition transaction through transaction code F-90 and expects the
capitalization and depreciation start date to be filled by the system. SAP help says the
capitalization date and depreciation start date will be filled by the system with the first
acquisition date. But this is not happening in his case. How can this be resolved?
As per SAP standard practice, on the first acquisition, the system will populate capitalization and
the first depreciation date. If this is not happening, check your configuration setting in
transaction code AO73 (menu path: IMG Financial Accounting Asset Accounting
Transactions Acquisitions Define Transaction Types for Acquisitions Define
Transaction Types for Acquisitions).

In the screen that appears, shown in Figure 3.13, check whether the Capitalize fixed asset box is
checked. If not, check it.

Issue No.: 51
While posting a transaction through transaction code ABSO- Miscellaneous Transaction, the
system returns an error message. After further analysis, the user finds that his company code is
activated for parallel currencies. How can the user set up depreciation areas for parallel
currencies?
If your company code is set up for multiple currencies and has implemented asset management,
then be sure you are complying with the following steps:
Verify how many currencies are active for your company code. You can verify this setting in
transaction code:______ (menu path: IMG Financial Accounting Financial Accounting
Global Settings Company Code Multiple Currencies Define additional local
currencies).
Review your depreciation areas in AA. In case of multiple currency scenarios, you should have
one additional depreciation area for each currency. You can check this setting in transaction code
OADB (menu path: IMG Financial Accounting Asset Accounting Valuation
Depreciation Areas Define Depreciation Areas).
For each additional depreciation area, define the depreciation transfer rule with transaction code
OABC (menu path: IMG Financial Accounting Asset Accounting Valuation
Depreciation Areas Specify Transfer of Depreciation Terms). You must set up the transfer
values for additional depreciation areas from book depreciation area 01.
Similar to step 3, you have to set up the APC transfer rule. You can set up this transfer rule
through transaction code OABD (menu path: IMG Financial Accounting Asset Accounting
Valuation Depreciation Areas Specify Transfer of APC Values).
Now you can set up currency for additional depreciation areas through transaction code OAYH
(menu path: IMG Financial Accounting Asset Accounting Valuation Currencies
Define Depreciation Areas for Foreign Currencies).