Data Dictionary
>
FPSAPP Views
> FPSAPP.WIP_WAFER_HIST_LOOP
View FPSBASE.CAL_SHIFT_CURR_AND_LAST
Get two lines of information for current and last shifts. Distinct is to attempt to force database to run this first when executing. Using (END_SHIFT - START_SHIFT) allows this view to work for any length shift.
|
Column |
Comment |
|---|---|
|
SHIFT |
Name of shift must be unique and can be in any format as long as it is display friendly since this is what we show everywhere. We prefer that other tables should reference start_shift rather than shift in case we want to change the naming convention for the shift. (* inherited from FPSINPUT.CAL_SHIFTS) |
|
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) |
|
END_SHIFT |
End of shift must be equal to the start of the next shift. Please note that the exact time which is both of the end of the previous shift and the start of the next shift is included in the next shift. In other words, start_shift <= inst < end_shift. (* inherited from FPSINPUT.CAL_SHIFTS) |
|
WORK_PERIOD |
|
|
WORK_GROUP |
Identifies the workforce on the shift so that we can compare performance of the different shifts. If the same people constantly work the same schedule this is the same as work_period. (* inherited from FPSINPUT.CAL_SHIFTS) |
|
SHIFT_INDEX |
0 represents the current shift. 1 is the next shift then 2 follows and so on. -1 is the previous shift and -2 is the shift before that and so on. This column is set automatically by trigger. (* inherited from FPSINPUT.CAL_SHIFTS) |
|
START_WORK_DAY |
Work days must be 24 hours in length and the start of the work day must be the start of one of the shifts. Contrast this to plan day which is independent of shift. (* inherited from FPSINPUT.CAL_WORK_DAYS) |
|
START_LAST_SHIFT |