Data Dictionary
>
FPSINPUT Views
> FPSINPUT.WIP_WAFER_HIST_LOOP
View FPSBASE.CHK_REWORK_START_END
Checks the rework start and end behave properly regarding route, main_route, and next_route.
|
Column |
Comment |
|---|---|
|
LOT |
A lot is a group of units that process together. Usually lot_id or lot_number in MES. All units in a lot are in the same carrier but there may be multiple lots in a carrier. (* inherited from FPSINPUT.WIP_LOTS_STATIC) |
|
INST |
Time when the event occurred. (* inherited from FPSINPUT.WIP_EVENT_HIST) |
|
LOT_SEQ_WITHIN_SEC |
For rows with identical timestamps, sequence records to get proper sequence (* inherited from FPSINPUT.WIP_EVENT_HIST) |
|
EVENT |
This is the event registered in the MES. This is for the historical record and display only. Each event is mapped to an FPS event_type and the event_type is what is used by FPS applications. (* inherited from FPSINPUT.WIP_EVENTS) |
|
ROUTE |
Route that has threading requirements (* inherited from FPSINPUT.RTG_STEP_THREADING) |
|
NEXT_ROUTE |
Event moved the lot to this new route (* inherited from FPSINPUT.WIP_EVENT_HIST) |
|
MAIN_ROUTE |
Primary route used by the prd. Excludes rework and alternate routing. We allow this column to be null in WIP_LOTS_VERIFY because we may not be certain what the main route is when we fix for missed events. In that event we trust the WIP_EVENT_HIST triggers has loaded the correct information into WIP_EVENTS_CURR_STEP. (* inherited from FPSINPUT.WIP_EVENT_HIST) |
|
IS_REWORK |
Y indicates the lot is on a rework route after the event is logged. If a lot is reworked then returns to the main route and repeats some steps, is_rework will be N but we will count those steps as repeats. (* inherited from FPSINPUT.WIP_EVENT_HIST) |
|
IS_REWORK_START |
Event started rework (* inherited from FPSINPUT.WIP_EVENT_HIST) |
|
IS_REWORK_END |
Event ended rework (* inherited from FPSINPUT.WIP_EVENT_HIST) |