5.11.2.4 Creating Unique Index on Load Table
This step is applicable for loading ledger data from Type I or Type II load table. A
unique index has to be created on each load table specifying the column alias for each
column within the load table. Column alias should match the column alias specified for
columns within LEDGER_STAT
table. LEDGER_STAT
load
procedure identifies the source columns that need to be loaded using the column aliases
and not by the physical column names. Column alias for LEDGER_STAT
columns are specified in the user-defined property (UDP) COLUMN_ALIAS within ERwin
model. Refer to ERwin model for getting the column alias for each of the
LEDGER_STAT
columns. Definition of the unique index is given
following:
CREATE UNIQUE INDEX &load_table_name ON &load_table_name ( ds, year_s,
accum_type, consolidat, isocrncycd, financ_id, org_id, gl_acct_id, cmn_coa_id,
prdct_id baltypecd, --------------------------------------------------------- --
Include all additional LEDGER_STAT primary key -- leaf columns here (use
PROPERTY_COLUMN from REV_COLUMN_PROPERTIES): –-----. . . -- )
The unique key of the load table must be identical to the unique key of LEDGER_STAT, with
the exception that instead of IDENTITY_CODE
, which is in LEDGER_STAT,
the load table has a column called DS (Data Source).