Service Agreement Rate Fields
effective_date is a new entry in the history. Having the same value
as a previously-sent effective_date is treated as a correction.
Note:
Although the fields below are described separately from the other fields in the Main Account Data File, they must be included in the same file as the other fields, with all columns included in every row. See Account Data File Specifications for more information.| Field | Description |
|---|---|
| sa_rate_code |
The rate used to calculate the service agreement’s bill segments. Multiple rows will only exist if the service agreement’s rate changes over time. Type: VARCHAR(40) Can Be Empty?: No. |
| effective_datetime |
The date the rate becomes effective. Type: DATETIME. See Date and Time Handling for details. Can Be Empty?: No. |
| service_agreement_rate_updated_at |
The date at which the record was updated in the source system. If left blank, the field does not store any data. Type: DATETIME. See Date and Time Handling for details. Can Be Empty?: Yes. |
Example Data
For example, consider the following sequence of files sent to Oracle Utilities Opower and the resulting operational state.
| File | service_agreement_id | other fields | sa_rate_code | effective_date | Result |
|---|---|---|---|---|---|
| 1 | 1234567890 | ... | ER-BASIC | 2018-01-01 00:00:00 | Inserted as first entry, effective from 2018-01-01 00:00:00 until the end of time. |
| 2 | 1234567890 | ... | ER-DMINU | 2018-05-01 00:00:00 | Inserted as second entry, effective from 2018-01-01 00:00:00 until the end of time. Previous entry now made to end as of 2018-04-30 23:59:59. |
| 3 | 1234567890 | ... | ER_BASIC | 2018-05-01 00:00:00 | Correction of
data in previous file #2, and sa_rate_code
updated.
|
| 4 | 1234567890 | ... | ERES1 | 2018-06-01 00:00:00 | Inserted as third entry, effective from 2018-01-06 00:00:00 until the end of time. Previous entry now made to end as of 2018-05-31 23:59:59. |