Data Dictionary
>
FPSAPP Views
> FPSAPP.WIP_WAFER_HIST_LOOP
View FPSAPP.DASH_E_REMOVE_OVR_SORT_ORDER
In 6.15 we moved sort_order from DASH_C_CATEGORY_TABLE_COLS to DASH_C_COLUMNS to standardize the column order across all tables. We kept ovr_sort_order in DASH_C_C_T_C for all tables where the standard order of displayed columns would be different from the current order. This view shows any tables where the ovr_sort_order does not change the order of displayed columns from what it would be if we cleared ovr_sort_order and used the standard sort_order. If any records exist in this view, we recommend clearing them: update dash_c_category_table_cols set ovr_sort_order = null where ovr_sort_order is not null and (facility, web_version, category, table_id) in (select distinct facility, web_version, category, table_id from dash_e_remove_ovr_sort_order);
|
Column |
Comment |
|---|---|
|
NUM_NOT_MATCHED |
|
|
RN_OVR |
|
|
RN_STD |
|
|
COLUMN_ID |
|
|
OVR_SORT_ORDER |
The default sort order of chambers within a tool is to put assist and virtual chambers last then sort by ch_type then ch_short_display. To override this sort order just populate this optional column. If this is set for some chambers but not all on the tool then chambers where this is blank will be last sorted by the default order. (* inherited from FPSINPUT.EQP_CHAMBERS) |
|
SORT_ORDER |
This is used to sort within the grouping. SORT_ORDER always has a deferrable unique key to ensure uniqueness while allowing the user to make changes without erroring until the commit is attempted. Because of this you must be careful to not violate the unique key otherwise you will lose all of your edits. (* inherited from FPSINPUT.GEN_FACILITIES) |
|
FACILITY |
Facility is included in almost every join in the DWH so this represents a definitive split. A route must have all steps on tools in the same facility. A tool must process all lots in the same facility. If your site has multiple buildings where lots run on routes using tools in multiple buildings then everything should be one facility. For example, multiple Fab buildings. But if your site has independent facilities like Fab and Test and Assembly where lot may progress from one to the next but on different routes then these should be different facilities. Since this column is in virtually every table it is critical that the value here is exactly matches what is in the MES if the MES has facility. Use facility_display for the display friendly name displayed in applications. See site_name comment for client/site/facility example. (* inherited from FPSINPUT.GEN_FACILITIES) |
|
WEB_VERSION |
|
|
CATEGORY |
|
|
TABLE_ID |