SAP Convergent Charging® 3.0 consists of the following business scenarios:
Charging process: Allows to rate and charge an event (for example, the sending of a SMS or a voice call) to an account. This process is performed through the pricing information included in a charge (price plan and charging plan) of an activated charge plan or a in a charge activated in a subscription.
Refilling process: Allows a customer to credit prepaid accounts manually or automatically. This process is performed through an activated refill plan.
Process of billable item creation: Allows to convert charged items and refill records into billable items which are sent to SAP Convergent Invoicing in SAP ERP/FI-CA. This process is performed through billable items.
For more information, see Help resources.
The charging and the refilling processes are configured through the decision tree of a charge or of the refill logic, which is made up of components (*):
(*): Except comparators and operators which are common components used both by the price plan, the charging plan, and the refill logic.
A price plan calculates an amount linked to a usage event, a recurring event, or a one-shot event. The amount is calculated by using a set of instructions described in a price plan that is contained within a charge. A charge always includes a unique price plan.
Remember that the taxes in SAP CC Core Tool are defined at the following levels:
Subscriber account
Charge in a charge plan
Offer
Tax computation only applies to price plan components but does not apply to charging and refill logic components.
For more information, refer to the online help of Core Tool (see the Taxes topic)
A charging plan defines which accounts will be charged or refilled with the amount of a service calculated by the related price plan.
To charge or refill an account, the charging plan is linked to a subscriber account through the mapping of charging references included in each subscription. When a customer subscribes to an offer, each charging reference used in a charging plan is connected to one account and optionally to a credit limit balance defined in the related subscriber account.
Part of a refill plan, the refill logic is a decision tree that computes the different credits (money, units, and so on) of a refill. Calculations in the refill logic are only performed when the refill plan is triggered by:
A usage event (usage refill)
A periodic event (recurring refill)
A one-shot event (one-shot refill)
To compute a refill event, the refill logic consists of a set of refill logic components.
|
Note: For information about help, refer to Help resources. |
Document version: 1.2 - April 2013
(c) Copyright 2011 SAP AG. All rights reserved.
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice.
This documentation may describe use cases that are not authorized for all customers in all regions. Please refer to your license agreement and comply with any territorial or use restrictions that apply.
Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.
All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.
These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.