data-dictionary
data-dictionary
Breadcrumbs

FPSINPUT.MSO_TAG_CONDITIONS_CHANGE_HIST

Data Dictionary

>

FPSINPUT Tables

> FPSINPUT.MSO_TAG_CONDITIONS_CHANGE_HIST

Table FPSINPUT.MSO_TAG_CONDITIONS_CHANGE_HIST"

Table contains the change history for all tag conditions that have been created or modified in MSO_TAG_CONDITIONS.

  • Schema: FPSINPUT

  • Tablespace: FPSDATAHIST

  • Primary key: TRANSACTION_ID


Column

Type

Nullable

Comment

TRANSACTION_ID

VARCHAR2(75)

N

EXPIRY_DEACTIVATE_INST

DATE

Date column that automatically sets the tag condition to inactive once the date is past. (* from FPSBASE.MSO_TAG_CONDITIONS)

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)

N

Flag to enable or disable the tag condition. (* from FPSBASE.MSO_TAG_CONDITIONS)

PARENT_TRANSACTION_ID

VARCHAR2(75)

TAG_CONDITION_ID

NUMBER(9)

N

Unique tag condition identification number. (* from FPSBASE.MSO_TAG_CONDITIONS)

TAG_CONDITION_NAME

VARCHAR2(64)

N

Unique name identifying the external tag condition. (* from FPSINPUT.MSO_EXTL_TAG_CONDITIONS)

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. (* from FPSINPUT.MSO_EXTL_TAG_CONDITIONS)

TRANSACTION_INST

DATE

N

TRANSACTION_TYPE

VARCHAR2(6)