|
Note: As of SP04, SAP Convergent Charging 4.0 features spending status monitoring to enable a registered and connected policy or monitoring system to make policy decisions that are based on information about an end customer and his service usage context. SAP CC converts some counter values in provider contracts as the form of spending statuses and manages the reporting of these indicators when they change. |
In online environment, the spending status monitoring enables to implement policy control in your system landscape. Downstream systems (policy, monitoring) can make policy decisions based on end customer experience and service spending information reported by SAP Convergent Charging.
The spending status monitoring adds a monitoring plan and spending status reporting features to SAP Convergent Charging.
The benefits of the spending status monitoring enables a flexible configuration in master data through:
The easy data configuration in pricing catalog (master data): Basic objects to configure monitoring plans
The fine configuration in customer master data: Configuration in contract items in provider contracts
|
Notes:
|
The SAP CC systems can detect changes in the business context of the end customers and sends spending status reports to the registered policy or monitoring system.
Refer to the SAP CC Configuration Guide (see in help resources) for more information about the implementation of this feature in your system landscape:
When SAP CC is connected to SAP CRM.
When SAP CC must be interfaced with another CRM or provisioning system.
Example
A service provider needs to focus on the quality of services it delivers to increase perceived quality and performances and reduce churn. It must implement a fair usage management function in the system landscape to be able to act on traffic control and service usage (consumption).
An end customer subscribes to a mobile data plan allowing for "unlimited data usage".
To protect itself from customer abuse in network usage, the operator adds a clause to the contract small prints.
It explains that data usage is unlimited with regular quality of service up to a consumption threshold (2.5GB per month). Once the customer has used these 2.5GB in a month, service is continued but throttled, downgraded in quality of service.
The service provider implements policy control in its system landscape to ensure fair usage and to optimize the network bandwidth allocation with predefined policy rules.
A policy system registers to the SAP CC system and monitor fair usage of end customers.
To model this business case in SAP CC, the service provider configures in the pricing catalog of this customer service:
The necessary entry in the counter name dictionary: 'DATA_USAGE' is a counter name that will be used in the charge plans and monitoring plans
The necessary reusable charge and charge plan
The necessary spending status description: 'Data fair usage'
The necessary range table class: 'RTC dedicated to data monitoring'
The necessary range tables: 'RT dedicated to data monitoring'
The necessary monitoring plan: 'Monitoring plan dedicated to data usage'
Spending statuses in reports
Data configuration:
In business data: Spending status descriptions
In pricing catalog (master data): Monitoring plans
In provider contracts (customer master data): Contract item activating a monitoring plan
SAP CC Library (Application Help) about the spending status monitoring feature and related processes