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.BenefitsCustomer Contract ManagementCustomer Service ManagementService Order ManagementPurchasingPeriodic BillingKey process flows coveredCreating a Customer ContractCreating a Service NotificationChanging the Service NotificationCreating a Service OrderChanging the Service OrderTime Recording (211)Travel Management (191)Confirming the Materials UsedCreating a Purchase OrderConfirming the Goods ReceiptEntering the Invoice for Purchase OrderDisplaying Planned/Actual CostsClosing the Service Order – Technical completeCreating the Billing of Contract
3 Required SAP Applications and Company Roles Enhancement package 5 for SAP ERP 6.0Company roles involved in process flowsService AgentService EmployeePurchaserAccounts Payable AccountantWarehouse ClerkBilling Administrator
4 Detailed Process Description Service Contract with Periodic BillingThe 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 DiagramService Contract with Periodic BillingService EmployeeWarehouse ClerkBilling AdministrationAccounts PayableService AgentCreate a Customer ContractBusiness Activity / EventGoods MovementCustomer creates a Purchase OrderCreate the Billing of ContractClose the Service Order – Technically completeEnter Invoice for Purchase OrderConfirm the Goods ReceiptCreate a Service OrderChange the Service NotificationCreate a Service NotificationChange the Service OrderTime Recording (211)Travel Management (191)Settle Service Orders (189)Close the Service Order – Business View (189)Display Planned / Actual CostsPurchaserConfirming the material usedCreating a purchase OrderEvent
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 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
7 Appendix Master Data Used Service Plant Material/Service Material Sold-to partyShip-to partyPayerPlantStorage LocationCompany CodeCO AreaPurchasing OrganizationSales organizationDistribution channelDivisionFunctional LocationPersonnel NumberWork CenterSupplier