Data Dictionary
>
FPSAPP Tables
> FPSAPP.DASH_C_CATEGORY_TABLE_COLS
Table FPSAPP.DASH_C_CATEGORY_TABLE_COLS"
DASH_C_CATEGORY_TABLE_COLS is used to determine the configuration of the columns of tables in each category
-
Schema: FPSAPP
-
Tablespace: FPSDATA
-
Primary key: WEB_VERSION, FACILITY, CATEGORY, TABLE_ID, COLUMN_ID
|
Column |
Type |
Nullable |
Comment |
|---|---|---|---|
|
WEB_VERSION |
VARCHAR2(12) |
N |
|
|
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) |
|
CATEGORY |
VARCHAR2(36) |
N |
|
|
TABLE_ID |
VARCHAR2(100) |
N |
|
|
COLUMN_ID |
VARCHAR2(100) |
N |
|
|
COLUMN_ENTITY_MAX_NUM |
NUMBER |
||
|
COLUMN_WIDTH_PCT |
NUMBER(3) |
||
|
OVR_HEADER_DISPLAY |
VARCHAR2(100) |
Normally we get the column_header_display from DASH_C_COLUMNS but certain tables have limited width available so this override allows us to set a shorter header for a particular table. For example, we might set column_header_display for SHIFT_OPER_MOVES to Oper Moves in DASH_C_COLUMNS but we might override by setting this value to Op Mv for the ROUTE_GROUP_SUMMARY table which has limited width. In addition, the special value of "null!" sets column_header_display to null when it is normally populated in DASH_C_COLUMNS. |
|
|
OVR_SORT_ORDER |
NUMBER |
Please note that we cannot have a unique constraint on this column because we allow multiple values of null in the same web_version+facility+category+table_id. Unique constraints allow multiple records with null for all columns in the column but do not allow multiple values with a mixture of not null values. |
|
|
SHOULD_AUTO_HIDE |
CHAR(1) |
If the flag is set to Y then the module will be hidden on the Dashboard even if it has active WIP or moves. (* from FPSINPUT.GEN_MODULES) |
|
|
SHOULD_DISPLAY |
CHAR(1) |
||
|
SHOULD_DISPLAY_EXP |
CHAR(1) |
||
|
SHOULD_EXPORT |
CHAR(1) |