FPSBASE.RTG_STEP_THREADING

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

START_STEP

VARCHAR2(256)

N

Start step that will impact the future thread step rank in RTG_TOOL_ASSIGNMENT_LOT

FUTURE_THREAD_STEP

VARCHAR2(256)

N

Future step(s) that will have its PERM_RANK altered based on the tool that processed the lot at the start step

THREAD_TOOL

VARCHAR2(16)

N

Tool that the lot will be forced to run on at the future thread step if the tool processes the lot at the start step

NON_THREAD_TOOL_RANK

VARCHAR2(1)

N

Rank for other tools at the End Step for the lot that processed on the thread tool at the start step

THREAD_GROUP

VARCHAR2(20)

N

This is an optional field for thread grouping. If populated then all possible tools will be the thread_tool. If not then it will be the tool where the lot ran on at the start thread step.