You are on page 1of 53

EHP3 for SAP ERP 6.

0 December 2009 English

Asset Accounting (162)


Business Process Documentation

SAP AG Dietmar-Hopp-Allee 16 69190 Walldorf Germany

SAP Best Practices

Asset Accounting (162): BPD

Copyright
Copyright 2009 SAP AG. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, System i, System i5, System p, System p5, System x, System z, System z9, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, Informix, i5/OS, POWER, POWER5, POWER5+, OpenPower and PowerPC are trademarks or registered trademarks of IBM Corporation. Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries. Oracle is a registered trademark of Oracle Corporation. UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group. Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc. HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C, World Wide Web Consortium, Massachusetts Institute of Technology. Java is a registered trademark of Sun Microsystems, Inc. JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape. SAP, R/3, xApps, xApp, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary. These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.

SAP AG

Page 2 of 53

SAP Best Practices

Asset Accounting (162): BPD

Icons
Icon Meaning Caution Example Note Recommendation Syntax External Process Business Process Alternative/Decision Choice

Typographic Conventions
Type Style Description

Example text Words or characters that appear on the screen. These include field names, screen titles, pushbuttons as well as menu names, paths and options. Cross-references to other documentation. Example text Emphasized words or phrases in body text, titles of graphics and tables. EXAMPLE TEXT Example text Names of elements in the system. These include report names, program names, transaction codes, table names, and individual key words of a programming language, when surrounded by body text, for example, SELECT and INCLUDE. Screen output. This includes file and directory names and their paths, messages, source code, names of variables and parameters as well as names of installation, upgrade and database tools. on the keyboard, for example, function keys (such as F2) or the ENTER key.

EXAMPLE TEXT Keys

Example text <Example text>

Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation. Variable user entry. Pointed brackets indicate that you replace these words and characters with appropriate entries.

SAP AG

Page 3 of 53

SAP Best Practices

Asset Accounting (162): BPD

Contents
Asset Accounting.................................................................................................................................5 1 Purpose.............................................................................................................................................5 2 Prerequisites.....................................................................................................................................6 2.1 Master Data................................................................................................................................6 2.2 Roles..........................................................................................................................................6 3 Process Overview Table....................................................................................................................8 4 Business Process Steps..................................................................................................................13 4.1 Asset Master Data Creation and Maintenance..........................................................................13 4.2 Asset Explorer ..........................................................................................................................17 4.3 Asset Acquisitions.....................................................................................................................19 4.3.1 Acquisition from Purchase with Vendor...............................................................................19 4.3.2 Acquisition with Automatic Offsetting Entry.........................................................................20 4.3.3 Retirement with Revenue...................................................................................................21 4.3.4 Asset Sale without Customer..............................................................................................24 4.3.5 Retirement Due to Scrapping..............................................................................................25 4.3.6 Intra-company Transfers.....................................................................................................26 4.3.7 Post-Capitalization..............................................................................................................28 4.3.8 Unplanned Depreciation.....................................................................................................30 4.4 Asset under Construction Settlement .......................................................................................31 4.5 Create Assets for Complete AUC Settlement............................................................................34 4.6 Complete Order and Update Final Settlement Rule...................................................................35 4.7 Execute Final Settlement .........................................................................................................36 4.8 Asset Explorer Periodic Reporting ........................................................................................38 4.8.1 Depreciation Posting Run...................................................................................................39 4.8.2 Recalculating Values..........................................................................................................42 4.8.3 Depreciation Simulation/Primary Cost Planning..................................................................44 4.8.4 Open and Close FI Period Asset.........................................................................................46 4.8.5 Account Reconciliation.......................................................................................................46 4.8.6 Fiscal Year Change............................................................................................................48 4.8.7 Year-End Closing...............................................................................................................49 4.9 Information System...................................................................................................................51 4.10 Check Consistency ................................................................................................................52

SAP AG

Page 4 of 53

SAP Best Practices

Asset Accounting (162): BPD

Asset Accounting 1 Purpose


The functions for Tangible Asset Handling enable you to illustrate and document the development of fixed assets for accounting purposes. Asset accounting is a subsidiary ledger of the general ledger and is used to manage and document in detail fixed asset transactions. Ledger accounting, you can update depreciation and changes to asset balance sheet values in asset accounting. You can also make various account assignments to cost accounting for these transactions. As a result of the integration in SAP ERP, Asset Accounting (FI-AA) transfers data directly to and from other SAP ERP components. For example, you can post from the Material Management (MM) component directly to FI-AA. When you purchase an asset or produce an asset in-house, you can directly post the invoice receipt or goods receipt, or the withdrawal from the warehouse to assets in the Asset Accounting component. At the same time, you can pass on depreciation and interest directly to the Financial Accounting (FI) and Cost Accounting (CO) components. From the Plant Maintenance (PM) component, you can settle maintenance activities that require capitalization to assets. To handle tangible assets, you can use the business functions of the following system components: Component Asset Accounting (FIAA) Cost Accounting (CO) Functions Valuation of fixed assets and settlement of assets under construction Posting cost-accounting depreciation Financial Accounting (FI) Integration with the general ledger and other subsidiary ledgers

Process Flow
The Tangible Asset Handling scenario provides detailed management and monitoring of fixed assets from the perspective of the lifecycle of individual assets. This scenario covers the entire life of the asset from the purchase order or initial acquisition (which can be managed as an asset under construction) right through to retirement of the asset. Between these two events, the system handles all asset-related business transactions and ensures integration with the general ledger.

SAP AG

Page 5 of 53

SAP Best Practices

Asset Accounting (162): BPD

2 Prerequisites
2.1 Master Data
A range of indispensable master and organizational data was created in your ERP system in the implementation phase, such as the data that reflects the organizational structure of your company, and master data that suits its operational focus, for example, master data for materials, vendors, customers, and so on. This master data consists of standardized SAP Best Practices default values and enables you to go through the process steps of this scenario.

You can test the scenario with other material, or organizational data for which you have created master data. To find out how to create master data, refer to the Master Data Procedures documentation. Use the following master data in the process steps described in this document: Master Data Cost Center Value * Selection All Comment All cost centers are possible

2.2 Roles
Business Role SAP_BPR_ASSET-S (Assets Accountant) Details Activity Transaction AS02 AS03 AS06 AS05 AS11 AW01N F-90 ABZON F-92 ABAON ABAVN ABUMN ABNAN ABZU ABMR ABAA AIAB AFAB

SAP AG

Page 6 of 53

SAP Best Practices Business Role Details

Asset Accounting (162): BPD Activity Transaction AFAR ASKBN S_ALR_87012936 and S_ALR_87099918 AJRW ABST2 AJAB OAAQ OAAR

SAP_BPR_AP_CLERK-S1 (Accounts Payable Accountant 1) SAP_BPR_AP_CLERK-S2 (Accounts Payable Accountant 2) SAP_BPR_FINACC-K (Finance Manager) SAP_BPR_EMPLOYEE-S (Employee (Professional User))

F-47 F-54 F-48 S_ALR_87003642 (OB52) SM37

SAP AG

Page 7 of 53

SAP Best Practices

Asset Accounting (162): BPD

3 Process Overview Table


Process step External process reference
See Create Assets (155.02) scenario

Business condition
A fixed asset is an object, a right, or another item owned by an enterprise that is intended for longterm use and can be individually identified in the balance sheet. Analyze changes in the value of an asset. The asset acquisition comes through the vendor. The asset acquisition comes before the receipt of the invoice. Make an asset sale with revenue with a customer sale.

Business role
Assets Accountant

Trans-action code
AS02, AS03, AS06, AS05, AS11

Expected results

Master Data Maintenance

The asset master record has been created under the number you specified in company code.

Asset Explorer Acquisition from purchase with vendor Acquisition with Automatic Offsetting Entry Retirement with Revenue

Assets Accountant Assets Accountant Assets Accountant

AW01N

The master data and values of the asset can be shown The asset has been capitalized with the amount specified. The asset has been capitalized with the amount specified.

F-90

ABZON

Assets Accountant

F-92

A retirement has been recorded for the specified asset. The gains or losses realized were calculated automatically and posted to the accounts defined in Customizing. A retirement has been recorded for the specified asset. The gains or losses realized were calculated automatically and posted to the accounts defined in Customizing. A retirement has been recorded for the specified asset. The gains or losses realized were calculated automatically and

Asset Sale without customer

Make an asset sale with revenue without a customer.

Assets Accountant

ABAON

Retirement due to scraping

Make a retirement without revenue with total loss to scrap.

Assets Accountant

ABAVN

SAP AG

Page 8 of 53

SAP Best Practices Process step External process reference Business condition

Asset Accounting (162): BPD Business role Trans-action code Expected results

posted to the accounts defined in Customizing. Intracompany transfers Carry intracompany transfer within a company. Assets Accountant ABUMN Either the entire acquisition and production costs (APC) and accumulated depreciation (complete transfer), or the specified APC portion with the relevant proportional accumulated depreciation (partial transfer) are transferred to the receiving asset. The postcapitalization is posted to the new asset. The unplanned depreciation has been posted to all of the depreciation areas specified and is displayed separately. The FI document is posted during the Depreciation run.

PostCapitalization

Subsequent correction to the acquisition and production cost of an asset. Unexpected permanent reduction in the value of an asset.

Assets Accountant

ABNAN

Unplanned Depreciation

Assets Accountant

ABAA

