Data Dictionary
>
FPSINPUT Views
> FPSINPUT.WIP_WAFER_HIST_LOOP
View FPSBASE.CHK_SHIFT_MOVES
Useful query to compare moves by shift to the raw data in WIP_STEP_HIST. This view should be used as a base for modification when shift moves do not match between different versions of DWH and/or Dashboard to see what is the root cause of the discrepancy. Once you prove that the numbers from the Dashboard and the numbers from the DASH query and the numbers from the WIP_STEP_HIST_PLUS query match then you can drill down into the WIP_STEP_HIST_PLUS query by grouping by more columns like event_type or prd or whatever. Frequently it is helpful to union this query to another copy of this query with all tables pointing to the other DWH via link.
|
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) |
|
START_SHIFT |
Shifts can be of any length and it is important that all queries get the shift length based on start_shift and end_shift rather than assuming a set number of hours. (* inherited from FPSINPUT.CAL_SHIFTS) |
|
QTY_MOVED |
|
|
QTY_COMP |
|
|
QTY_ISKIP |
|
|
QTY_DSKIP |
|
|
QTY_REPEAT |