data-dictionary
data-dictionary
Breadcrumbs

FPSBASE.UPO_W_PROCSUBFAM_SOLUTION

Data Dictionary

>

FPSBASE Tables

> FPSBASE.UPO_W_PROCSUBFAM_SOLUTION

Table FPSBASE.UPO_W_PROCSUBFAM_SOLUTION"

Table to store output of use percent optimizer solution for tool usage across process_subfamilies. The solution is how many units a tool should run of the goal remaining for each process_subfamily.

  • Schema: FPSBASE

  • Tablespace: FPSDATA

  • Primary key: FACILITY, PROCESS_FAMILY, PROCESS_SUBFAMILY, TOOL, TIME_PERIOD

  • Foreign keys: UPO_W_PROCSUBFAM_SOLUTI_FK_FAC: FACILITY REFERENCES FPSINPUT.GEN_FACILITIES (FACILITY)


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)

PROCESS_FAMILY

VARCHAR2(50)

N

See https://help.inficonims.com/display/DW/Guide+to+Process+Families. (* from FPSINPUT.RTG_PROCESS_FAMILIES)

PROCESS_SUBFAMILY

VARCHAR2(100)

N

Route step family is used for the Dashboard to separate processes in a process family based on shared but limited assignments. It is also the base for GP subfamily. (* from FPSBASE.RTG_ROUTE_STEPS_PLUS)

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)

TIME_PERIOD

VARCHAR2(32)

N

the period (cycle) for each period. can be work_week, work_day, work_shift (* from FPSINPUT.RTG_PROCESS_COUNTERS)

NUM_UNITS

NUMBER