Data Dictionary
>
FPSAPP Tables
> FPSAPP.RTG_ACTIVE_THREADING_LOTS
Table FPSAPP.RTG_ACTIVE_THREADING_LOTS"
This table contains the list of lots that have run through a threading start step and contains the future linked steps with the corresponding thread tool and non thread tool rank. This table should only have rows for lots that have not completed the linked steps.
-
Schema: FPSAPP
-
Tablespace: FPSDATA
-
Primary key: FACILITY, LOT, ROUTE, STEP, THREAD_TOOL
|
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) |
|
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) |
|
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) |
|
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 (* from FPSINPUT.RTG_STEP_THREADING) |
|
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 (* from FPSINPUT.RTG_STEP_THREADING) |
|
START_STEP_TOOL |
VARCHAR2(16) |
N |
This is the tool the lot ran on at the start thread step. If a lot is threading by tool then START_STEP_TOOL will be equal to the THREAD_TOOL. If lots are threading by THREAD_GROUP then this value will be all possible tools at the future step. |
|
THREAD_TOOL_RANK |
VARCHAR2(1) |
N |