Data Dictionary
>
FPSAPP Tables
> FPSAPP.RTG_SMP_LINK_STEPS
Table FPSAPP.RTG_SMP_LINK_STEPS"
Assigns each sampleable step to its relevant linked step which is typically the process step before the metrology step.
-
Schema: FPSAPP
-
Tablespace: FPSDATA
-
Primary key: FACILITY, ROUTE, SMP_STEP, LINK_STEP
-
Foreign keys: RTG_SMP_LINK_STEPS_FK_FAC: FACILITY REFERENCES FPSINPUT.GEN_FACILITIES (FACILITY)
|
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) |
|
ROUTE |
VARCHAR2(256) |
N |
Route that has threading requirements (* from FPSINPUT.RTG_STEP_THREADING) |
|
SMP_STEP |
VARCHAR2(256) |
N |
Sampling step. |
|
LINK_STEP |
VARCHAR2(256) |
N |
Linked step assigned to the sampling step. |
|
IS_PRI_LINK |
CHAR(1) |
N |
Flag indicating if this link_oper is the primary link_oper for this smp_oper |
|
IS_PRI_SMP_BY_TYPE |
CHAR(1) |
N |
Flag indicating if this route-step is the primary smp_oper for this smp_type |