Upload
don555232
View
220
Download
0
Embed Size (px)
Citation preview
8/11/2019 109 Scen Overview en De
1/6
Sales Order Processing:
Sale from StockSAP Best Practices Baseline Package
SAP Best Practices
8/11/2019 109 Scen Overview en De
2/6
Scenario Overview 1
Purpose
This scenario describes the entire process sequence for a standard sales
process (Sale from Stock) with a customer. The business process encompasses
all steps from creating an order to the clearing of a customer account after
payment is received.
Benefits When an order is entered, an availability check is performed and a shipping
point is determined automatically
A billing document is created and postings to FI and CO are made
Key process flows covered
Create sales order
Order confirmation
Delivery
Picking
Goods issue
Billing
Purpose and Benefits:
8/11/2019 109 Scen Overview en De
3/6
Scenario Overview 2
Required
SAP enhancement package 4 for SAP ERP 6.0
Company roles involved in process flows Sales Administrator
Warehouse Clerk
Billing Administrator
SAP Applications Required:
8/11/2019 109 Scen Overview en De
4/6
Scenario Overview 3
Sales Order Processing: Sale from Stock
The process starts with the creation of a customer's standard sales order.Depending on the customer and the material, various special events takeplace during order entry, such as customer/material pricing, insertion ofapplicable discounts, checking the availability of the materials, and checkingthe customers credit history.
It is checked if enough material exists in the required storage location. If not,a stock movement takes place. Then, the picking slips are generated to thewarehouse clerks to stage the product for shipment to the customer.
Once picked, the physically shipped quantity has to be registered in thesystem to ensure that there are no differences between the sales order andthe delivery document. In case of actual differences, this can also bedocumented and it ensures correct postings.
After the completion of picking, the warehouse clerk will have tosystematically relieve the inventory. This relief of inventory is the actual
recording of the physical quantity that is being shipped to the customer. Thisresults in the recording of the cost of goods sold in financial accounting.
Once the inventory has been relieved, the delivery can be invoiced and therevenue, together with the cost of goods sold, is recorded in managementaccounting. This step signifies the end of the business transaction in Salesand Distribution.
The final step of this document describes how invoices are posted, customerstatements are prepared and printed, and the incoming payments arerecorded, and then cleared to make sure that the open customer account
balance is reconciled.
Detailed Process Description:
8/11/2019 109 Scen Overview en De
5/6
Customer
Process Flow Diagram
Sales Order Processing: Sale from Stock
Sa
les
Adm
inistr
ator
WarehouseClerk
Accounts
Receivable
Accountant
Event
Sales Order
Entry
CustomerNeeds to Buy
Product
InventoryCOGS
AR= Accounts Receivable, COGS = Cost of Goods Sold
Delivery NoteOrderConfirmation
Pick List
Delivery DueList
Post GoodsIssue
ARIncomingPayment
(157)
(Optional)Sales
Quotation(112)
BillingDocument
CreditManagement
(108)
CreditManagement
(108)
Check Batches/ Assign Serial
Number(optional)
Sales: PeriodEnd ClosingOperations
(203)
Billing
Adminis
trator
Billing
8/11/2019 109 Scen Overview en De
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
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
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.
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