FPSADMIN.RTG_ROUTES_PLUS

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)

ROUTE

VARCHAR2(256)

N

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

ACTIVE_VERSION

VARCHAR2(12)

The most recent version of the route. (* from FPSINPUT.RTG_ROUTES)

BG_COLOR

VARCHAR2(24)

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

CONSIDER_IN_BANK

CHAR(1)

N

Some sites want lots which are on certain routes and/or on hold with certain hold types to count as in bank rather than in active WIP. This flag tells WIP_LOTS_PLUS for route or hold_type to consider in bank. Please note this does not affect WIP_EVENT_HIST nor WIP_STEP_HIST but only the current WIP. (* from FPSINPUT.RTG_ROUTES)

DESCRIPTION

VARCHAR2(256)

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

FIRST_STEP

VARCHAR2(256)

HIDE_LOTS_IN_DASH

CHAR(1)

N

This flag is similar to CONSIDER_IN_BANK but even more extreme. This flag will completely hide all lots and moves on this route from the Dashboard. Honestly we discourage anyone from using this flag (and strongly discourage it for anything but test wafers) but it is here at least for Dashboard only if a particular site really wants it. (* from FPSINPUT.RTG_ROUTES)

INCLUDE_IN_CTA_IF_NOT_MAIN

CHAR(1)

N

By default, we only include the main route for each prd in Cycle Time Analyzer. If we want to include alternate main routes in CTA then we can set this flag. Note that these must be full alternate routes for the prd and not rework routes nor short loop routes as those are not added properly to the overall calculation. (* from FPSINPUT.RTG_ROUTES)

IS_EXCLUDED_LINE_BALANCE

CHAR(1)

Lots on hold are excluded from line balance calculations if this flag for the hold type is set to Y. By default this is N which means that lots on hold of this type are included in line balance calculations. (* from FPSINPUT.WIP_HOLD_TYPES)

IS_MAIN_ROUTE

CHAR(1)

Y indicates the route is the main processing route for PRD. N indicates it is a rework or alternate route. (* from FPSBASE.RTG_ACTIVE_PRD_ROUTES_BASE)

IS_OVR_START_STEP

CHAR(1)

IS_TW_ONLY

CHAR(1)

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. (* from FPSBASE.RTG_ACTIVE_PRD_ROUTES_BASE)

MODE_LOT_TYPE

VARCHAR2(24)

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. (* from FPSBASE.RTG_ACTIVE_PRD_ROUTES_BASE)

NUM_PHOTO_LAYERS

NUMBER(3)

NUM_PROCESS_STEPS

NUMBER(5)

NUM_STEPS

NUMBER(5)

OPERATION_OF_START_STEP

VARCHAR2(50)

OVR_EVENT_TYPE_AT_START_STEP

VARCHAR2(12)

This value specifies what event at the OVR_START_STEP_IF_NOT_FIRST step is the official start inst of the lot. The options here are BEGIN, END, COMP, or DISPATCH. If you configure BEGIN, then it will use the beg_proc_ordered_not_null time from wip_step_hist for first step on the lots route. END will use the end_proc_ordered_not_null time, COMP will use the inst value, and DISPATCH will use the dispatch_ordered_not_null value. If this value is left null, then it will use the step_ent_inst. (* from FPSINPUT.RTG_ROUTES)

ROUTE_FAMILY

VARCHAR2(36)

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

ROUTE_FAMILY_SCORE

NUMBER(2)

Scheduler Evaluation slider value for route family priority slider (* from FPSINPUT.RTG_ROUTE_FAMILIES)

ROUTE_GROUP

VARCHAR2(36)

N

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

ROUTE_MSO_GROUP

VARCHAR2(64)

N

Route group to be used for the Metrology Sampling Optimizer, generally based on similarity of technology or volume. (* from FPSINPUT.RTG_ROUTES)

ROUTE_SCORE

NUMBER(2)

Scheduler Evaluation slider value for route priority slider (* from FPSINPUT.RTG_ROUTES)

SEQ_NUM_OF_START_STEP

NUMBER(7,2)

START_STEP

VARCHAR2(256)

Start step that will impact the future thread step rank in RTG_TOOL_ASSIGNMENT_LOT (* from FPSINPUT.RTG_STEP_THREADING)

STEP_SEC_LONG_WAVG_TO_EOL

NUMBER(11)

TW_TOTAL_MAX_QTY

NUMBER(7)

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

TW_TOTAL_MIN_QTY

NUMBER(7)

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

TW_USE_MAX_QTY

NUMBER(7)

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

TW_USE_MIN_QTY

NUMBER(7)

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

TW_USE_MODULE

VARCHAR2(12)

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

USE_CMT_TGT_IF_NOT_MAIN

CHAR(1)

N