About logic components

SAP Convergent Charging 4.0 consists of the following business scenarios:

• Process of charging: Allows to rate a usage event and debit the price amount from an account or credit it to an account. The SAP CC system performs this process through the execution of a price plan and a charging plan configured in a charge and subscribed in a provider contract or in a subscription.

• Process of refilling: Allows a customer to credit prepaid accounts manually or automatically. This process is performed through the execution of a refill plan activated in a provider contract item.

• Process of creating billable items: Allows to convert charged items and refill records into billable items that are sent to SAP Convergent Invoicing in SAP ERP. This process is performed through the execution of the billable item mapping. For more information, see Help resources.

• Process of creating consumption items: Allows to convert chargeable items into consumption items that are sent to SAP Convergent Invoicing in SAP ERP for charging or deferred charging purposes, for example. For more information, see Help resources.

• Process of using allowances: Allows to create allowances, send events to these allowances from the charging or refilling process, modify these events, and redefine the validity period of allowances. For revenue recognition purposes, SAP CC can inform SAP CI through billable items when an allowance is created, used, and has expired. The billable items contain information so that SAP ERP can recognize revenues. For more information, see Help resources.

Process configuration

You configure the charging process and the refilling process by:

• Designing and specifying the pricing logic

• Configuring the relevant master data included in the pricing catalog of a service provider

This logic is configured through the decision trees of a charge or the refill logic. These trees consist of logic components (*):

• Price plan components

• Charging plan components

• Refill logic components

• Allowance logic components

(*): Except comparators and operators which are basic components used both by the price plan, the charging plan, the refill logic, and the allowance logic.

Price plan

A price plan specifies the logic to calculate 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.

About taxes

Remember that the taxes are defined at the following levels in SAP CC:

• Subscriber account

• Charge in a charge plan (charging based on provider contracts)

• Charge in an offer (charging based on subscriptions)

Tax computation only applies to price plan components but does not apply to charging and refill logic components. For more information, consult the online Help of SAP CC Core Tool (see the Taxes topic).

Charging plan

A charging plan specifies 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.

Refill logic

Part of a refill plan, the refill logic specifies the logic to compute 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-off event (one-shot refill)

To compute a refill event, the refill logic consists of a set of refill logic components.

Allowance logic

Part of an allowance plan, the allowance logic defines the rules and conditions of use of an allowance and can model an algorithm based on several types of triggers: Event-based, one-shot, and recurring.

Calculations in the allowance logic are only performed when the allowance plan is triggered by:

•  Any event (event-based trigger)

•  A periodic event (recurring trigger)

•  A one-shot event (one-shot trigger)

To compute an allowance event, the allowance logic consists of a set of allowance logic components.

Online help version

Document version: 2.5 - October 2015

(c) Copyright 2015 SAP SE or an SAP affiliate company. 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 SE. 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 SE 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 SE 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.