Asset under Construction Settlement

There are three processing types defined for settlement

Assets Accountant

KO88

Preliminary settlement rule allocates revenues to alternate CO object with primary cost transfer. Settlement rule for costs is created automatically with assignment to AUC asset. The costs captured in the order are posted to the AUC asset and reflected on the balance sheet.

SAP AG

Page 9 of 53

SAP Best Practices Process step External process reference Business condition In this activity, you create assets for complete AUC settlement

Asset Accounting (162): BPD Business role Run the Create Asset (155.02) scenario document, with master data provided. that is, linear asset class 9100 for company code #1000
Assets Accountant KO04

Trans-action code

Expected results

Create Assets for Complete AUC Settlement

Create final assets in recognition of substantial completion and legal title transfer of ownership.

Complete Order and Update Final Settlement Rule

This step is only relevant for order type YK60

Internal order for AUC asset is technically complete so the system performs full settlement during next order settlement run
Full Settlement of costs results in capitalization of final asset, which is depreciated in subledger

Execute Final Settlement

The full settlement transfers the costs from the AUC asset to the completed asset Allows you to analyze changes in the value of individual asset master records
The depreciation posting should be run periodically (annually, semiannually, quarterly, or monthly). The system creates posting documents for each depreciation area and account group in accordance with the posting cycles specified in Customizing In certain circumstances, you might need to

Assets Accountant

KO88

Asset Explorer Periodic Reporting

Assets Accountant

AW01N

The Planned Values tab shows all the transactions.

Depreciation Posting Run

Assets Accountant

AFAB

The planned depreciation is posted to the accounts defined in Customizing through collective documents.

Recalculating Values

Assets Accountant

AFAR

If changes have occurred as a result of the recalculation

SAP AG

Page 10 of 53

SAP Best Practices Process step External process reference Business condition
recalculate the planned annual depreciation for a variety of fixed assets.

Asset Accounting (162): BPD Business role Trans-action code Expected results

process, the planned depreciation is adjusted for the fixed assets concerned. The new planned depreciation is used as the basis for subsequent depreciation posting runs. Assets Accountant S_ALR_87012936 and S_ALR_87099918 The planned costs are posted directly to the assigned Controlling objects and can be evaluated via cost center reporting or internal order reporting.

Depreciation Simulation/ Primary Cost Planning

Forecast the planned depreciation of complex fixed assets over several years. Post the planned depreciation as planned costs to the cost centers or internal orders to which the individual fixed assets are assigned. Close the posting periods for FI-AA and open the new periods for FI-AA.

Open and Close FI Period Asset

Finance Manager

S_ALR_87003642 (OB52)

No more FI-AA postings can be made to the previous period. Postings for the future periods are allowed. The report generates a list of accounts showing differences. When there are differences, the differences must be analyzed, before the next step (Year-End Closing) is started. The asset values from the previous fiscal year are carried forward cumulatively into the new fiscal year. Postings can now be made to the new fiscal year. If you have performed the yearend closing in update mode, you can no longer post to the closed fiscal year.

Account Reconciliation

Account reconciliation between FI and AA.

Assets Accountant

ABST2

Fiscal Year Change

The fiscal year change can only be carried out (even in test mode) for the new fiscal year.

Assets Accountant

AJRW

Year End Closing

You can use the year-end closing program to close the fiscal year for one or more company codes from an

Assets Accountant

AJAB and OAAQ and OAAR

SAP AG

Page 11 of 53

SAP Best Practices Process step External process reference Business condition
accounting perspective. Information System The Information System in Asset Accounting features a series of reports arranged in a tree structure. After you have made all the required system settings, you can now check their consistency.

Asset Accounting (162): BPD Business role Trans-action code Expected results

Assets Accountant

various reports

Check Consistency

SAP AG

Page 12 of 53

SAP Best Practices

Asset Accounting (162): BPD

4 Business Process Steps


4.1 Asset Master Data Creation and Maintenance
Use
A fixed asset is an object, a right, or another item owned by an enterprise that is intended for long-term use and can be individually identified in the balance sheet. Maintaining fixed assets involves creating, changing, and displaying asset master records. The different items of information are structured according to area of use and functions in the system to make it easier for users to create, maintain, and evaluate master data. Each asset master record consists of two parts that are described below.

General Master Data / Organizational Assignments


This part of the master record contains general information about the fixed asset. The following field groups exist: General information (description, quantity, and so on) Account assignment Posting information (for example, capitalization date) Time-dependent assignments (for example, cost center) Information for plant maintenance Entries for net worth tax Information on real estate Information on the origins of the asset Physical inventory data User fields/evaluation groups Insurance data

To define the layout of an asset master record, you use a screen layout rule that is defined within the asset class. For example, you can hide the license plate number for real estate and buildings, but define it as a required entry field for vehicles.

Valuation Parameters
In the valuation section of an asset master record, you define how a fixed asset is valuated for each depreciation area. In our example, the main depreciation parameters are the start date for ordinary depreciation that is determined by the depreciation key and the asset value date of the acquisition posting, the depreciation key, and the useful life.

Prerequisites
Cost Center Master Data are created.

SAP AG

Page 13 of 53

SAP Best Practices

Asset Accounting (162): BPD

To execute this activity, run the processes in the Create Cost Center (155.03) scenario, using the master data from this document.

Procedure
Create Asset Master Data. Create 8 new assets to be used in subsequent steps: four legacy takeover assets with transaction AS91 and four current assets with transaction AS01. Final asset is created in line with accounting policy in recognition of legal ownership and transfer of title.

Master Data
Create four legacy takeover assets with transaction AS91 with master data provided. # Tcode Asset Class Company Description Cost Capitalizat Depr Useful Cum. Acq Accu Code Center ion Date ** Life Value m. Key Years Ordin ary Depr 1000 1000 1000 1000 Water Mains 901032 12/31/2008 LINA 100 Fire Truck# 1 700040 12/31/2008 LINA 8 $1,200,00 0 $96,000 $90,000 $1,800,00 0 $0 $0 $0 $0

1 AS91 2 AS91 3 AS91 4 AS91

9100 3100 2000 1000

Pump House 951033 12/31/2008 LINA 15 Machinery Land 100010 12/31/2008 0000 999

Capitalized on ** AS91<Date in closed fiscal year prior to data take-on date defined in configuration> 1. Access the transaction choosing one of the following navigation options: Option 1: SAP Graphical User Interface (SAP GUI) SAP ERP Menu Transaction code Accounting Financial Accounting Fixed Assets Asset Create Asset AS91 Create legacy takeover asset (0ne time only) Asset accountant Assets Accountant (SAP_BPR_ASSET-S) Asset Accounting Assets Create Asset Master Record

Business Role Business role (Name) Business role Menu

Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business role

2. On the Create Asset: Initial screen, enter asset class (select from the list provided), company code (1000), number of similar assets. Choose Enter.

SAP AG

Page 14 of 53

SAP Best Practices

Asset Accounting (162): BPD

3. On the Create Asset: Master data screen, in the General tab, enter a description in the Description field and uncheck the Manage historically check box. 4. Enter capitalization date, historical date asset was purchased. 5. Choose the Time-dependent tab. 6. Enter a cost center. 7. Go through the other tabs. 8. Enter other required fields as necessary (depending on the asset class). 9. Choose Depreciation areas. 10. Enter or change the depreciation keys and useful lives for the appropriate depreciation areas, if required. 11. Choose takeover values and enter cumulative acquisition value and accumulated ordinary depreciation for each depreciation area. Note: Accumulated ordinary depreciation needs to be entered as a credit value to reduce net book value of asset. 12. Choose Save. 13. Note Asset number created.

Result
The asset is created with takeover values in asset sub-ledger. Note: Take-over values also need to be entered into GL with transfer posting (transaction code OASV) to ensure sub-ledger and general ledger agree with each other. Remember to include profit center for each entry.

Master Data
Create four assets with transaction AS01 with master data provided. # 5 6 7 8 T-code AS01 AS01 AS01 AS01 Asset Class 3100 9100 3100 1100 Company Code 1000 1000 1000 1000 Description Police Car Gas Line Segment Fire Truck #2 Building B Cost Center 601040 801031 700040 100010 Depr Key LINA LINA LINA LINA Useful Life Years 4 30 10 60

SAP AG

Page 15 of 53

SAP Best Practices

Asset Accounting (162): BPD

14. Access the transaction choosing one of the following navigation options: Option 1: SAP Graphical User Interface (SAP GUI) SAP ERP Menu Transaction code Business Role Business role (Name) Business role Menu Accounting Financial Accounting Fixed Assets Asset Create Asset AS01 Create asset Asset accountant Assets Accountant (SAP_BPR_ASSET-S) Asset Accounting Assets Create Asset Master Record

Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business role

15. On the Create Asset: Initial screen, enter asset class (select from the list provided), company code (1000), number of similar assets. Choose Enter. 16. On the Create Asset: Master data screen, in the General tab, enter a description in the Description field and uncheck the Manage historically check box. 17. Choose the Time-dependent tab. 18. Enter a cost center. 19. Go through the other tabs. 20. Enter other required fields as necessary (depending on the asset class). 21. Choose Depreciation areas. 22. Enter or change the depreciation keys and useful lives for the appropriate depreciation areas, if required. 23. Choose Save. 24. Note Asset number created.

Result
The asset is created. Assets have no values initially in area: 01 when new assets are created with transaction AS01. Legacy assets created during initial conversion with transaction code AS91 typically have takeover values.

