Components

Purpose

Components describe the individual technical elements inside an object or installation in Professional Services. They help structure the installed base in detail and connect service, contract, and billing processes precisely to concrete installed elements.

Prerequisites

• related objects and, where needed, installations exist
• component types, calculation types, and relevant item or resource assignments are aligned from a business perspective
• if service or contract references should be used, the related master data and processes are configured

Functional focus

Master data and technical classification

The component stores object and installation references, description, component type, calculation type, and sales-related references. In addition, installation and activation dates, quantities, units, serial or lot numbers, version numbers, and manufacturer information can be maintained.

Hierarchy within the installed base

Components can be structured hierarchically. Parent components, position types, and main positions help model technical structures transparently and break larger installations into logically related parts.

Service, contract, and billing reference

Components can be enriched with service information such as manufacturer care packs or warranty periods. It also remains visible in which billing-type assignments and purchase or sales contract references a component is used. This makes it possible to connect technical elements directly with recurring services and contractual agreements.

Attributes and batch updates

Attributes store additional characteristics. For mass changes, batch processing is available so customer, object, or other assignments can be adjusted for multiple components at the same time.

Outcome

Components make the installed base analyzable and operationally usable down to the concrete technical unit. This makes service linkage, contract logic, and data maintenance in Professional Services more detailed and consistent.