Data Dictionary
>
FPSINPUT Views
> FPSINPUT.WIP_WAFER_HIST_LOOP
View FPSBASE.CHK_OPER_MOVES
Please refer to https://help.finalphasesystems.com/display/DW/Guide+to+Moves+Matching for a complete guide to Oper Moves Matching. This is a template of a view to use for moves matching. If your site populates WIP_OVR_OPER_MOVES_HIST then you can actually use this as is. But at most sites it will need to be adapted with some site specifics and saved a new view named FPSINPUT.LOAD_CHK_OPER_MOVES. This is fully described in the guide on the Help Site.
|
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) |
|
MES_OPER |
|
|
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) |
|
QTY |
Quantity of units in the lot according the qty_unit defined for the facility. It is required for all lots in each facility to have their qty defined in the same units therefore the change in the unit is critical to defining the facility. For example, a pretest facility might have a sort step in the middle where we learn the qty of die. Prior to this step we know only the wafer qty but after this step we know both wafer and die. Since wafer is the only qty we know throughput the flow then wafer must be defined as the qty unit for this facility. Die can then be populated as sec_qty when it is known. Similarly the wafer saw facility might have a step in the middle where we cut the wafers into die. After this step we no longer know the number of wafers which means that die must be the qty unit for this facility and wafers can be the sec_qty prior to the saw step. Please note that a lot with qty of 0 is allowed but only if the sec_qty is greater than 0. This is unusual but one case is where we know the wafers will be scrapped but cannot be scrapped quite yet. (* inherited from FPSINPUT.WIP_EVENT_HIST) |
|
IS_OPER_MOVE |
The critical Dashboard metric we call oper moves is moves according to the specific definition of the site, usually the moves calculation they used prior to installation of the FPS Dashboard. If Y then this step move meets the specific criteria for the site to be counted as an oper move. (* inherited from FPSBASE.WIP_STEP_HIST) |
|
IS_OPER_MOVE_VERIFY |
|
|
IS_SITE_MOVE |
|
|
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) |
|
MOVE_TYPE |
Move_type is populated with a value in WIP_MOVE_TYPES (COMP, ISKIP, etc.) for all records where is_next = Y. It is null when the qty changes but is_next = N and these "delta only" records will always have a delta_type. Note that it is possible and not unusual to have both move_type and delta_type when the lot both moves and changes qty with the same event. (* inherited from FPSBASE.WIP_STEP_HIST) |
|
WHY_NOT_OPER_MOVE_VERIFY |
|
|
WHY_NOT_OPER_MOVE |
|
|
WHY_NOT_SITE_MOVE |
|
|
IS_ALREADY_COMP_THIS_OPER |
|
|
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) |
|
NEXT_BANK |
Event moved the lot to this new bank (* inherited from FPSINPUT.WIP_EVENT_HIST) |
|
MES_NEXT_OPER |
|
|
FPS_NEXT_OPER |
|
|
NUM_FPS_MOVES_PER_SEC |