...
| Info | ||
|---|---|---|
| ||
For investigation purposes it is important to know the logic of the B-Number method. Click on the number plan on the Product Configuration GUI and then the Edit button. This will open the Edit Number Plan pop-up GUI where operators can see which method is configured for the number plan and read its description. |
The most common B-Number Methods are getRatingKey and getBNumber: they will use return the billing record's rating key and B-Number respectively.
Best Match
TODO
Example
In the screenshot below, the b-number method for the number plan Mobile National is getRatingKey. This means that the billing record's rating key in the will be used to find the plan element.
...
5
...
: Find the Plan Element
The rating process finds the plan element via 'Best Match' using the b-number method information. Once the plan element has been found, the rating process looks at the rate day information associated with that plan element. In order to look at the plan element, use the b-number method to select a plan element from the 'Plan Elements' panel.
For example, if the b-number is getRatingKey, then compare the value of the rating key with the available plan elements. In the screenshot below, 'MOBILE..Mobile national' is the plan element selected when looking at the rating key in the billing record (for example the rating key = MOBILE).
using the outcome of the B-Number method.
Best Match Algorithm
The algorithm is explained below.
Dot and double dot
When handling plan elements, there are a few important things to consider. In particular, sometimes the dot "." must to be used in order to have a proper plan element tree configuration. The lack of usage of this character will make the rating failNot always the plan element found by the best match algorithm is the one that points to the charges. The plan elements tree can be used to group several elements under one parent, which points to the charges that are valid for all its children.
| Info |
|---|
If a plan element is named by using a dot , ''.'' then that plan element is defined as the price holder of the charges on behalf of all its sub elements. |
In the example above,the price is defined in the element below the charges are defined by the element Group 1. The elements below children of Group 1 do do not point to a charge item; the parent defines the price. Remember that if double dot ''..'' is not put in the beginning of the children, then they will not call the parent ''.'' for accessing the charge item, hence the rating would fail. Since the parent Group 1 is defining the charge item so it is being edited to use ''.'' in the beginning and not the double dot ''..''.
Step 6 - Check the Rate Days
Now the rating process looks at the configured rate days. The rating process will compare the event/charge date present within the billing record with the charges.
6: Rate Day
The process loads the relevant rate day attached to the plan element. The billing record's event date is used against the start and end dates listed configured in the 'Rate Day' configuration.In order to look at the 'Rate Day' configuration, select the relevant plan element and then have a look at the 'Rate Day' panel. Please note that the charge/event date should be equal to or should lie between the configured dates. In the screenshot it can be seen that the rate day is 'N-SINGLE' and rate day itself.
Example
| Info | ||
|---|---|---|
| ||
In the Product Configuration GUI, click on a plan element and the GUI will automatically display the corresponding rate days in the Rate Day frame below the plan elements tree. |
In the screenshot below, the rate day assigned to then MOBILE plan element is N-SINGLE and has an open start and end date.
...
7
...
: Day
...
Charge
After the rating process has found the rate day, it looks at the day charges. It again compares the charge/event data present in the billing record with the configured day charges.
...