data-dictionary
data-dictionary
Breadcrumbs

FPSINPUT.FDC_EQP_LOOKUP

Data Dictionary

>

FPSINPUT Tables

> FPSINPUT.FDC_EQP_LOOKUP

Table FPSINPUT.FDC_EQP_LOOKUP"

Lookup table used by any FDC system to determine tool and entity when the values fed from the FDC system do not match perfectly with values in the FPS DWH. This table is often used initially to start FPS-FDC integration until the tools and entity names are updated in the FDC system to match those in the MES and FPS DWH.

  • Schema: FPSINPUT

  • Tablespace: FPSDATA

  • Primary key: FDC_TOOL, FDC_CHAMBER

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


Column

Type

Nullable

Comment

FDC_TOOL

VARCHAR2(16)

N

The tool identifier within the FDC system. This could match the tool in the MES or DWH but this is not guaranteed.

FDC_CHAMBER

VARCHAR2(32)

N

The chamber identifier within the FDC system which is unique to that FDC_TOOL. This can be a string or number.

DESCRIPTION

VARCHAR2(256)

Tool desciption. This value is only used to display in the Dashboard. (* from FPSINPUT.EQP_TOOLS)

ENTITY

VARCHAR2(19)

N

The lowest level of the equipment hierarchy that an event can be logged against. Tools, subtools, shared parent tools, chambers, ports are all entities. Load locks are also included although we consider them as ports. (* from FPSINPUT.EQP_STATUS_VERIFY)

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)