data-dictionary
data-dictionary
Breadcrumbs

FPSAPP.EQP_PROCESS_CHG_TO_IGNORE

Data Dictionary

>

FPSAPP Tables

> FPSAPP.EQP_PROCESS_CHG_TO_IGNORE

Table FPSAPP.EQP_PROCESS_CHG_TO_IGNORE"

This is the configuration table to store the recipes and/or setups to ignore the change. Ignore basically means that we keep the previous value as the current recipe or setup.

  • Schema: FPSAPP

  • Tablespace: FPSDATA

  • Primary key: TOOL, CHANGE_TYPE, CHANGE_VALUE, FACILITY

  • Foreign keys: EQP_PROCESS_CHG_IGNORE_FK_TOOL: FACILITY, TOOL REFERENCES FPSINPUT.EQP_TOOLS (FACILITY, TOOL)


Column

Type

Nullable

Comment

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)

CHANGE_TYPE

VARCHAR2(64)

N

This must be either RECIPE or SETUP.

CHANGE_VALUE

VARCHAR2(100)

N

The value of the RECIPE or SETUP to ignore. We also have two special values for this field, Missing and No Setup. We insert a record for Missing for either RECIPE or SETUP if we want to ignore the recipe or setup change on the tool when the lot-route-step has no record in WIP_STEP_FUT_ASSIGNMENTS. We insert a record for No Setup only for SETUP if we want to ignore the setup change on the tool for a record with no setup information.

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)

DESCRIPTION

VARCHAR2(256)

An optional description field to add why we are ignoring.