You can also use the following functions to maintain your fixed assets: SAP ERP Menu Transaction Code Accounting Financial Accounting Fixed Assets Asset AS91 (Create Legacy Asset) AS92 (Change Legacy Asset) AS93 (Display Legacy Asset) AS01 (Create Asset) AS02 (Change Asset) AS03 (Display Asset) AS06 (Delete Asset)

SAP AG

Page 16 of 53

SAP Best Practices AS05 (Lock Asset) AS11 (Create Subnumber)

Asset Accounting (162): BPD

Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role Business role Business role menu SAP_BPR_ASSET-S (Assets Accountant) Asset Accounting Assets Create Asset Master Data Asset Accounting Assets Change Asset Master Data Asset Accounting Assets Display Asset Master Data Asset Accounting Assets Delete Asset. Asset Accounting Assets Change Asset Master Data Asset Accounting Assets Block Asset Asset Accounting Assets Create Asset Subnumber

You can create asset subnumbers for a main asset number. The asset subnumber is a sequential number assigned by the system (starting with 1) and is appended to the main asset number. There are several reasons for managing asset components as subnumbers: o o o o o The development of values for asset components is separate for each subnumber. The subnumbers have different cost accounting assignments (for example, different cost centers). Assets are subdivided due to technical considerations (for example, links to equipment in Plant Maintenance). Investment support can be represented as negative subnumbers. If you must manage subsequent acquisitions separately to be able to monitor their depreciation and book values individually, you must manage these acquisitions for independent subnumbers. For all subsequent acquisitions, you must create a subnumber per year of acquisition. You can make sure that this is the case by setting the Acquisition only in the capitalization year indicator in the depreciation key.

4.2 Asset Explorer


Use
The Asset Explorer allows you to analyze changes in the value of individual asset master records. It shows both the planned and posted balance sheet and depreciation values of a fixed asset in different forms and summarization levels. The Asset Explorer consists of A header section where you enter the company code and required asset An overview tree for navigating between different depreciation areas An overview tree that shows the objects that are related to the asset

SAP AG

Page 17 of 53

SAP Best Practices

Asset Accounting (162): BPD

A tab for analyzing planned values, posted values, different parameters, and for comparing fiscal years and depreciation areas.

For a detailed description of these functions and more information about using the Asset Explorer, refer to the SAP ERP documentation

Prerequisites
Asset master records have been created and posted to in the system.

Procedure
1. Access the transaction choosing one of the following navigation options: Option 1: SAP Graphical User Interface (SAP GUI) SAP system menu Transaction code Business role Business role menu Accounting Financial Accounting Fixed Assets Asset Asset Explorer AW01N SAP_BPR_ASSET-S (Assets Accountant) Asset Accounting Assets Asset Explorer

Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role

2. On the Asset Explorer Screen, enter the required data: Field name Company Code Asset Fiscal Year Depreciation Areas Description User action and values #1000 <number of the asset> <fiscal year> <select one depreciation area> for example, 2000 for example, <current year> For example, 01 Book Depreciation Comment

Result
The Planned Values tab shows all the transactions that change the acquisition and production costs, all the depreciation values that have been calculated for the asset (including proportional value adjustments), the net book value, and any calculated interest. The Posted Values tab shows all the booked transactions. The Comparison tab shows the several years. The Parameters tab shows the depreciation key and further characteristics of the asset. Note: Assets have no values initially in area: 01 when new assets are created with transaction AS01. Assets created during initial conversion with transaction code AS91 typically have takeover values.

SAP AG

Page 18 of 53

SAP Best Practices

Asset Accounting (162): BPD

4.3 Asset Acquisitions


4.3.1 Use
An external asset acquisition is a business transaction resulting from the acquisition of an asset from a business partner (in contrast to an in-house acquisition). You can post the acquisition of an external asset in several different ways: In Asset Accounting (FI-AA) integrated with Accounts Payable (FI-AP) In Asset Accounting without integration with Accounts Payable (posting to a clearing account with or without clearing). There are two scenarios: a) The asset acquisition comes before the receipt of the invoice. The offsetting entry is posted automatically. b) The asset acquisition is posted after the receipt of the invoice. The invoice was posted as an open item to a clearing account. This scenario is not described further here. For more information, refer to the Accounts Payable Accounting documentation - N76.

Acquisition from Purchase with Vendor

Prerequisites
You can also create the asset master record directly from the posting transaction. In the following step, however, it is assumed that the asset master record has already been created using transaction AS01 (as described under scenario Create Assets (155.02)).

Procedure
1. Access the transaction choosing one of the following navigation options: Option 1: SAP Graphical User Interface (SAP GUI) SAP system menu Transaction code Business role Business role menu Field name Document Date Type Company Code Reference PstKy Posting Key Accounting Financial Accounting Fixed Assets Posting Acquisition External Acquisition With Vendor F-90

Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role SAP_BPR_ASSET-S (Assets Accountant) Asset Accounting Postings Acquisition from purchase w. vendor Description User action and values <document date> KR #1000 <reference information> 31 Any, for example, invoice number Comment for example, today

2. On the Acquisition from purchase with vendor screen, make the following entries:

SAP AG

Page 19 of 53

SAP Best Practices Field name Account Amount in Document Currency Calculate tax PstKy Account Posting Key Asset Description Vendor User action and values <vendor number> <ENTER> <amount>

Asset Accounting (162): BPD Comment for example, 300000 for example, 11,900

<activate> 70 <asset number> Select one from list that was created in step 4.1 with AS01 transaction code..

TType

Transaction type

100 <ENTER>

Amount Tax Code Tax Jur. Quantity Tax code Tax Jurisdiction Quantity

<amount> <domestic tax code>

for example, 11,900 for example, <P0 > For example, CAON

Quantity of assets purchased

for example, 1

3. Post the document (CTRL+S). 4. Repeat Procedure steps 1-3 again for second, third and fourth assets created in step 4.1 (with AS01 transaction code). Select another vendor and assign a unique value for each asset..

Result
The four assets have been capitalized with the amount specified.. In the asset master record, the capitalization and depreciation start dates were set when the first acquisition was posted.

4.3.2 Use

Acquisition with Automatic Offsetting Entry

With this transaction the asset can be posted automatically against the Clearing account fixed asset acquisition.

Procedure
1. Access the transaction choosing one of the following navigation options: Option 1: SAP Graphical User Interface (SAP GUI) SAP system menu Accounting Financial Accounting Fixed Assets Posting Acquisition External Acquisition Acquis. w/Autom. Offsetting Entry

SAP AG

Page 20 of 53

SAP Best Practices Transaction code Business role Business role menu ABZON

Asset Accounting (162): BPD

Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role SAP_BPR_ASSET-S (Assets Accountant) Asset Accounting Postings Acquis. w/Autom. Offsetting Entry

2. When you open up the Enter Asset Transaction: Acquis. w/Autom. Offsetting Entry screen for the first time, you see the Enter a Company Code dialog box. Select the value 1000 and choose Continue. 3. On the Enter Asset Transaction: Acquis. w/Autom. Offsetting Entry screen, make the following entries: Field name Existing Asset Document Date Amount Posted Quantity 4. Post the document. Description User action and values <no. of the asset> <document date> <amount> Quantity Comment Select fourth item from list that was created in step 4.1 with AS01 transaction code. for example, today for example, 10,000 For example, 1

Result
The asset has been capitalized with the amount specified. In the asset master record, the capitalization and depreciation start dates were set when the first acquisition was posted.

4.3.3 Use

Retirement with Revenue

Fixed asset retirement is the removal of an asset or part of an asset from the asset portfolio. This removal of a complex fixed asset (or part of a complex fixed asset) is posted from a bookkeeping perspective as an asset retirement. In Asset Accounting, you can post both the sale of an asset and the resulting revenue in one single step. At the same time, you can decide whether to integrate the posting with Accounts Receivable Accounting or to post to a clearing account. Depending on organizational considerations or the business transaction that leads to the retirement, you can distinguish the following types of retirement: An asset is sold, resulting in revenue. The sale is posted with a customer. An asset is sold, resulting in revenue. The sale is posted against a clearing account. An asset had to be scrapped, with no revenue.

An asset retirement can refer to an entire fixed asset (complete retirement) or part of a fixed asset (partial retirement). In both cases, the system uses the asset retirement dates you enter to automatically determine the amounts to be written off for each depreciation area. You can start the partial retirement of a fixed asset by entering one of the following: The amount of the acquisition and production costs being retired

SAP AG

Page 21 of 53

SAP Best Practices A percentage rate A quantity

Asset Accounting (162): BPD

Based on the asset value date and period control, the system automatically determines the reference period for the retirement. The system also automatically calculates any depreciation (value adjustments) applicable to the part of the asset being retired, up to the reference period (retirement). The system automatically retires this depreciation at the time of the retirement transaction. This procedure ensures that the percentage of the book value that is retired is identical to the percentage of the acquisition and production costs that is retired. You must always specify a transaction type to distinguish between prioryear and current-year acquisitions.

Prerequisites
In the following steps, it is assumed that the asset master record has already been created using transaction AS01 (as described under Master Data Maintenance) and has received acquisition postings.

