data-dictionary

FPSBASE.RTG_QUEUE_TIMER_STEP_PCT

Data Dictionary

>

FPSBASE Tables

> FPSBASE.RTG_QUEUE_TIMER_STEP_PCT

Table FPSBASE.RTG_QUEUE_TIMER_STEP_PCT"

See comments in RTG_REF_QUEUE_TIMER_STEP_PCT view.

  • Schema: FPSBASE

  • Tablespace: FPSDATA

  • Primary key: FACILITY, TIMER_ID, ROUTE, STEP


Column

Type

Nullable

Comment

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)

TIMER_ID

NUMBER(9)

N

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

ROUTE

VARCHAR2(256)

N

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

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)

COMMIT_PCT_AT_STEP

NUMBER(6,2)

COMMIT_SEC_AT_STEP

NUMBER(7)

COMMIT_SEC_TOTAL

NUMBER(11)

COMMIT_STEP_SEC_CURR

NUMBER(7)

COMMIT_STEP_SEC_END

NUMBER(7)

COMMIT_STEP_SEC_START

NUMBER(7)

COMMIT_STEP_SEC_TO_EOL_CURR

NUMBER(11)

COMMIT_STEP_SEC_TO_EOL_END

NUMBER(11)

COMMIT_STEP_SEC_TO_EOL_START

NUMBER(11)

CT_PCT_AT_STEP

NUMBER(6,2)

CT_SEC_AT_STEP

NUMBER(7)

CT_SEC_TOTAL

NUMBER(11)

END_STEP

VARCHAR2(256)

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

EXPIRED_SEC

NUMBER(7)

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

PROC_SEC_CURR

NUMBER(7)

PROC_SEC_END

NUMBER(7)

PROC_SEC_START

NUMBER(7)

SEQ_NUM

NUMBER(7,2)

Sequence number of step in route (* from FPSINPUT.RTG_ROUTE_STEPS)

SEQ_NUM_END

NUMBER(7,2)

SEQ_NUM_START

NUMBER(7,2)

START_STEP

VARCHAR2(256)

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

STEP_SEC_CURR

NUMBER(7)

STEP_SEC_END

NUMBER(7)

STEP_SEC_START

NUMBER(7)

STEP_SEC_TO_EOL_CURR

NUMBER(11)

STEP_SEC_TO_EOL_END

NUMBER(11)

STEP_SEC_TO_EOL_START

NUMBER(11)

TCT_SEC_AT_STEP

NUMBER(7)

TCT_SEC_CURR

NUMBER(7)

TCT_SEC_END

NUMBER(7)

TCT_SEC_START

NUMBER(7)

TCT_SEC_TOTAL

NUMBER(11)

TCT_SEC_TO_EOL_CURR

NUMBER(11)

TCT_SEC_TO_EOL_END

NUMBER(11)

TCT_SEC_TO_EOL_START

NUMBER(11)

TIMER_END_EVENT

VARCHAR2(12)

The WIP event type which ends the queue timer at the end step. Prior to Scheduler version 1.18.1, the only choice is BEGIN so all timers will end when the lot starts processing at the end step. For 1.18.1+, DISPATCH, BEGIN, END, and COMP are all available options. Please note that scheduling timers that end on COMP and END events is much more difficult, as many factors can introduce significant variability to the processing time of a lot. DISPATCH and BEGIN are the preferred event types to use here. (* from FPSINPUT.RTG_QUEUE_TIMERS)

TIMER_START_EVENT

VARCHAR2(12)

The WIP event type which starts the queue timer at the start step. The default and preferred choice is END since most timers should start when the lot ends processing at the start step but other choices are DISPATCH, BEGIN, and COMP. These four choices are a subset of list in WIP_EVENT_TYPES. This column would be more accurately named TIMER_START_EVENT_TYPE but this is in use everywhere and changing ETL makes upgrades significantly more difficult so we are leaving this slightly confusing column name. (* from FPSINPUT.RTG_QUEUE_TIMERS)