109 scen overview en in

Sales Order Processing: Sale from Stock

SAP Best Practices Baseline Package (India)

SAP Best Practices

Scenario Overview 1

This scenario include two parts:

Sales from Factories

Sales from Depots

Scenario Overview – Sales from Factories 1

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

process (Sale from Factories) 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

Purpose and Benefits:


Required SAP enhancement package 4 for SAP ERP 6.0

Company roles involved in process flows Sales Administrator Warehouse Clerk Billing Administrator Excise Clerk

Key process flows covered Create sales order Order confirmation Delivery Picking Goods issue Billing Excise Invoice

SAP Applications Required:


Sales Order Processing: Sale from Factory

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 next 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.

Excise Payable entry is posted.

Sales from Factory-Detailed Process Description:

Cu

sto

mer

Process Flow DiagramSales Order Processing: Sale from Stock-Factory Sales

Sal

es

A

dm

inis

tra

tor

War

eh

ou

se

Cle

rk

Acc

ou

nts

R

ecei

vab

le

Acc

ou

nta

nt

Ev

en

t

Sales Order Entry

Customer Needs to Buy

Product

Inventory COGS

AR= Accounts Receivable, COGS = Cost of Goods Sold

Delivery NoteOrder Confirmation

Pick List

Delivery Due List

Post Goods Issue

AR–Incoming Payment

(157)

(Optional)Sales

Quotation (112)

Billing Document

Credit Management

(108)

Credit Management

(108)

Check Batches /

Assign Serial Number

(optional)

Sales: Period End Closing Operations

(203)

Bill

ing

A

dm

ini

stra

tor

Billing

Exc

ise

Cle

rk Excise Invoice

Excise Payable

Scenario Overview – Sales from Depots 1

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

process (Sale from Depot Stock) with a customer. The business process encompasses all steps from creating an stock transfer order/ Purchase 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

Purpose and Benefits:


Required SAP enhancement package 4 for SAP ERP 6.0

Company roles involved in process flows Sales Administrator Warehouse Clerk Billing Administrator Excise Clerk

Key process flows covered Stock transfer to Depot for finish goods to Capture Excise Goods receipt according to Purchase Order for trading goods Capture

Excise Sales order at depot Delivery at depot Excise invoice at depot Commercial invoice at Depot

SAP Applications Required:


Sales Order Processing: Sale from Depot

The Depot sales process starts with creation of stock transfer order or purchase order to create stock of required material at depot for further sale according to customer requirement.

If stock at Depot is created with STO from Depot to manufacturing plant , then delivery and picking is performed at manufacturing plant. Performa invoice is create with ref. to delivery. Excise invoice is created with ref. to Performa invoice to crate excise payable entry at manufacturing plant.

If stock at Depot is created with PO to vendor , them purchase order from depot is created for required amount of stock.

Material is received at Depot with ref. to delivery at manufacturing plant or PO to vendor and excise values are captured .

Once stock is built up at depot, sales order for sale from depot is created according to customer requirement.

Delivery of material is created with ref. to sales order. Excise invoice is created for delivery at depot. Commercial invoice is created with ref. to delivery at depot.

Detailed Process Description:

Cu

sto

mer

Process Flow DiagramSales Order Processing: Sale from Stock-Depots Sales

Sal

es

A

dm

inis

tra

tor

War

eh

ou

se

Cle

rk

Acc

ou

nts

R

ecei

vab

le

Acc

ou

nta

nt

Ev

en

t

Sales Order Entry

Customer Needs to Buy

Product

Inventory COGS

AR= Accounts Receivable, COGS = Cost of Goods Sold

Delivery NoteOrder Confirmation

Pick List

Delivery Due List

Post Goods Issue

AR–Incoming Payment

(157)

(Optional)Sales

Quotation (112)

Billing Document

Credit Management

(108)

Credit Management

(108)

Check Batches /

Assign Serial Number

(optional)

Sales: Period End Closing Operations

(203)

Bill

ing

A

dm

ini

stra

tor

Billing

Exc

ise

Cle

rk Excise Invoice

Excise Payable

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 two tasks in a scenario process or a non-step event

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

Does not correspond to a task step in the document

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

Corresponds to a task step in the document

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


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


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

Does not usually correspond to a task step in the document; Reflects a choice to be made after step execution

Symbol Description Usage Comments

To next / From last Diagram: Leads to the next / previous page of the Diagram

Flow chart continues on the next / previous page

Hardcopy / Document: Identifies a printed document, report, or form

Does not correspond to a task step in a document; instead, it is used to reflect a document generated by a task step; this shape does not have any outgoing flow lines

Financial Actuals: Indicates a financial posting document


Budget Planning: Indicates a budget planning document


Manual Process: Covers a task that is manually done

Does not generally correspond to a task step in a document; instead, it is used to reflect a task that is manually performed, such as unloading a truck in the warehouse, which affects the process flow.

Existing Version / Data: This block covers data that feeds in from an external process

Does not generally correspond to a task step in a document; instead, this shape reflects data coming from an external source; this step does not have any incoming flow lines

System Pass / Fail Decision: This block covers an automatic decision made by the software

Does not generally correspond to a task step in the document; instead it is used to reflect an automatic decision by the system that is made after a step has been executed.

<F

unct

ion>

Ext

erna

l to

SA

P

Business Activity /

Event

Unit Process

Process Reference

Sub-Process

Reference

Process

Decision

Diagram Connection

Hardcopy / Document

Financial Actuals

Budget Planning

Manual Proces

s

Existing Version /

Data

System Pass/F

ail Decisio

n

© 2010 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.

Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation.

Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries.

Oracle is a registered trademark of Oracle Corporation.

UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.

Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology.

Java is a registered trademark of Sun Microsystems, Inc.

JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape.

SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, Clear Enterprise, SAP BusinessObjects Explorer, 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 other countries.

Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP France in the United States and in other countries.

All other product and service names mentioned 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. No part of this document may be reproduced, copied, or transmitted in any form or for any purpose without the express prior written permission of SAP AG.

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. Please note that this document is subject to change and may be changed by SAP at any time without notice.

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.

109 scen overview en in

Documents