Process catalog

Mon, 01 Jan 0001 00:00:00 +0000

Goal

This process catalog summarizes the main end-to-end flows of Professional Services. It shows how sales contracts, recurring billing, ticketing, work orders, and purchase contracts work together from a business perspective.

Context

Professional Services connects sales, service, and purchasing processes through shared contract, project, and billing objects. This creates linked process paths from the initial quote to recurring invoicing or from a service case to a billable service transaction.

Prerequisites

The core setup for contracts, billing types, tickets, and work orders is maintained.
Projects, customers, vendors, and relevant number series exist.
Teams have defined which processes are triggered manually, from contracts, or from external systems.

Process catalog

Process Sales quote to recurring billing Quotes, sales contracts, and recurring invoicing are directly connected in Professional Services. +

A sales quote can be created with the Professional Services sales type and linked directly to a new or existing sales contract.
The sales contract stores billing assignments, contract duration, service level agreements, and other recurring service components.
Once the contract is activated, due services are collected in the recurring invoice list.
From recurring billing, multiple invoices can be created, reviewed, printed, and posted.

Process Purchase contracts and purchasing-side contract visibility Purchasing is connected with customer-side contract scenarios through purchase contracts. +

Purchase contracts define the contractual framework with a vendor, including validity and optional customer reference.
Contract lines maintain services, quantities, prices, and validity periods.
Purchase contracts can be linked to sales contracts for transparency across vendor and customer scenarios.
Activated purchase contracts can be considered in batch purchase-order generation or trigger purchase orders directly.

Process Ticketing and service billing Service cases are captured in tickets, released, and transferred into billable service output. +

Tickets can be created manually in Professional Services or transferred from external ticketing systems through the API.
The ticket stores responsibilities, ticket lines, project reference, and optional contract or contingent reference.
Once completed and released, the ticket can be transferred and posted, which creates project planning lines.
These services are then collected and invoiced through service billing.

Process Work orders and operational service execution Work orders structure planned field or service activities and convert execution into billable services. +

Work orders can be created manually, from tickets, or from property-related master data.
The process maintains header data, order lines, and later the actual service lines delivered.
Status changes such as completed and released control when the order is ready for print, handover, or billing.
When transferred or posted, the system creates project planning lines that can be invoiced through service billing.

Process Recurring tasks and work packages Plannable activities are prepared in a structured way and turned into operational tickets or work orders. +

Recurring activities can be defined as work tasks and grouped into work packages.
Depending on the configuration, these structures generate tickets or work orders for execution.
This standardizes repeatable service activities and makes them easier to schedule and process.
Final billing still follows the service and contract logic of Professional Services.

Outcome

Sales, service, and purchasing flows are combined into one shared process picture.
Contract and billing objects form the common backbone across the individual steps.
Recurring services can be managed in a traceable way from the first commercial step to the final billed service.

Processes on Product Documentation

Process catalog

Goal

Context

Prerequisites

Process catalog

Outcome