Data Dictionary
>
FPSINPUT Tables
> FPSINPUT.RTG_LINE_SECTIONS
Table FPSINPUT.RTG_LINE_SECTIONS"
List of line sections in the facility. If the facility only has one section and we do not want to divide dashboard by section then we should leave this table empty and the LINE_SECTION column blank.
-
Schema: FPSINPUT
-
Tablespace: FPSDATA
-
Primary key: FACILITY, LINE_SECTION
|
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) |
|
LINE_SECTION |
VARCHAR2(32) |
N |
Large grouping of the line, e.g. FEOL, BEOL, Cu, etc. There should be only a handful of values for the entire facility - or if the facility only has one section then we can leave this column blank. |
|
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) |
|
|
DESCRIPTION |
VARCHAR2(256) |
Tool desciption. This value is only used to display in the Dashboard. (* from FPSINPUT.EQP_TOOLS) |
|
|
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_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) |
|
|
IS_IGNORE_MOVABLE_TURNS |
CHAR(1) |
Movable turns differs from our standard turns calculation in that we ignore steps where lots are not expected to move like staging steps or logistics steps. Like is_ignore_turns, this flag can be set in either RTG_OPERATION_FAMILIES, RTG_PROCESSES, or RTG_LINE_SECTIONS. (* from FPSINPUT.RTG_OPERATION_FAMILIES) |
|
|
IS_IGNORE_TURNS |
CHAR(1) |
This flag is in RTG_OPERATION_FAMILIES, RTG_PROCESSES, and RTG_LINE_SECTIONS. If this flag is Y in any of the three tables then we do not count turns at the route-step towards the total for the facility. We also ignore turns at route-steps where we ignore WIP and/or moves which makes sense since turns is moves divided by WIP. Finally we ignore turns for certain line sections towards the facility average. (* from FPSINPUT.RTG_OPERATION_FAMILIES) |