Data Dictionary
>
FPSAPP Views
> FPSAPP.WIP_WAFER_HIST_LOOP
View FPSBASE.CTM_REF_SUMMARY_P1_MEDIANS
This view feeds CTM_SUMMARY but it is independent and complicated enough to split into its own view for improved understanding, documentation, and testing. The complicated part of this is the logic for moves for lots which have either split or merged earlier in the step. Basically we want the original step_ent_inst of the units which are in the lot which moved out. If the lot was split then we want the step_ent_inst of the parent lot from which it was split. This is normally s2.step_ent_inst (h.step_ent_inst is the time of the split, sm.split_lot is the parent, s2.step_ent_inst is the step_ent_inst of the parent) but sometimes it is just sm.step_ent_inst. If the lot was merged, we want the latest of the step_ent_inst values for each of the two lots which were merged together (sm.step_ent_inst is the "to" lot which is moving out while m2.step_ent_inst is the "from" lot which no longer exists after the merge).
|
Column |
Comment |
|---|---|
|
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) |
|
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) |
|
ROUTE |
Route that has threading requirements (* inherited from FPSINPUT.RTG_STEP_THREADING) |
|
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) |
|
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) |
|
PRTY_CTM_GROUP |
This is one of the primary keys of our CTM tables. We use this group rather than the priority because we often have several different priorities which are close and are expected to have the same cycle time. (* inherited from FPSINPUT.WIP_PRIORITIES) |
|
LOT_GROUP |
Lot_group is a grouping of lot_family and is the highest grouping in the lot type hierarchy. There should be only a few values for lot_group, i.e. Prod, Dev, TW. We group WIP and moves by lot_group on the dashboard and we group cycle time calculations by lot_group so this is an important field. (* inherited from FPSINPUT.WIP_LOT_GROUPS) |
|
IS_NONSTD |
Our column to indicate non-standard processing at the step. For example, an experiment or a chain that is only active at a particular step or set of steps and then goes back to being normal for the route. If an experiment is severe enough that it affects the final product and has to be planned separately then it will be its own prd or planprd. (* inherited from FPSBASE.WIP_LOT_HIST) |
|
NUM_LOTS_7D_MED_NOT_ISKIP_R |
|
|
STEP_SEC_7D_MED_NOT_ISKIP_R |
|
|
AT_LEAST_ONE_HOLD_SEC_7D_MED_R |
|
|
AT_LEAST_ONE_HOLD_SEC_7D_AVG_R |
|
|
NUM_LOTS_AT_LEAST_ONE_HOLD_7D |
|
|
QTY_AT_LEAST_ONE_HOLD_7D |