Data Dictionary
>
FPSBASE Views
> FPSBASE.WIP_WAFER_HIST_LOOP
View FPSBASE.WIP_OPER_MOVE_HIST
A convenient view used for oper moves debugging which shows all moves for all lots with the all of the columns necessary to show if each move was counted as an oper move. It also limits the columns and sorts in a logical order. Remember the logic is to check for any reason why the lot should NOT be counted as an oper move then if we find no reason we count it. By default this view shows the previous shift although it can be easily copied then edited to filter on any range. Sample queries: select * from wip_oper_move_hist where lot = 'LOT1'; select * from wip_oper_move_hist where (prd = 'PRD1' or route = 'Sailboat'); Also we did not make a separate view but you can query WIP_END_SHIFT_HIST or WIP_PLAN_DAY_HIST and see oper moves like this: select start_shift, end_shift, route, process, bank, qty_comp, qty_oper_moves, operation from fpsbase.wip_end_shift_hist where (prd = 'PRD1' or route = 'Sailboat') and start_shift > sysdate - 1 order by route, step;
|
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) |
|
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) |
|
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) |
|
WHY_NOT_OPER_MOVE |
|
|
PROCESS |
Process defines what occurs at a step. Different steps can share the same process if they are identical. Process should normally determine allowed tools and recipe although it can be overridden by step, route, prd, lot, and experiment for exceptions. Each process is dynamically assigned to one or more eqp_type-process_family combinations with use_pct. One process_family is determined to be primary. If grouping is done correctly, a process should only be one eqp_group with no crossover. (* inherited from FPSINPUT.RTG_PROCESSES) |
|
OPERATION |
Operation is usually the primary level of routing in the MES and the level where the facility typically reports moves. FPS only allows one tool per step so our step is a lower level of routing than operation although both may be the same if the MES only allows one tool per operation. Note that because operation can include multiple steps and therefore multiple process families that we cannot have any association to equipment by operation. (* inherited from FPSINPUT.RTG_OPERATIONS) |
|
NEXT_OPERATION |
Operation of the next_step used primarily to determine is_oper_move. Populated by trigger. (* inherited from FPSBASE.WIP_LOT_HIST) |
|
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) |
|
IS_REWORK_START |
Event started rework (* inherited from FPSINPUT.WIP_EVENT_HIST) |
|
IS_REWORK_END |
Event ended rework (* inherited from FPSINPUT.WIP_EVENT_HIST) |
|
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) |
|
QTY_DELTA |
Difference in number of wafers due to an event that changes lot quantity (* inherited from FPSINPUT.WIP_EVENT_HIST) |
|
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) |
|
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) |
|
ROUTE |
Route that has threading requirements (* inherited from FPSINPUT.RTG_STEP_THREADING) |