Asset Accounting. SAP Best Practices

Transcription

1 Asset Accounting SAP Best Practices

2 Purpose, Benefits, and Key Steps Purpose The Asset Accounting (FI-AA) component is used for managing and supervising fixed assets with the SAP system. In Financial Accounting, it serves as a subsidiary ledger to the General Ledger, providing detailed information on transactions involving fixed assets. Benefits Entire lifetime of the asset from purchase order or the initial acquisition (possibly managed as an asset under construction) through its retirement. Calculate values for depreciation and interest Depreciation forecast Key Steps Acquisition from purchase with vendor Acquisition with automatic offsetting entry Retirement with revenue Asset Sale without customer Post-Capitalization Write-Ups Assets Under Construction Depreciation Posting Run Posting Acquisition and Production Costs Values Depreciation Simulation/Primary Cost Planning 2014 SAP SE or an SAP affiliate company. All rights reserved. 2

3 Required SAP Applications and Company Roles Required Enhancement package 7 for SAP ERP 6.0 Company Roles Asset Accountant Accounts Payable Accountant General Ledger Accountant 2014 SAP SE or an SAP affiliate company. All rights reserved. 3

4 Detailed Description Acquisition from Purchase with Vendor An external asset acquisition is a business transaction resulting from the acquisition of an asset from a business partner. The acquisition can be posted integrated with Accounts payable or without Accounts payable. Acquisition with Automatic Offsetting Entry The asset can be posted automatically against the clearing account fixed asset acquisition. Retirement with Revenue 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. Asset Sale without Customer Asset Sale with partial retirement without customer 2014 SAP SE or an SAP affiliate company. All rights reserved. 4

5 Detailed Description Post-Capitalization Post-capitalization represents subsequent corrections to the acquisition and production costs (APC) of a fixed asset. Write-Ups A write-up is generally understood to be a subsequent change to the valuation of an asset. Assets Under Construction Assets under construction (AuC) are a special form of tangible asset. The AuC process includes a down payment, final invoice and the final settlement SAP SE or an SAP affiliate company. All rights reserved. 5

6 Detailed Description Depreciation Posting Run The depreciation posting should be run periodically because the depreciation accounts are not updated immediately. The system creates posting documents for each depreciation area and account group in accordance with the posting cycles specified in Customizing. Posting Acquisition and Production Costs Values In addition to the posting of depreciation (using the depreciation posting run), the most important periodic processing you perform is the posting of changes to asset balance sheet values. These changes consist of all postings that affect the APC of the asset, including acquisitions, retirements, and so on. Depreciation Simulation / Primary Cost Planning 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 SAP SE or an SAP affiliate company. All rights reserved. 6

7 Asset Accountant Event Flow Diagram Asset Accounting - Overview Periodic ing Asset Acquired Asset to be retired Intracompany Transfers Post-Capitalization Asset Explorer Write-Ups Decision Decision Transfer of Reserves Unplanned Deprecation Acquisition with Automatic Offsetting Entry Acquisition from purchase with vendor Retirement Due to Scrapping Decision Asset Sale without Customer Retirement with Revenue 2014 SAP SE or an SAP affiliate company. All rights reserved. 7

8 Accounts Payable Accountant Asset Accountant Event Flow Diagram Asset Accounting Asset under Construction Asset needs to be Constructed without Investment Order Create Asset under Construction and Asset for Final Settlement (155.02) Post Closing Invoice Maintain Settlement Rules for Assets under Construction Down Payment Request for Assets under Construction Post Down Payment Clear Down Payment 2014 SAP SE or an SAP affiliate company. All rights reserved. 8

9 Flow Diagram General Ledger Accountant Asset Accounting Periodic ing Asset Accountant Event Asset Period End Closing Settlement of Assets under Construction Recalculate Values Depreciation Posting Run Year-End Closing Account Reconciliation Fiscal Year Change Primary Cost Planning Periodic Postings (APC Values Posting) Depreciation Simulation Open and Close FI Period Asset 2014 SAP SE or an SAP affiliate company. All rights reserved. 9

10 External to SAP <Function> Legend Symbol Description Usage Comments Symbol Description Usage Comments Band: Identifies a user role, such as Accounts Payable Clerk or Sales Representative. This band can also identify an organization unit or group, rather than a specific role. The other process flow symbols in this table go into these rows. You have as many rows as required to cover all of the roles in the scenario. External Events: Contains events that start or end the scenario, or influence the course of events in the scenario. Role band contains tasks common to that role. Diagram Connection Hardcopy / Document To next / From last Diagram: Leads to the next / previous page of the Diagram Hardcopy / Document: Identifies a printed document, report, or form Flow chart continues on the next / previous page Does not correspond to a task step in a document; instead, it is used to reflect a document generated by a task step; this shape does not have any outgoing flow lines Flow line (solid): Line indicates the normal sequence of steps and direction of flow in the scenario. Flow line (dashed): Line indicates flow to infrequently-used or conditional tasks in a scenario. Line can also lead to documents involved in the process flow. Connects two tasks in a scenario process or a non-step event Financial Actuals Financial Actuals: Indicates a financial posting document Does not correspond to a task step in a document; instead, it is used to reflect a document generated by a task step; this shape does not have any outgoing flow lines Business Activity / Event Business Activity / Event: Identifies an action that either leads into or out of the scenario, or an outside that happens during the scenario Does not correspond to a task step in the document Budget Planning Budget Planning: Indicates a budget planning document Does not correspond to a task step in a document; instead, it is used to reflect a document generated by a task step; this shape does not have any outgoing flow lines Unit Reference Unit : Identifies a task that is covered in a step-by-step manner in the scenario Reference: If the scenario references another scenario in total, put the scenario number and name here. Corresponds to a task step in the document Corresponds to a task step in the document Manual Manual : Covers a task that is manually done Does not generally correspond to a task step in a document; instead, it is used to reflect a task that is manually performed, such as unloading a truck in the warehouse, which affects the process flow. Sub- Reference Sub- Reference: If the scenario references another scenario in part, put the scenario number, name, and the step numbers from that scenario here Corresponds to a task step in the document Existing Version / Data Existing Version / Data: This block covers data that feeds in from an external process Does not generally correspond to a task step in a document; instead, this shape reflects data coming from an external source; this step does not have any incoming flow lines Decision Decision: Identifies a decision / branching point, signifying a choice to be made by the end user. Lines represent different choices emerging from different parts of the diamond. Does not usually correspond to a task step in the document; Reflects a choice to be made after step execution System Pass/Fail Decision System Pass / Fail Decision: This block covers an automatic decision made by the software Does not generally correspond to a task step in the document; instead it is used to reflect an automatic decision by the system that is made after a step has been executed SAP SE or an SAP affiliate company. All rights reserved. 10

11 2014 SAP SE or an SAP affiliate company. 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 SE or an SAP affiliate company. SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. Please see for additional trademark information and notices. Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors. National product specifications may vary. These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP SE or its affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP SE or SAP affiliate company 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. In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or any related presentation, or to develop or release any functionality mentioned therein. This document, or any related presentation, and SAP SE s or its affiliated companies strategy and possible future developments, products, and/or platform directions and functionality are all subject to change and may be changed by SAP SE or its affiliated companies at any time for any reason without notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking statements, which speak only as of their dates, and they should not be relied upon in making purchasing decisions SAP SE or an SAP affiliate company. All rights reserved. 11