| ACTIVE_IND |
NUMBER |
N |
The table row is active or inactive. A row is generally active unless it is in an inactive state such as logically deleted, combined away, pending purge, etc. |
| APPLY_WHERE_IND |
NUMBER |
Y |
Indicates if the where_clause will be performed during an ADS replicate. Should be set to 1 when: Extract_method in 'BYCONFIG','STATIC' |
| DATA_CLASS_TYPE |
VC2(30) |
Y |
Indicates the type of extract, values: ACTIVITY, ACTIVITY-MIXED, MIXED, REFERENCE, REFERENCE-MIXED |
| DM_ADS_EXTRACT_STG_ID |
NUMBER |
N |
Sequence based unique identifier for table. |
| DRIVER_KEYCOL_NAME |
VC2(30) |
Y |
There driver column name used to retrieve the sample keys. |
| DRIVER_RANKCOL_NAME |
VC2(30) |
Y |
The column by which columns should be ranked. Future use, in case the config_method of CURRENT is chosen and we want to rank on a column that is not the unique key for the table. (e.g. Get Current person_ids by highest updt_dt_tm vs. by highest person_id). |
| DRIVER_TABLE_IND |
NUMBER |
Y |
Indicates if the table is an Activity driver table. |
| DRIVER_TABLE_NAME |
VC2(30) |
Y |
The Ultimate driver parent table name for the extract. For activity data, it will be a table in this table where driver_table_ind =1. For reference data, this field will be null. For Activity extracts where the extract_method = ALL, the driver table may be also be blank (if increasing driver keys cannot impact the data for the extract). |
| DUPDEL_SKIP_IND |
NUMBER |
Y |
Dupe Delete. - Indicate where we may not want to perform a duplicate row cleanup for tables with multiple extracts. |
| EXPIMP_LEVEL_NBR |
NUMBER |
Y |
The logical order/level/priority in which the extract should be performed, such that any and all parent tables are extracted to ensure data is properly extracted. |
| EXPIMP_PARENT_TABLE_NAME |
VC2(30) |
Y |
The table's immediate parent table on which the extract is driven. |
| EXTRACT_METHOD |
VC2(30) |
Y |
Indicates the method of extraction during replicates:ALL: The entire table is moved. BYCONFIG: The table is moved by the clients specified configuration method and pct values (Clients will have METHODs of RECENT, EVERYNTH) and can specify how much activity data to move by pct (10%, 20% etc.). Typically, this means the where clause for this will reference the immediate parent table. EVERYNTHPCT: The table will sample every nth row based on the client's configuration pct. These are typicall |
| OWNER_NAME |
VC2(30) |
N |
Owner of the table being extracted |
| TABLE_COMMENT |
VC2(2000) |
Y |
Any information useful to describe / document how the extract is related to the Millennium data model. May be used by Cerner support organizations to better understand, use the data for clients. |
| TABLE_EXTRACT_INSTANCE_NBR |
NUMBER |
N |
Instance/Version of the extract for a table (in case we want to ship multiple versions that can be active). |
| TABLE_EXTRACT_NBR |
NUMBER |
N |
Extract number for a table |
| TABLE_NAME |
VC2(30) |
N |
Table being extracted |
| UPDT_APPLCTX |
NUMBER |
N |
The application context number from the record info block. |
| UPDT_CNT |
NUMBER |
N |
Set to 0 on insert. Incremented by 1 on update. Used to recognize update conflict where data in a row updated by one application is at risk of being lost by a second application attempting to update the row. |
| UPDT_DT_TM |
DATE |
N |
The date and time the row was last inserted or updated. |
| UPDT_ID |
NUMBER |
N |
The person_id of the person from the personnel table (prsnl) that caused the last insert or update of the row in the table. |
| UPDT_TASK |
NUMBER |
N |
The registered (assigned) task number for the process that inserted or updated the row. |
| WHERE_CLAUSE |
VC2(4000) |
Y |
The where_clause the extract will use to get the intended data, either for an activity based sample, referenced-mixed data,etc.. |
