Presentation on theme: "Sales Order Processing for Prospect"— Presentation transcript:
1Sales Order Processing for Prospect SAP Best Practices
2Purpose, Benefits, and Key Process Steps This scenario describes the process of creating a sales order without having a customer master record for the prospect available at the beginning of the order process (create sales order with dummy customer)BenefitsSales order processing without the customer’s account numberSales Order entry with material determinationKey Process StepsCreate sales order w/o having the customer’s account numberCreate customer master recordAssign customer account numberPick and ship itemsPost goods issueBilling
3Required SAP Applications and Company Roles SAP enhancement package 5 for SAP ERP 6.0Company RolesSales AdministrationWarehouse ClerkSales BillingAccounts Receivable
4Detailed Process Description Sales Order Processing for ProspectIn this scenario, you process sales order documents without having a customer master record for the prospect available at the beginning of the order process.A dummy customer is used when your sales order processors need to investigate an order for a prospect. The sales order can be saved but remains incomplete until a valid customer account number has been entered in the sales order. This function is particularly useful for companies that take phone orders. For example, a prospect calls and requests pricing and information on a catalog item. The order processor can build the entire order without needing an account number until the end. Then, your sales employee can ask the prospect for the data needed to create the customer master record (“Dear Madam/dear Sir, thank you for your order. To fulfill it, we now need some additional information from you. Please let me know your name, address, …”). Once the customer’s account number has been created, it can be assigned to the sales order and replace the dummy customer entry.
5Sales Order Processing for Prospect Process Flow DiagramSales Order Processing for ProspectEventnew Customer Needs to Buy ProductDaily Shipment Work list, enough InventoryCustomerOrder ConfirmationDelivery NoteBill of LadingSales Administra-tionSales Order Entry with dummy customerChange Sales OrderWarehouse ClerkDelivery Due ListPick ListCheck Batches / Assign Serial Number (optional)Goods IssueSales BillingBillingAccounts ReceivableInvoiceCreate Customer Master (155.18)(Optional) Sales: Period End Closing Operations (203)Accounts Receivable (157)End Process
6Legend 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