FPSADMIN.WIP_LOTS_STATIC

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.

ASSIGNED_CARRIER

VARCHAR2(32)

This column is needed for lot/carrier association for NextMove. When a lot is removed from its carrier to process on a tool, the now empty carrier can be moved independently of the lot. At this time the carrier field in WIP_LOTS_STATIC will be blank as the lot is no longer in the carrier however this column will keep track of the carrier to which the lot is assigned. This enables the ability to scan empty carriers on racks while the lot is processing on the tool. This column is strictly optional. All applications including NextMove will work as normal if this column is left blank. It should only be populated for sites using NextMove where empty carriers are allowed to leave the load port and remain assigned to lot(s) which are processing.

BUNCH_ID

VARCHAR2(17)

Chain lots together for Goal Planner

CARRIER

VARCHAR2(32)

RFID of the cassette or FOUP the lot is currently in. (* from FPSINPUT.MHS_CARRIERS)

CREATED_INST

DATE

N

Time when the lot was created, either lot start or split.

CURR_PRIORITY

VARCHAR2(7)

N

The priority at the current step. As the lot moves along the route after LAST_STEP_CURR_PRTY it will revert to PLAN_PRIORITY. For example, timelink or sendahead priority is only temporary.

CURR_PRIORITY_REASON

VARCHAR2(128)

An optional description of why the priority is set as it is. This is typically shown as additional information on pages related to priority lots.

DUE_INST

DATE

Time when the lot has to complete the main route of the current facility to remain on schedule.

ENGR_COMMENT

VARCHAR2(128)

Special comments made by engineering about this lot. These comments are about the lot in general and not about a specific step.

EXPT_ID

VARCHAR2(12)

Experiment identifier which indicates the lot will process differently that normal for its product on at least one step of the route.

EXPT_INSTRUCTIONS

VARCHAR2(512)

General instructions about the experiment performed on this lot. This is a long string field for display only.

EXPT_VARIATION

VARCHAR2(12)

Assigned to sibling lots to indicate which variation of the experiment will be performed on the lot. For example, variation 0 might get the normal recipe while variation 1 might get a different recipe then we can compare the different wafers in each split at a following measurement or test step. (* from FPSINPUT.RTG_TOOL_ASSIGNMENTS_LOT)

GBL_SORT

NUMBER(38)

Sorting used for dispatching or allocation systems to sort lots based on priority, critical ratio, etc.

IS_CHILD_LOT_FOR_MSO

CHAR(1)

Field specific for telling MSO if a lot is a child lot or not. Tag conditions can be set to no allow child lots to be tagged. This field controls what is a child lot for MSO.

LAST_STEP_CURR_PRTY

VARCHAR2(256)

The last step where the current lot_priority applies. After this step we assume the lot will return to its plan_priority.

LOT_SUBTYPE

VARCHAR2(8)

This is an optional field to add a level to lot_type. This field is not used in logic but is displayed on hold and scrap pages of Dashboard.

LOT_TYPE

VARCHAR2(24)

N

Lot_type is the base of the hierarchy that determines lot_family then lot_group. Ideally lot_type will come straight from the MES with little modification. (* from FPSINPUT.WIP_LOT_TYPES)

NUM_SIBLING_LOTS

NUMBER(2)

A count of other lots that were also split from the same parent.

ORDER_ID

VARCHAR2(64)

The customer order to which this lot belongs.

ORIG_DUE_INST

DATE

Original due date for this lot in the current facility which was set for the lot at its creation or when it entered this facility.

ORIG_PLAN_OUT_INST

DATE

Original plan out date for this lot in the current facility which was set for the lot at its creation or when it entered this facility.

OVR_CUSTOMER

VARCHAR2(64)

Normally customer is defined in RTG_PLANPRDS but in some cases we have different lots of the same planprd which go to different customer so we can override here by lot.

OVR_IS_QUEUE_ALLOWED

CHAR(1)

We stop lots from starting the first step in a queue timer when WIP is too high but this flag allows this specific lot to start despite this. Use for priority lots or sendahead lots or when we want to trickle lots into the timer.

PARENT_LOT

VARCHAR2(32)

The parent lot should ideally be the original parent but it could be the most recent parent if multiple splits have occurred.

PLAN_OUT_INST

DATE

Current planned out date for this lot in the current facility.

PLAN_PRIORITY

VARCHAR2(7)

N

Permanent priority of the lot set in the MES generally by planning. (* from FPSINPUT.WIP_EVENT_HIST)

QUEUE_STATUS

VARCHAR2(8)

Display field showing the current status of this lot within a queue time sequence.

SAH_CHAMBERS

VARCHAR2(24)

Send ahead chambers

SAH_TOOL

VARCHAR2(16)

Send ahead tool

SAH_TYPE

VARCHAR2(8)

Send ahead type is primarily used to set lot_priority. We often want to prioritize a sendahead lot only to the metrology tool so we can get metrology as soon as possible and start processing more lots. (* from FPSINPUT.WIP_SAH_TYPES)

SCH_CRITICAL_RATIO_OVR

NUMBER(5,2)

This column allows for a user defined CRITICAL RATIO to be used by the scheduler. If this value is populated, it will be used by the scheduler instead of any value of CRITICAL RATIO that would be calculated by the FPS sytems.

SCH_DAYS_LATE_OVR

NUMBER(5,2)

Our normal days late calculation uses due_inst and changes over time as that date approaches. This value overrides that normal calculation with a fixed number of days late that does not change over time. A positive value means the lot is behind schedule. This only applies to the Scheduler. The normal use case is for important development lots where we do not really have a due date but we just want them to always count as two days late putting them ahead of normal lots that are less than two days late but behind normal lots that are more than two days late.

TW_BAD_QTY

NUMBER(7)

Only applicable to TW lots. This is the number of test wafers in the lot which are considered BAD.

TW_GOOD_QTY

NUMBER(7)

Only applicable to TW lots. This is the number of test wafers in the lot which are considered GOOD.

TW_RECYCLE_COUNT

NUMBER(4)

Only applicable to TW lots. This is the number of times the test wafers have been reused

UPDATED_INST

DATE

Time when the record was updated according to the source data. Note this is not the time when the record was actually updated in this table - it will almost always be earlier. (* from FPSINPUT.GEN_FACILITIES)

WAIT_SEC_TO_SCHED

NUMBER(7)

The lot may be scheduled but must not be allowed to dispatch or start until this number of seconds has elapsed.

WAIT_SEC_UPDATED_INST

DATE

Time which may be used to adjust wait_sec_to_sched, usually based on how long a timer was been stopped.