Sales Order Processing From Stock1

8/6/2019 Sales Order Processing From Stock1

http://slidepdf.com/reader/full/sales-order-processing-from-stock1 1/7



Scenario Overview – 1

Purpose

This scenario describes the entire process sequence for a standard sales process

(Make-to-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 isdetermined 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:




Required

SAP ECC 6.0 EhP3

Company roles involved in process flows Sales Administration Warehouse Clerk

Sales Billing Accounts Receivable

SAP Applications Required:




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 of applicable discounts, checking the availability of the materials, and checkingthe 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 tothe warehouse 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 the

revenue, 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,customer statements are prepared and printed, and the incoming paymentsare recorded, and then cleared to make sure that the open customer

account balance is reconciled.

Detailed Process Description:



Custome

r

Process Flow Diagram

Sales Order Processing: Sale from Stock

Sales

Adminis

tr

ation

Wareh

ouseClerk

Account

s

Receiva

ble

Event

Sales Order

Entry

Customer Needs to Buy

Product

InventoryCOGS

AR= Accounts Receivable, COGS = Cost of Goods Sold

Delivery NoteOrder Confirmation

Pick List

Delivery DueList

Post GoodsIssue

AR–Incoming Payment

(157)

(Optional)Sales

Quotation(112)

BillingDocument

CreditManagement

(108)

CreditManagement

(108)

CheckBatches /

Assign SerialNumber

(optional)

ClosingOperations

SD (203)

Sales

Billing

Billing



Legend

Symbol Description Usage Comments

Band: Identifies a user role, such as Accounts Payable

Clerk or Sales Representative. This band can alsoidentify an organization unit or group, rather than aspecific role.

The other process flow symbols in this table go intothese rows. You have as many rows as required to cover all of the roles in the scenario.

Role band contains

tasks common tothat role.

External Events: Contains events that start or end thescenario, or influence the course of events in thescenario.

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 alsolead to documents involved in the process flow.

Connects two tasksin a scenarioprocess or a non-step event

Business Activity / Event: Identifies an action that either leads into or out of the scenario, or an outside Processthat happens during the scenario

Does notcorrespond to a taskstep in thedocument

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

Corresponds to atask step in thedocument

Process Reference: If the scenario references another scenario in total, put the scenario number and name

here.

Corresponds to atask step in the

document

Sub-Process Reference: If the scenario references another scenario in part, put the scenario number, name, and thestep numbers from that scenario here

Corresponds to atask step in thedocument

Process Decision: Identifies a decision / branching point,signifying a choice to be made by the end user. Linesrepresent different choices emerging from different partsof the diamond.

Does not usuallycorrespond to a taskstep in thedocument; Reflectsa choice to be madeafter step execution

Symbol Description Usage Comments

To next / From last Diagram: Leads tothe 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 task step ina document; instead, it is used toreflect a document generated by a taskstep; this shape does not have anyoutgoing flow lines

Financial Actuals: Indicates a financialposting document


Budget Planning: Indicates a budgetplanning document


Manual Process: Covers a task that ismanually done

Does not generally correspond to atask step in a document; instead, it isused to reflect a task that is manuallyperformed, such as unloading a truckin the warehouse, which affects theprocess flow.

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

Does not generally correspond to atask step in a document; instead, thisshape reflects data coming from anexternal source; this step does nothave any incoming flow lines

System Pass / Fail Decision: This blockcovers an automatic decision made bythe software

Does not generally correspond to atask step in the document; instead it isused to reflect an automatic decisionby the system that is made after a stephas been executed.

<Function>

External

toSAP

BusinessActivity /

Event

Unit Process

ProcessReference

Sub-Process

Reference

Process

Decision

DiagramConnection

Hardcopy /Document

FinancialActuals

BudgetPlanning

ManualProces

s

ExistingVersion /

Data

SystemPass/F

ailDecisio

n



Copyright 2008 SAP AG

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 AG. The information contained herein may be changed

without prior notice.

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.

SAP, R/3, xApps, xApp, SAP NetWeaver, Duet, SAP Business ByDesign, ByDesign, PartnerEdge and other SAP products and services mentioned herein as well as their respective logos are

trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned and associated logos displayed

are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.

The information in this document is proprietary to SAP. This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. This document

contains only intended strategies, developments, and functionalities of the SAP® product and is not intended to be binding upon SAP to any particular course of business, product strategy,

and/or development. SAP assumes no responsibility for errors or omissions in this document. SAP does not warrant the accuracy or completeness of the information, text, graphics, links, or

other items contained within this material. This document is provided without a warranty of any kind, either express or implied, including but not limited to the implied warranties of

merchantability, fitness for a particular purpose, or non-infringement.

SAP shall have no liability for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of these materials. This limitation

shall not apply in cases of intent or gross negligence.The statutory liability for personal injury and defective products is not affected. SAP has no control over the information that you may access through the use of hot links contained in these

materials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages.

Sales Order Processing From Stock1

Documents