Account

Account Data Model

The following data model illustrates the account object.

Account Data Model

Account Table Names

*Data Model Name*	*Table Name*	*Generated Keys*	*Object Validation Batch Control*	*Referential Integrity Validation Batch Control*	*Key Assignment Batch Control*	*Insertion Batch Control*
Account	CI_ACCT	Yes CI_ACCT_K	VAL-ACCT		CIPVACCK	CIPVACCI See Optional FK Note below.
Bill Message	CI_ACCT_MSG	No. The key is account ID plus bill message code.		CIPVMSGV		CIPVMSGI
Autopay Option	CI_ACCT_APAY	Yes CI_ACCT_APAY_K		CIPVAAPV	CIPVAAPK Has dependencies	CIPVAAPI
Characteristic	CI_ACCT_CHAR	No. The key is ACCT_ID plus an edate and a char type.		CIPVACHV		CIPVACHI
Person/Account	CI_ACCT_PER	No. The key is account ID plus person ID.		CIPVACPV		CIPVACPI
Person / Account Char	CI_ACCT_PER_CHAR	No. The key is account ID plus person ID plus an edate and a char type.		CIPVAPCV		CIPVAPCI
Person/Account Address Override	CI_PER_ADDR_OVRD	No. The key is Account ID plus Person ID		CIPVPAOV		CIPVPAOI
Compliance Rating Transaction	CI_CR_RAT_HIST	Yes CI_CR_RAT_HIST_K		CIPVCRTV	CIPVCRRK Has dependencies	CIPVCRTI
ADM Trigger	CI_ADM_RVW_SCH	No. The key is account ID plus date		CIPVARSV		CIPVARSI

Account Suggestions

An account must have at least one row on the account / person table and at least one account / person must be marked as being the main customer. Please see column notes for the account / person table for inter-field validation in respect of the various switches (e.g., if main customer switch is on, then the person must also be financially responsible).

We recommend storing an ADM trigger (CI_ADM_RVW_SCH) for every account where the trigger date is the conversion date. This will cause the account to be reviewed by the overdue monitor when it next runs. We have supplied a dedicated batch process for this purpose that simply inserts a row in this table with the review date set equal to the current date. This will ensure that all converted accounts are reviewed after they are inserted into production. This program is named CIPVADMB and goes by the batch control ID of CNV-ADM.

If your legacy system has the equivalent of a compliance rating, you should create compliance rating transactions. The values you create need to be consistent with the base and threshold compliance rating on the installation record. Refer to the account user documentation for more information.

This maintenance object includes a character large object field that your organization may be using to capture implementation specific data as defined by your business objects. For records of this type, the process to insert the records to the staging table is responsible for populating the data in this CLOB as per the record's business object schema.

Optional FK Note

Account has an optional foreign key MAILING_PREM_ID to the Location (CI_PREM) table. If your implementation is planning to convert accounts, but not locations the key generation program for Location must still be run. Refer to The Big Picture of Key Assignment for more information.