FPSAPP.SCH_W_SCHED_CURR_JOBS

RUN_ID

VARCHAR2(50)

N

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

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)

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)

TOOL

VARCHAR2(16)

N

Tool is generally just the main tool. The exception is when different entities on the tool run completely independently and it is physically impossible to run wafers of the same lot across multiple entities. In this exception case, we may want to assign the entities to different eqp_types and therefore we should define each entity as a tool. Please note that when we do this there is no indication whatsoever that these different entities are on the same tool. (* from FPSINPUT.EQP_TOOLS)

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)

JOB_ID

VARCHAR2(64)

N

Automatically set by trigger when the first lot of a job logs an event to the tool. (* from FPSBASE.WIP_LOT_HIST)

SCHED_START_INST

DATE

N

CHANGE_TYPE

VARCHAR2(64)

the change for this process max usages. only allow setup, recipe, recipe_family, recipe_group (* from FPSINPUT.EQP_PROCESS_USAGES)

CH_TO_USE

VARCHAR2(24)

CREATE_INST

DATE

FROM_DURABLE

VARCHAR2(129)

FROM_RECIPE

VARCHAR2(100)

FROM_RQD_SETUP

VARCHAR2(100)

Setup that is changed from. This should match a value in rqd_setup in RTG_TOOL_ASSIGNMENTS. (* from FPSINPUT.EQP_SETUP_CHG_MANUAL)

JOB_SEQ_NUM

NUMBER

JOB_TYPE

VARCHAR2(50)

PROCESS_CAPACITY

NUMBER(5)

PROCESS_JOB_ID

VARCHAR2(200)

QUEUE_SORT_ORDER

NUMBER

RECIPE

VARCHAR2(100)

the recipe; the est_machine_recipe (* from FPSINPUT.EQP_RECIPES)

RQD_SETUP

VARCHAR2(100)

Rqd_setup is determined by ovr_rqd_setup in RTG_TOOL_ASSIGNMENTS and use_process_as_rqd_setup and use_est_mach_rcp_as_rqd_setup from EQP_TYPES. The latter two columns allow us to easily specify for an eqp_type that setup times should be calculated by process or est_machine_recipe. For traditional setups that are a group of recipes we use ovr_rqd_setup. (* from FPSBASE.WIP_LOT_HIST)