When we create the Charge Object, two main Nodes are created automatically. The top node is called the Charging Plan and it has a subnode called Default Charging.
On the tree structure, click the ‘Charging Plan’ Node.
Add a Charging Reference Name of type Postpaid called ‘Default’ to the Internal Reference Dictionary.
Then, under the Default Charging branch, add an Internal Reference component called ‘Default Reference’, using the ‘Default’ reference you have just created.
Right Click on the ‘Default Charging’->Add Component->References->Internal Reference
Give the name as ‘Default Reference’. Under the Internal Reference Drop Down List (DDL), choose ‘Default’. This value comes from the Internal Reference Dictionary at the Charging Plan definition.
Let’s map the configuration that we have done above with our telco example.
Let’s say you only have one postpaid mobile plan with the carrier operator. The account number is 138888. At the Charging Plan, instead of adding the ‘Default’ in the Internal Reference Dictionary, you enter 138888 with the type Postpaid.
Under the Default Reference node (subnode of the Default Charging), you will see the account number 138888 value under the DDL.
This account number will then be supplied to the billing processes for invoicing.
So there you have it. Charge Plan is responsible for determining the account to be charged.
Now save the Charge.
Select File->Save->In the Database
Choose the owner T01 and the Catalog T01. Click Save.
The diagram below shows the objects that have been created thus far.
Charging Plan in Detail:
It determines the account to be charged and also holds the information such as postpaid and prepaid account type.
When you create a new Charge, the Charging Plan and Price Plan will be created automatically. Additionally, the Default Charging node is also created under the Charging Plan node in the Decision Tree.
However, apart from the Default Charging component, there are 3 more components that can be attached to the Charging Plan.
This component is triggered when its chargeable item class name is the same as the usage event triggered in the Price Plan.
This component has no properties.
It is triggered by all recurring events contained within the Price Plan.
Only one recurring charging is available per charging plan.
This component has no properties.
It will be triggered by all one-shot events contained in the Price Plan.
Only one one-shot charging is available per charging plan.
This component is triggered when the chargeable event does not correspond to any root component.
It represents either Prepaid or External Account.
Only internal references can be mapped at charging mapping level.
Internal References must be defined with a Type (Postpaid or Prepaid) in the Internal Reference Dictionary (in the Charging Plan Definition)
When a customer creates a contract values for the charging references must be supplied for billing
For our tutorial scenario, see the diagram below. Familiarize yourself with the flow of the data and how they are linked and where they come from. In this example, when the number dialed starts with the prefix +33, the company account will be charged. If the number is dialed using other prefixes, the employee account will be charged. Note that Functions and Splitters component are not allowed! But you are free to use the Prefix Switching component or the Translation Table Operator etc.
Now let’s get started.
In the menu bar, select Window->View Catalogs. Select catalog ‘[T01]’.
Right click on the charge ‘[T01] Mobile Usage Charge’ and select ‘Open as Copy’
Rename the charge to ‘[T01] Business Mobile Usage Charge’.
Click on the Charging Plan. Add references for ‘Company’ and ‘Employee’.
Add a new Usage Charging plan. Set the Chargeable Item Class to ‘[T01] Call’. Name it ‘Call Charging’.
Add a new Prefix Switching comparator called ‘Check if call is local.’ Set the prefix to +33.
Add an Internal Reference for the Company account when the dialed number starts with ‘+33’ and to the Employee account for other cases.
Verify and save the Charge in the Database.
Charging Plan Summary:
- Charging represents the process to identify a unique entity to charge for the use of a service.
- This entity is usually called an account, however at this level, we can only talk about a “Charging Reference”.
- The account to be charged is not yet identified and charging plan only leads to a charge reference.
- A Charging Reference must be mapped to an account at the Provider Contract level.
Speaking about Provider Contract, in the next chapter, let’s look at how Customer Master Data is maintained in SAP CC.