FPSBASE.MSOUI_P_FLTR_PRM_VALS_CHG_HIST

PARENT_TRANSACTION_ID

TRANSACTION_INST

TRANSACTION_TYPE

TRANSACTION_ID

FACILITY

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

FILTER

The name of the filter to be defined in the UI. The filter can be used by multiple rules. (* inherited from FPSBASE.MSO_FILTER_PARAM_VALUES)

FILTER_PARAMETER

The filter parameter. The parameter options will be limited and pre-defined unless the IS_LOT_PARAMETER flag is set to Y. In this case, the user will input the parameter, which will be looked up in WIP_LOT_PARAMETERS. (* inherited from FPSBASE.MSO_FILTER_PARAM_VALUES)

FILTER_VALUE

The value for the filter parameter. (* inherited from FPSBASE.MSO_FILTER_PARAM_VALUES)

IS_LOT_PARAMETER

Flag to determine if the parameter is a lot parameter or one of the pre-defined paramter options. (* inherited from FPSBASE.MSO_FILTER_PARAM_VALUES)

USER_ID

The user Id that initiated the last move of this carrier (* inherited from FPSINPUT.MHS_CARRIERS)