Account

This section describes support for converting the account object.

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.

Auto pay 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 Override1

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

Note: Note 1. Mailing Location and the Person / Account Override Addresses are only supported for legacy addresses. Refer to Address Support for more information.

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 taxpayer. Please see column notes for the account / person table for inter-field validation in respect of the various switches (e.g., if main taxpayer 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. Conversion for locations is no longer supported. However, the key generation program for Location (CIPVPRMK) must still be run. Refer to The Big Picture of Key Assignment for more information.