Procedure
1. Access the transaction choosing one of the following navigation options: Option 1: SAP Graphical User Interface (SAP GUI) SAP system menu Transaction code Business role Business role menu Accounting Financial Accounting Fixed Assets Posting Retirement Retirement w/Revenue With Customer F-92

Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role SAP_BPR_ASSET-S (Assets Accountant) Asset Accounting Postings Asset Retire. frm Sale w/ Customer User action and values <document date> DR #1000 <any reference> CAD Posting Key Customer Revenue (sales price) 01 <customer no.> <ENTER> Amount Calculate tax <amount> <activate> for example, 100 for example, 100003 Comment for example, today

2. On the Asset Retire. frm Sale w/Customer: Header Data screen, make the following entries: Field name Document Date Type Company Code Reference Currency PstKy Account Description

SAP AG

Page 22 of 53

SAP Best Practices Field name Date PstKy Account Description Baseline date Posting Key Revenue clearing account

Asset Accounting (162): BPD User action and values Date 50 <revenue account> <ENTER> for example, 700130 Comment for example, todays date

Amount TaxCode Tax Jurisdiction Cost Center Asst Retirement

Revenue (sales price)

<amount> <GST code> CA00

for example, 100 for example, S1 For example, CAON / CAAB for example, 300020

Enter a valid cost center. <activate> Select more data icon from the menu <ENTER>

Asset

<asset no.>

Select one from list that was created in step 4.1 with asset values.. 210 = retirement with revenue 260 = Retirement of current-year acquis. with revenue

Trans. Type

260 or 210

Asset Val. Date Compl.Retirement Amount Posted

Retirement date Amount of APC being retired with partial retirement Amount of APC being retired with partial retirement Number of assets being retired (collective management) with partial retirement

<value date> <amount>

for example, today for example, 100

Percentage Rate

Quantity

<ENTER> 3. Post the document.

SAP AG

Page 23 of 53

SAP Best Practices

Asset Accounting (162): BPD

Result
A partial retirement has been recorded for the specified asset. The gains or losses realized were calculated automatically and posted to the accounts defined in Customizing. If the asset retirement was a complete retirement, the retirement date was set automatically in the asset master record upon posting.

4.3.4 Use

Asset Sale without Customer

In this step, you can book an asset sale without a customer.

Procedure
1. Access the transaction choosing one of the following navigation options: Option 1: SAP Graphical User Interface (SAP GUI) SAP system menu Transaction code Business role Business role menu Field name Asset Accounting Financial Accounting Fixed Assets Posting Retirement Retirement w/Revenue Asset Sale Without Customer ABAON

Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role SAP_BPR_ASSET-S (Assets Accountant) Asset Accounting Postings Asset Sale without Customer User action and values <no. of the asset> <document day> <posting date> Retirement date Revenue (sales price) Net book value from depreciation area as revenue <Choose Partial Retirement (tab)> Amount Posted Percentage Rate Percentage of APC being retired with partial retirement Amount of APC being retired with partial retirement <amount posted> for example, 200 <value date> <revenue> Comment Select one from list that was created in step 4.1.with asset values. for example, today for example, today for example, today for example, 50

2. On the Enter Asset transaction: Asset Sale without Customer screen, make the following entries: Description

Document Date Posting Date Asset Val. Date Manual Revenue Rev. from NBV

SAP AG

Page 24 of 53

SAP Best Practices Quantity Number of assets being retired (collective management) with partial retirement <activate>

Asset Accounting (162): BPD

From Cur.Yr.Acq.

3. Post the document. Use Save on the top of the screen.

Result
A partial retirement has been recorded for the specified asset. The gains or losses realized were calculated automatically and posted to the accounts defined in Customizing. If the asset retirement was a complete retirement, the retirement date was set automatically in the asset master record upon posting.

4.3.5 Use

Retirement Due to Scrapping

Retirement without revenue involves the removal of a complex fixed asset from a companys fixed assets without revenue being realized for the asset (such as in scrapping). When an asset is retired without revenue, the system generates a loss for asset retirement without revenue equal to the retired net book value instead of the revenue and gain/loss posting.

Procedure
1. Access the transaction choosing one of the following navigation options: Option 1: SAP Graphical User Interface (SAP GUI) SAP system menu Transaction code Business role Business role menu Accounting Financial Accounting Fixed Assets Posting Retirement Asset Retirement by Scrapping ABAVN

Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role SAP_BPR_ASSET-S (Assets Accountant) Asset Accounting Postings Asset Retirement by Scrapping

2. On the Enter Asset transaction: Asset Retirement by Scrapping screen, make the following entries: Field name Asset Description User action and values <no. of the asset> <document date> <posting date> Retirement date <value date> <Choose Comment Select one from list that was created in step 4.1 with asset values.. for example, today for example, today for example, today

Document Date Posting Date Asset Val. Date

SAP AG

Page 25 of 53

SAP Best Practices Partial Retirement (tab)> Amount Posted Amount of APC being retired with partial retirement Amount of APC being retired with partial retirement Number of assets being retired (collective management) with partial retirement <activate> <amount>

Asset Accounting (162): BPD

for example, 200

Percentage Rate Quantity

From Curr.Yr.Acquis.

Activate if asset created using AS01 and dont activate if created using AS91.

3. Post the document. Use Save on the top of the screen.

Result
A partial retirement has been recorded for the specified asset. The gains or losses realized were calculated automatically and posted to the accounts defined in Customizing. If the asset retirement was a complete retirement, the retirement date was set automatically in the asset master record upon posting.

4.3.6 Use

Intra-company Transfers

There are three reasons why you might need to carry out an intra-company transfer within a company code: o o o If changes are made to organizational structures (reclassification of asset classes, changes to profit centers, and so on). An intra-company transfer might be necessary if account assignments are incorrect (for example, incorrect asset class). A managed asset under construction is completed for summary settlement.

Intra-company transfers from one fixed asset to another within the same company code can be carried out in one step. Automatic intra-company transfers are only possible, however, if no values from the sending asset are lost and every area of the target asset is supplied with values.

Prerequisites
If a current-year acquisition must be transferred, you should always first perform a reverse posting, followed by a (correct) acquisition posting. You should only transfer current-year acquisitions if no depreciation keys for automatic calculation exist in the master records. If the intra-company transfer involves a transfer to a new asset master record that has yet to be created, you can create the master record as described earlier or generate it from the transfer transaction.

SAP AG

Page 26 of 53

SAP Best Practices

Asset Accounting (162): BPD

In the following example, it is assumed that you have already created the master record before you perform the transfer.

Procedure
1. Access the transaction choosing one of the following navigation options: Option 1: SAP Graphical User Interface (SAP GUI) SAP system menu Transaction code Business role Business role menu Accounting Financial Accounting Fixed Assets Posting Transfer Transfer within Company Code ABUMN

Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role SAP_BPR_ASSET-S (Assets Accountant) Asset Accounting Postings Transfer within Company Code

2. On the Enter Asset transaction: Transfer within Company Code screen, make the following entries: Field name Asset Description User action and values <no. of asset> Comment Select one from list that was created in step 4.1. (with acquisition value) for example, today for example, today for example, today Select one from list that was created in step 4.1. (without acquisition value)

Document Date Posting Date Asset Val. Date Existing Asset Existing asset

<document date> <posting date> <posting date> <no. of the asset> <Choose Partial Transfer (tab)>

Amount Posted Percentage Rate Quantity

Amount of APC being retired with partial transfers Amount of APC being retired with partial transfers Number of assets being retired (collective management) for partial transfers

<posted amount>

for example, 200

From Cur.Yr.Acq.

<activate>

3. Post the document. Use Save on the top of the screen.

Result
SAP AG Page 27 of 53

SAP Best Practices

Asset Accounting (162): BPD

Either the entire acquisition or production costs (APC) and accumulated depreciation (complete transfer), or the specified APC portion with the relevant proportional accumulated depreciation (partial transfer) are transferred to the receiving asset. The standard transaction type for intra-company transfers (300) is configured in such a way that the receiving asset adopts the capitalization start date and the depreciation start date historically from the asset being retired. The transaction types 310, 320, 330 do not adopt the capitalization date and depreciation start date.

4.3.7 Use

Post-Capitalization

Post-capitalization represents subsequent corrections to the acquisition and production costs (APC) of a fixed asset. An example of when you need this type of correction is if you neglect to add expenditures and costs linked with the acquisition or assembly of an asset to its APC in a fiscal year that is now closed. This example can apply to both part assets and entire complex fixed assets. The following example is based on an entire complex fixed asset.

Prerequisites
A post-capitalization asset is created.

To execute this activity, run the procedure below with master data provided.

Procedure
Create a post-capitalization asset master record. Access the transaction choosing one of the following navigation options: Option 1: SAP Graphical User Interface (SAP GUI) SAP ERP Menu Transaction code Business Role Business role (Name) Business role Menu Accounting Financial Accounting Fixed Assets Asset Create Asset AS01 Create Asset (Post Capitalization) Asset accountant Assets Accountant (SAP_BPR_ASSET-S) Asset Accounting Assets Create Asset Master Record

Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business role

1. On the Create Asset: Initial screen, set post-capitalization indicator, enter asset class (select from the list provided), company code (1000), number of similar assets and Enter. 2. On the Create Asset: Master data screen, in the General tab, enter a description in the Description field and uncheck the Manage historically check box. 3. Enter capitalization date for post capitalization missed legacy asset. 4. Choose the Time-dependent tab. 5. Enter a cost center. 6. Go through the other tabs. 7. Enter other required fields as necessary (depending on the asset class).

