FPSINPUT.RTG_ACTIVE_PRD_ROUTES_BASE

FACILITY

VARCHAR2(6)

N

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. (* from FPSINPUT.GEN_FACILITIES)

PRD

VARCHAR2(64)

N

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. (* from FPSINPUT.RTG_PRDS)

PLANPRD

VARCHAR2(64)

N

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. (* from FPSINPUT.RTG_PLANPRDS)

ROUTE

VARCHAR2(256)

N

Route that has threading requirements (* from FPSINPUT.RTG_STEP_THREADING)

HAS_MOVES_WITHIN_THREE_DAYS

CHAR(1)

HAS_STARTS

CHAR(1)

IS_BEST_RECORD_FOR_PLANPRD

CHAR(1)

IS_MAIN_ROUTE

CHAR(1)

N

Y indicates the route is the main processing route for PRD. N indicates it is a rework or alternate route.

IS_TW_ONLY

CHAR(1)

N

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.

LAST_ACTIVITY_MORE_THAN_2D_AGO

DATE

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.

MODE_LOT_TYPE

VARCHAR2(24)

N

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.

NUM_LOTS_NOT_ON_HOLD

NUMBER(6)

PCT_STEPS_WITH_GOOD_CT_DATA

NUMBER(3)

REASON_WHY_ACTIVE

VARCHAR2(64)

N

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.