Data Dictionary
>
FPSAPP Views
> FPSAPP.WIP_WAFER_HIST_LOOP
View FPSBASE.RTG_REF_ACTIVE_PRD_ROUTES_BASE
This view determines all of the (FACILITY, PRD, PLANPRD, ROUTE) tuples that should be considered active in their own right. From highest to lowest priority, the reasons that a particular tuple should be considered active are: * moves within last 3 days * active lots in WIP_LOTS_VERIFY or WIP_LOTS_REALTIME * off-main-route lots in WIP_LOTS_REALTIME * starts planned * demand for this PLANPRD * relevant for multi-facility sites where we only have starts for first facility. * will only add records for a single PRD with a corresponding DEFAULT_PLANPRD * will only add records if this (FACILITY, PLANPRD) is not active for any other reason * the same (FACILITY, PRD, PLANPRD, ROUTE) has been active recently * the REF-view recursively looks at the contents of table generated from it * these rows are removed from the output after GEN_FACILITIES.DAYS_TO_KEEP_PRD_ACTIVE days * CM scenario exists * force keep-active (FPSINPUT.RTG_PRDS.KEEP_ACTIVE='Y') Where there are multiple reasons to consider a tuple active, this view outputs only the highest priority reason. The view RTG_ACTIVE_PRD_ROUTES expands on this one by also including tuples which are in the flush-forward path of a tuple considered active according to this view.
|
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) |
|
REASON_WHY_ACTIVE |
This shows the highest-priority reason which this PRD/ROUTE is considered active. See RTG_REF_ACTIVE_PRD_ROUTES_BASE for the list and ordering of possible reasons. (* inherited from FPSBASE.RTG_ACTIVE_PRD_ROUTES_BASE) |
|
IS_TW_ONLY |
IS_TW_ONLY indicates that a PRD or ROUTE has only test wafer lots. This flag is slightly different than IS_TW, which is associated with lots via their LOT_GROUP. Some PRDS/ROUTEs are mixed and this is set to N if there are any non-TW lots. (* inherited from FPSBASE.RTG_ACTIVE_PRD_ROUTES_BASE) |
|
MODE_LOT_TYPE |
Most frequently used lot type for the ROUTE. This is used as a default lot type for starts of this PRD if the lot type is not specified in the starts plan. (* inherited from FPSBASE.RTG_ACTIVE_PRD_ROUTES_BASE) |
|
LAST_ACTIVITY_MORE_THAN_2D_AGO |
For frequently used PRDs and ROUTEs we do not want to keep updating the last activity time on every update. But we need to store the last activity time for PRD/ROUTEs which have no recent activity as we will delete them after GEN_FACILITIES.DAYS_TO_KEEP_PRD_ACTIVE days. To achieve these objectives, we only populate this field if the last activity was more than 2 days ago and then we clear it when the lot has new activity. (* inherited from FPSBASE.RTG_ACTIVE_PRD_ROUTES_BASE) |
|
IS_MAIN_ROUTE |
Y indicates the route is the main processing route for PRD. N indicates it is a rework or alternate route. (* inherited from FPSBASE.RTG_ACTIVE_PRD_ROUTES_BASE) |
|
IS_BEST_RECORD_FOR_PLANPRD |
|
|
HAS_MOVES_WITHIN_THREE_DAYS |
|
|
HAS_STARTS |
|
|
NUM_LOTS_NOT_ON_HOLD |
|
|
PCT_STEPS_WITH_GOOD_CT_DATA |