SAP AG

Page 28 of 53

SAP Best Practices 8. Choose Depreciation areas.

Asset Accounting (162): BPD

9. Enter or change the depreciation keys and useful lives for the appropriate depreciation areas, if required. 10. Choose Save.

Master Data Example


Asset Class 3100 Description Police Vehicle Cost Center 601040 Useful Life 5

The asset needs following entries: Post-Capitalization <activate> Capitalized on <Date in fiscal year that is already closed>

Result
The post-capitalization asset is created. Note: Assets have no values initially in area: 01 when post-capitalization assets are created with transaction AS01. Values are added with subsequent step with transaction ABNAN.

Prerequisites
Post-capitalization revenue posting requires a true account assignment object for revenue. Select an existing order (type Y010) that can accept revenues or create and release a new one prior to postcapitalization entry (ABNAN).

An Internal order is created. To execute this activity, select an order or run the processes in the Create Order (155.12) scenario (order type Y010)

Procedure
Enter Post-capitalization transaction to record historical asset values and post-capitalization revenue. 1. Access the transaction choosing one of the following navigation options: Option 1: SAP Graphical User Interface (SAP GUI) SAP system menu Accounting Financial Accounting Fixed Assets Posting Post-Capitalization

SAP AG

Page 29 of 53

SAP Best Practices Transaction code Business role Business role menu Field name Existing Asset Amount posted Document Date Orig. Val. Dat The historical asset value date is the same as the historical capitalization date. APC Description ABNAN

Asset Accounting (162): BPD

Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role SAP_BPR_ASSET-S (Assets Accountant) Asset Accounting Postings Post-Capitalization User action and values <no. of the asset> <amount> <document date> <Value date of transaction> Comment for example, 7 for example, 2150 for example, today Historical capitalization date, not in current fiscal year Comment

2. On the Enter Asset transaction: Post-Capitalization screen, make the following entries:

Simulate transaction (F9) and double-click line item corresponding to credit side of entry for postcapitalization revenue. Enter true account assignment object with revenue: :Coding Block Order

User action and values <no. of the order>

Select an order (Y010 order type)

3. Post the document. Use Save at the top of the screen.

Result
The post-capitalization is posted to the new asset with standard transaction type 400. The historical depreciation (accumulated depreciation) is determined automatically based on the value date originally specified. If the asset is already written off completely as a result of the accumulated depreciation determined, a posting is only made from the asset balance sheet account to the accumulated depreciation account. If a net book value still exists at this time, it is posted to the revenue from postcapitalization account defined in Customizing.

4.3.8 Use

Unplanned Depreciation

Unplanned depreciation occurs as a result of an unexpected permanent reduction in the value of an asset. Unplanned depreciation occurs in addition to the automatically determined ordinary depreciation.

Prerequisites

SAP AG

Page 30 of 53

SAP Best Practices

Asset Accounting (162): BPD

Procedure
1. Access the transaction choosing one of the following navigation options: Option 1: SAP Graphical User Interface (SAP GUI) SAP system menu Transaction code Business role Business role menu Field name Company Code Asset Document Date Posting Date Trans. Type Accounting Financial Accounting Fixed Assets Posting Manual Value Correction Unplanned Depreciation Area ABAA

Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role SAP_BPR_ASSET-S (Assets Accountant) Asset Accounting Postings Unplanned depreciation Area User action and values #1000 <no. of the asset> <document date> <posting date> 650 <ENTER> Amount Posted Asset Val. Date Amount Posted Amount of unplanned depreciation Amount of unplanned depreciation <posted amount> (Depreciation area 01) <Asset value date> <ENTER <posted amount> <repeat until Depreciation Area 80> 3. Choose Enter. 4. Post the document. Use Save on the top of the screen. for example, 200 for example, 200 for example, today Select one of the assets created in step 4.1 for example, today for example, today Comment

2. On the Unplanned Depreciation: Initial screen, make the following entries: Description

Result
The unplanned depreciation has been posted to all of the depreciation areas specified and is displayed separately. At this stage, the posting has only taken place in the Asset Management module. The unplanned depreciation is posted to Financial Accounting during the depreciation posting run.

4.4 Asset under Construction Settlement


SAP AG Page 31 of 53

SAP Best Practices

Asset Accounting (162): BPD

Use
In contrast to assessment, you cannot perform settlement across fiscal year boundaries. The system automatically determines the posting date from the posting period/fiscal year using the last day of the posting period. There are three processing types defined for settlement: Automatic: The system selects all the distribution rules for a sender. Periodic: All distribution rules with settlement types PER and AUC are selected. PER rules are applied first. In investment measures, this is followed by settlement to assets under construction. Partial capitalization: Use this processing type to partially capitalize an investment measure that is not yet complete (for example, to settle part of the overall cost to finished assets).

Preliminary settlement rule allocates revenues to alternate CO object with primary cost transfer. Settlement rule for costs is created automatically with assignment to AUC asset. The costs captured in the order are posted to the AUC asset and reflected on the balance sheet. Account Assignment Category Settlement Receiver Settlement % Settlement Type Source Assignment Distribution Rule Primary Cost Element Used for Settlement 530999 (AUC Settlement) account defaulted in configuration

FXA

AUC asset from class 4001. See step 4.2 (Scenario 381) for AUC created and assigned to order, Choose Extras Asset under Construction.

100

AUC

N/A

Prerequisites
Capital Order and preliminary settlement rule created in steps 4.2 & 4.3 and financial document postings in steps 4.6-8 (Scenario 381). Redo these steps to fulfill stand alone scenario 162.

Procedure
1. Access the transaction choosing one of the following navigation options: Option 1: SAP Graphical User Interface (SAP GUI) SAP system menu Transaction code Accounting Controlling Internal Orders Period-End Closing Single Functions Settlement Individual Processing KO88

Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role

SAP AG

Page 32 of 53

SAP Best Practices Business role (name) Business role menu Field name Selection

Asset Accounting (162): BPD SAP_BPR_ASSET_PS-S (Assets Accountant) Asset Accounting Internal Orders Actual Settlement: Order User action and values AUC, order type YK60, Company code #1000,Controlling area #1000 Comment Select capital order created in step 4.2 (Scenario 381). Redo step to fulfill stand alone scenario 162. (YK60 order type),

2. On the initial screen, enter the following data: Description

Settlement period Fiscal Year Posting Period Processing Type Test Run Check trans. Data 3. Choose

<Current period> <Current fiscal year> <Current period> 1 Automatic <Deselected> At first flag this field to check for possible errors

Execute. not recommended because of possible long runtime.

Recommendation: Run this process in the background: 1. Choose Background Processing in the Processing Options, and then choose Execute. 2. On the Background Processing Options dialog box, choose Start Immediately. Note the job number. 3. Choose Check. 4. Choose Confirm. 5. On the Background Print Parameters dialog box, choose the Output device, and then choose Continue. 6. Choose from the top of the screen the System, select it and then select the Own Jobs line. 7. On the Job Overview screen, choose Jobname. 8. Choose Joblog to see the results.

Result
Preliminary settlement rule settles all revenues to alternate cost object (order by funding source) assigned in rule. The monthly costs from the investment order are posted to the AUC asset, and included in the balances for AUC general ledger account.

SAP AG

Page 33 of 53

SAP Best Practices

Asset Accounting (162): BPD

The Actual Settlement: Orders Basic List report displays the results of the settlement, for example, the number of messages. It goes on to list the processing senders based on the categories. The system only outputs a detail list if you choose the corresponding option in the Settlement initial screen. Choose Detail list to see the list displayed. During background processing, the messages are output in the settlement log if required. AUC Asset not technically complete Debited Accounts Asset under Construction, with AUC Asset AUC asset is technically complete Debited Accounts Asset Balance Sheet G/L(based on asset class), with Capital Asset Credited Accounts Asset under Construction G/L, with AUC Asset Credited Accounts Expense, with AUC Internal Order

Option A: If the asset construction is complete, proceed to the next step. Option B: If the asset construction is not complete, repeat this step Error: Reference source not found.

4.5 Create Assets for Complete AUC Settlement


Use
In this activity, you create assets for complete AUC settlement.

Procedure

For this activity, run the Create Asset (155.02) scenario document, with master data provided. Select linear asset class 9100 for company code #1000.

Master Data
Final Asset is created in line with accounting policy.

Example
Asset Class 9100 Description Water Mains Cost Center 901032 Useful Life 90 years

SAP AG

Page 34 of 53

SAP Best Practices

Asset Accounting (162): BPD

4.6 Complete Order and Update Final Settlement Rule


Use
This step is only relevant for order type YK60

Prerequisites
Final asset created in previous step 4.5. All costs for asset build are confirmed (prerequisite for scenario 162 step 4.4, redo steps 4.6-8 - Scenario 381) in capital order. Choose same capital order settled to AUC in step 4.4.

Procedure
1. Access the transaction choosing one of the following navigation options: Option 1: SAP Graphical User Interface (SAP GUI) SAP system menu Transaction code Accounting Controlling Internal Orders Master Data Order Manager KO04

Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role Business role (name) Business role menu SAP_BPR_ASSET_PS-S (Assets Accountant) Asset Accounting Internal Orders Order Manager

2. If the Set Controlling area dialog box displays, enter Controlling Area 1000. 3. In the Order Manager, select order from Personal worklist, use shown in list, and choose (Change) then choose Enter. (Find by Order) if not

