data-dictionary
data-dictionary
Breadcrumbs

FPSINPUT.DASH_W_TARGETS_OPERFAM

Data Dictionary

>

FPSINPUT Tables

> FPSINPUT.DASH_W_TARGETS_OPERFAM

Table FPSINPUT.DASH_W_TARGETS_OPERFAM"

This table stores manual targets for the Dashboard by operation family. Only the TURNS value is currently used and this is directly in the Dashboard application but other values could be used in the future if necessary. This table is not used in any FPSBASE objects. DASH_W tables can be populated in one of four ways: 1) manually, 2) by REF view linking to client databases like ETL, 3) with an APF report linking to client data sources like ETL, 4) via the GUI within the Dashboard.

  • Schema: FPSINPUT

  • Tablespace: FPSDATA

  • Primary key: FACILITY, OPERATION_FAMILY, TARGET_TYPE


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)

OPERATION_FAMILY

VARCHAR2(36)

N

Grouping of route-step that is completely dependent on routing information from MES. The primary use of this field is for filtering on Operations Dashboard. Unfortunately for our database structure and naming convention, this field no longer has any link to operation. This is because operation is used primarily for Oper Moves and it is normal for steps in an operation to belong to multiple MES routing groups. For example, a sink step and a furnace step and a measurement step are in the same operation but each step belongs to the appropriate sink/furnace/measurement MES routing groups which we store in operation family. Since Dashboard already uses both operation and operation_family extensively and independently, we decided not to rename either column but simply remove the link. Please note that operation family is similar to process family and in fact they are often the same. The key differences are that operation family has nothing to do with equipment and that comes straight from ETL with no complex logic. Process family is the link between routing and equipment for the Operations Dashboard and therefore has complex logic. (* from FPSINPUT.RTG_OPERATION_FAMILIES)

TARGET_TYPE

VARCHAR2(36)

N

TARGET_NOTES

VARCHAR2(512)

TARGET_VALUE

NUMBER