Data Dictionary
>
FPSADMIN Views
> FPSADMIN.WIP_WAFER_HIST_LOOP
View FPSAPP.DASH_P_MNT_MODULES
View used to get list of mnt_module values for web pages. This is necessary because not all modules are mnt_modules. As of Jan 2022 this view is used in core only. In DWH 6.20.4/7.5.5 and higher we could change the core query to DASH_P_MODULES with the filter on is_mnt_module = Y and then drop this view. But admittedly it is not really hurting anything to have this as a separate view.
|
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) |
|
MNT_MODULE |
MNT_MODULE is the module responsible for maintaining the tool and is a property of MNT_FAMILY. See comments on the module column in GEN_MODULES for how it relates to eqp_module and mnt_module. (* inherited from FPSINPUT.EQP_MNT_FAMILIES) |
|
MNT_MODULE_DISPLAY |
|
|
MNT_MODULE_SORT_ORDER |