If the Option 2 steps 4.1.2 -4.1.3 are different (4.1.3 is covered via the POWL, then 4.1.2 must be done) Scenario 381 Select same capital order (YK60 order type) settled to AUC in step 4.4

4. Choose the Control Data tab; choose Field name Line 1: Cat Settlement Receiver % Account Assignment category FXA <No. of asset > Description

and then choose Settlement Rule. User action and values Comment Asset, created in step 4.5

5. On the Maintain Settlement Rule: Overview screen, enter the following values:

<Portion of AuC APC that can be capitalized>

for example, 100

SAP AG

Page 35 of 53

SAP Best Practices Settlement type No. 6. Choose Save 7. Final settlement rule is saved. Distribution rule number FUL 3

Asset Accounting (162): BPD

Result
Settlement rule is updated on capital order. Internal order for AUC asset is technically complete so the system is able to perform full settlement during next order settlement run. The full settlement transfers the costs from the AUC asset to the completed asset. Account Assignment Category FXA Settlement Receiver Final asset linear class created in step 4.5 Settlement % 100 Settlement Type Ful Source Assignment N/A Distribution Rule 3

4.7 Execute Final Settlement


Use
The full settlement transfers the costs from the AUC asset to the completed asset. Execute Final
settlement when asset is in service and legal title is confirmed.

Account Assignment Category FXA

Settlement Receiver Final asset

Settlement % 100

Settlement Type Ful

Source Assignment N/A

Distribution Rule 3

SAP AG

Page 36 of 53

SAP Best Practices linear class created in step 4.5

Asset Accounting (162): BPD

Prerequisites
Final asset is in service with legal title transfer. All costs for asset build are confirmed in capital order and available for capitalization. Execute final settlement with capital order updates from step 4.6.

Procedure
1. Access the transaction choosing one of the following navigation options: Option 1: SAP Graphical User Interface (SAP GUI) SAP system menu Transaction code Accounting Controlling Internal Orders Period-End Closing Single Functions Settlement Individual Processing KO88

Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role Business role (name) Business role menu Field name Selection SAP_BPR_ASSET_PS-S (Assets Accountant) Asset Accounting Internal Orders Actual Settlement: Order User action and values AUC, order type YK60, Company code #1000,Controlling area #1000 Settlement period Fiscal Year Posting Period Asset Value Date Processing Type Test Run Detail List 9. Choose <Current period> <Current fiscal year> <Current period> Select last day of month Full Settlement <Deselected> <Selected> Execute. Not recommended because of possible long runtime. At first flag this field to check for possible errors Dependent on settlement period Comment Select capital order with final settlement rule update from step 4.6 (YK60 order type)

8. On the initial screen, enter the following data: Description

SAP AG

Page 37 of 53

SAP Best Practices

Asset Accounting (162): BPD

Recommendation: Run this process in the background: 1. Choose Background Processing in the Processing Options, and then choose Execute. 2. On the Background Processing Options dialog box, choose Start Immediately. Note the job number. 3. Choose Check. 4. Choose Confirm. 5. On the Background Print Parameters dialog box, choose the Output device, and then choose Continue. 6. Choose from the top of the screen the System, select it and then select the Own Jobs line. 7. On the Job Overview screen, choose Jobname. 8. Choose Joblog to see the results.

Result
Full Settlement of costs results in capitalization of final asset, which is depreciated in sub-ledger. Settlement sets capitalization date in master record with impact to depreciation start date and planned depreciation postings in asset sub-ledger.

Debited Accounts Asset Balance Sheet G/L(based on asset class), with Capital Asset 160085 for linear assets

Credited Accounts Asset under Construction G/L, with AUC Asset - 160090

4.8 Asset Explorer Periodic Reporting


Use
The Asset Explorer allows you to analyze changes in the value of individual asset master records. It shows both the planned and posted balance sheet and depreciation values of a fixed asset in different forms and summarization levels. The Asset Explorer consists of: A header section where you enter the company code and required asset An overview tree for navigating between different depreciation areas An overview tree that shows the objects that are related to the asset A tab for analyzing planned values, posted values, different parameters, and for comparing fiscal years and depreciation areas.

For a detailed description of these functions and more information about using the Asset Explorer, refer to the SAP ERP documentation

SAP AG

Page 38 of 53

SAP Best Practices

Asset Accounting (162): BPD

Prerequisites
Asset master records have been created and posted to in the system.

Procedure
1. Access the transaction choosing one of the following navigation options: Option 1: SAP Graphical User Interface (SAP GUI) SAP system menu Transaction code Business role Business role menu Accounting Financial Accounting Fixed Assets Asset Asset Explorer AW01N SAP_BPR_ASSET_PS-S (Assets Accountant) Asset Accounting Assets Asset Explorer

Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role

2. On the Asset Explorer Screen, enter the required data: Field name Company Code Asset Fiscal Year Depreciation Areas Description User action and values #1000 <number of the asset> <fiscal year> <select one depreciation area> for example, 2000 for example, <current year> For example, 01 Book Depreciation Comment

Result
The Planned Values tab shows all the transactions that change the acquisition and production costs, all the depreciation values that have been calculated for the asset (including proportional value adjustments), the net book value, and any calculated interest. The Posted Values tab shows all the booked transactions. The Comparison tab shows the several years. The Parameters tab shows the depreciation key and further characteristics of the asset.

4.8.1 Use

Depreciation Posting Run

A posting to a fixed asset initially causes the planned depreciation to change in Asset Accounting. The accumulated depreciation accounts and depreciation accounts of the balance sheet and profit and loss statement are not updated immediately, however. The total planned depreciation is not posted to Financial Accounting (only collective documents are created) until the periodic depreciation posting run is executed. The depreciation posting should be run periodically (annually, semi-annually, quarterly, or monthly). When executed as an update run, the program must be started in the background. The system creates posting documents for each depreciation area and account group in accordance with the posting cycles specified in Customizing. As the posting date, the system uses The last day of the period for normal periods (no special periods)

SAP AG

Page 39 of 53

SAP Best Practices The last day of the fiscal year for special periods

Asset Accounting (162): BPD

Prerequisites
Document type AF has been defined in Customizing for posting depreciation. In the Customizing definition of the document type, number range 03 has been specified with internal number assignment. The Customizing settings also specify that depreciation in depreciation areas 01 (book depreciation) is posted in the general ledger. You can define the depreciation posting cycle by specifying the length of time in posting periods between two posting runs. The system is set in such a way that depreciation is posted monthly. You do not have to keep strictly to this posting cycle. You can also choose an unplanned depreciation posting run using an indicator on the initial screen of the depreciation posting run. When you set this indicator, you can skip over several periods and post the total depreciation for all of the skipped periods in one period. The system supports two different procedures for distributing the forecasted depreciation over the posting periods. The difference between the two procedures becomes evident when you process acquisitions within the fiscal year or handle post-capitalization. With the catch-up method, depreciation due on a transaction within the fiscal year (from the depreciation start date, according to period control, up to the current period) is posted in one total. The depreciation posting program posts this amount in the period in which the posting date of the acquisition lies. With the smoothing method, the annual depreciation amount determined is distributed equally over the periods from the current posting period to the year end. The catch-up procedure is configured in the system for all depreciation areas. For each depreciation area, you must specify whether depreciation is to be posted to the cost center and/or to the order. This information is taken from the asset master record and passed on to Financial Accounting as an additional account assignment.

Procedure
1. Access the transaction choosing one of the following navigation options: Option 1: SAP Graphical User Interface (SAP GUI) SAP system menu Transaction code Business role Business role menu Field name Company Code Fiscal Year Posting Period Accounting Financial Accounting Fixed Assets Periodic Processing Depreciation Run Execute AFAB

Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role SAP_BPR_ASSET-S (Assets Accountant) Asset Accounting Periodic and Closing Activities Depreciation Run Description User action and values #1000 <current fiscal year> <posting period> next period according to Comment

2. On the Depreciation posting run screen, make the following entries:

SAP AG

Page 40 of 53

SAP Best Practices Field name Description User action and values <activate>

Asset Accounting (162): BPD Comment posting cycle

Planned Posting Run Repeat Restart Unplanned Posting Run List Assets List of Manual Depreciation Test Run Explanations:

Activate Activate

Planned Posting Run You can post to the next period that is specified according to the posting cycle. During a regular posting run of this kind, the system does not allow you to limit the run to particular assets. Repeat Run You can request a repeat posting run for the last period posted. You might need to carry out a repeat run if the depreciation terms were changed for individual assets in connection with the year-end closing, for example. During a repeat posting run, the system only posts the differences that resulted between the first posting run and the repeat posting run. You can limit the run to particular assets. Restart If a posting run terminated for technical reasons and changes had already been made to the database, you must restart the program in restart mode. Using the restart mode ensures that all system activities that were interrupted by the termination are repeated. Unplanned Posting Run If, for whatever reason, you want to skip over one or more posting periods, you can do this by specifying an unplanned posting run. The system then creates postings for all the periods that were skipped, and for the period entered. The posting period that you specify, however, must fit into the posting cycle. If you specify period 7 for a quarterly posting cycle, for example, no posting occurs.

3. Once you have made all the necessary entries, execute the depreciation posting run in the background (Program Execute in Background) 4. For performance reasons, the depreciation program must be executed in the background. Start the program, therefore, in the background (on the selection screen for the program: Program Exec. In Background). Field name Output Device Start Time Save Description User action and values LOCL Choose Immediate Choose Save Comment

