Data Dictionary
>
FPSBASE Views
> FPSBASE.WIP_WAFER_HIST_LOOP
View FPSAPP.CTR_B_DIE_BANK
CTR logic adds a fake facility for Die Bank and this stores the values easier than a single row table since these are used in multiple views.
|
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) |
|
FACILITY_DISPLAY |
The name of the facility displayed on all dashboards and reports. Facility is a short field since it is used in every join so we allow a longer more descriptive name here although often this will be the same as the facility. (* inherited from FPSINPUT.GEN_FACILITIES) |
|
FACILITY_COLOR |
|
|
FACILITY_HTML_COLOR |
|
|
FACILITY_SORT_ORDER |