data-dictionary
data-dictionary
Breadcrumbs

FPSINPUT.DASH_W_TARGETS_PRCS_RG_LG

Data Dictionary

>

FPSINPUT Tables

> FPSINPUT.DASH_W_TARGETS_PRCS_RG_LG

Table FPSINPUT.DASH_W_TARGETS_PRCS_RG_LG"

This table stores manual targets for the Dashboard by process, route_group, and lot_group. Only the COMPLETES value is allowed which is used by the logic in WIP_REF_GOAL_EST_SHIFT that allocates COMPLETES targets down to the lowest level of prd-route-step-lot_group-priority. This table is not used in the Dashboard application. 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, PROCESS, ROUTE_GROUP, LOT_GROUP, 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)

PROCESS

VARCHAR2(50)

N

Process defines what occurs at a step. Different steps can share the same process if they are identical. Process should normally determine allowed tools and recipe although it can be overridden by step, route, prd, lot, and experiment for exceptions. Each process is dynamically assigned to one or more eqp_type-process_family combinations with use_pct. One process_family is determined to be primary. If grouping is done correctly, a process should only be one eqp_group with no crossover. (* from FPSINPUT.RTG_PROCESSES)

ROUTE_GROUP

VARCHAR2(36)

N

Route_group is the parent of route_family. Route_group is used on the Dashboard and other applications as a large grouping for filtering. At many sites this is referred to as technology. (* from FPSINPUT.RTG_ROUTE_GROUPS)

LOT_GROUP

VARCHAR2(8)

N

Lot_group is a grouping of lot_family and is the highest grouping in the lot type hierarchy. There should be only a few values for lot_group, i.e. Prod, Dev, TW. We group WIP and moves by lot_group on the dashboard and we group cycle time calculations by lot_group so this is an important field. (* from FPSINPUT.WIP_LOT_GROUPS)

TARGET_TYPE

VARCHAR2(36)

N

TARGET_NOTES

VARCHAR2(512)

TARGET_VALUE

NUMBER