5. To start the depreciation posting run, save the start time values.

SAP AG

Page 41 of 53

SAP Best Practices

Asset Accounting (162): BPD

You can monitor the job scheduled in the background as follows: 6. Access the transaction choosing one of the following navigation options: SAP ERP Menu Transaction Code Business role Business role menu System Services Jobs Job Overview SM37 SAP_BPR_EMPLOYEE-S (Employee (Professional User)) Control Panel Background Processing Overview of job selection

Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role

You can accept the default values on the selection screen. Choose F8 to execute the program. The job always displays under the name RAPOST2000. The Status column shows the current status of the job. Choose Refresh or F8 to update the information. As soon as the status of the job is Finished, select your job and choose Spool. To go from the overview to your list, choose F6. When this list was generated, the fixed assets in question were also updated to include the posted depreciation. The planned depreciation for every complex fixed asset is not totaled for each posting level and posted directly to Financial Accounting until the periodic depreciation posting run has been executed.

If List of manual depreciation is activated two spool-lists are created. In the Step List Overview screen, to the RAPOST200 only the last spool-list number is shown. To list all spool-lists on the step list overview screen, choose RAPOST2000 and select All Spool Lists. Now you can select all the created lists. You can also monitor the periodic depreciation runs of Asset Accounting in the Schedule Manager Monitor. Choose application FI-AA Financial Accounting: Fixed Assets and Execute.

Result
The planned depreciation is posted to the accounts defined in Customizing. The system always creates collective documents (not individual documents for each asset) when posting depreciation.

4.8.2 Use

Recalculating Values

In certain circumstances, you might need to recalculate the planned annual depreciation for a variety of fixed assets. You can use the Recalculate Depreciation function to do so (program RAAFAR00). This program (which you can also start as a test run) enables you to recalculate the planned depreciation for a number of fixed assets. You can also execute the program in the background. For more information, refer to the section on the depreciation posting run.

You cannot use this function to recalculate depreciation in past fiscal years (such as in fiscal years that are already closed).

SAP AG

Page 42 of 53

SAP Best Practices

Asset Accounting (162): BPD

It is possible, that the program will be terminated with an ABAP short dump. This could be caused if the list contains no data. Start the program again.

Prerequisites
You might need to recalculate planned annual depreciation in certain company codes or for individual fixed assets. This might be necessary if: You have changed depreciation keys in Customizing. You have made mass changes that you programmed yourself and these changes affected data relevant to depreciation.

Procedure
1. Access the transaction choosing one of the following navigation options: Option 1: SAP Graphical User Interface (SAP GUI) SAP menu Transaction code Business role Business role menu Accounting Financial Accounting Fixed Assets Environment Recalculate Values AFAR

Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role SAP_BPR_ASSET-S (Assets Accountant) Asset Accounting Periodic and Closing Activities Recalculate Depreciation Description User action and values #1000 Comment

2. On the Recalculation Depreciation screen, make the following entries: Field name Company Code Main Asset Number/Asset SubNumber Account Group (w/Leading 0s) Depreciation Area FROM Fiscal Year List Assets Test Run Value Difference Over Limit 3. For performance reasons, the recalculation program must be executed in the background. Start the program, therefore, in the background (on the selection screen for the program: Program Exec. In Background). Field name Output Device Start Time Description User action and values LOCL Choose Immediate Comment <Select> <Deselect>

SAP AG

Page 43 of 53

SAP Best Practices Field name Save Description

Asset Accounting (162): BPD User action and values Choose Save Comment

4. The system tells you Background job was scheduled for program RAAFAR00. 5. Explanation: If you enter an amount in the value difference over limit field, the list is output at individual fixed asset level for all the fixed assets where the recalculated depreciation differs from the formerly planned depreciation by the amount specified or by a higher amount.

Result
If changes have occurred as a result of the recalculation process, the planned depreciation is adjusted for the fixed assets concerned. The new planned depreciation is used as the basis for subsequent depreciation posting runs. Check the log using transaction SP01.

4.8.3 Use

Depreciation Simulation/Primary Cost Planning

You can use standard reports to help you forecast the planned depreciation of complex fixed assets over several years. In addition to the simple list display option, you can also post the planned depreciation as planned costs to the cost centers or internal orders to which the individual fixed assets are assigned.

Procedure
1. Access the transaction choosing one of the following navigation options: Option 1: SAP Graphical User Interface (SAP GUI) SAP menu Accounting Financial Accounting Fixed Assets Information System Reports on Asset Accounting Depreciation Forecast Depreciation on Capitalized Assets (Depreciation Simulation) S_ALR_87012936

Transaction code Business role

Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role SAP_BPR_ASSET-S (Assets Accountant) Asset Accounting Reporting Depreciation Forecast User action and values #1000 <report date> For example, last day of actual year which is the end of the forecast. (Specify here the number of years for which the simulation is to run.) for example, 01 Comment Business role menu

2. On the Depreciation Simulation screen, make the following entries: Field name Company Code Report Date Description

Depreciation Area

<depreciation area>

SAP AG

Page 44 of 53

SAP Best Practices

Asset Accounting (162): BPD

3. You can use simulation versions to simulate changes with regard to the types of asset valuation (depreciation key, useful life, for example). You must define simulation versions in Customizing. 4. In addition to the selection fields above, there are various other fields that you can use to limit the report to particular complex fixed assets. 5. Execute the report and analyze the result. 6. The following section describes how to post the forecast depreciation as planned costs to the Controlling objects that are assigned to the assets. 7. Access the transaction choosing one of the following navigation options: SAP ERP Menu Transaction Code Business role Business role menu 8. Enter the required data. Field Name Company Code Depreciation Area Planning Periods Fiscal Year Planning Periods From Period To Plan Version Test Run Summary Report 0 Deactivate Deactivate Description User Action and Values #1000 01 Current fiscal year No restriction means from 1 to 12 Comment Accounting Financial Accounting Fixed Assets Periodic Processing Primary Cost Planning: Depreciation/Interest S_ALR_87099918

Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role SAP_BPR_ASSET-S (Assets Accountant) Asset Accounting Reporting Primary Cost Planning Dep./Interest

9. In addition to the selection fields above, there are various other fields that you can use to limit the report to particular complex fixed assets. 10. Execute the report. You can execute the report in the background. The section on depreciation posting runs contains information on monitoring the job and spool.

You can execute the report more than once. The value that already exists in a Controlling object for the cost element and period is overwritten during this process.

Result
The system does not create a batch input session. The planned costs are posted directly to the assigned Controlling objects and can be evaluated via cost center reporting or internal order reporting.

SAP AG

Page 45 of 53

SAP Best Practices

Asset Accounting (162): BPD

The cost element that is specified in Customizing for Asset Accounting as the expense account for the respective depreciation type is used.

4.8.4 Use

Open and Close FI Period Asset

In this activity, you close the posting periods for FI-AA and open the new periods for FI-AA. Select posting period variant 0010 assigned to company code 1000.

Procedure
1. Access the transaction choosing one of the following navigation options: Option 1: SAP Graphical User Interface (SAP GUI) SAP menu Transaction code Business role Business role menu Accounting Financial Accounting General Ledger Environment Current Settings Open and Close Posting Periods S_ALR_87003642 (OB52)

Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role SAP_BPR_FINACC-K (Finance Manager) General Ledger Closing Preparation Open / Close Posting Periods

2. On the Posting Periods: Specify Time Intervals screen, make the following entries for posting period variant 0010: Field name From per 1 Year To period Year 3. Choose Save. Description User action and values <new period> <actual year> or at the year-end <new year> <the highest permitted posting period> <the highest permitted posting year> Comment New period for Account Type A year for Account Type A For Example, Current Period For Example, Current Year

Result
No more FI-AA postings can be made to the previous period. Postings for the future periods are allowed.

4.8.5 Use

Account Reconciliation

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. Then this table is read, and the values are reconciled with the G/L accounts.

SAP AG

Page 46 of 53

SAP Best Practices The following accounts are reconciled: 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 deprec.

Asset Accounting (162): BPD

You should start the report before year-end closing.

Prerequisites
Before you can start the transaction, the asset balance sheet account values (historical load values for conversion assets) must be completely posted in the general ledger (with transfer posting transaction code OASV)

Procedure
1. Access the transaction choosing one of the following navigation options: Option 1: SAP Graphical User Interface (SAP GUI) SAP menu Transaction code Business role Business role menu Accounting Financial Accounting Fixed Assets Periodic Processing Year-End Closing Account Reconciliation ABST2

Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role SAP_BPR_ASSET-S (Assets Accountant) Asset Accounting Reporting Reconciliation FI-AA (Accts w/ differences)

2. On the Reconcile Program FI-AA <> G/L: List of accounts showing differences screen, make the following entries: Field name Company Code 3. Choose Execute. Description User action and values #1000 Comment

Result
The report generates a list of accounts showing differences. When there are differences, the differences must be analyzed, before the next step (Year-End Closing) is started. Differences should be reduced to zero by making postings if necessary using transfer posting transaction OASV.

SAP AG

Page 47 of 53

SAP Best Practices

Asset Accounting (162): BPD

4.8.6 Use

Fiscal Year Change

