Data Dictionary
>
FPSADMIN Tables
> FPSADMIN.EQP_RECIPE_FAMILIES
Table FPSADMIN.EQP_RECIPE_FAMILIES"
is the configuration table to store the recipe_family - recipe_group info
-
Schema: FPSADMIN
-
Tablespace: FPSDATA
-
Primary key: EQP_TYPE, RECIPE_FAMILY, RECIPE_GROUP, FACILITY
-
Foreign keys: EQP_RECIPE_FAM_FK_FAC: FACILITY REFERENCES FPSINPUT.GEN_FACILITIES (FACILITY)
|
Column |
Type |
Nullable |
Comment |
|---|---|---|---|
|
EQP_TYPE |
VARCHAR2(50) |
N |
the eqp type |
|
RECIPE_FAMILY |
VARCHAR2(100) |
N |
the recipe family for this eqp type; each family can have be assigned to multiple groups |
|
RECIPE_GROUP |
VARCHAR2(100) |
N |
the recipe group for this eqp type; each group can have multiple families |
|
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) |
|
DESCRIPTION |
VARCHAR2(256) |
the description |