Rate Tier Definitions File
For tiered rate plans, the rate tier definitions file provides the metadata used to configure the tiers for the plan. The data must be provided in a single file that follows a specific naming convention. See File Name Conventions for more information.
Note: This data is only required if you have a tiered rate plan. Your Delivery Team will create the file and work with you to gather the necessary inputs.
Column Name |
Description |
---|---|
rate_plan_identifier |
Unique rate plan for which the tier definition is applicable. This may be a wildcard (*) if the tier definition is applicable to all rate plans. Type: VARCHAR Can Be Empty?: No. |
rate_component |
The unique identifier of the rate component for which the tier definition is applicable. This may be a wildcard (*) if tier definition is applicable to all rate components in the specified rate plan. Type: VARCHAR Can Be Empty?: No. |
tier |
Tier number (for example, ‘1’). Type: INTEGER Can Be Empty?: No. |
lower_bound |
The lower bound of the tier. The lower bound is inclusive. The unit of measure should be the same as the associated service point’s unit of measure. Type: DECIMAL (12,6). See Supported Decimal Formats for details. Can Be Empty?: No. |
upper_bound |
The upper bound of the tier. The upper bound is exclusive. This may be NULL for the highest tier. The unit of measure should be the same as the associated service point’s unit of measure. Type: DECIMAL (12,6). See Supported Decimal Formats for details. Can Be Empty?: Yes. |
effective_start_date |
The date on which this tier configuration becomes effective. Type: DATE (YYYYMMDD) Can Be Empty?: No. |
effective_end_date |
Date on which this tier configuration is no longer effective. (This day is not part of the period covered by the rate tier definition.) Type: DATE (YYYYMMDD) Can Be Empty?: Yes. |
Rate Tier Sample Data
This example assumes the tier definitions are constant across all rate plans for this particular client.
rate_plan_identifier |
rate_component |
tier |
lower_bound |
upper_bound |
effective_start_date |
effective_end_date |
---|---|---|---|---|---|---|
* |
* |
1 |
0 |
100 |
20090101 |
|
* |
* |
2 |
100 |
130 |
20090101 |
|
* |
* |
3 |
130 |
200 |
20090101 |
|
* |
* |
4 |
200 |
300 |
20090101 |
|
* |
* |
5 |
300 |
|
20090101 |
|