129 scen overview en uk

8/12/2019 129 Scen Overview en UK

http://slidepdf.com/reader/full/129-scen-overview-en-uk 1/6

Consumable PurchasingSAP Best Practices Baseline Package

SAP Best Practices



Scenario Overview – 1

Purpose

Purchasing of consumable goods or services

Benefits

Possibility of quick one-time-purchases: Material consumption is directly posted,no posting into storage

Use of service entry sheets as inspection report of performed services

Key process flows covered Purchase order creation for consumable goods

Approval of purchase orders for consumables

Goods receipt of consumables

Purchase order creation for services

Service entry sheet creation

Service entry sheet approval Invoice receipt by line item

Period-end plant

Purpose and Benefits:




Required SAP EHP3 for SAP ERP 6.0 EhP3

Company roles involved in process flows Buyer

Purchasing Manager

Warehouse Clerk

Service Employee Accounts Payable Accountant

SAP Applications Required:




Consumable Purchasing

This scenario deals with purchase order creation activities during the procurementprocess. Furthermore, it describes the additional process steps of a purchase orderapproval, goods receipt of consumables, approval of service entry sheets and invoicereceipts by line item. The process also covers the related processing of outgoingpayments and period-end plant and period-end closing.

Consumable items (goods or services) are entered without material number but rathera short text description as the main identifiable characteristic. The purchase order issubject to approval based on predefined parameters prior to being issued to a vendor.

For consumable goods, there is no inventory in the system. By posting a goods receiptthe value of the goods is expensed to a cost center or another cost element.

Procurement of a consumable service follows the same general process. Thedifference is that the consumable service is not posted by means of a goods receipt,

but with a service entry sheet. The invoice follows the same rules in both cases.

Detailed Process Description:



Legend

Symbol Description Usage Comments

To next / From last Diagram: Leadsto 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

Does not correspond to a taskstep in a document; instead, it isused to reflect a documentgenerated by a task step; this

shape does not have any outgoingflow lines

Budget Planning: Indicates abudget planning document

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

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.

DiagramConnection

Hardcopy /Document

FinancialActuals

BudgetPlanning

ManualProces

s

ExistingVersion /

Data

SystemPass/F

ailDecisio

n

Symbol Description Usage

Comments

Band: Identifies a user role, such as AccountsPayable 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 bandcontains 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 anotherscenario in total, put the scenario number and namehere.


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


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 be

made after stepexecution

< F u n c t i o n >

E x t e r n a l

t o

S A P

BusinessActivity /

Event

Unit Process

ProcessReference

Sub-Process

Reference

Process

Decision

129 scen overview en uk

Documents