FPSBASE.SCH_W_H_S_DURABLE_ASGNS_COMBO

COMBINATION_ID

VARCHAR2(64)

N

User can use COMBINATION_ID to define multiple different combinations of durables for the same lot/process. For example, user can define durable A and C with COMBINATION_ID 1 and durable B and D with COMBINATION_ID 2, the scheduler will either schedule to use durable (A and C) or (B and D) to run this process on this tool. Meanwhile, if the durable assignment is defined for the certain lot/route/step/tool in this table, then the scheduler will also ignore the durable assignment from RTG_DURABLE_ASSIGNMENTS table. (* from FPSINPUT.RTG_DURABLE_ASGNS_COMBO)

CREATE_INST

DATE

DURABLE

VARCHAR2(64)

N

Durables are either reticles for Litho or probe cards for Wet or Sort. A durable can either be in a carrier or at a location without a carrier. (* from FPSINPUT.RTG_DURABLES)

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)

LOT

VARCHAR2(32)

N

A lot is a group of units that process together. Usually lot_id or lot_number in MES. All units in a lot are in the same carrier but there may be multiple lots in a carrier. (* from FPSINPUT.WIP_LOTS_STATIC)

PERM_RANK

VARCHAR2(1)

N

Permanent rank is typically loaded by ETL from a combination of the MES, recipe management system, and existing preference logic already used at the site. Possible values are in FPSADMIN.RTG_PERM_RANKS. (* from FPSINPUT.RTG_TOOL_ASSIGNMENTS)

ROUTE

VARCHAR2(256)

N

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

RUN_ID

VARCHAR2(50)

N

the run id from the last successful scheduler (* from FPSAPP.SCH_W_SCHED_GROUP_STATUS)

SCHED_GROUP

VARCHAR2(36)

N

This is the grouping of tools and processes which the FPS Scheduler schedules together. Since this is a parent of tool via tool->process_group and a parent of process via process->process_group, by definition each tool and each process can only be in one sched group. We need all related tools and processes to be in the same sched group for efficient scheduling. One example is sinks and furnaces because of queue times and batching. Another example is for smaller facilities like Assembly or Test where we might schedule the entire facility together. (* from FPSINPUT.RTG_PROCESS_GROUPS)

SHOULD_USE

CHAR(1)

This flag determines if the scheduler should use this data or not

STEP

VARCHAR2(256)

N

A single processing step within a route representing a single tool visit. Step is often a very complex string and should rarely be displayed. Instead we should use process_display. (* from FPSINPUT.RTG_ROUTE_STEPS)