Account Fields

The account fields include data related to the account ID, name, setup, classification, and billing cycle of a customer's account.

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

account_id

The primary identifier of an account.

Type: VARCHAR(40)

Can Be Empty?: No. Primary key.

account_name

A user-friendly name for the account. The purpose of this field is to make the account name easier to understand when displayed in the user interface of an Oracle Utilities product.

Type: VARCHAR(40)

Can Be Empty?: Yes.

setup_datetime

The identified setup date for an account.

Type: DATETIME. See Date and Time Handling for details.

Can Be Empty?: No.

customer_class

The classification for the customer. Depending on what channels and products are enabled for your Oracle Utilities program, this field segments your customer population for different experiences on printed reports or on the web.

Allowed Values:

  • AGRICULTURAL
  • COMMERCIAL
  • INDUSTRIAL
  • RESIDENTIAL
  • SMB
  • OTHER

Type: VARCHAR(40)

Can Be Empty?: Yes. When empty, this defaults to RESIDENTIAL.

bill_cycle_code

Any unique alphanumeric string that specifies the time of month at which the meter read occurs. For Oracle Utilities products that include normative comparison features, this data is used to ensure customers are compared against other customers with recent usage reads. This field should designate the service points that are read at approximately the same time. Utilities typically have 21 distinct read cycles corresponding to the business days in a month.

Example Values: M01,M02

Type: VARCHAR(24)

Can Be Empty?: Yes, but preferred to not be empty.

bill_cycle_description

A description of the bill cycle.

Example Values:

  • Monthly bill cycle - day 1
  • Monthly bill cycle - day 2

Type: VARCHAR(255)

Can Be Empty?: Yes.

account_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.