About monitoring plans

Note: As of SP04, SAP Convergent Charging 4.0 features monitoring plans that are available in the pricing catalogs in the master data. You create monitoring plans only when SAP CC is connected to a policy control system and when the spending status monitoring function is implemented in your system landscape.

 

A monitoring plan defines the generation of spending statuses that you can monitor in a connected policy system (or monitoring system) during charging and refilling operations relating to an end customer. The plan defines a list of spending status identifiers and the monitored sources (counters), and some rules for determining their label values.

Note: You configure the logic to convert the value of a counter stored in a contract into a label reported in a spending status by setting up a range table dedicated to this scope.

They are then combined and assigned to commercial products in a CRM application or a provisioning system and are finally activated in the provider contract of an end customer of the service provider.

The monitoring plan consists of:

Example

You implement policy control in your system landscape to ensure fair usage and to optimize the network bandwidth allocation with predefined policy rules. You can configure a monitoring plan 'Monitoring plan dedicated to data usage' that defines the reporting of a spending status that indicates if the service quota is still valid.

Before starting

Before creating and setting up a monitoring plan, you must be familiar with the following:

Prerequisites

You must at least:

Integration

This master data is used in an interfaced CRM or provisioning system to model commercial products. Once the plan is released, its signature cannot not change anymore. For example, SAP CRM manages some monitoring plans as charge plans.

Versions

You can modify and save different versions of a monitoring plan.

Transport

To transport a monitoring plan between different system landscapes

You can:

See also