Data Dictionary
>
FPSAPP Views
> FPSAPP.WIP_WAFER_HIST_LOOP
View FPSBASE.CHK_WIP_END_SHIFT_HIST_LAST
This view validates data from last shift in WIP_END_SHIFT_HIST such that the endwip is the expected result given the activity during the shift. We expect that startwip + arrival - moves = endwip but we must adjust for create, terminate, split, merge, scrap, etc. The logic in this view is identical to CHK_WIP_END_SHIFT_HIST_REAL but this checks the table rather than the view.
|
Column |
Comment |
|---|---|
|
PROJ_QTY_DELTA |
|
|
PROJ_LOTS_DELTA |
|
|
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) |
|
STEP |
A single processing step within a route representing a single tool visit. Step is often a very complex string and should rarely be displayed. Instead we should use process_display. (* inherited from FPSINPUT.RTG_ROUTE_STEPS) |
|
ROUTE |
Route that has threading requirements (* inherited from FPSINPUT.RTG_STEP_THREADING) |
|
BANK |
Lots which are not on a route are considered in a bank and the bank name indicates why the lot is off route. Bank must be NA for lots which are on a route. Our standard filter for active lots is bank = NA. (* inherited from FPSINPUT.RTG_BANKS) |
|
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) |
|
QTY_STARTWIP |
|
|
QTY_ARRV_BEF_GPC |
|
|
QTY_ARRV_AFT_GPC |
|
|
QTY_COMP |
|
|
QTY_ISKIP |
|
|
QTY_DSKIP |
|
|
QTY_RT_OR_PRD |
|
|
QTY_DELTA_FOR_DTONLY |
|
|
QTY_ENDWIP |
|
|
PROJ_QTY_ENDWIP |
|
|
NUM_LOTS_STARTWIP |
|
|
NUM_LOTS_ARRV_BEF_GPC |
|
|
NUM_LOTS_ARRV_AFT_GPC |
|
|
NUM_LOTS_COMP |
|
|
NUM_LOTS_ISKIP |
|
|
NUM_LOTS_DSKIP |
|
|
NUM_LOTS_RT_OR_PRD |
|
|
NUM_LOTS_CREATED |
|
|
NUM_MERGES_TO |
|
|
NUM_MERGES_FROM |
|
|
NUM_SPLITS_TO |
|
|
NUM_SPLITS_FROM |
|
|
NUM_LOTS_FINAL_SHIP |
|
|
NUM_LOTS_SCRAP_FULL |
|
|
NUM_LOTS_ENDWIP |
|
|
PROJ_LOTS_ENDWIP |