Data Dictionary
>
FPSBASE Tables
> FPSBASE.RTG_PRD_FACILITY_REVERSE
Table FPSBASE.RTG_PRD_FACILITY_REVERSE"
See comments in RTG_REF_PRD_FACILITY_REVERSE view.
-
Schema: FPSBASE
-
Tablespace: FPSDATA
-
Primary key: SOURCE_FACILITY, SOURCE_PRD, FACILITY, PRD, FLUSH_PATH
|
Column |
Type |
Nullable |
Comment |
|---|---|---|---|
|
SOURCE_FACILITY |
VARCHAR2(6) |
N |
First facility in the process flow when a lot visits multiple facilities in sequence. (* from FPSINPUT.RTG_PRD_FACILITY_NEXT) |
|
SOURCE_PRD |
VARCHAR2(64) |
N |
First prd in the process flow when a lot visits multiple facilities in sequence. (* from FPSINPUT.RTG_PRD_FACILITY_NEXT) |
|
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) |
|
PRD |
VARCHAR2(64) |
N |
Prd determines the route which is used to process the lot in the facility and what tools, recipes, durables, etc. can be used at each step. Prd also determines the next facility for the lot when it finishes its route. For detailed information on prd vs. planprd see table comments in RTG_PLANPRDS. (* from FPSINPUT.RTG_PRDS) |
|
FLUSH_PATH |
VARCHAR2(4000) |
N |
|
|
CONSUMABLE_TYPE |
VARCHAR2(36) |
For assembly only, this optional field stores what type of consumable is being assembled into another part. (* from FPSINPUT.RTG_PRD_FACILITY_NEXT) |
|
|
CTM |
NUMBER(5,1) |
||
|
IS_INITIAL_START |
CHAR(1) |
||
|
IS_SHIP_PRD |
CHAR(1) |
||
|
IS_TW |
CHAR(1) |
Our standard filter to exclude test wafers is is_tw = N but what we really mean with this filter is to exclude any lots that do not add value for the facility. Lots which add value including sellable, development, and engineering and these lot groups should have is_tw set to N. Lots which do not add value are commonly grouped together and named "test wafers" which is why this flag is named is_tw. These include true test wafers like monitors and quals and dummies but also could include virtual lots used for training or testing, bare wafers, or really anything else including in the MES as a lot which does not add value. All of these lot groups should have is_tw set to Y. You could argue that the is_tw field might be more accurately named is_value or is_valuable or is_prod_eng_dev but is_tw is generally clear to most people. Plus it has the advantage that it is short which is nice given how frequently we use the is_tw = N filter. (* from FPSINPUT.WIP_LOT_GROUPS) |
|
|
LAST_BANK_CT_DAYS |
NUMBER(5,1) |
||
|
NUM_SOURCES_TO_ASSEMBLE |
NUMBER(1) |
||
|
PATH_CT |
NUMBER(5,1) |
||
|
PATH_LY |
NUMBER(6,5) |
||
|
PRD_FAC_SEQ_NUM |
NUMBER(3) |
||
|
QTY_NEEDED |
NUMBER(2) |
The number of units needed of the source product for each unit in the next product. Typically this is 1 but occasionally we might assemble 2 A and 1 B together to make 1 C. (* from FPSINPUT.RTG_PRD_FACILITY_NEXT) |
|
|
SOURCE_BANK_CT_DAYS |
NUMBER(5,1) |
||
|
SOURCE_EST_LINE_YIELD_PCT |
NUMBER(6,3) |
||
|
SOURCE_FAC_QTY |
NUMBER(7) |
||
|
SOURCE_GROSS_DIE_PER_WFR |
NUMBER(6) |
||
|
SOURCE_MAIN_ROUTE |
VARCHAR2(256) |
||
|
SOURCE_ROUTE_CT_DAYS |
NUMBER(5 |