Data Dictionary
>
FPSINPUT Views
> FPSINPUT.WIP_WAFER_HIST_LOOP
View FPSAPP.DASH_REF_P_GANTT_PRIORITY_LOTS
This view gets all of the information for the priority lot Gantt chart. This view is designed to be filtered for all priority lots using the is_in_prty_gantt index on WIP_STEP_FUTURE. This view is similar to DASH_P_GANTT_LOT_STEPS with two important distinctions. First DASH_P_GANTT_LOT_STEPS has a single lot filter where this view filters for all priority lots making this view far more sensitive for speed. Second this view uses WIP_STEP_HIST which results in a single history bar for each step as that is more appropriate for the priority lot Gantt history while the other view uses ECT_HIST to provide more detailed history. If we make changes to this view, we should review DASH_P_GANTT_LOT_STEPS to see if the same change is necessary.
|
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) |
|
IS_HIST |
|
|
IS_CURR |
Boolean flag where Y indicates this row is for the current main route or product. Same as flush_seq_num = 1. (* inherited from FPSBASE.WIP_FLUSH) |
|
IS_FUTURE |
This should be set to Y if the state does not apply immediately. Production runoff and alarms are two examples where we do not want to set this state in ETP until the tool misses the cascade and starts to lose productivity. (* inherited from FPSINPUT.EQP_L5_TRANSITION_STATES) |
|
PRD |
Prd determines the route which is used to process the lot in the facility and what tools, recipes, durables, etc. can be used at each step. Prd also determines the next facility for the lot when it finishes its route. For detailed information on prd vs. planprd see table comments in RTG_PLANPRDS. (* inherited from FPSINPUT.RTG_PRDS) |
|
PLANPRD |
Planning product used for all planning purposes. All lots with the same planprd are interchangeable to ship to the customer regardless of their prd, route, technology, wafer size, etc. For detailed information on prd vs. planprd see table comments in RTG_PLANPRDS. (* inherited from FPSINPUT.RTG_PLANPRDS) |
|
BUILDING |
Building is the top of our MHS hierarchy at each site. It is independent of facility which is at the top of our EQP/RTG hierarchy. It is possible for a building to include multiple facilities and for a facility to include multiple buildings but we do not even need to define these relationships because EQP_TOOLS determines this by the combination of the facility and bay columns (since bay points to building). (* inherited from FPSINPUT.MHS_BUILDINGS) |
|
OVERALL_LOT_SEQ_NUM |
|
|
IS_HOLD_CURR |
|
|
CURR_HOLD_NOTE |
|
|
ALLOWED_TOOL_LIST |
|
|
PLAN_PRIORITY |
Permanent priority of the lot set in the MES generally by planning. (* inherited from FPSINPUT.WIP_EVENT_HIST) |
|
PLAN_PRIORITY_DISPLAY |
|
|
PLAN_PRIORITY_SORT |
|
|
CURR_PRIORITY |
The priority at the current step. As the lot moves along the route after LAST_STEP_CURR_PRTY it will revert to PLAN_PRIORITY. For example, timelink or sendahead priority is only temporary. (* inherited from FPSINPUT.WIP_LOTS_STATIC) |
|
CURR_PRIORITY_DISPLAY |
|
|
CURR_PRIORITY_SORT |
|
|
AS |