Sales Order Processing:

Sale from Stock

SAP Best Practices Baseline Package

SAP Best Practices

Scenario Overview – 1

Purpose and Benefits:

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
Scenario Overview – 2

SAP Applications Required:

Required
 SAP enhancement package 4 for SAP ERP 6.0

Company roles involved in process flows

 Sales Administrator
 Warehouse Clerk
 Billing Administrator
Scenario Overview – 3

Detailed Process Description:

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 take
place during order entry, such as customer/material pricing, insertion of
applicable discounts, checking the availability of the materials, and checking
the customer‘s 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 the
warehouse clerks to stage the product for shipment to the customer.
 Once picked, the physically shipped quantity has to be registered in the
system to ensure that there are no differences between the sales order and
the delivery document. In case of actual differences, this can also be
documented and it ensures correct postings.
 After the completion of picking, the warehouse clerk will have to
systematically relieve the inventory. This relief of inventory is the actual
recording of the physical quantity that is being shipped to the customer. This
results in the recording of the cost of goods sold in financial accounting.
 Once the inventory has been relieved, the delivery can be invoiced and the
revenue, together with the cost of goods sold, is recorded in management
accounting. This step signifies the end of the business transaction in Sales
and Distribution.
 The final step of this document describes how invoices are posted, customer
statements are prepared and printed, and the incoming payments are
recorded, and then cleared to make sure that the open customer account
balance is reconciled.
Process Flow Diagram
Sales Order Processing: Sale from Stock

Customer Credit Credit

Needs to Buy Management Management
Event

Product (108) (108)

(Optional)
Sales
Quotation
(112)
Customer

Order Delivery Note Billing

Confirmation Document
Administr
Sales
ator

Sales Order
Entry

Check Batches
Warehouse Clerk

Delivery Due / Assign Serial Post Goods

List Number Issue
(optional)

Inventory
Pick List COGS
Adminis
Billing
trator

Billing
Accountant
Receivable
Accounts

Sales: Period
AR–Incoming End Closing
Payment Operations
(157) (203)

AR= Accounts Receivable, COGS = Cost of Goods Sold

 Legend

Symbol Description Usage Symbol Description Usage Comments

Comments

Band: Identifies a user role, such as Accounts Role band To next / From last Diagram: Leads Flow chart continues on the next /
to the next / previous page of the previous page
Payable Clerk or Sales Representative. This band contains tasks Diagram
<Function>

can also identify an organization unit or group, common to that Diagram

rather than a specific role. role. Connection
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. Hardcopy / Document: Identifies a Does not correspond to a task
printed document, report, or form step in a document; instead, it is
Hardcopy / used to reflect a document
External Events: Contains events that start or end the Document generated by a task step; this
External

scenario, or influence the course of events in the shape does not have any outgoing
to SAP

scenario. flow lines

Financial Actuals: Indicates a Does not correspond to a task

Flow line (solid): Line indicates the normal sequence Connects two financial posting document step in a document; instead, it is
tasks in a Financial used to reflect a document
of steps and direction of flow in the scenario. scenario generated by a task step; this
Flow line (dashed): Line indicates flow to infrequently-
Actuals
process or a shape does not have any outgoing
used or conditional tasks in a scenario. Line can non-step event flow lines
also lead to documents involved in the process flow.

Business Activity / Event: Identifies an action that Does not Budget Planning: Indicates a Does not correspond to a task
either leads into or out of the scenario, or an outside correspond to a budget planning document step in a document; instead, it is
Business Process that happens during the scenario task step in the used to reflect a document
Budget generated by a task step; this
Activity / document
Planning shape does not have any outgoing
Event flow lines

Unit Process: Identifies a task that is covered in a Corresponds to

step-by-step manner in the scenario a task step in Manual Process: Covers a task Does not generally correspond to
the document that is manually done a task step in a document;
Unit Process Manual instead, it is used to reflect a task
Proces that is manually performed, such
s as unloading a truck in the
warehouse, which affects the
process flow.
Process Reference: If the scenario references another Corresponds to
scenario in total, put the scenario number and name a task step in
Process here. the document
Existing Version / Data: This block Does not generally correspond to
Reference covers data that feeds in from an a task step in a document;
Existing external process instead, this shape reflects data
Version / coming from an external source;
Data this step does not have any
Sub-Process Reference: If the scenario references Corresponds to incoming flow lines
another scenario in part, put the scenario number, a task step in
Sub- name, and the step numbers from that scenario here the document
Process
Reference System Pass / Fail Decision: This Does not generally correspond to
System block covers an automatic a task step in the document;
Pass/F decision made by the software instead it is used to reflect an
Process Decision: Identifies a decision / branching Does not
ail automatic decision by the system
Decisio that is made after a step has been
point, signifying a choice to be made by the end usually executed.
user. Lines represent different choices emerging correspond to a n
Proces
from different parts of the diamond. task step in the
s document;
Decisio Reflects a
n choice to be
made after step
execution