allows you to create new properties that can be used in the price plan, the charging plan, the refill logic, or the allowance logic.|
Important: You cannot redefine a translation table at charge plan, refill plan, or allowance plan levels if your global charging services are based on provider contracts. We recommend that you use mapping tables and subscriber mapping tables. |
A translation table allows you to create new properties that can be used in the price plan, the charging plan, the refill logic, or the allowance logic.
A translation table is an n-dimensional table that consists of:
A set of input columns (I1, I2, I3,..., I(i)) with i less than or equal to 5
A set of output columns (O1, O2, O3,..., O(o)) with o less than or equal to 15
A set of rows
Each row of the table consists of a set of values of input columns (I1, I2, I3,..., I(i)) to which corresponds a set of values of output columns (O1, O2, O3,..., O(o)).
After you have created a translation table, you can then add it to the price plan, the charging plan, the refill logic, or the allowance logic. You can use the same translation table more than once in any price plan, charging plan, or refill logic.
Example
The rate per minute for the U.S. during weekdays (out of holidays) depends on the destination. To calculate the consumption price in US dollars, you create a table with the following inputs and outputs: Destination number (input), Price per minute (output) and Connection fee (output). The following translation table determines the related price per minute and connection fee for a specified destination number:
You can modify and save different versions of a translation table.
|
Note: Read the note about the order of the rows in a translation table. |