Presentation is loading. Please wait.

Presentation is loading. Please wait.

Service Contract with Periodic Billing

Similar presentations


Presentation on theme: "Service Contract with Periodic Billing"— Presentation transcript:

1 Service Contract with Periodic Billing
SAP Best Practices

2 Purpose, Benefits, and Key Process Steps
A service provider has a service contract with a customer. The business process starts with a notification and a service order. Benefits Customer Contract Management Customer Service Management Service Order Management Purchasing Periodic Billing Key process flows covered Creating a Customer Contract Creating a Service Notification Changing the Service Notification Creating a Service Order Changing the Service Order Time Recording (211) Travel Management (191) Confirming the Materials Used Creating a Purchase Order Confirming the Goods Receipt Entering the Invoice for Purchase Order Displaying Planned/Actual Costs Closing the Service Order – Technical complete Creating the Billing of Contract

3 Required SAP Applications and Company Roles
Enhancement package 6 for SAP ERP 6.0 Company roles involved in process flows Service Agent Service Employee Purchaser Accounts Payable Accountant Warehouse Clerk Billing Administrator

4 Detailed Process Description
Service Contract with Periodic Billing The costs (fee, spare parts and travel expenses) resulting from the service order are account assigned to the service order and billed to the customer by Contract Periodic Billing. The services provided are represented in the sales contract and sales order per units of service, so the service can be divided and billed into discrete units. The price of the service unit is not calculated by the system in this example, but updated manually in the contract by the service provider after negotiating it with the customer. If necessary, spare parts are ordered and purchased.

5 Service Contract with Periodic Billing
Process Flow Diagram Service Contract with Periodic Billing Service Employee Warehouse Clerk Billing Administration Accounts Payable Service Agent Create a Customer Contract Business Activity / Event Goods Movement Customer creates a Purchase Order Create the Billing of Contract Close the Service Order – Technically complete Enter Invoice for Purchase Order Confirm the Goods Receipt Create a Service Order Change the Service Notification Create a Service Notification Change the Service Order Time Recording (211) Travel Management (191) Settle Service Orders (189) Close the Service Order – Business View (189) Display Planned / Actual Costs Purchaser Confirming the material used Creating a purchase Order Event

6 Legend 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 event Business Activity / Event: Identifies an action that either leads into or out of the scenario, or an outside Process that happens during the scenario Does not correspond to a task step in the document 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 Process 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 here Process 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 execution Symbol Description Usage Comments To next / From last Diagram: Leads to the next / previous page of the Diagram Flow chart continues on the next / previous page Hardcopy / Document: Identifies a printed document, report, or form Does 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 lines Financial Actuals: Indicates a financial posting document Budget Planning: Indicates a budget planning document Manual Process: Covers a task that is manually done Does 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 process Does 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 lines 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; 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 SAP Hardcopy / Document Financial Actuals Business Activity / Event Budget Planning Unit Process Manual Process Process Reference Sub-Process Reference Existing Version / Data Process Decision System Pass/Fail Decision

7 Appendix Master Data Used Service Plant Material/Service Material
Sold-to party Ship-to party Payer Plant Storage Location Company Code CO Area Purchasing Organization Sales organization Distribution channel Division Functional Location Personnel Number Work Center Supplier

8


Download ppt "Service Contract with Periodic Billing"

Similar presentations


Ads by Google