163 asset aquisition with direct capitalization scenario

5/25/2018 163 Asset Aquisition With Direct Capitalization Scenario

1/6

Asset Acquisition through

Direct CapitalizationSAP Best Practices Baseline Package(France)

SAP Best Practices


2/6

Scenario Overview 1

Purpose

Purchasing asset investments that do not have an asset under constructionphase (AuC).

Benefits

Transparent view of outstanding orders, shipments and inventory

Automated efficient processing.

Key process flows covered

Capitalize the asset directly in Asset Accounting.

Purpose and Benefits:


3/6

Scenario Overview 2

Required

EHP3 for SAP ERP 6.0

Company roles involved in process flow

Requestor Approver

Asset Accountant

Purchasing Manager

Purchaser

Warehouse Clerk

Accounts Payable

AP Supervisor

SAP Applications Required:


4/6

Scenario Overview 3

Asset Acquisition through Direct Capitalization

To purchase an asset investment(s) that does not have an asset under construction

(AuC) phase, you capitalize the asset directly in Asset Accounting. The need for a

new asset is requested and approved by the cost center manager, purchased through

the purchasing department, and the costs associated with the purchase order are

capitalized when the vendor invoice is processed.

Detailed Process Description:


5/6

Process Flow DiagramAsset Acquisition through Direct Capitalization

A

sse

t

Accoun

t

-an

t

Buyer

Even

t

Accoun

ts

Paya

ble

Requisition

approved?

AccountsPayables

(158)

Capital AssetNeeds to BePurchased

ReviewPurchaseRequisitio

n

PurchaseRequisition

Debit AssetCredit Vendor

AP = Accounts Payable

Ware-

house

Clerk

Purch.

Mgr.

IncomingVendorInvoice

End Process

Convert Requisition toPurchase Order with

Account Assignment A

ApprovePurchase Order

Purchase OrderAccurat

e?

Create Asset

(155.02)

AP

Super-

visor

Create Purchase Requisition withAccount Assignment as U Unknown

Yes

Yes

No

UnloadMaterials

fromTruck

ChangePurchase Order

Receive Goodsfrom Vendor toPurchase Order

Invoice Receiptby Line Item

No

Approver

Reques

-tor


6/6

Legend

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.

Role band

contains tasks

common to that

role.

External Events: Contains events that start or end the

scenario, or influence the course of events in the

scenario.

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 twotasks in ascenario

process or anon-step event

Business Activity / Event:Identifies an action thateither leads into or out of the scenario, or an outsideProcess that happens during the scenario

Does notcorrespond to atask step in thedocument

Unit Process: Identifies a task that is covered in astep-by-step manner in the scenario

Corresponds toa task step inthe document

Process Reference: If the scenario references another

scenario in total, put the scenario number and namehere.

Corresponds to

a task step inthe document

Sub-Process Reference: If the scenario referencesanother scenario in part, put the scenario number,name, and the step numbers from that scenario here

Corresponds toa task step inthe document

Process Decision: Identifies a decision / branchingpoint, signifying a choice to be made by the enduser. Lines represent different choices emergingfrom different parts of the diamond.

Does notusuallycorrespond to atask step in thedocument;Reflects achoice to bemade after stepexecution

Symbol Description Usage Comments

To next / From last Diagram:Leads

to the next / previous page of theDiagram

Flow chart continues on the next /

previous page

Hardcopy / Document: Identifies aprinted document, report, or form

Does not correspond to a taskstep in a document; instead, it isused to reflect a documentgenerated by a task step; thisshape does not have any outgoingflow lines

Financial Actuals: Indicates afinancial posting document


Budget Planning: Indicates abudget planning document


Manual Process: Covers a taskthat is manually done

Does not generally correspond toa task step in a document;instead, it is used to reflect a taskthat is manually performed, suchas unloading a truck in thewarehouse, which affects theprocess flow.

Existing Version / Data: This blockcovers data that feeds in from anexternal process

Does not generally correspond toa task step in a document;instead, this shape reflects datacoming from an external source;this step does not have anyincoming flow lines

System Pass / Fail Decision: Thisblock covers an automaticdecision made by the software

Does not generally correspond toa task step in the document;instead it is used to reflect anautomatic decision by the systemthat is made after a step has beenexecuted.

External

to

SAP

BusinessActivity /

Event

Unit Process

ProcessReference

Sub-Process

Reference

Process

Decision

DiagramConnection

Hardcopy /Document

FinancialActuals

BudgetPlanning

ManualProces

s

ExistingVersion /

Data

SystemPass/F

ailDecisio

n

163 asset aquisition with direct capitalization scenario

Documents