From a system perspective, a fiscal year change represents the creation of a new fiscal year for a company code. At the fiscal year change, the asset values from the previous fiscal year are carried forward cumulatively into the new fiscal year. Once the fiscal year change takes place, you can post to assets using value dates in the new fiscal year. At the same time, you can, however, continue to post in the previous fiscal year, provided this has not been closed as a result of the year-end closing.

Prerequisites
The fiscal year change can only be carried out (even in test mode) for the new fiscal year. The earliest that you can carry out a fiscal year change is in the last month of the old fiscal year. Before you can change to fiscal year YYYY, you must have already closed fiscal year YYYY-2. You can have a maximum of two fiscal years open for posting at one time. No business transactions can be posted in a new fiscal year before the fiscal year change. You can continue to post in the old fiscal year, even after the fiscal year change. The system automatically corrects any values that have already been carried forward and that are affected by postings in the past. The fiscal year change must be carried out as background processing for performance reasons. You can carry out test runs with fewer than 1,000 assets in the foreground.

Procedure
1. Access the transaction choosing one of the following navigation options: Option 1: SAP Graphical User Interface (SAP GUI) SAP menu Transaction code Business role Business role menu Accounting Financial Accounting Fixed Assets Periodic Processing Fiscal Year Change AJRW

Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role SAP_BPR_ASSET-S (Assets Accountant) Asset Accounting Periodic and Closing Activities Fiscal Year Change Description User action and values #1000 <current fiscal year +1> <deactivate> To test the change, activate this step Comment

2. On the Asset Fiscal Year Change Screen, make the following entries: Field name Company Code New Fiscal Year Test Run

SAP AG

Page 48 of 53

SAP Best Practices

Asset Accounting (162): BPD

If the company code has been set to production (company code status = blank), you cannot carry out the fiscal year change until the last month of the current fiscal year (in update mode). If the company code is a test company code (company code status = 2), you can change the fiscal year as and when required. You set the company code status in Customizing for Asset Accounting. No more than two fiscal years, however, can be open at the same time. Carry out the fiscal year change as a test run. If more than 1,000 assets exist in the system, you must start the program by choosing Program Execute in Background. The section on depreciation posting runs contains information on monitoring the job and spool. If fewer than 1,000 assets exist in the system, you can also start the report online.

Result
If you started the report in update mode, the asset values from the previous fiscal year are carried forward cumulatively into the new fiscal year. Postings can now be made to the new fiscal year. You can also monitor the fiscal year change of Asset Accounting in the Schedule Manager Monitor. Choose application FI-AA Financial Accounting: Fixed Assets and Execute.

4.8.7 Use

Year-End Closing

You can use the year-end closing program to close the fiscal year for one or more company codes from an accounting perspective. Once the fiscal year is closed, you can no longer post or change values within Asset Accounting (for example, by recalculating depreciation). The fiscal year that is closed is always the year following the last closed fiscal year. You cannot close the current fiscal year.

The year-end closing in Asset Accounting must be performed before the year-end closing in General Ledger Accounting. The fiscal year change must be carried out in Asset Accounting before the year-end closing (SAP FI-AA).

Prerequisites
You must carry out the year-end closing as background processing for performance reasons. Start the program, therefore, as a background job (on the selection screen for the program: Program Exec. in Background). You can carry out test runs with fewer than 1,000 assets in the foreground.

The system only closes a fiscal year in a company code if the system found no errors during the calculation of depreciation (such as incorrectly defined depreciation keys). Planned depreciation from the depreciation areas to be posted has been completely posted to the general ledger. Balances from depreciation areas that are posted periodically have been completely posted to the general ledger. All assets acquired in the fiscal year have already been capitalized. As this check does not make sense for assets under construction, you can prevent it from being performed for these assets via the asset class.

SAP AG

Page 49 of 53

SAP Best Practices

Asset Accounting (162): BPD

All incomplete assets (master records) have been completed.

The system lists any assets that do not meet the above requirements in the year-end closing log. The log also shows the reason for the errors.

Procedure
1. Access the transaction choosing one of the following navigation options: Option 1: SAP Graphical User Interface (SAP GUI) SAP menu Transaction code Business role Business role menu Field name Company Code Asset Classes Asset u. Const. Fiscal Year to Be Closed Test Run <current fiscal Year> To perform a test, activate this flag Accounting Financial Accounting Fixed Assets Periodic Processing Year-End Closing Execute AJAB

Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role SAP_BPR_ASSET-S (Assets Accountant) Asset Accounting Periodic and Closing Activities Year-End Closing Description User action and values #1000 Comment

2. On the Year-End closing Asset Accounting Screen, make the following entries:

3. Execute the year-end closing and analyze the log. You can execute the report in the background. The section on depreciation posting runs contains information on monitoring the job and spool.

You can undo a year-end closing that has already been performed. You might need to do this if you establish that fixed assets do have to be corrected after all. You can undo the year-end closing for the entire company code or for each depreciation area. Undoing the year-end closing for entire company codes: SAP ERP Menu Transaction Code Business role Business role menu Accounting Financial Accounting Fixed Assets Periodic Processing Year-End Closing Undo Entire Company Code OAAQ

Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role SAP_BPR_ASSET-S (Assets Accountant) Asset Accounting Periodic and Closing Activities Cancel year-end closing for company code

SAP AG

Page 50 of 53

SAP Best Practices Undoing the year-end closing by depreciation area: SAP ERP Menu Transaction Code Business role Business role menu

Asset Accounting (162): BPD

Accounting Financial Accounting Fixed Assets Periodic Processing Year-End Closing Undo By Area OAAR

Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role SAP_BPR_ASSET-S (Assets Accountant) Asset Accounting Periodic and Closing Activities Cancel yearend closing by area

Result
If you have performed the year-end closing in update mode, you can no longer post to the closed fiscal year. You can also monitor the year end closing of Asset Accounting in the Schedule Manager Monitor. Choose application FI-AA Financial Accounting: Fixed Assets and Execute.

4.9 Information System


Use
The Information System in Asset Accounting features a series of reports arranged in a tree structure. As they are launched with predefined variants, all of the reports in the standard selection tree have an initial screen that is clearly structured and easy to use. These input screens allow you to define various primary selections (for example, by asset number, asset class, cost center, location, and so on). By choosing the All Selections button, you can display the entire input screen. All of the reports are started as standard with the display group totals only option. To display the individual assets, however, you can change this option by choosing All Selections. By choosing the Dynamic Selections button in the report selection screen, you can use all the fields in the general master record section as selection parameters, in addition to the standard selections. Of all the selection criteria, the report date is important. It specifies which fiscal year will be analyzed. The report date is in the past or in the current fiscal year In this case, the report date can be the end of the year or a period-end date during the fiscal year. With fiscal years that are already closed, the report date must be the end of the year. The report date is in a future fiscal year In this case, the system changes the report date to the last day in the relevant fiscal year.

Procedure
1. You can find all the standard reports under the following menu path: SAP ERP Menu Accounting Financial Accounting Fixed Assets Information System Reports on Asset Accounting

2. It is possible to assign customer specific the following reports to the business role SAP_BPR_ASSET-S (Assets Accountant) in the business role menu Asset Accounting Reporting. 3. An overview of the most important reports and their position in the menu tree:

SAP AG

Page 51 of 53

SAP Best Practices SAP ERP Menu Asset Balances Balance Lists Asset Balances Report Balance List by

Asset Accounting (162): BPD

Asset Balances Inventory List by Inventory Lists Physical Inventory List Notes to Financial Statements International Explanations for P&L International Depreciation Explanations for P&L International Cost Accounting Depreciation Forecast Preparations for Closing International Day-to-Day Activities International History Asset History Sheet

Total Depreciation, Ordinary Depreciation, Special Depreciation, Unplanned Depreciation, Transfer of Reserves Write-Ups, Depreciation Comparison, Manual Depreciation Depreciation and Interest Depreciation on Capitalized Assets (Depreciation Simulation) Gain for Transfer of Reserves, Changes to Asset Master Records Asset Transactions, Asset Acquisitions, Asset Retirements, Intracompany Asset Transfers, Directory of Unposted Assets, List of Origins of Asset Debits, List of Origins by Cost Elements Asset History (asset chart)

4.10
Use

Check Consistency

After you have made all the required system settings, you can now check their consistency. You should carry out this test for the following reasons: Along with the dialog checks, you should also check the consistency of your system settings at the end as a whole (in overview). You should print out the settings. In this step, you can check the plausibility of your system settings and print them out.

Prerequisites
You must have worked through all of the necessary settings (Customizing).

Procedure
Check the system settings for charts of accounts, company codes, and depreciation areas in the corresponding overview lists. 1. You can find all the overview lists under the following menu path:

SAP AG

Page 52 of 53

SAP Best Practices SAP ERP Menu Transaction Code SAP ERP Menu

Asset Accounting (162): BPD Tools Customizing IMG Execute Project SPRO

2. Choose SAP Reference IMG. Financial Accounting (New) Asset Accounting Preparing for Production Startup Check consistency Overview Report: Asset Classes Overview Report: Charts of Depreciation Overview Report: Company Codes Overview Report: Depreciation Areas Tr. code ANKA Tr. code OAK1 Tr. code OAK2 Tr. code OAK3

3. Choose one of the following: o o o o o o

Consistency Report: Asset G/L Accounts Tr. code OAK4 Consistency Report: FI-AA Customizing Tr. code OAK6.

If necessary, the following SAP Notes give support to the error analysis, for example: 617311, 788380, 74668, 327088, and 25255.

SAP AG

Page 53 of 53