FPSADMIN.DASH_P_RTG_ROUTES

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)

ROUTE

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

DESCRIPTION

Tool desciption. This value is only used to display in the Dashboard. (* inherited from FPSINPUT.EQP_TOOLS)

ROUTE_FAMILY

Route_family indicates that all routes within the family have similar or even identical steps and have the same segments. At facilities where various prds share the same route it is likely that the route will be the route_family. This is sometimes referred to as the main process flow. It is used on Segment Summary and Line Viewer to group similar routes. (* inherited from FPSINPUT.RTG_ROUTE_FAMILIES)

ROUTE_GROUP

Route_group is the parent of route_family. Route_group is used on the Dashboard and other applications as a large grouping for filtering. At many sites this is referred to as technology. (* inherited from FPSINPUT.RTG_ROUTE_GROUPS)

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)

TW_USE_MODULE

Applicable to TW routes only. This is the module that owns the use of the test wafer for process characterization. (* inherited from FPSINPUT.RTG_ROUTES)

TW_USE_MIN_QTY

Applicable to TW routes only. This is the minimum quantity of test wafers on this route which should be available for use. (* inherited from FPSINPUT.RTG_ROUTES)

TW_USE_MAX_QTY

Applicable to TW routes only. This is the maximum quantity of test wafers on this route which should be available for use. (* inherited from FPSINPUT.RTG_ROUTES)

TW_TOTAL_MIN_QTY

Applicable to TW routes only. This is the minimum quantity of test wafers on this route which should be available for use OR in the process of being built. (* inherited from FPSINPUT.RTG_ROUTES)

TW_TOTAL_MAX_QTY

Applicable to TW routes only. This is the maximum quantity of test wafers on this route which should be available for use OR in the process of being built. (* inherited from FPSINPUT.RTG_ROUTES)

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)

BG_COLOR

Background color assigned. BG_COLOR is in English like red or blue or light green and we look up the HTML color like #FF0000 in the GEN_COLORS table. BG_COLOR must be set manually but the FPSADMIN view BLD_POPULATE_COLORS will generate queries to randomly set bg_color for all values in a table. (* inherited from FPSINPUT.GEN_CUSTOMERS)