data-dictionary
data-dictionary
Breadcrumbs

FPSBASE.WIP_CURR_JOBS

Data Dictionary

>

FPSBASE Tables

> FPSBASE.WIP_CURR_JOBS

Table FPSBASE.WIP_CURR_JOBS"

Store current and max information about each active job which is updated by WIP_EVENT_HIST_INSERT_BEF trigger. Current columns qty_in_job and carriers_in_job are used by WIP_LOTS_PLUS while max_qty_in_job and max_carriers_in_job are used to populate WIP_STEP_HIST. This is necessary because the current values count up and down. A simple example of a two lot batch will have qty_in_job of 25 after first lot is dispatched, 50 after second lot is dispatched, stay at 50 while processing, 25 after first lot moves out, and then record is deleted from this table after second lot moves out.

  • Schema: FPSBASE

  • Tablespace: FPSDATA

  • Primary key: FACILITY, JOB_ID


Column

Type

Nullable

Comment

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)

JOB_ID

VARCHAR2(64)

N

Automatically set by trigger when the first lot of a job logs an event to the tool. (* from FPSBASE.WIP_LOT_HIST)

CARRIERS_IN_JOB

NUMBER(2)

N

Set to the number of carriers in the job. The value in WIP_EVENT_HIST represents the number of carriers which have started processing in this job *so far*, while the value in WIP_STEP_HIST (written after the job completes processing) represents the total number of carriers in the job. (* from FPSBASE.WIP_LOT_HIST)

EET_SEC_LAST_LOT

NUMBER(7)

FIRST_LOT_IN_JOB

VARCHAR2(32)

N

The first lot in the job determined by the order of events. When this first lot logs the first tool event which is usually a reserve or dispatch then the job_id is created with only this lot. Then subsequent lots join this job. While we use job_id to identify lots that will process or are processing or processed together, first_lot_in_job is still a useful field. (* from FPSBASE.WIP_LOT_HIST)

JOB_CREATED_INST

DATE

N

LAST_EVENT

VARCHAR2(48)

N

LAST_EVENT_INST

DATE

N

LAST_EVENT_TYPE

VARCHAR2(12)

N

LAST_LOT

VARCHAR2(32)

N

LOTS_IN_JOB

NUMBER(2)

N

Set to the number of lots in the job. The value in WIP_EVENT_HIST represents the number of lots which have started processing in this job *so far*, while the value in WIP_STEP_HIST (written after the job completes processing) represents the total number of lots in the job. (* from FPSBASE.WIP_LOT_HIST)

MAX_CARRIERS_IN_JOB

NUMBER(2)

N

MAX_EET_SEC_IN_JOB

NUMBER(7)

MAX_LOTS_IN_JOB

NUMBER(2)

N

MAX_QTY_IN_JOB

NUMBER(7)

N

Normally we assume that the maximum qty in a job for a non-batch tool is the max_qty_per_carrier for the facility. However sometimes the maximum per job is less than that and this column allows us to override. For example, the max_qty_per_carrier for the facility is 25 but a certain eqp type can do no more than 13 units per job. In this case, if the carrier has 13 wafers or less then we schedule normally but if it has more than 13 then we must ask for a split. (* from FPSINPUT.EQP_TYPES)

MAX_TCT_SEC_IN_JOB

NUMBER(7)

QTY_IN_JOB

NUMBER(7)

N

The number of units in the job. For example a batch tool with 5 carriers each with a 25 wafer lot would have 125 in the job. This is also important for non-batch tools where we have multiple lots in a carrier as the job might include all lots or only selected lots. (* from FPSBASE.WIP_LOT_HIST)

TCT_SEC_LAST_LOT

NUMBER(7)

TOOL

VARCHAR2(16)

N

Tool is generally just the main tool. The exception is when different entities on the tool run completely independently and it is physically impossible to run wafers of the same lot across multiple entities. In this exception case, we may want to assign the entities to different eqp_types and therefore we should define each entity as a tool. Please note that when we do this there is no indication whatsoever that these different entities are on the same tool. (* from FPSINPUT.EQP_TOOLS)