Sales Order Processing with Export Control

SAP Best Practices for Apparel and Footwear (India)

SAP Best Practices

Benefits and Key Process Flows: Purpose This scenario describes the export Sales Order process from Sales Order Entry to Billing for the Apparel and Footwear industry. Sales order which are blocked for failed legal control can be released in exceptional cases. The scenario contains additional R/3 standard and AFS-specific functionality:  Pricing conditions (SKU Pricing)  Availability check (on batch level) incl. legal control check can be done automatically. It helps process the foreign trade business more accurately. dialog  Allocation Run (FIFO logic.Scenario Overview – 1 Purpose. It is more flexible in processing of sales order. The process is designed to demonstrate the various AFS functionalities for sales order processing. Key process flows covered       Creating sales order Releasing Sales Order Order confirmation Allocation Run Delivery plus Picking and Post Goods Issue Billing . fulfillment rate)  Foreign Trade: Legal control Benefits   When selling of legal control relevant materials to customers.

Scenario Overview – 2 SAP Applications and Company Roles: Required  EHP3 for SAP ERP 6.0 Company roles involved in process flows    Sales Administration Warehouse Clerk Sales Billing .

if there is no valid license master for the combination of material classification and the destination country. Once the inventory has been relieved. the warehouse clerk will have to systematically relieve the inventory. During Sales Order Entry ATP allocates existing stock only temporarily. Delivery is executed on the basis of the sales order after A-Run. The allocation of goods is necessary to create a delivery note. customer statements are prepared and printed. The A-Run will put the status “F” (fixed) if the fulfillment rate is fulfilled. and then cleared to make sure that the open customer account balance is reconciled. This step signifies the end of the business transaction in Sales and Distribution. availability check is performed in the background. the delivery can be invoiced and the revenue. This results in the recording of the cost of goods sold in financial accounting. When an order is entered. The quantities are entered on material-size-color-level (Matrix-Entry). An order confirmation after sales order creation can be created and printed. Different price will be found (SKU Pricing) base on different material size. together with the cost of goods sold. So we need to release the sales orders which are blocked for further processing. In exceptional cases it could be necessary to allow the export. This relief of inventory is the actual recording of the physical quantity that is being shipped to the customer.Scenario Overview – 3 Detailed Process Description: Sales Order Processing with Export Control     The process starts with the creation of a foreign customer's sales order. the quantity of the material is completely picked. . To the material which is activated individual legal control.    The final step of this document describes how invoices are posted. Then. is recorded in management accounting. and the incoming payments are recorded. So we need to do Allocation Run to allocate stock to sales orders finally. the sales order will be blocked.

Process Flow Diagram Sales Order Processing with Export Control Event Customer Needs to Buy Product Customer Order Confirmation Delivery Note Billing Document Sales Administration Sales Order Entry Valid legal control ? Yes Order Confirmation(Print Sales Order) Allocation Run No Release Sales Order Warehouse Clerk Delivery plus Pick and Post Goods Issue Inventory COGS Sales Billing Billing Accounts Receivabl e AR–Incoming Payment (157) Closing Operations SD (203) AR= Accounts Receivable. COGS = Cost of Goods Sold .

or influence the course of events in the scenario. instead. Lines represent different choices emerging from different parts of the diamond. External Events: Contains events that start or end the scenario. this shape reflects data coming from an external source. it is used to reflect a document generated by a task step. The other process flow symbols in this table go into these rows. this shape does not have any outgoing flow lines Business Activity / Event Does not correspond to a task step in the document Budget Planning: Indicates a budget planning document Budget Planning Does not correspond to a task step in a document. this shape does not have any outgoing flow lines 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 Manual Process: Covers a task that is manually done Unit Process Manual Proces s Process Reference: If the scenario references another scenario in total. and the step numbers from that scenario here Corresponds to a task step in the document Existing Version / Data Existing Version / Data: This block covers data that feeds in from an external process Proces s Decisio n Process Decision: Identifies a decision / branching point. instead. which affects the process flow. rather than a specific role. this shape does not have any outgoing flow lines Flow line (solid): Line indicates the normal sequence of steps and direction of flow in the scenario. it is used to reflect a task that is manually performed. This band can also identify an organization unit or group. Does not generally correspond to a task step in a document. Flow line (dashed): Line indicates flow to infrequentlyused or conditional tasks in a scenario. put the scenario number. Corresponds to a task step in the document Does not generally correspond to a task step in a document. such as Accounts Payable Clerk or Sales Representative. . instead. put the scenario number and name here. Does not usually correspond to a task step in the document. signifying a choice to be made by the end user. You have as many rows as required to cover all of the roles in the scenario. Line can also lead to documents involved in the process flow. instead it is used to reflect an automatic decision by the system that is made after a step has been executed. or form External to SAP Does not correspond to a task step in a document.Legend Symbol Description Usage Comments Role band contains tasks common to that role. instead. Business Activity / Event: Identifies an action that either leads into or out of the scenario. such as unloading a truck in the warehouse. or an outside Process that happens during the scenario Connects two tasks in a scenario process or a non-step event Financial Actuals: Indicates a financial posting document Financial Actuals Does not correspond to a task step in a document. Reflects a choice to be made after step execution System Pass/F ail Decisio n 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. report. name. instead. this step does not have any incoming flow lines Process Reference SubProcess Reference Sub-Process Reference: If the scenario references another scenario in part. it is used to reflect a document generated by a task step. Symbol Description Usage Comments <Function> Band: Identifies a user role. it is used to reflect a document generated by a task step. Diagram Connection To next / From last Diagram: Leads to the next / previous page of the Diagram Flow chart continues on the next / previous page Hardcopy / Document Hardcopy / Document: Identifies a printed document.

Sign up to vote on this title
UsefulNot useful