Data Dictionary
>
FPSAPP Tables
> FPSAPP.MSO_RULE_GROUPS_CHANGE_HIST
Table FPSAPP.MSO_RULE_GROUPS_CHANGE_HIST"
Table contains the change history for all sampling rule groups that have been created or modified in MSO_RULE_GROUPS.
-
Schema: FPSAPP
-
Tablespace: FPSDATAHIST
-
Primary key: TRANSACTION_ID
|
Column |
Type |
Nullable |
Comment |
|---|---|---|---|
|
TRANSACTION_ID |
VARCHAR2(75) |
N |
|
|
BG_COLOR |
VARCHAR2(24) |
N |
Background color assigned. BG_COLOR is in English like red or blue or light green and we look up the HTML color like #FF0000 in the GEN_COLORS table. BG_COLOR must be set manually but the FPSADMIN view BLD_POPULATE_COLORS will generate queries to randomly set bg_color for all values in a table. (* from FPSINPUT.GEN_CUSTOMERS) |
|
DESCRIPTION |
VARCHAR2(256) |
Tool desciption. This value is only used to display in the Dashboard. (* from FPSINPUT.EQP_TOOLS) |
|
|
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) |
|
IS_DYNAMIC_TOOLSTATUS_COND_ON |
CHAR(1) |
Flag that sets the rule group to allow dynamic adjusting of the sample condition and min condition override depending on tool conditions for the rule group. (* from FPSBASE.MSO_RULE_GROUPS) |
|
|
LINKS_REQ_ALLOWED_TAG_COND |
CHAR(1) |
N |
Define if rule links require an allowed tag condition to be able to tag at the main process step. This is usually set to N unless the metrology step requires recipes to exist in those cases we set to Y to be able to only TAG when an allowed tag condition for the rule link is defined. (* from FPSBASE.MSO_RULE_GROUPS) |
|
PARENT_TRANSACTION_ID |
VARCHAR2(75) |
||
|
RULE_CLASS |
VARCHAR2(36) |
Unique name for the class. (* from FPSBASE.MSO_RULE_CLASSES) |
|
|
RULE_GROUP |
VARCHAR2(36) |
N |
Unique name for the group. (* from FPSBASE.MSO_RULE_GROUPS) |
|
RULE_GROUP_DISPLAY |
VARCHAR2(36) |
N |
Display name to show on the dashboard. (* from FPSBASE.MSO_RULE_GROUPS) |
|
RULE_GROUP_Q_SKIP_WIP_LIMIT |
NUMBER(12) |
WIP limit used to trigger post tag skipping of lots for rules where allowed. If WIP for the rule group exceeds this limit, then lots will be allowed to skip by the queue manager if the lots pass checks and rule allows. (* from FPSBASE.MSO_RULE_GROUPS) |
|
|
RULE_GROUP_SORT |
NUMBER(3) |
N |
Display order of the group on the dashboard. (* from FPSBASE.MSO_RULE_GROUPS) |
|
RULE_GROUP_TOOL_MSO_GROUP |
VARCHAR2(64) |
Sets the assigned tool mso group for the rule group. This allows us to determine the percent of tools that are up for the rule group. (* from FPSBASE.MSO_RULE_GROUPS) |
|
|
TRANSACTION_INST |
DATE |
N |
|
|
TRANSACTION_TYPE |
VARCHAR2(6) |