data-dictionary

FPSADMIN.RTG_REF_QUEUE_TIMERS_LOT_CURR

Data Dictionary

>

FPSADMIN Views

> FPSADMIN.WIP_WAFER_HIST_LOOP

View FPSBASE.RTG_REF_QUEUE_TIMERS_LOT_CURR

Status of lots currently subject to queue timers. This is refreshed into a table even though it is fast because it is used in WIP_REF_LOTS_COLS_W_DD_PRTN and it was strangely slow as a view even with a having clause.

Column

Comment

LOT

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. (* inherited from FPSINPUT.WIP_LOTS_STATIC)

TIMER_SORT_BY_EXP_WITHIN_LOT

DESCRIPTION

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

TIMER_DISPLAY

This column can be displyed on the Dashboard for the lot popup and lot search pages and is a shorter display field than the queue timer. (* inherited from FPSINPUT.RTG_QUEUE_TIMERS)

TIMER_ID

Unique number representing the queue timer to index with other tables. Automatically populated with RTG_QUEUE_TIMERS_ID_SEQ sequence. (* inherited from FPSINPUT.RTG_QUEUE_TIMERS)

TIMER_START_INST

TIMER_WARN_INST

TIMER_EXPIRED_INST

TIMER_MIN_WAIT_INST

FACILITY

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. (* inherited from FPSINPUT.GEN_FACILITIES)

ROUTE

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

START_STEP

Start step that will impact the future thread step rank in RTG_TOOL_ASSIGNMENT_LOT (* inherited from FPSINPUT.RTG_STEP_THREADING)

END_STEP

The step upon move out where the WIP balance limit is no longer applied (* inherited from FPSINPUT.RTG_STEP_BALANCE)

RWK_ROUTE

If the queue timer is from a rework route to the main route then this is the name of the rework route and the route column is the name of the main route. (* inherited from FPSINPUT.RTG_QUEUE_TIMERS)

RWK_START_STEP

If the queue timer moves to a rework route and step from the main route then this is the start step on the rework route. The timer handling is treated the same once it enters rework, with the rework step starting the timer like the normal start step. (* inherited from FPSINPUT.RTG_QUEUE_TIMERS)

STARTED_ON_RWK_ROUTE

ELAPSED_SEC

WARN_SEC

Seconds from the start event until warning limit for queue time restriction. Lots that remain in the timer sequence longer than this warning limit should be prioritized to prevent them from expiring. (* inherited from FPSINPUT.RTG_QUEUE_TIMERS)

EXPIRED_SEC

Seconds from the start event until queue time restriction is expired. After expiration, the lot must rework or scrap or otherwise be evaluated. (* inherited from FPSINPUT.RTG_QUEUE_TIMERS)

MIN_WAIT_SEC

All lots must wait at least this many seconds at the step before processing. This column is the opposite of the others and can only be populated if the others are null. Also start_step and end_step must be the same since this can only apply at a single step. (* inherited from FPSINPUT.RTG_QUEUE_TIMERS)