Data Dictionary
>
FPSADMIN Tables
> FPSADMIN.DASH_W_TARGETS_PRD
Table FPSADMIN.DASH_W_TARGETS_PRD"
This table stores manual targets for the Dashboard by prd. Only the TURNS value is allowed which is used directly in the Dashboard application. 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: FPSADMIN
-
Tablespace: FPSDATA
|
Column |
Type |
Nullable |
Comment |
|---|---|---|---|
|
FACILITY |
VARCHAR2(6) |
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) |
|
|
PRD |
VARCHAR2(64) |
Prd determines the route which is used to process the lot in the facility and what tools, recipes, durables, etc. can be used at each step. Prd also determines the next facility for the lot when it finishes its route. For detailed information on prd vs. planprd see table comments in RTG_PLANPRDS. (* from FPSINPUT.RTG_PRDS) |
|
|
TARGET_TYPE |
VARCHAR2(36) |
||
|
TARGET_NOTES |
VARCHAR2(512) |
||
|
TARGET_VALUE |
NUMBER |