Holidays and Seasons File

Many pricing plans have pricing associated with holidays and seasons. For example, in some TOU plans, all weekends and holidays may be considered “off peak.” Additionally, in many rate plans, prices vary between summer and winter. The purpose of this file is to provide holiday and/or season information to Oracle Utilities. The data 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	The unique rate plan for which the event is applicable. This may be a wildcard () if the event is applicable to all rate plans. Type: VARCHAR Can Be Empty?*: No.
rate_component	The unique identifier of the rate component for which the event is applicable (for example, "CPP"). This may be a wildcard () if the event is applicable to all rate components in the specified rate plan. Type: VARCHAR Can Be Empty?*: No.
season	The applicable season. This is not applicable for holiday definitions. Only include this if sending season information. Type: ENUM Allowed Values: WINTER SPRING SUMMER FALL Can Be Empty?: Yes.
day_type	The type of day. This is used to define the holiday. This is not applicable for season definitions. Type: ENUM Allowed Values: WEEKEND WEEKDAY HOLIDAY Can Be Empty?: No.
period	The period being defined. This is not applicable for holiday definitions. Type: ENUM Allowed Values: ON_PEAK PART_PEAK OFF_PEAK CRITICAL_PEAK NON_CRITICAL_PEAK Can Be Empty?: Yes.
ordinal	Allows for distinguishing events with same season, day_type, and period. This is not applicable for holiday definitions. Type: INTEGER (1-10) Can Be Empty?: Yes.
resolution	Used in combination with the `duration` to indicate the length of time covered by the event. The value should be ‘DAY’ for holiday definitions. Type: ENUM Allowed Values: QUARTER_HOUR HALF_HOUR HOUR DAY BILLING MONTH YEAR Can Be Empty?: No.
duration	Used in combination with the `resolution` to indicate the length of time covered by the event. The value should be 1 for holiday definitions. Type: INTEGER Can Be Empty?: No.
start_date	The start date of the season. This is not applicable for holiday definitions. Type: DATE (MMDD) Can Be Empty?: Yes.
start_time	Start time of the event in military time. The value should be 0000 for holiday definitions. Do not specify a timezone. The local timezone of the utility is assumed. Type: TIME (HHMM) Can Be Empty?: No.
event_date	The date of the holiday. This is not applicable for seasons. Type: DATE (YYYYMMDD) Can Be Empty?: Yes.
effective_start_date	Not applicable for holiday definitions. Type: DATE (YYYYMMDD) Can Be Empty?: Yes.
effective_end_date	Not applicable for holiday definitions. Type: DATE (YYYYMMDD) Can Be Empty?: Yes.