data-dictionary
data-dictionary
Breadcrumbs

FPSADMIN.RTG_OPERATIONS

Data Dictionary

>

FPSADMIN Tables

> FPSADMIN.RTG_OPERATIONS

Table FPSADMIN.RTG_OPERATIONS"

Operation is the lowest level of routing in the MES. FPS only allows one tool per step so our step is an even lower level of routing than operation. For facilities which have the same requirement, this entire table can be left blank and we will use step as the operation in RTG_ROUTE_STEPS_PLUS. But for facilities which allow processing on multiple tools within an operation, we will populate this table and use operation as a grouping of step. Note that because operation can include multiple steps and therefore multiple eqp_families we cannot have any association to equipment by operation.

  • Schema: FPSADMIN

  • Tablespace: FPSDATA

  • Primary key: FACILITY, OPERATION

  • Foreign keys: RTG_OPERATIONS_FK_MODULE: FACILITY, OVR_OPERATION_MODULE REFERENCES FPSINPUT.GEN_MODULES (FACILITY, MODULE)


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)

OPERATION

VARCHAR2(50)

N

Operation is usually the primary level of routing in the MES and the level where the facility typically reports moves. FPS only allows one tool per step so our step is a lower level of routing than operation although both may be the same if the MES only allows one tool per operation. Note that because operation can include multiple steps and therefore multiple process families that we cannot have any association to equipment by operation.

DESCRIPTION

VARCHAR2(256)

Tool desciption. This value is only used to display in the Dashboard. (* from FPSINPUT.EQP_TOOLS)

DO_NOT_COUNT_OPER_MOVE_FROM

CHAR(1)

We might never want to count oper moves from certain special operations like staging or adhoc.

DO_NOT_COUNT_OPER_MOVE_TO

CHAR(1)

We might never want to count oper moves to certain special operations like staging or adhoc

OPERATION_DISPLAY

VARCHAR2(50)

N

All xxx_display columns are used in place of the column xxx for display purposes. The values of these columns can be changed at any time without having to worry about other tables referencing it.

OVR_OPERATION_MODULE

VARCHAR2(12)

Populating this field will force an operation to be assigned the specified module. If this field is not populated then the module that has the most processes in the operation will be assigned automatically.

SORT_ORDER_IN_DASH

NUMBER(5)

This is the sort order can be used in the Dashboard on the Top Operations Summary section. User can leave it blank and the DWH will sort this based on the DEFAULT_SORT_COLUMN_ID in DASH_C_CATEGORY_TABLES for the TOP_OPERATIONS table or they can configure it to display in certain order