FPSBASE.MSO_MES_INTERACTION_HIST

FACILITY

VARCHAR2(6)

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)

INST

DATE

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

LOT

VARCHAR2(32)

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)

MES_PARM_TYPE

VARCHAR2(50)

MES_PROCEDURE

VARCHAR2(40)

PARAMETER_NAME

VARCHAR2(50)

The name of the parameter. (* from FPSINPUT.WIP_PARAMETERS)

PARAMETER_VALUE

VARCHAR2(50)

PROCEDURE_PARAMETERS

VARCHAR2(4000)

ROUTE

VARCHAR2(256)

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

SMP_RULE_ID

NUMBER(9)

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)

SYS_TIME

TIMESTAMP(6)

This is always SYSTIMESTAMP when the record was inserted in the MSO_MES_INTERACTION_HIST table.