FPSBASE.MSO_TRIGGERED_MES_ACTIONS_HIST

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)

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)

INST

DATE

N

Time when the event occurred. (* from FPSINPUT.WIP_EVENT_HIST)

LOT

VARCHAR2(32)

N

A lot is a group of units that process together. Usually lot_id or lot_number in MES. All units in a lot are in the same carrier but there may be multiple lots in a carrier. (* from FPSINPUT.WIP_LOTS_STATIC)

ROUTE

VARCHAR2(256)

N

Route that has threading requirements (* from FPSINPUT.RTG_STEP_THREADING)

FROM_STEP

VARCHAR2(256)

N

MSO_RULE_COUNTER_TYPE

VARCHAR2(30)

N

The type of counter that is evaluated.

FROM_MSO_PROCESS

VARCHAR2(100)

MES_PARAMETER

VARCHAR2(100)

MSO_RULE_COUNTER_LIMIT

NUMBER(9)

The rule limit that causes the MES action to trigger.

MSO_RULE_COUNTER_VALUE

NUMBER(9)

The value for the rule counter at the time the MES action is triggered.

REASON

VARCHAR2(1000)

Reason why the action was triggered. This is used to provide a comment to MES.

TOOL

VARCHAR2(16)

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)

TO_MSO_PROCESS

VARCHAR2(100)

The tag condition is only applies at a FROM_MSO_PROCESS that is linked to the specified MSO_PROCESS in this column. If the value is NULL then it applies to all proceses. (* from FPSINPUT.MSO_EXTL_RULE_TAG_COND)