FPSBASE.MSO_TAG_CONDITIONS

Data Dictionary

>

FPSBASE Tables

> FPSBASE.MSO_TAG_CONDITIONS

Table FPSBASE.MSO_TAG_CONDITIONS"

All Metrology Sampling Optimizer tag conditions which define which lots are allowed to be tagged to clear a sampling rule. One or more tag conditions can be assigned to each sampling rule.

Schema: FPSBASE
Tablespace: FPSDATA
Referenced by: FPSBASE.MSO_TAG_CONDITION_CONTEXT (TAG_CONDITION_ID)

Column	Type	Nullable	Comment
TAG_CONDITION_ID	NUMBER(9)		Unique tag condition identification number.
EXPIRY_DEACTIVATE_INST	DATE		Date column that automatically sets the tag condition to inactive once the date is past.
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_ACTIVE	CHAR(1)		Flag to enable or disable the tag condition.
TAG_CONDITION_NAME	VARCHAR2(64)	N	Unique name given by the user for each tag condition. This can be renamed and always tied to the primary key value which is the TAG_CONDITION_ID.
TAG_CONDITION_TYPE	VARCHAR2(32)	N	Define if the tag condition is either "ALLOWED", "ALWAYS", or "NEVER". ALLOWED: If all the conditions defined for the associated rule and lot at the FROM_MSO_PROCESS are true, then the lot can be tagged to measure at the TO_MSO_PROCESS. ALWAYS: If all the conditions defined for the associated rule and lot at the FROM_MSO_PROCESS are true, then the lot will ALWAYS be tagged to measure at the TO_MSO_PROCESS. NEVER: If all the conditions defined for the associated rule and lot at the FROM_MSO_PROCESS are true, then the lot can NEVER be tagged to measure at the TO_MSO_PROCESS. In all cases the counter value will still increment.
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)