FPSINPUT.SCH_W_H_S_TOOL_ASGN_DETAILS

CREATE_INST

DATE

ELIGIBILITY_MESSAGE

VARCHAR2(4000)

This column stores eligibility messages for this tool assignment.

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)

FIND_SCHED_FOR_TOOL_ASGN_COUNT

NUMBER(7)

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)

PROCESS_CONTEXTS_COUNT

NUMBER(7)

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)

SCENARIO_ID

VARCHAR2(50)

N

SCHED_BATCH_DETAILS

VARCHAR2(4000)

SCHED_CH_TO_USE

VARCHAR2(24)

Please note that the Scheduler often populates this with M which indicates the main tool therefore we often should filter out a value of M when using this value since that it not a valid chamber combination. When this is populated with any value other than M then we use this as est_ch_used rather than calculating with GET_CH_ALLOWED_STATUS or GET_CH_PATH_STATUS. (* from FPSBASE.WIP_STEP_FUTURE_SCHED)

SCHED_COMMENT

VARCHAR2(4000)

SCHED_DURABLE

VARCHAR2(129)

SCHED_END

DATE

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)

SCHED_SCORE

NUMBER(20,4)

SCHED_SCORE_DETAILS

VARCHAR2(4000)

SCHED_START

DATE

The first start time for the durable to be used (* from FPSBASE.RTG_DURABLE_FUTURE_SCHED)

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)