FPSADMIN.RTG_ROUTES

FACILITY

VARCHAR2(6)

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)

A route includes all normal processing steps for a product in a facility in sequence. Each product must have only one main route per facility. This means if the MES allows multiple routes in sequence for a product then we must use the product as the route and that route must include all steps from all of the routes for the product.

ACTIVE_VERSION

VARCHAR2(12)

The most recent version of the route.

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)

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.

DESCRIPTION

VARCHAR2(256)

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

HIDE_LOTS_IN_DASH

CHAR(1)

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.

INCLUDE_IN_CTA_IF_NOT_MAIN

CHAR(1)

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.

IS_EXCLUDED_LINE_BALANCE

CHAR(1)

Flag to exclude route from line balance consideration including WIP levels and schedule scoring.

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.

OVR_START_STEP_IF_NOT_FIRST

VARCHAR2(256)

This value specifies which step in the route is the official start step for lots to begin accruing cycle time for this route.

ROUTE_FAMILY

VARCHAR2(36)

N

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_MSO_GROUP

VARCHAR2(64)

Route group to be used for the Metrology Sampling Optimizer, generally based on similarity of technology or volume.

ROUTE_SCORE

NUMBER(2)

Scheduler Evaluation slider value for route priority slider

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.

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.

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.

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.

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.

UPDATED_INST

DATE

Time when the record was updated according to the source data. Note this is not the time when the record was actually updated in this table - it will almost always be earlier. (* from FPSINPUT.GEN_FACILITIES)