Presentation on theme: "Sales of Nonstock Item with Order Specific Procurement"— Presentation transcript:
1Sales of Nonstock Item with Order Specific Procurement SAP Best Practices
2Purpose, Benefits, and Key Process Steps In this scenario a customer orders a material that is currently not in stock. The material is therefore procured from an external supplier.BenefitsHandover of customer’s requirements directly to external supplierMaterial is sent from external supplier to trader. The trader stays in charge for the complete delivery processFulfillment of customer’s requirements despite of material shortageKey Process StepsCreate Sales OrderConvert Purchase Requisitions to Purchase OrderApproval of Purchase OrdersPost Goods ReceiptInvoice VerificationDelivery Processing and Goods IssueBilling
3Required SAP Applications and Company Roles Enhancement package 5 for SAP ERP 6.0Company RolesSales AdministratorPurchasing ManagerPurchaserBilling AdministratorWarehouse ClerkAccounts Payable AccountantAccounts Receivable Accountant
4Detailed Process Description Sales of Non-stock Item with Order Specific ProcurementIn this scenario a customer orders a material that is currently not in stock. The material is therefore procured from an external supplier.Example:The customer orders 100 PC of the material H14 at the sales organization 1000.When creating the sales order, a purchase requisition is generated. In the next step, the purchase requisition is converted into a purchase order for the supplierThe goods receipt is created on a customer’s special stock for the customer The delivery and the invoice follow from here. Finally the invoice verification for the goods receipt is created.Toward the end of this process, you will also check the customer’s credit level.
5Sales of Nonstock Item with Order specific Procurement Process Flow DiagramSales of Nonstock Item with Order specific ProcurementVendorDelivery of Items to Trader’s WarehouseIncoming Vendor InvoiceCustomerCustomer Request for MaterialCredit Management(108)Order ConfirmationBilling DocumentSales Adminis-tratorCreate Sales Order(Optional)Change Order QuantityCredit Management(108)Auto-generates a RequisitionPurchasing ManagerQuotation for Procurement(128)Display List of Purchase Requisitions to be AssignedConvert Assigned Requisitions to Purchase OrdersApproval of Purchase OrdersBilling AdministratorBillingWarehouse ClerkDelivery Due ListPost Goods IssuePrint GR SlipPost Goods ReceiptPick ListAccounts Payable/ Receivable AccountantAP –Outgoing Payment(158)COGS VendorInvoice ReceiptAR–Incoming Payment(157)AP = Accounts Payables, AR = Accounts Receivables, COGS = Cost of Goods Sold, GR = Goods Receipt
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