Data Dictionary
>
FPSADMIN Views
> FPSADMIN.WIP_WAFER_HIST_LOOP
View FPSBASE.CHK_WIP_STEP_HIST_LAG
This view checks that all "from" properties of each event in WIP_EVENT_HIST and WIP_STEP_HIST match the "to" properties of the previous event for that lot. We do check this automatically to some degree in the WIP_EVENT_HIST_INSERT_BEF trigger and insert DIFF events in WIP_STEP_HIST to fix some differences real-time. Therefore this view ignores any discrepancies in WIP_EVENT_HIST where a DIFF event has been logged. Then we also ignore any MISS or DIFF events so this view is a comprehensive summary of any inconsistencies with WIP_EVENT_HIST logging and a great check for our ETL.
|
Column |
Comment |
|---|---|
|
PROBLEM |
|
|
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) |
|
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) |
|
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) |
|
IS_NEXT |
Indicates record goes into WIP_STEP_HIST (* inherited from FPSBASE.WIP_LOT_HIST) |
|
PREV_INST |
|
|
PREV_MOVE_TYPE |
|
|
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) |
|
STEP |
A single processing step within a route representing a single tool visit. Step is often a very complex string and should rarely be displayed. Instead we should use process_display. (* inherited from FPSINPUT.RTG_ROUTE_STEPS) |
|
ROUTE |
Route that has threading requirements (* inherited from FPSINPUT.RTG_STEP_THREADING) |
|
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) |
|
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) |
|
LOT_TYPE |
Lot_type is the base of the hierarchy that determines lot_family then lot_group. Ideally lot_type will come straight from the MES with little modification. (* inherited from FPSINPUT.WIP_LOT_TYPES) |
|
PLAN_PRIORITY |
Permanent priority of the lot set in the MES generally by planning. (* 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) |
|
PREV_QTY |
|
|
STEP_ENT_INST |
Time when the lot entered the step. (* inherited from FPSBASE.WIP_LOT_HIST) |
|
PREV_STEP_ENT |
|
|
PREV_NEXT_FACILITY |
|
|
PREV_NEXT_STEP |
|
|
PREV_NEXT_ROUTE |
|
|
PREV_NEXT_BANK |
|
|
PREV_NEXT_PRD |
|
|
PREV_NEXT_PLANPRD |
|
|
A_SORT |