Data Dictionary
>
FPSBASE Views
> FPSBASE.WIP_WAFER_HIST_LOOP
View FPSAPP.CM_P_SCENARIO_INFO_COLS
This view will replicate CM_C_SCENARIO_INFO_COLS
|
Column |
Comment |
|---|---|
|
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) |
|
CM_SCENARIO |
This is the scenario to which the column should be added. Currently, the options are: STARTS, EQUIP, CALC for starts, equipment, and calculation scenarios respectively. (* inherited from FPSAPP.CM_C_SCENARIO_INFO_COLS) |
|
COLUMN_NAME |
Name of the column in DWH. Note: The column may exist in more than one table and/or schema. (* inherited from FPSINPUT.GEN_EXPLANATIONS) |