FPSINPUT.FR_W_MNT_DEF_VERSIONS

VERSION_NAME

VARCHAR2(200)

EVENT_DEFINITION

VARCHAR2(200)

EVENT_GROUP

VARCHAR2(128)

Event group is the second highest level in the maintenance event hierarchy it could be used to denote the group even maintenance definitions such as PMs, Adhoc tasks, OCAPS, Quals, or inspections. This grouping will be a collection of maintenance definitions. (* from FPSAPP.SMMS_B_EVENT_GROUPS)

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_TO_PROD

DATE

INST_TO_TEST

DATE

VERSION_DESCRIPTION

VARCHAR2(500)

VERSION_ENVIRONMENT

VARCHAR2(50)

VERSION_MULTIPLE_CHAMBER

CHAR(1)

VERSION_NUMBER

NUMBER(10)

VERSION_REVIEW_ROLE

VARCHAR2(200)

VERSION_STATE

VARCHAR2(20)

VERSION_SUBMIT_USER_EMAIL

VARCHAR2(200)