FPSADMIN.DASH_P_COMING_LOTS_COLS

Data Dictionary

>

FPSADMIN Tables

> FPSADMIN.DASH_P_COMING_LOTS_COLS

Table FPSADMIN.DASH_P_COMING_LOTS_COLS"

See comments in DASH_REF_P_COMING_LOTS_COLS view.

Schema: FPSADMIN
Tablespace: FPSDATA
Primary key: FACILITY, ARRV_HRS_DISPLAY

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)
ARRV_HRS_DISPLAY	VARCHAR2(50)	N
ARRV_HRS_SORT	NUMBER
ARRV_IN_HOURS	NUMBER
FROM_ARRV_IN_HRS	NUMBER
HIDE_COL_IF_ZERO	CHAR(1)
INCLUDE_IN_SUMMARY	CHAR(1)
IS_BANK_COL	CHAR(1)
IS_NORMAL_HRS_COL	CHAR(1)