Convergent Charging Overview
Convergent Invoice (CC) terminology and definition
Charging: Charging is nothing but whom to charge/to whom we are sending the final
invoice.
Rating: What is the logic behind the calculation for the final billing and invoicing.
Chargeable Item Class: Chargeable item class is nothing but how the services getting
consumed Ex:- telecom industry we have chargeable item classes like - Voice calls (Local and
ISD calls), SMS, MMS, Data service etc and which is based on business scenario.
Charge: The charge is a representation of an amount, which is charged to end customer and
charge is nothing but how much amount we charge to the customer
Price Plan – Basically this is a calculation engine, we are creating it in decision tree
on CC and which determine how the prices getting calculated with logic.
Charging Plan – Which is used to which account (end customer) to be charged.
Tables -
Macros -
Charge Plan: Charge plan is used to define conditions for Price plan and Charging plan.
Technical data -
Charged Item Class –
Note: Charge contains the Price plan and Charging plan, Charge is assigned to Charge plan
Cross catalog Mapping :
Price plan components as below
Subscriber account -
Subscriber mapping table – In this mapping table we can assign customer price list
(discount, some special customer pricing list etc)
Subscriber range table -
Save to Database once we complete the setup
Chargeable Item Class: Input properties
Charged Item Class: Output Properties which pass the information to CI for generating
BITs
Master Data:
Subscriber account is nothing but Business partner(BP) in SOM and CC. which is used to
provide service to end customer. Subscriber account is 2 types Prepaid and External
account.
Subscriber account replicated from SOM to CC so, if you do any changes in subscriber
account in CC then those changes will not reflect in SOM. We should any changes in BP in
SOM then those will reflect in Subscriber account in CC.
Subscriber account contain all the Prepaid and External accounts
Prepaid account: For prepaid account the customer is credited when customer refills
(recharge) and then use the service (Ex:- Mobile pre-paid recharge).
External account (Post-paid): External account is an account which is refers to outside
SAP CC which is managed by third party services (Credit management) for billing and
invoice, the customer is debited when customer consume service (Ex:- Mobile Post-paid
service).
External account in CC = Contract account in CI
**************************************************************************
In CI we can combine different type billing into single invoice. It may service, Sales,
product etc (this is very useful for high volume data processing industry like telecom,
coke)
Q. What is the difference between CIT and BIT?
BIT is ready for billing and invoicing which means the rating and charging happened
in CC and create the BITs for billing and invoicing in CI.
Where in CIT’s may be rated or unrated items and it is later billing functionality, once
the date is reached which means unrated CITs send back from CI to CC for re-rating
and once the rating is done BITs will generate for billing and invoicing.
Customer master data (BP) we can create two ways via SOM or S/4 HANA then
replicate in SOM via middleware.
We can use web service/SOAP for push the data from external source system to CM
What does Bulk-loader sub component inside CC? : Bulk loader sub component is
used to interconnect in between CC to CI and push the rating and charging to CI
CM – Java based, we can create rules and all
FICA-CI – Using ABAP
CC – Web services (We cannot do any development in CC) , cross catolog mapping
SOM – In SOM, Cross catalog mapping is derived into a product automatically via
web service from CC
BP – Business partner: Business partner holds the Credit worthiness, all customer related
information like address,communication, bank information, payment method et
CA – Contract account: Contract account holds the posting related attributes like bank
details, payment method, dunning, taxes, account determination id, payment terms,
clearing category etc.
What is Selection variant?:
What is Grouping variant?:
What is Aggregation?:
Clarification case: Clarification case is nothing but do the further validation at invoice
level, example if the invoice amount is not fall in the given amount then system
could create clarification case and user/customer can validate the clarification
invoice move further process.