FPSAPP.WIP_HOLD_FUTURE

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)

STEP

VARCHAR2(256)

N

A single processing step within a route representing a single tool visit. Step is often a very complex string and should rarely be displayed. Instead we should use process_display. (* from FPSINPUT.RTG_ROUTE_STEPS)

ROUTE

VARCHAR2(256)

N

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

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)

EVENT_KEY

VARCHAR2(512)

N

EVENT_KEY needs to be populated with a unique value for each different future hold. The idea here is that if we have a line hold that all lots on hold for that same line hold have the same EVENT_KEY. Where the MES does not create a unique key for each line hold, we use EVENT_COMMENT as EVENT_KEY, and we hash it prior to passing it as a key to the web applications.

EST_DURATION_SEC

NUMBER(8)

Estimate of the duration of the future hold if known. If blank we use the estimate for the hold_type.

EVENT_COMMENT

VARCHAR2(512)

N

Comment associated with the event.

EVENT_CREATE_INST

DATE

N

Time when the hold event was created in the MES or other host system.

HOLD_TYPE

VARCHAR2(24)

N

Generally hold_type will come directly from the MES. (* from FPSINPUT.WIP_HOLD_TYPES)

IS_AT_COMP

CHAR(1)

Specifies if the hold will occur when the lot completes the step.

IS_AT_DISP

CHAR(1)

Specifies if the hold will occur when the lot is dispatched to a tool.

IS_AT_ENTER

CHAR(1)

Specifies if the hold will occur when the lot enters the step, which in some cases will be when the lot finishes the previous step.

IS_SPECIFIC_PRD

CHAR(1)

This indicates if the future hold is a line hold applicable to all lots at the step for the specific product.

IS_SPECIFIC_ROUTE

CHAR(1)

This indicates if the future hold is a line hold applicable to all lots at the step for the specific route.

OPERATOR

VARCHAR2(64)

N

In history tables, this is the username of the person or system who logged the event. In EQP_MNT_FUTURE, this is the username of the person who input the information about the maintenance event. Usernames can be looked up in GEN_USERS to get full names, email address, etc. Please note that the existence of each username in GEN_USERS is optional, meaning that it is never required for the username logged in the operator column to be in GEN_USERS. (* from FPSINPUT.WIP_EVENT_HIST)