Rate Prices File

In order to properly apply prices for cost calculation, Oracle Utilities must receive the prices to charge for each rate attribute, period, and charge. Typically this file is provided once during setup of a new plan and on a periodic basis when prices for existing rate plans change (typically 2-4 times a year). For real time pricing plans, this file should be provided daily as soon as prices become available. This data is required and must be provided in a single file that follows a specific naming convention. See File Name Conventions for more information.

Column Name	Description
rate_plan_identifier	A unique rate plan for which the price is applicable. This may be a wildcard () if the price is applicable to all rate plans. Type: VARCHAR Can Be Empty?*: No.
rate_component	The unique identifier of the rate component for which the price is applicable. This may be a wildcard () if the price is applicable to all rate components in the specified rate plan. Type: VARCHAR Can Be Empty?*: No.
rate_group	Applicable for rates that have different prices for different customer groups. Type: VARCHAR Can Be Empty?: Yes.
season	The season for which the prices are applicable. This is required for seasonal rates. Type: ENUM Allowed Values: WINTER SPRING SUMMER FALL Can Be Empty?: Yes.
period	The period for which the prices are applicable. This is required for TOU, TOU-tiered, and PDP components. Type: ENUM Allowed Values: ON_PEAK PART_PEAK OFF_PEAK CRITICAL_PEAK NON_CRITICAL_PEAK Can Be Empty?: Yes.
price_type	The type of price. CHARGE means something that is taken away from the customer (when positive, the usual case). CREDIT means something that is given back (when negative, the usual case). Type: ENUM Allowed Values: CHARGE CREDIT Can Be Empty?: No.
tier	The tier for which the price(s) are applicable. This is required for tiered and TOU-tiered rates. Type: INTEGER Can Be Empty?: Yes.
start_time	The start time of the applicable price in military time (for example, 0800, 1700). Valid values for hourly prices are 0000 to 2300. Do not specify a timezone. The local timezone of the utility is assumed. Type: TIME (HHMM) Can Be Empty?: Yes.
price	Price to be applied. The prices should always be provided in dollars, not cents. Credits must be preceded by a minus sign (-) to indicate a negative value. Type: DECIMAL (12,6). See Supported Decimal Formats for details. Can Be Empty?: No.
effective_start_date	The date on which this specified price becomes effective. Type: DATE (YYYYMMDD) Can Be Empty?: Yes.
effective_end_date	Date on which the specified price is no longer effective. (This day is not part of the period covered by the specified price.) A NULL date means the end date is yet unknown and the price is effective indefinitely until an end date is provided. Type: DATE (YYYYMMDD) Can Be Empty?: Yes.