Data Dictionary
>
FPSBASE Views
> FPSBASE.WIP_WAFER_HIST_LOOP
View FPSAPP.DASH_P_SPLIT_MERGE_HIST
This view is an wrapper on FPSBASE.WIP_SPLIT_MERGE_HIST and it is critical that this view be used with a filter on this_lot like this: select * from dash_p_split_merge_hist where this_lot = 'LOT1' order by inst desc;
|
Column |
Comment |
|---|---|
|
RELATED_REASON |
|
|
THIS_LOT |
|
|
FINISHED_LOT |
|
|
INST |
Time when the event occurred. (* 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) |
|
NEXT_FACILITY |
Event moved the lot to this new facility (* inherited from FPSINPUT.WIP_EVENT_HIST) |
|
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) |
|
NEXT_PRD |
Event moved the lot to this new prd (* inherited from FPSINPUT.WIP_EVENT_HIST) |
|
ROUTE |
Route that has threading requirements (* inherited from FPSINPUT.RTG_STEP_THREADING) |
|
START_INST |
Time when the lot started. (* inherited from FPSINPUT.WIP_STARTS) |
|
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_AFTER |
|
|
SPLIT_FROM_LOT |
|
|
SPLIT_FROM_LOT2 |
|
|
MERGE_TO_LOT_ON_FINISH |
|
|
FIRST_BANK |
|
|
SECOND_BANK |