Data Dictionary
>
FPSINPUT Tables
> FPSINPUT.MSO_RULE_EQP_EVENTS
Table FPSINPUT.MSO_RULE_EQP_EVENTS"
This table lists the equipment events that are mapped to a sample rule when the EVENT rule type is configured.
-
Schema: FPSINPUT
-
Tablespace: FPSDATA
-
Primary key: FACILITY, SMP_RULE_ID, EVENT
-
Foreign keys: MSO_RULE_EQP_EVENTS_FK_ID: SMP_RULE_ID REFERENCES FPSBASE.MSO_RULES (SMP_RULE_ID)
|
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) |
|
SMP_RULE_ID |
NUMBER(9) |
N |
The sample rule id associated to the equipment event. |
|
EVENT |
VARCHAR2(128) |
N |
Equipment event that will trigger MSO to sample the lots that process immediately after. Multiple equipment events can be mapped to one rule, but only one counter is kept per rule. |
|
UPDATED_INST |
DATE |
Time when the record was updated according to the source data. Note this is not the time when the record was actually updated in this table - it will almost always be earlier. (* from FPSINPUT.GEN_FACILITIES) |