This action might not be possible to undo. Are you sure you want to continue?
SAP Best Practices for Chemicals
and billing © 2011 SAP AG. delivery processing. delivery processing. picking. requisition. and billing • Supply material from own plant to swap partner’s customer – Creating sales quantity contract.Purpose. goods issue. All rights reserved. 2 . goods issue. • The sale order swap process is based on a contract between two Companies/manufacturers to supply similar product to customer of one company whose location is in the same region as the other. external to each other. The basis for the SWAP process is to avoid logistics costs to the benefit of both the companies. Benefits • By performing swap sales with partner companies in the industry. Key Process Steps • Supply material to end customer via swap partner – Creating swap sales order. Benefits. approval. and Key Process Steps Purpose • This scenario deals with Swap Sales process involving two companies. shipment of chemicals is handled locally for customers. picking. reducing travel time and expense.
00 enhancement package 5 Company Roles Purchaser Sales Administrator Purchasing Manager Warehouse Clerk Billing Administrator Accounts Payable Accountant © 2011 SAP AG. All rights reserved.Required SAP Applications and Company Roles Required SAP Applications SAP ECC 6. 3 .
A Sales Order is created in the Ordering company and swap material is delivered to the supplying company’s customer. 4 . and then bills the end customer. For the ordering company. The ordering company hands over the requirement (by creating a Purchase Order) to the supplying company that is defined as a vendor. The supplying company enters into contract with the ordering company and sends an order for its customer. The end customer receives an invoice from the ordering company and the Supplying company sends an invoice based on contract price to the ordering company.© 2011 SAP AG.Detailed Process Description Swap Sales in Chemical Industry The ordering company enters into contract with the supplying company and receives an order for product from its end customer. the scenario focuses on: Creation of Sales Quantity Contract Creation of Customer Material information Creation of a Sales order Creation of Delivery and posting of Goods issue Creation of Billing document for ordering company . Billing is offset with an invoice from the supplying company. the scenario focuses on: Creation of the Purchasing Quantity Contract Creation of a sales order for the end Customer Creation of a Purchase Request and converted into a Purchase Order Posting of Statistical Goods Receipt Creation of Delivery and posting of Goods issue Ordering Company in this scenario refers to SAP Best Practices Company Code 1000 Creation of Billing Document for end customer Verification and posting of Vendor Invoice For the supplying company (your company as swap partner). All rights reserved. A reconciliation is carried out at the end of month or quarter for final settlement between the two companies.
Billing Billing Accts Payable Acct.Process Flow Diagram Refurbishment Management Supply Matl to End Customer from Swap Partner Purchaser Event APAccounts Payable (158) Create Purchasing Quantity Contract Assign Requisition and Create PO Create Swap Sales Order Create Sales Quantity Contract Create Customer Material Information (Sales Admin_FM) Sales Admin. All rights reserved. 5 . Invoice Verification Supply Material from Own Plant to Swap Partner’s Customer Supply Material from End Customer from Swap Partner © 2011 SAP AG. Create Sales Order Purchasing Manager Approve POs (Optional) Warehouse Clerk Statistical Goods Receipt Delivery Processing Picking (Optional) Post Goods Issue Delivery Processing Picking (Optional) Post Goods Issue Billing Admin.
report. This band can also identify an organization unit or group. 6 . this shape reflects data coming from an external source. it is used to reflect a task that is manually performed. signifying a choice to be made by the end user. Lines represent different choices emerging from different parts of the diamond. which affects the process flow. instead. 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. or form Does not correspond to a task step in a document. instead. External Events: Contains events that start or end the scenario. it is used to reflect a document generated by a task step. it is used to reflect a document generated by a task step. instead it is used to reflect an automatic decision by the system that is made after a step has been executed. 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 SubProcess Reference Sub-Process Reference: If the scenario references another scenario in part. Does not usually correspond to a task step in the document. such as Accounts Payable Clerk or Sales Representative. Line can also lead to documents involved in the process flow. Symbol Description Usage Comments <Function> Band: Identifies a user role. instead. or an outside Process that happens during the scenario Does not correspond to a task step in the document Budget Planning Does not correspond to a task step in a document. this step does not have any incoming flow lines Process Reference Process Reference: If the scenario references another scenario in total. © 2011 SAP AG. Does not generally correspond to a task step in a document. and the step numbers from that scenario here Corresponds to a task step in the document Proces s Decisio n Process Decision: Identifies a decision / branching point. 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. All rights reserved. or influence the course of events 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 Unit Process Corresponds to a task step in the document Manual Process: Covers a task that is manually done Manual Proces s Does not generally correspond to a task step in a document. Flow line (dashed): Line indicates flow to infrequently-used or conditional tasks in a scenario. You have as many rows as required to cover all of the roles in the scenario. put the scenario number. Diagram Connection To next / From last Diagram: Leads to the next / previous page of the Diagram Flow chart continues on the next / previous page External to SAP Hardcopy / Document Hardcopy / Document: Identifies a printed document. such as unloading a truck in the warehouse. rather than a specific role. it is used to reflect a document generated by a task step. instead. this shape does not have any outgoing flow lines Budget Planning: Indicates a budget planning document Business Activity / Event Business Activity / Event: Identifies an action that either leads into or out of the scenario. 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. put the scenario number and name here. name. instead. The other process flow symbols in this table go into these rows.Legend Symbol Description Usage Comments Role band contains tasks common to that role.