Service Agreement Service Points File

The service agreement service points file includes fields related to the relationship between a customer's service point and service agreement. The data for this entity is expected to be sent in a separate file that follows a specific naming convention. See Account Data File Name Conventions for details.

If there are any changes to a service agreement's service point list, then Oracle Utilities Opower will attempt to merge them into a cohesive history. However, the sa_sp_start_date and sa_sp_end_date history must not overlap for a single service agreement and service point combination. If the same combination of service_agreement_id, service_point_id, and sa_sp_start_date is sent again, it is assumed to be a correction and will overwrite previously-imported values.

Field	Description
service_agreement_id	The unique identifier of a service agreement. Type: VARCHAR(40) Can Be Empty?: No. Primary Key.
service_point_id	The unique identifier of a service point on a service agreement. This relates to the `service_point_id` field in the Premise file. See Service Point Fields for more information. Type: VARCHAR(40) Can Be Empty?: No. Primary Key.
service_point_name	A user-friendly name for the service point. The purpose of this field is to make the service point name easier to understand when displayed in the user interface of an Oracle Utilities product. Type: VARCHAR(40) Can Be Empty?: Yes. Business Key.
usage_flag	A flag that indicates whether usage for this service point is additive or subtractive for the overall service agreement, or if the usage is informational only. Allowed Values: + (plus sign) Add the value for the overall usage of the service agreement. - (minus sign) Subtract the value from the overall usage of the service agreement. c Check. Check service points are ignored by billing. They may be used to track informational meters such as those that directly track solar generation for customers. This value can be uppercase (C) or lowercase (c). Note: Rows containing any values for this field other than plus (+), minus (-), or c will be rejected. Type: ENUM Can Be Empty?: No.
usage_percent	The percentage contribution to the total usage of the related service agreement. For example, a service agreement in a roommate arrangement may have one service point but is only contributing 50% of its usage to each of two different service agreements. This field defaults to 100 if no value is provided. Type: DECIMAL(3,0) Can Be Empty?: Yes.
sa_sp_start_datetime	The date on which the service agreement was associated with the service point. Type: DATETIME. See Date and Time Handling for details. Can Be Empty?: No. Primary Key.
sa_sp_end_datetime	The date on which the service agreement was disassociated from the service point. Type: DATETIME. See Date and Time Handling for details. Can Be Empty?: Yes.