Data Dictionary
>
FPSINPUT Tables
> FPSINPUT.EQP_CURR_PATTERN
Table FPSINPUT.EQP_CURR_PATTERN"
this is the current pattern supplied that has been run on the tool. assumptions/ground rules: 1) recipe sequencing is assumed to be active if a tool exists 2) the order for curr_pattern is assumed left to right, where right is the most recent process run on the tool. example: a,b,b,b,c. recipe c just ran on the tool. 3) if recipe sequencing active, a null curr_pattern is interpreted as no history exists. the scheduler will can effectively run anything as to initiate a sequence. 4) the assumption is that the curr_pattern supplied is comma delimited.
-
Schema: FPSINPUT
-
Tablespace: FPSDATA
-
Primary key: FACILITY, TOOL
-
Foreign keys: EQP_CURR_PATTERN_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) |
|
TOOL |
VARCHAR2(16) |
N |
tool on which the pattern exists. |
|
CURR_PATTERN |
VARCHAR2(2000) |
the comma delimited history of process sequences run on the tool. see table comments for ground rules |
|
|
PATTERN_START_INST |
DATE |
N |
the point in time where the pattern should start to be considered. any wsh entry that has started is considered as part of the existing pattern |
|
PROCESS_CHANGE_TYPE |
VARCHAR2(64) |
N |
defines what change type each value in the sequence represents. setup/recipe/recipe_family/recipe_group. note: cannot mix change_types |
|
UNIT_TYPE |
VARCHAR2(12) |
N |
the unit type indicates how to count a distinct part of the sequence. we can count by lot or job. for example every lot that is run is counted regardless of batched or not. for example. if lot, and 5 lot batch processes with recipe a, the scheduler will evaluate the sequence as aaaaa if job, 5 lots in batch job, runs a particular recipe a are counted as 1 the scheduler will evaluate the sequence as a |