...
These are the activities performed after a CDR is loaded into a billing record and mediated.
| Drawio | ||||
|---|---|---|---|---|
|
1: Billing Record Information
...
The algorithm is explained below.
| Drawio | ||||
|---|---|---|---|---|
|
Dot (".") as Plan Element Name
...
- The subscriber must be assigned to an active campaign.
- The campaign must have one bundle mapped to the very same plan element (or one of its ancestors) used during the standard prices rating.
| Drawio | ||||
|---|---|---|---|---|
|
In that case the bundle's rating logic is involved:
...
- After loading and mediation the billing record goes through the rating according to the standard prices.
- If a valid campaign is detected, then the bundle's logic is involved. Otherwise the invoice detail line is saved on the database and process is finished.
- The bundle will assign temporary rating code and rating key values to the billing record.
- The billing record goes through the very same standard rating process it has just left. This time, different rating code and rating key values will make it hit (possibly) a different rate plan, number plan and plan element. This will lead to the creation of a new invoice detail line.
| Drawio | ||||
|---|---|---|---|---|
|
| Warning |
|---|
Since the billing record essentially passes through the standard rating process at least twice, it is even more important to understand how the standard product configuration and the Restrict Active framework work. Remember that the new set of rating code and rating key are not persistent; therefore it is up to the operator to find out which campaign/bundle was involved and what happened during the on-the-fly mediation. |
...