Presentation on theme: "Sales Order Processing: Sale from Stock"— Presentation transcript:
1 Sales Order Processing: Sale from Stock SAP Best Practices
2 Purpose, Benefits, and Key Process Steps 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.BenefitsWhen an order is entered, an availability check is performed and a shipping point is determined automaticallyA billing document is created and postings to FI and CO are madeKey Process StepsCreate sales orderOrder confirmationDeliveryPickingGoods issueBilling
3 Required SAP Applications and Company Roles Enhancement package 5 for SAP ERP 6.0Company roles involved in process flowsSales AdministratorWarehouse ClerkBilling Administrator
4 Detailed Process Description Sales Order Processing: Sale from StockThe 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.
5 Sales Order Processing: Sale from Stock Process Flow DiagramSales Order Processing: Sale from StockEventCustomer Needs to Buy ProductCredit Management (108)Credit Management (108)(Optional)Sales Quotation (112)CustomerOrder ConfirmationDelivery NoteBilling DocumentSales AdministratorSales Order EntryWarehouse ClerkDelivery Due ListCheck Batches / Assign Serial Number (optional)Post Goods IssueInventory COGSPick ListBilling AdministratorBillingAccounts Receivable AccountantAR–Incoming Payment(157)Sales: Period End Closing Operations (203)AR= Accounts Receivable, COGS = Cost of Goods Sold
6 Legend Symbol Description Usage Comments Symbol Description 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 eventBusiness Activity / Event: Identifies an action that either leads into or out of the scenario, or an outside Process that happens during the scenarioDoes not correspond to a task step in the documentUnit Process: Identifies a task that is covered in a step-by-step manner in the scenarioCorresponds to a task step in the documentProcess 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 hereProcess 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 executionSymbolDescriptionUsage CommentsTo next / From last Diagram: Leads to the next / previous page of the DiagramFlow chart continues on the next / previous pageHardcopy / Document: Identifies a printed document, report, or formDoes 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 linesFinancial Actuals: Indicates a financial posting documentBudget Planning: Indicates a budget planning documentManual Process: Covers a task that is manually doneDoes 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 processDoes 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 linesSystem Pass / Fail Decision: This block covers an automatic decision made by the softwareDoes 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.Diagram Connection<Function>External to SAPHardcopy / DocumentFinancial ActualsBusiness Activity / EventBudget PlanningUnit ProcessManual ProcessProcess ReferenceSub-Process ReferenceExisting Version / DataProcess DecisionSystem Pass/Fail Decision