Data Dictionary
>
FPSADMIN Tables
> FPSADMIN.RTG_QUEUE_TIMERS_LOT_CURR
Table FPSADMIN.RTG_QUEUE_TIMERS_LOT_CURR"
See comments in RTG_REF_QUEUE_TIMERS_LOT_CURR view.
-
Schema: FPSADMIN
-
Tablespace: FPSDATA
-
Primary key: LOT, TIMER_SORT_BY_EXP_WITHIN_LOT
|
Column |
Type |
Nullable |
Comment |
|---|---|---|---|
|
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) |
|
TIMER_SORT_BY_EXP_WITHIN_LOT |
NUMBER(4) |
N |
|
|
DESCRIPTION |
VARCHAR2(256) |
Tool desciption. This value is only used to display in the Dashboard. (* from FPSINPUT.EQP_TOOLS) |
|
|
ELAPSED_SEC |
NUMBER(12) |
||
|
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) |
|
|
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) |
|
HIDE_TIMER_IN_DASH |
CHAR(1) |
This configuration will remove WIP for this timer_id from the Dashboard Queue Timer report. (* from FPSINPUT.RTG_QUEUE_TIMERS) |
|
|
MIN_WAIT_SEC |
NUMBER(7) |
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. (* from FPSINPUT.RTG_QUEUE_TIMERS) |
|
|
ROUTE |
VARCHAR2(256) |
N |
Route that has threading requirements (* from FPSINPUT.RTG_STEP_THREADING) |
|
RWK_ROUTE |
VARCHAR2(256) |
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. (* from FPSINPUT.RTG_QUEUE_TIMERS) |
|
|
RWK_START_STEP |
VARCHAR2(256) |
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. (* from FPSINPUT.RTG_QUEUE_TIMERS) |
|
|
STARTED_ON_RWK_ROUTE |
CHAR(1) |
N |
|
|
START_STEP |
VARCHAR2(256) |
Start step that will impact the future thread step rank in RTG_TOOL_ASSIGNMENT_LOT (* from FPSINPUT.RTG_STEP_THREADING) |
|
|
TIMER_DISPLAY |
VARCHAR2(48) |
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. (* from FPSINPUT.RTG_QUEUE_TIMERS) |
|
|
TIMER_EXPIRED_INST |
DATE |
||
|
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) |
|
TIMER_MIN_WAIT_INST |
DATE |
||
|
TIMER_START_INST |
DATE |
||
|
TIMER_WARN_INST |
DATE |