Data Dictionary
>
FPSINPUT Views
> FPSINPUT.WIP_WAFER_HIST_LOOP
View FPSAPP.DASH_E_SHOULD_DISPLAY_EXP
Most clients use the expanded view of each table to see what columns are available to be displayed on that table in the main page. To this end, we would generally like to show all of the available columns that make sense. The logic in this view suggests to show all columns except the following that we decided do not make sense although they are still technically available: * Shift columns on Day version * Day columns on Shift version * "Bar" columns if corresponding "Non-Bar" column is displayed * "Non-Bar" columns if corresponding "Bar" column is displayed * "Moves" columns since Completes and Oper Moves are preferred * "IO2 Oper Moves" columns since IO2 Completes are preferred * "Oper Mvins" columns since Mvins or Oper Moves are preferred
|
Column |
Comment |
|---|---|
|
SDE_IDEAL |
|
|
SHOULD_DISPLAY |
|
|
SHOULD_DISPLAY_EXP |
|
|
SHOULD_EXPORT |
|
|
WEB_VERSION |
|
|
COLUMN_ID |
|
|
CATEGORY |
|
|
TABLE_ID |
|
|
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) |
|
Q |