Data Dictionary
>
FPSBASE Tables
> FPSBASE.GEN_WAFER_SIZES
Table FPSBASE.GEN_WAFER_SIZES"
List of wafer sizes in the facility. If the facility only has one size and we do not want to divide dashboard by wafer size then we should leave this table empty and all wafer_size columns blank.
-
Schema: FPSBASE
-
Tablespace: FPSDATA
-
Primary key: FACILITY, WAFER_SIZE
|
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) |
|
WAFER_SIZE |
VARCHAR2(8) |
N |
If the facility only has one wafer size then this column should be null in both RTG_PRDS and EQP_TYPES. If the facility has more than one wafer size then a value of null in EQP_TYPES means that those tools can run all wafer sizes. See column IS_ANY_WAFER_SIZE for details. |
|
BG_COLOR |
VARCHAR2(24) |
Background color assigned. BG_COLOR is in English like red or blue or light green and we look up the HTML color like #FF0000 in the GEN_COLORS table. BG_COLOR must be set manually but the FPSADMIN view BLD_POPULATE_COLORS will generate queries to randomly set bg_color for all values in a table. (* from FPSINPUT.GEN_CUSTOMERS) |
|
|
IS_DEFAULT_UNCHECK_ON_DASH |
CHAR(1) |
Flag used for lot group, wafer size, and line section that indicates whether this value should be unchecked by default on the Dashboard. All TW must be unchecked. (* from FPSINPUT.WIP_LOT_GROUPS) |
|
|
IS_DEFAULT_UNCHECK_ON_DCTA |
CHAR(1) |
Flag used for lot group, wafer size, and line section that indicates whether this value should be unchecked by default on Dynamic Cycle Time Analyzer. All TW must be unchecked. (* from FPSINPUT.WIP_LOT_GROUPS) |
|
|
IS_DEFAULT_UNCHECK_ON_FLCT |
CHAR(1) |
Flag used for lot group and wafer size that indicates whether this value should be unchecked by default on Finished Lot Cycle Time. Please note that line section does not apply to FLCT. All TW must be unchecked. (* from FPSINPUT.WIP_LOT_GROUPS) |
|
|
IS_DEFAULT_UNCHECK_ON_PERF |
CHAR(1) |
Flag used for lot group, wafer size, and line section that indicates whether this value should be unchecked by default on Performance. All TW must be unchecked. (* from FPSINPUT.WIP_LOT_GROUPS) |
|
|
IS_DEFAULT_UNCHECK_ON_WF |
CHAR(1) |
Flag used for lot group, wafer size, and line section that indicates whether this value should be unchecked by default on WIP Flush. All TW must be unchecked. (* from FPSINPUT.WIP_LOT_GROUPS) |
|
|
SORT_ORDER |
NUMBER(4) |
N |
This is used to sort within the grouping. SORT_ORDER always has a deferrable unique key to ensure uniqueness while allowing the user to make changes without erroring until the commit is attempted. Because of this you must be careful to not violate the unique key otherwise you will lose all of your edits. (* from FPSINPUT.GEN_FACILITIES) |
|
WAFER_SIZE_DISPLAY |
VARCHAR2(16) |
N |
The name of the wafer_size displayed on all dashboards and reports. We allow a longer more descriptive name here although often this will be the same as the wafer_size. |