Sales Order Processing with Export Control

SAP Best Practices for Apparel and Footwear (India)

SAP Best Practices

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

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

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

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 .

such as Accounts Payable Clerk or Sales Representative. Does not generally correspond to a task step in a document. instead. 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. Line can also lead to documents involved in the process flow. instead. instead. Lines represent different choices emerging from different parts of the diamond. . such as unloading a truck in the warehouse. 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. 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. 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. report. it is used to reflect a document generated by a task step. it is used to reflect a document generated by a task step. name. it is used to reflect a task that is manually performed. this shape reflects data coming from an external source. Corresponds to a task step in the document Does not generally correspond to a task step in a document. it is used to reflect a document generated by a task step. put the scenario number and name here. instead. Business Activity / Event: Identifies an action that either leads into or out of the scenario. This band can also identify an organization unit or group. Does not usually correspond to a task step in the document. External Events: Contains events that start or end the scenario. Symbol Description Usage Comments <Function> Band: Identifies a user role. The other process flow symbols in this table go into these rows. instead it is used to reflect an automatic decision by the system that is made after a step has been executed. instead. signifying a choice to be made by the end user. or influence the course of events in the scenario. this step does not have any incoming flow lines Process Reference SubProcess Reference Sub-Process Reference: If the scenario references another scenario in part. which affects the process flow.Legend Symbol Description Usage Comments Role band contains tasks common to that role. or form External to SAP Does not correspond to a task step in a document. 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. You have as many rows as required to cover all of the roles in the scenario. Flow line (dashed): Line indicates flow to infrequentlyused or conditional tasks in a scenario. 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. put the scenario number. rather than a specific role. 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.

Sign up to vote on this title
UsefulNot useful