FPSINPUT.MSO_RULE_TOOL_SKIP_WAIVERS

WAIVER_ID

NUMBER(9)

Unique ID for waiver.

CHAMBER

VARCHAR2(19)

Chambers belong to a main tool, have a state which is independent of the main tool and other chambers on the same tool, and can have events logged against it. The difference between a chamber and a port is that a chamber processes lots while port is just a location. (* from FPSINPUT.EQP_CHAMBERS)

DESCRIPTION

VARCHAR2(256)

N

Explanation as to why the waiver is needed provided by the users.

EXPIRE_INST

DATE

Time when the waiver is expired.

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_EXPIRED_ON_NEXT_MEASURE

CHAR(1)

N

Defines if the waiver will expire once a lot is measured at Metrology. If the falg is set to Y the waiver will espire and is deleted even if the scan happens prior to the expiration time defined for the waiver.

IS_EXPIRED_ON_NEXT_TAG

CHAR(1)

N

Defines if the waiver will expire when the next lot is tagged or not. If the flag is set to Y the waiver expires and is deleted even if the tagged lot is before the expiration time defined for the waiver.

IS_PRESET

CHAR(1)

Used by MSOUI to determine what waivers are done through the UI preset option.

MAX_CONSECUTIVE_SKIP_WARN_WVR

NUMBER(5)

The warning value consecutive skips for the defined rule and tool waiver.

MAX_CON_SKIP_TAG_NEXT_LOT_WVR

NUMBER(5)

When the consecutive skips count reaches this limit, MSO will tag the next available lot for the defined rule and tool waiver.

MAX_CON_SKIP_TRG_MES_ACTN_WVR

NUMBER(5)

When the consecutive skips count reaches this limit, MES action will be triggered for the defined rule and tool waiver.

MAX_LAR_TRIGGER_MES_ACTN_WVR

NUMBER(9)

When the lots at risk value reaches this limit, MES action will be triggered for the defined rule and tool waiver.

MAX_LAR_WARN_WVR

NUMBER(9)

The warning value of lots at risk for the defined rule and tool waiver.

MIN_CON_SKIP_ALLOW_TAG_WVR

NUMBER(5)

When the consecutive skips count reaches this limit, MSO will begin to allow tagging lots if the sampling criteria is met for the defined rule and tool waiver.

SMP_RULE_ID

NUMBER(9)

N

The tag condition that corresponds with the specified sample rule. This must already be defined in MSO_EXTL_TAG_CONDITIONS. (* from FPSINPUT.MSO_EXTL_RULE_TAG_COND)

TOOL

VARCHAR2(16)

N

Tool is generally just the main tool. The exception is when different entities on the tool run completely independently and it is physically impossible to run wafers of the same lot across multiple entities. In this exception case, we may want to assign the entities to different eqp_types and therefore we should define each entity as a tool. Please note that when we do this there is no indication whatsoever that these different entities are on the same tool. (* from FPSINPUT.EQP_TOOLS)

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)

USER_ID

VARCHAR2(50)

N

The user making the changes to the MSO_RULE_TOOL_SKIP_WAIVERS table. If not defined it will default to the session OS user.