FPSAPP Tables

LABEL_NAME

Many clients have their own names that they use to label certain fields in the DWH. For example, they refer to facility_segment as Quartile or they refer to route_group as Technology. This table allows us to display the client accepted display name on our applications, particularly in Options and Filters. The wafer_size column merits special mention because at most clients we use the wafer_size field to represent something other than wafer size. This is because wafer_size is part of the default filters for all web applications and because it is the only default filtering field on Dashboard which filters both processes and tools. In a perfect world, we might rename this field in the DWH to something more generic but in the real world the best solution is to be able to configure the display name used when labeling this field which we can do in this table.

Stores the roles for each application

USER_LOGIN

app_W_USERS table used to store user information for each user

APP_NAME, ROLE_NAME, USER_ID

app_W_USERS_ROLES table used to store role information for each user

FACILITY, PRD, ROUTE, LOT_TYPE, START_INST

See comments in CM_REF_B_PROD_STARTS view.

SCENARIO, FACILITY, ROUTE, WORKWEEK

CM_B_SCENARIOS_STARTS_VALIDATE is used to validate starts for the Capacity Model

This table stores global configurations for the Capacity Model application.

MENU_TYPE, MENU_VALUE

CM_C_MENU_ITEMS is used to configure the menu for the Capacity Model

FACILITY, CM_SCENARIO, COLUMN_NAME

This table stores a list of columns, configurable by site, that customers would like to see for informational purposes only when downloading a scenario template in the capacity model application. As an example, in a calculation scenario, THP data is shown by (RORP,SETP). It is often the case that this information is not easily human-readable, and that by adding a column like PROCESS, the template makes more sense to the end user.

FACILITY, RORP, STEP, EQP_TYPE

See comments in CM_REF_P_RORP_STEP_EQPTYPES view.

FACILITY, ROUTE, STEP, EQP_TYPE

See comments in CM_REF_P_ROUTE_STEP_EQP view.

FACILITY, EQP_TYPE, ROUTE, STEP, WORKWEEK, SCENARIO

Table contains override for throughput in the Capacity Model. This table is populated by upload from the CM website.

FACILITY, EQP_TYPE, ROUTE, STEP, WORKWEEK, SCENARIO

Table contains override for rework percentage in the Capacity Model. This table is populated by upload from the CM website.

FACILITY, EQP_TYPE, ROUTE, STEP, WORKWEEK, SCENARIO

Table contains override for sample percentage in the Capacity Model.. This table is populated by upload from the CM website.

FACILITY, EQP_TYPE, ROUTE, STEP, WORKWEEK, SCENARIO

Table contains override for use percentage in the Capacity Model. This table is populated by upload from the CM website.

SCENARIO, FACILITY, PRD, WORKWEEK

This table stores demand scenarios uploaded from Excel files to the capacity model web site.

SCENARIO, FACILITY, EQP_TYPE, WORKWEEK

This table stores eqptype scenarios uploaded from Excel files to the capacity model web site.

SCENARIO, FACILITY, ROUTE, WORKWEEK

This table stores starts scenarios uploaded from Excel files to the capacity model web site.

SCENARIO, FACILITY, EQP_TYPE, WORKWEEK

This table stores throughput+sampling+rework+yield scenarios (also called calculation scenarios) uploaded from Excel files to the capacity model web site.

Log table for any failures of Capacity Model scenario generation.

FACILITY, BANK, LOT_GROUP, PRTY_CTM_GROUP, ROUTE, STEP, PRD, PLANPRD

See comments in CTA_REF_P_BASE view.

START_WEEK, FACILITY, BANK, LOT_GROUP, PRTY_CTM_GROUP, ROUTE, STEP, PRD, PLANPRD

See comments in CTA_APD_P_BASE_WK view.

START_PERIOD, FACILITY, PRD, PLANPRD, LOT_GROUP

See comments in CTR_REF_B_FINISHED_BY_PERIOD view.

FACILITY, COMBINED_ROUTE, ROUTE_SEGMENT, STEP

See comments in CTR_REF_B_RRS_FOR_SAME_FAC_SEQ view.

FACILITY_ALL_OR_ONE, ITEM_NAME

Table to config colors for CTR chart.

FACILITY, TOOL, ENTITY, FROM_INST, TO_INST

This table exists solely to improve speed of Dashboard Tool State Gantt charts using DASH_P_GANTT_ENTITY_STATE. It has a NONUK rather than a PK because it can have duplicates for either from_inst or to_inst for a given facility, tool, entity therefore there is no reason to force a PK.

FACILITY, ROUTE, STEP, BANK, PRD, PLANPRD, LOT_TYPE, PLAN_PRIORITY, IS_NONSTD, START_PLAN_DAY

See comments in DASH_APD_B_H_PLAN_DAY_SUMMARY view.

FACILITY, ROUTE, STEP, BANK, PRD, PLANPRD, LOT_TYPE, PLAN_PRIORITY, IS_NONSTD, START_SHIFT

See comments in DASH_APD_B_H_SHIFT_SUMMARY view.

CATEGORY, KEY

This is a table for miscellaneous configurations for each category (page). In this case, for a configuration regarding a chart on the tool page, which would not fit in DASH_C_CATEGORY_TABLES. It is also not feasible to create a rigid DASH_C_CATEGORY_CHARTS or something of the sort, because many of the charts on the Dashboard are fundamentally different and would require different settings. A table like this allows for much more flexibility.

WEB_VERSION, FACILITY, CATEGORY, TABLE_ID

DASH_C_CATEGORY_TABLES is used to determine the configuration of tables in each category

WEB_VERSION, FACILITY, CATEGORY, TABLE_ID, COLUMN_ID

DASH_C_CATEGORY_TABLE_COLS is used to determine the configuration of the columns of tables in each category

This table is used to set the property of each column_id which are the same across all tables, categories, facilities, and web versions at each site.

FACILITY, SECTION, LINK_TEXT

List of custom reports to show links on Dashboard.

FACILITY, SECTION

Section grouping for custom reports for nicer display on Dashboard.

Options for time dropdown.

FACILITY, CRITERIA

Table to config redirect criteria for search

WEB_VERSION, FACILITY, CATEGORY, CODE

DASH_C_SPOTLIGHTS table is a config table for the spotlight for each page - including operations, modules, toolset, etc.

TARGET_TYPE

Table to configure allowed TARGET_TYPE values in DASH_P_TARGET tables, along with limits that will affect the coloring of these values on the Dashboard. See Help site for more information on target coloring: http://help.finalphasesystems.com/display/FD/Target+Coloring

WEB_VERSION

This is a table for global configuration values associated with each web version.

CATEGORY, TABLE_ID

This global table lists all of the rows which should be in DASH_C_CATEGORY_TABLES. CHK_LOAD_CFG checks that the rows indeed match up.

CATEGORY, TABLE_ID, COLUMN_ID

This global table lists all of the rows which should be in DASH_C_CATEGORY_TABLE_COLS. CHK_LOAD_CFG checks that the rows indeed match up.

COLUMN_ID

This global table lists all of the rows which should be in DASH_C_COLUMNS. CHK_LOAD_CFG checks that the rows indeed match up.

ITEM_DISPLAY

Table to configure the colors for each additional display values for the Gantt charts. It is possible that different sites might use different colors.

CATEGORY, CODE

This global table lists all of the rows which should be in DASH_C_SPOTLIGHTS. CHK_LOAD_CFG checks that the rows indeed match up.

FACILITY, ARRV_HRS_DISPLAY

See comments in DASH_REF_P_COMING_LOTS_COLS view.

FACILITY, ROW_DISPLAY

See comments in DASH_REF_P_COMING_LOTS_ROWS view.

INST, LOT_SEQ_WITHIN_SEC, LOT

See comments in DASH_P_CURR_SH_D_MOVES_CUSTOM procedure.

INST, LOT_SEQ_WITHIN_SEC, LOT

See comments in DASH_P_CURR_SH_D_MVINS_CUSTOM procedure.

FACILITY, TOOL

See comments in DASH_REF_P_CV_AVAIL view.

FACILITY, TOOL, ENTITY

See comments in DASH_REF_P_CV_AVAIL_ENTITY view.

END_PLAN_DAY, FACILITY, ECT_STATE, PROCESS_STATE, ROUTE, PRD, LOT_GROUP, PLAN_PRIORITY, PROCESS, BANK

See comments in DASH_APD_P_ECT_WIP_DAY_HIST view.

END_HOUR_OF_SHIFT_OR_DAY, FACILITY, ROUTE, PRD, LOT_GROUP, PLAN_PRIORITY, PROCESS, BANK, PROCESS_STATE, ECT_STATE

See comments in DASH_P_ECT_WIP_HOURLY_CUSTOM procedure.

END_SHIFT, FACILITY, ECT_STATE, PROCESS_STATE, ROUTE, PRD, LOT_GROUP, PLAN_PRIORITY, PROCESS, BANK

See comments in DASH_APD_P_ECT_WIP_SHIFT_HIST view.

LOT, OVERALL_LOT_SEQ_NUM

See comments in DASH_REF_P_GANTT_PRIORITY_LOTS view.

FACILITY, EVENT_KEY, LOT

See comments in DASH_REF_P_LINE_HOLDS view.

FACILITY, OPERATION

See comments in DASH_REF_P_OPERATIONS view.

FACILITY, PROCESS

See comments in DASH_REF_P_PROCESSES view.

FACILITY, PROCESS_SUBFAMILY, PROCESS_FAMILY

See comments in DASH_REF_P_PROCESS_SUBFAMILIES view.

FACILITY, TOOL

See comments in DASH_REF_P_TOOL_WIP_METRICS view.

TOOL, START_INST

See comments in DASH_REF_P_TOOL_WIP_NEXT_30D view.

LOT, STEP, ROUTE, FACILITY

See comments in DASH_REF_P_WIP_STEP_FUTURE view.

FACILITY, MODULE

Table to store labor availability by module.

FACILITY, EVENT_ID

Stores override to the maintenance event information in EQP_MNT_FUTURE made within the Maintenance Manager web application. Here we can only override certain fields for existing events. In MNT_W_FUTURE_ADD we can create new maintenance events which are not already in EQP_MNT_FUTURE.

FACILITY, EVENT_ID, MNT_TECH_USERNAME

Stores the association between maintenance technicians and a maintenance event instance, allowing for multiple technicians to be assigned to an instance.

FACILITY, TARGET_TYPE

Used to store manual targets by facility. When lower level targets are also provided, the targets in this table will override the lower level targets. The COMPLETES value is used by the logic in WIP_REF_GOAL_EST_SHIFT that allocates COMPLETES targets down to the lowest level of prd-route-step-lot_group-priority. All other values in this table are used directly in the Dashboard application and not in any FPSBASE objects. DASH_W tables can be populated in one of four ways: 1) manually, 2) by REF view linking to client databases like ETL, 3) with an APF report linking to client data sources like ETL, 4) via the GUI within the Dashboard.

FACILITY, MODULE, TARGET_TYPE

This table stores manual targets for the Dashboard by module. The COMPLETES value is used by the logic in WIP_REF_GOAL_EST_SHIFT that allocates COMPLETES targets down to the lowest level of prd-route-step-lot_group-priority. All other values in this table are used directly in the Dashboard application and not in any FPSBASE objects. DASH_W tables can be populated in one of four ways: 1) manually, 2) by REF view linking to client databases like ETL, 3) with an APF report linking to client data sources like ETL, 4) via the GUI within the Dashboard.

FACILITY, MODULE, LOT_PRIORITY, TARGET_TYPE

This table stores manual targets for the Dashboard by module and priority. All values in this table are used directly in the Dashboard application and not in any FPSBASE objects. DASH_W tables can be populated in one of four ways: 1) manually, 2) by REF view linking to client databases like ETL, 3) with an APF report linking to client data sources like ETL, 4) via the GUI within the Dashboard.

FACILITY, OPERATION, TARGET_TYPE

This table stores manual targets for the Dashboard by operation. All values in this table are used directly in the Dashboard application and not in any FPSBASE objects. DASH_W tables can be populated in one of four ways: 1) manually, 2) by REF view linking to client databases like ETL, 3) with an APF report linking to client data sources like ETL, 4) via the GUI within the Dashboard.

FACILITY, OPERATION_FAMILY, TARGET_TYPE

This table stores manual targets for the Dashboard by operation family. Only the TURNS value is currently used and this is directly in the Dashboard application but other values could be used in the future if necessary. This table is not used in any FPSBASE objects. DASH_W tables can be populated in one of four ways: 1) manually, 2) by REF view linking to client databases like ETL, 3) with an APF report linking to client data sources like ETL, 4) via the GUI within the Dashboard.

FACILITY, PROCESS, LOT_TYPE, TARGET_TYPE

This table stores manual targets for the Dashboard by process and lot_type. Only the COMPLETES value is allowed which is used by the logic in WIP_REF_GOAL_EST_SHIFT that allocates COMPLETES targets down to the lowest level of prd-route-step-lot_group-priority. This table is not used in the Dashboard application. DASH_W tables can be populated in one of four ways: 1) manually, 2) by REF view linking to client databases like ETL, 3) with an APF report linking to client data sources like ETL, 4) via the GUI within the Dashboard.

FACILITY, PROCESS, ROUTE_GROUP, LOT_GROUP, TARGET_TYPE

This table stores manual targets for the Dashboard by process, route_group, and lot_group. Only the COMPLETES value is allowed which is used by the logic in WIP_REF_GOAL_EST_SHIFT that allocates COMPLETES targets down to the lowest level of prd-route-step-lot_group-priority. This table is not used in the Dashboard application. DASH_W tables can be populated in one of four ways: 1) manually, 2) by REF view linking to client databases like ETL, 3) with an APF report linking to client data sources like ETL, 4) via the GUI within the Dashboard.

This table stores manual targets for the Dashboard by prd. Only the TURNS value is allowed which is used directly in the Dashboard application. This table is not used in any FPSBASE objects. DASH_W tables can be populated in one of four ways: 1) manually, 2) by REF view linking to client databases like ETL, 3) with an APF report linking to client data sources like ETL, 4) via the GUI within the Dashboard.

FACILITY, LOT_PRIORITY, TARGET_TYPE

Used to store manual targets by priority. All values in this table are used directly in the Dashboard application and not in any FPSBASE objects. DASH_W tables can be populated in one of four ways: 1) manually, 2) by REF view linking to client databases like ETL, 3) with an APF report linking to client data sources like ETL, 4) via the GUI within the Dashboard.

This table stores manual targets for the Dashboard by process. The COMPLETES value is used by the logic in WIP_REF_GOAL_EST_SHIFT that allocates COMPLETES targets down to the lowest level of prd-route-step-lot_group-priority. All other values in this table are used directly in the Dashboard application and not in any FPSBASE objects. DASH_W tables can be populated in one of four ways: 1) manually, 2) by REF view linking to client databases like ETL, 3) with an APF report linking to client data sources like ETL, 4) via the GUI within the Dashboard.

This table stores manual targets for the Dashboard by process family. The COMPLETES value is used by the logic in WIP_REF_GOAL_EST_SHIFT that allocates COMPLETES targets down to the lowest level of prd-route-step-lot_group-priority. All other values in this table are used directly in the Dashboard application and not in any FPSBASE objects. DASH_W tables can be populated in one of four ways: 1) manually, 2) by REF view linking to client databases like ETL, 3) with an APF report linking to client data sources like ETL, 4) via the GUI within the Dashboard.

FACILITY, ROUTE_GROUP, LOT_GROUP, TARGET_TYPE

This table stores manual targets for the Dashboard by route_group and lot_group. Only the COMPLETES, OPER_MOVES, and WIP values are allowed which are used by the logic in WIP_REF_GOAL_EST_SHIFT that allocates targets down to the lowest level of prd-route-step-lot_group-priority. This table is not used in the Dashboard application. DASH_W tables can be populated in one of four ways: 1) manually, 2) by REF view linking to client databases like ETL, 3) with an APF report linking to client data sources like ETL, 4) via the GUI within the Dashboard.

FACILITY, BANK, LOT_GROUP, PRTY_CTM_GROUP, ROUTE, STEP, PRD, PLANPRD, ROUTE_FAMILY

See comments in ECTA_REF_P_BASE view.

START_WEEK, FACILITY, BANK, LOT_GROUP, PRTY_CTM_GROUP, ROUTE, STEP, PRD, PLANPRD

See comments in ECTA_APD_P_BASE_WK view.

START_PERIOD, FACILITY, PRD, PLANPRD, LOT_GROUP

See comments in ECTFL_REF_B_FINISHED_BY_PERIOD view.

ISSUE_TYPE

This is a list of allowable issue types for feedback items

STATUS

This is a list of allowable statuses for feedback items

ID

Table stores information about all feedbacks from all applications.

FEEDBACK_ID, COMMENT_ID_NUM

In order to track comments and emails sent on specific feedbacks, we need a table that holds the comments. This table uses the FBK_GET_FEEDBACK_ID_NUM function to increments the id numbers of the feedback comments.

This table holds FabGuard Broker API Database activity if logging is enabled in the FabGuard procedures.

ID

Stores the upgrade date and version of FabRecover software

Stores the details for each FabRecover maintenance definition version

ID

Makes the connection between the tasks and the maintenance definition version, where a procedure is a group of maintenance tasks

VERSION_NAME, APPROVER_USER_NAME

Stores the current approvers required for the maintenance definition version

ID

Stores the change log of changes made to maintenance definition versions

EQP_TYPE, FACILITY, VERSION_NAME

Stores the relationships between FabRecover maintenance definition versions and equipment types, both being foreign keys in this table

MESSAGE_TYPE, EQP_TYPE, FACILITY

Stores the messages used in FabRecover for communication about safety reminders and other message types

ID

Stores the change log of changes made to FabRecover messages

ID

Stores unique maintenance event sessions and session details for a given instance of a maintenance event

MNT_SESSION_ID, INST_UTC

Stores comments related to a maintenance event session which are inputted by a user, primarily for cancellation of maintenance events, but may be used for other purposes as well

MNT_SESSION_ID, REPORT_CAPTION

Stores pdf report of completed maintenance session

MNT_SESSION_ID, FR_USER_LOGIN

Stores a history of user safety acknowledgment for each mnt session as required by FabRecover configuration

ID

Stores the tasks which are part of a maintenance session

MNT_SESSION_TASK_ID, VARIABLE_NAME

Stores each form input from a maintenance task

MNT_SESSION_TASK_ID, UNIQUE_FILE_NAME

Stores files uploaded by users during a maintenance session task.

ID

Stores maintenance task data in LogicNets required format

MNT_SESSION_TASK_ID, FR_USER_LOGIN, INST_START_UTC

Stores the interactions between users and maintenance session tasks

MNT_TASK

Stores tasks which are subcomponents of a maintenance event as defined in FabRecover

ID

Stores the change log of changes made to maintenance task definitions

EQP_TYPE, MNT_TASK

Stores the relationships between FabRecover tasks and equipment types, both being foreign keys in this table

VERSION_NAME

Stores the definition details for each FabRecover task version

ID

Stores the change log of changes made to maintenance task version definitions

VERSION_NAME, APPROVER_USER_NAME

Stores the current approvers required for the maintenance task version

EQP_TYPE, FACILITY, USER_NAME

Stores the relationships between users in FabRecover and equipment types

ID

LogicNets stores all instances workflows in this table. Each instance of a workflow is uniquely identified by its id, this id will be used throughout the other tables for linking to the workflow.

ID

LogicNets stores the link between parent and child workflows in this table. This allows the system to execute parallel workflows and step a parent workflow forward whenever a task in a child workflow is completed.

ID

LogicNets stores persistent workflow data as a single CLOB in this table. All tasks from the same workflow share the same data container, so you can pass this data between tasks in the same workflow.

ID

LogicNets stores all instances of tasks from all workflows in this table and provides each instance of a task a unique identifier. The system stores this id in the workflow_instance column of this table. With this ID you can retrieve all tasks associated with a particular workflow.

ID

LogicNets stores tags associated with each task in this table. Each task tag is linked to a task by its id.

FACILITY, ROUTE, STEP

See comments in GP_REF_B_ROUTE_STEPS view.

FACILITY, COMMON_STEP

Goal planner configuration of COMMON_STEP parameters. Used as input when calculating goals for the shift.

FACILITY, COMMON_STEP, ROUTE

Goal planner configuration of COMMON_STEP parameters that apply to specified ROUTEs. Used as input when calculating goals for the shift.

FACILITY

Goal planner configuration of FACILITY parameters for drum and line balance. Used as input when calculating goals and Scheduler priority.

FACILITY, PROCESS

Goal planner configuration of PROCESS parameters. Used as input when calculating goals for the shift.

FACILITY, PROCESS, ROUTE

Goal planner configuration of PROCESS parameters that apply to specified ROUTESs. Used as input when calculating goals for the shift.

Goal planner configuration of GP_SUBFAMILY parameters. Used as input when calculating goals for the shift.

FACILITY, GP_SUBFAMILY_OR_EACH, ROUTE_OR_EACH

Goal planner configuration of GP_SUBFAMILY parameters that apply to specified ROUTEs for each COMMON_STEP. Used as input when calculating goals for the shift.

FACILITY, GP_SUBFAMILY_OR_EACH, ROUTE_OR_EACH

Goal planner configuration of GP_SUBFAMILY parameters that apply to specified ROUTEs for each PROCESS. Used as input when calculating goals for the shift.

FACILITY, ROUTE_SECTION, ROUTE_OR_EACH

Goal planner configuration of ROUTE_SECTION parameters that apply to specified ROUTEs for each COMMON_STEP. Used as input when calculating goals for the shift.

FACILITY, ROUTE_SECTION, ROUTE_OR_EACH

Goal planner configuration of ROUTE_SECTION parameters that apply to specified ROUTEs for each PROCESS. Used as input when calculating goals for the shift.

FACILITY, ROUTE, STEP

See comments in GP_REF_P_PRIORITY_DRUM view.

FACILITY, ROUTE, STEP

See comments in GP_REF_P_PRIORITY_LINE_BALANCE view.

FACILITY, ROUTE, STEP

See comments in GP_REF_P_ROUTE_STEPS view.

FROM_MSO_INST, FACILITY, SMP_RULE_ID, FROM_MSO_TOOL, CHAMBER, LOT

See comments in MSOUI_APD_B_TOOL_RISK_WK_HIST view.

CONFIG_NAME

Configuration table for the MSO UI. This configuration table takes in configuration key value pairs to allows setting default behavior and control of UI display settings.

TRANSACTION_ID

Master MSO transaction history. All changes are made at lower level tables. One record for each transaction is stored in this table and the transaction id is what links all the sub tables together based on the parent_transaction_id.

FACILITY

This table is always empty and is a placeholder for a client developed view. Eventually we will change this and build the carrier movement logic into NextMove with appropriate configuration.

FACILITY, BAY, BAY_ROTATION

A table that contains the list of bays that are paired for baymonitor rotation

BAY, FACILITY, OBJ_ID, OBJ_TYPE

A table that contains the objects per BAY for My lists feature within NextMove

FACILITY, CARRIER

nmv_w_carrier_claims is used to manage claims on carriers by vehicles and users made in the NextMove UI. Only one claim can be made on a carrier at a given time

This table will hold NextMoveService API Database activity

To record the carrier delivery state change history.

FACILITY, RETICLE

Table to store override moves to be made to and from a tool internal reticle library, useful for testing or integration with an external system.

Log history of next destination for each call to the NMV_IRL_NEXT_DESTINATION procedure.

Log history of next destination for each lot for NextMove.

LIST_ID

A table that contains list details and user associations

LIST_ID, FACILITY, OBJ_ID, OBJ_TYPE

A table that contains the objects per LIST_ID for My lists feature within NextMove

LIST_ID, FACILITY, TOOL

A table that contains the tools per LIST_ID for My Tools feature within NextMove. This table has a foreign key on EQP_TOOLS with "on delete cascade" which means that records will be automatically deleted when a tool is deleted from EQP_TOOLS. Normally this is a good feature but in the case where you have a blip with your EQP_TOOLS ETL and accidentally delete a tool (or all tools) and then quickly reinsert you will have to manually rebuild this table.

LIST_ID

A table that contains My Tools list details and user associations

FACILITY, PROCESS_FAMILY

This table will hold process families that the client needs to be filtered from BAYMONITOR in NextMove

INSERTED_TIME, LOT, STEP, ROUTE, FACILITY

Logging table for external system calls

Log history of next destination for each call to the NMV_RETICLE_STOCKER_NEXT_DEST procedure.

This table allows the drop down lists in the Performance Application to be configurable

FACILITY, LOT_GROUP, PLAN_PRIORITY, WIP_MODULE, BANK, ROUTE, WAFER_SIZE, ROUTE_FAMILY, ROUTE_GROUP, OPERATION_FAMILY, PROCESS_FAMILY, LINE_SECTION, IS_IGNORE_WIP, IS_IGNORE_MOVES, CALENDAR_DAY

See comments in PERF_APD_P_H_COMP_WIP_DAY view.

FACILITY, LOT_GROUP, PLAN_PRIORITY, WIP_MODULE, BANK, ROUTE, WAFER_SIZE, ROUTE_FAMILY, ROUTE_GROUP, OPERATION_FAMILY, PROCESS_FAMILY, LINE_SECTION, IS_IGNORE_WIP, IS_IGNORE_MOVES, START_MONTH

See comments in PERF_APD_P_H_COMP_WIP_MONTH view.

FACILITY, LOT_GROUP, PLAN_PRIORITY, WIP_MODULE, BANK, ROUTE, WAFER_SIZE, ROUTE_FAMILY, ROUTE_GROUP, OPERATION_FAMILY, PROCESS_FAMILY, LINE_SECTION, IS_IGNORE_WIP, IS_IGNORE_MOVES, START_SHIFT

See comments in PERF_APD_P_H_COMP_WIP_SHIFT view.

FACILITY, LOT_GROUP, PLAN_PRIORITY, WIP_MODULE, BANK, ROUTE, WAFER_SIZE, ROUTE_FAMILY, ROUTE_GROUP, OPERATION_FAMILY, PROCESS_FAMILY, LINE_SECTION, IS_IGNORE_WIP, IS_IGNORE_MOVES, START_WEEK

See comments in PERF_APD_P_H_COMP_WIP_WEEK view.

FACILITY, ROUTE, STEP, START_SHIFT

See comments in PERF_APD_P_H_LINEBAL_SHIFT view.

LOT, FACILITY, START_SHIFT

See comments in PERF_APD_P_H_OTD_SHIFT view.

FACILITY, TOOL, CARRIER, CLAIMED_START

Carrier Claim Hist

FACILITY, CREATE_INST

This table is used to store information we want to display to the user during upgrades or at other times.

FACILITY, RETICLE

Table to store override moves to be made to and from a tool internal reticle library, useful for testing or integration with an external system.

Log history of next destination for each call to the RM_IRL_NEXT_DESTINATION procedure.

INSERTED_INST, FACILITY, LOT, ROUTE, STEP, TOOL

Reticle Manager table to store history of lots with no reticle.

Log history of next destination for each call to the RM_RETICLE_STOCKER_NEXT_DEST procedure.

WEB_CONFIG_ID, APP_SETTING_ID

This table is used to store the app setting details

FACILITY, SLOT_NUM

This table is used to store the pod/carrier slot num configuration. currently it needs to be set by facility level, but in the future if it needs to be set by different way, then we can do it too

FACILITY, CARRIER, SLOT_NUM

This table is used to store the pod/carrier slot state. it can be either UP or DOWN; if it set to DOWN, then the scheduler will try not to use this slot

FACILITY, SCHED_GROUP, TOOL, CONFIG_ID, SETTING_ID

This table is used to store the eqp tool setting details

FACILITY, SCHED_GROUP, EQP_TYPE, CONFIG_ID

This table is to store the basic configuration for each eqp type. Please note that this table has data for older config_id values and therefore does not have a foreign key on FPSINPUT.EQP_TYPES although the current config_id should typically only have values in EQP_TYPES.

FACILITY, SCHED_GROUP, EQP_TYPE, CONFIG_ID, SETTING_ID

This table is used to store the eqp type setting details

FACILITY, SCHED_GROUP, PROCESS_GROUP, CONFIG_ID

This table is to store the basic configuration for each process group. Please note that this table has data for older config_id values and therefore does not have a foreign key on FPSINPUT.RTG_PROCESS_GROUPS although the current config_id should typically only have process groups that are in RTG_PROCESS_GROUPS.

FACILITY, SCHED_GROUP, PROCESS_GROUP, CONFIG_ID, EVALUATION_ID

This table is used to store the evaluation information for each process group.

FACILITY, SCHED_GROUP, PROCESS_GROUP, CONFIG_ID, SETTING_ID

This table is used to store process groups settings details

This table is to store the basic configuration for each sched group.

This table is used to store the evaluation information for each sched group.

FACILITY, SCHED_GROUP, CONFIG_ID, KPI_ID

This table contains there Scheduler KPI configuration for each sched_group

JOB_NAME

To configure how to run sched job

This table is used to store other durable families.

FACILITY, MNT_NAME

This table is used for the durable Maintenances configurations

FACILITY, DURABLE_STATE

This table is used for the durable state configurations

EVALUATION_ID

Custom display values for each evaluation used for this site

FACILITY

This table is used for the facilities configurations

This table is used to configure the # steps away and hours of the first step of the lot to schedule based on the sched-group and lot-group

FACILITY, SCHED_GROUP, HOST_TYPE, DATABASE_NAME

This table is used to define which server to run the scheduler for each sched group.

FACILITY, SCHED_GROUP, GBL_SORT

This table is used to define the sched rank for each gbl_sort for each sched group.

This table is used to define the sched rank and % of process time look ahead (for batching) for each priority for each sched group.

FACILITY, SCHED_GROUP, LOT_TYPE

This table is used to define the sched weight for each lot type for each sched group.

FACILITY, SCHED_GROUP, PERM_RANK

This table is used to define the sched weights for each perm rank - sched group.

FACILITY, SCHED_GROUP, PRE_BATCH_ID

This table is used to configure the pre-batch criterias.

FACILITY, SCHED_GROUP, PRE_BATCH_ID, PROCESS_KEY

This table is used to configure the pre-batch sequence.

FACILITY, SCHED_GROUP, RQD_SETUP

This table is used to denote the server host for service, reporting, web.

FACILITY, LINK_ID

This table is used to determine if the next step is required to scheduled the current step

PARAMETER_NAME

this table is used to store all parameters

FACILITY, SCHED_RANK

This table is used to setup the sched rank for different lot priority

FACILITY, TOOL_TYPE, FROM_SETUP, TO_SETUP, DURABLE_FAMILY

This table is used to store the required durable while making setup change

This table is to store the basic evaluations templates for each process group.

FACILITY, SCHED_GROUP, PROCESS_GROUP, TEMPLATE_ID, EVALUATION_ID

This table is used to store the evaluation information for process group template.

FACILITY, SCHED_GROUP, TEMPLATE_ID

This table is to store the basic evaluations templates for each sched group.

This table is used to store the evaluation information for sched group template.

FACILITY, TOOL

This table is used for the tool configurations

APP_SETTING_ID

sch_g_app_settings table used to store global app-settings

This table is to store the default configuration for each sched group.

This table is used to store the default evaluation information for each sched group.

SCHED_GROUP, KPI_ID

This table contains the default Scheduler KPI configuration for each sched_group

SETTING_ID

table used to store global eqp-tool settings.

SETTING_ID

table used to store global eqp-type settings.

EVALUATION_ID

This table is used to setup all basic evaluations that will be used on the sched group weights.

JOB_TYPE

This table is used to indicate the different job type, for example process job and process setup job.

KPI_ID

This table is used to setup all basic kpi list that will be used on the sched group.

SETTING_ID

table used to store global process group settings.

SCHED_STATE

List of FPS Scheduler Sched States, including RESERVE, TIMER, COMING, MISSING

FACILITY, DURABLE, SCHED_SORT

See comments in SCH_REF_P_DISPATCH_DURABLES view.

FACILITY, DURABLE, EVENT, START_INST

This table is for storing sched events for each durable.

FACILITY, RUN_ID

This table is for storing snapshot ids that are too be purged from the system.

This table is used to store all of logs.

This table is used to store the historical refresh time for the kitting page.

RUN_ID, SCHED_GROUP, FACILITY

This table is used to store the historical run data every time when the scheduler runs.

This table is used to store the historical run data on the carriers

This table is used to store the historical run data on carrier assignment

This table is used to store the historical run data on ch-path assignments for each lot where they can run

This table is used to store the historical run data on durables

see comments in fpsinput.rtg_durable_asgns_combo

This table is used to store the historical run data on durable assignments

this table is used to store the historical run data on durable_family

This table is used to store the historical run data on durable stockers

This table is used to store the historical run data on tool entities.

This table is used to store the historical run data on process changes to ignore

Contains the scheduler snapshot data for the specific recipe sequences. See the following view fpsapp.sch_p_eqp_pattern_hist

This table is used to store the historical run data on process limits

Contains the scheduler snapshot data for the specific recipe sequences. See the following view FPSAPP.SCH_P_EQP_PROCESS_PATTERNS and tables FPSINPUT.SITE_EQP_PROCESS_PATTERNS, and FPSINPUT.SITE_EQP_PROCESS_PATTERN_SEQ for more details.

This table is used to store the historical run data on process change from one to another one

This table is used to store the historical run data on eqp-type and recipe

This table is used to store the historical run data on eqp-type and recipe

This table is used to store the historical run data on lots

This table is used to store lot sched details to lot step level

This table is used to store the historical run data on resource counter.

This table is used to store the historical run data on resource counter.

This table is used to store the historical run data on process group.

This table is used to store the historical run data on coming queue steps

This table is used to store the historical run data on lots queue stopped

This table is used to store the historical run data on lot queue timer for both in the timer loop or will be in the timer loop

This table is to store all historical sched jobs info.

This table is used to store the historical run data on setup information

This table is used to store the historical run data on threading assignments

This table is used to store sched details to tool level

This table is used to store the historical run data on tool assignments for each lot where they can run

This table is used to store the historical run data on tool events

This table is used to store the historical run data on tool pod ports

This table is used to store the historical run data on primary stockers for the tools

This table is used to store the historical run data for the tool types.

This table is used to store the historical run data on zones for the tools

Scheduler Snapshot Table to store manual WIP_STEP_HIST entries

This table is used to store all of trigger coming from wip and tool events.

This table is to used to store the trigger information.

This table is used to store the user while visiting.

JOB_NAME

To log sched job

This table is used to store the user while visiting.

This table is for storing app pool recycle requests when the scheduler is in an unhealthy state.

FACILITY, SCHED_GROUP, CARRIER, DURABLE_TO_UNLOAD, TIME_TO_UNLOAD, DURABLE_TO_LOAD, TIME_TO_LOAD

this table is used to store all scheduled info for carrier.

RUN_ID, FACILITY, SCHED_GROUP, TOOL, DURABLE, JOB_ID, SCHED_START_INST

This table is to store all sched jobs info.

FACILITY, DURABLE

This table is to store the schedule of durable inspections.

FACILITY, SCHED_GROUP

store run_id for successful scheduler run for each sched group

RUN_ID, FACILITY, SCHED_GROUP

This table is to used to store the summary for each scheduler run.

RUN_ID, FACILITY, SCHED_GROUP

This table is to used to store the summary for each scheduler run.

FACILITY, SCHED_GROUP

This table is to used to store the summary statistics for current scheduler run.

FACILITY, SCHED_GROUP, RUN_ID

This table is to used to store the summary statistics for each scheduler run.

This table is used to store scheduled event for all tools.

FACILITY, CREATE_INST

This table is used to store information we want to display to the user during upgrades or at other times.

APPLICATION_ID

Contains the applications (ex: Dashboard, NextMove, Factory Forum).

AUTHENTICATION_TYPE

Contains the various types of authentication allowed for each user (Database, ActiveDirectory, etc...).

USER_STATE

Contains the various states of users (Enabled, Disabled, etc...).

GROUP_ID

Contains the list of user groups associated with each application. (Ex: Administrators, Super Users).

GROUP_ID, ROLE_ID

Contains the associations of groups to roles.

ROLE_ID

Contains the list of roles for each application. System roles such as "Edit Application Security" are automatically created and should not be deleted..

USER_ID

Contains the list of users who can log in to the applications.

USER_ID, GROUP_ID

Contains the associations of users to groups.

USER_ID, ROLE_ID

Contains the associations of users to roles.

EVENT_DEFINITION, LOGGED_ENTITY

Adhoc based Maintenance events. These are specific happening of an event_definition on an entity. If an event-definition happens on an entity, populatiing this is how we know about it. Only populatiing EVENT_DEFINITION and LOGGED_ENTITY are required. This table is effectivly an override table. It includes attributes that exist in MNT_EVENT_DEFINITIONS_ADHOC, if they exist in here they will override the values at the definition-level.

EVENT_DEFINITION, LOGGED_ENTITY

Counter (cntr) based Maintenance events. These are specific happening of an event_definition on an entity. If an event-definition happens on an entity, populatiing this is how we know about it. Only populatiing EVENT_DEFINITION and LOGGED_ENTITY are required. This table is effectivly an override table. It includes attributes that exist in MNT_EVENT_DEFINITIONS_OCAP, if they exist in here they will override the values at the definition-level.

EVENT_DEFINITION, LOGGED_ENTITY

Out of Control Action Plan (OCAP) Maintenance events. These are specific happening of an event_definition on an entity. If an event-definition happens on an entity, populatiing this is how we know about it. Only populatiing EVENT_DEFINITION and LOGGED_ENTITY are required. This table is effectivly an override table. It includes attributes that exist in MNT_EVENT_DEFINITIONS_OCAP, if they exist in here they will override the values at the definition-level.

EVENT_DEFINITION, LOGGED_ENTITY

Time based Maintenance events. These are specific happening of an event_definition on an entity. If an event-definition happens on an entity, populatiing this is how we know about it. Only populatiing EVENT_DEFINITION and LOGGED_ENTITY are required. This table is effectivly an override table. It includes attributes that exist in MNT_EVENT_DEFINITIONS_OCAP, if they exist in here they will override the values at the definition-level.

EVENT_GROUP, EVENT_DEFINITION

Adhoc based maintenance definitions define a group of events to be performed on many entities. These event definitions can be a little more free form than our other definitions. These could require that the tool stop processing WIP a specific time in the future. This table should include all possible ad hoc events that can occur. These events will not have a frequency but could repeat. There are three different type of ad hoc events that we see. First, ones that are an emergency and goes on the schedule now and no lots can be started. Second, something that needs to get done at some point but it is not super critical so lots can keep running till it is done. An example of this second case is restarting a tool computer. Third, ad hoc events that need to happen at a specific point in the future, for these events lots can run until that specific point in time. An example of this third case is when a vendor is scheduled to be on-site and they need to tool to be available at a specific time. This table includes attributes that exist in MNT_EVENTS if they exist in MNT_EVENTS they will override the values at the family level.

EVENT_GROUP, EVENT_DEFINITION

Counter (CNTR) based Maintenance definitions define a group of events to be performed on many entities. These counters could be based on lots, wafers, or any time of consumable material. This table includes attributes that exist in MNT_EVENTS if they exist in MNT_EVENTS they will override the values at the family level.

EVENT_GROUP, EVENT_DEFINITION

Out of Control Action Plan (OCAP) based maintenance definitions define a group of events to be performed on many entities. All possible OCAP tasks that can occur. These will not have a frequency but could repeat and could be tool or WIP actions. They are tied to a control application (E.G. SPC or FabGuard). This table includes attributes that exist in MNT_EVENTS if they exist in MNT_EVENTS they will override the values at the family level.

EVENT_GROUP, EVENT_DEFINITION

Time based maintenance definitions define a group of events to be performed on many entities. For example, a definition could be a weekly PM that is performed weekly on a group of tools that are all the same. (e.g. weekly PM). This table includes attributes that exist in MNT_EVENTS if they exist in MNT_EVENTS they will override the values at the family level.

EVENT_CLASS, EVENT_GROUP

This table denotes the two highest levels in the Maintenance Event Hierarchy. This level is entirely up to the site to define. The highest level is Event_class, this can be set to whatever the site would like to configure. Event_class is a collection of Event_groups. Event_Groups are a collection of similar event_definitions, these event groups can be whatever the site would like to configure.

MNT_EVENT, FACILITY

Stores the definition of maintenance events definition created by SMMS suite of applications. The application will control what columns are populated.

ID

Stores the change log of changes made to maintenance event definitions

Configuration table to set parameter values for sysmonitor alerts

In this table, we set specific configurations for various checks based on view_name. Records in this table are optional and all SYSMNTR_P_CHK views will appear in SYSMNTR_P_CHECKS. The view has default configuration to use in the case that no record exists in this table.

TABLESPACE_NAME

Configuration table to set percentage limit at which to send email/text alerts in SysMonitor.

See comments in SYSMNTR_APD_P_CONFORMANCE_HIST view.

This table stores configuration information for the Use Percent Optimizer.

EQP_TYPE

This table is a temporary storage location for the equipment type information used by the Use Percent Optimizer

PROCESS

This table is a temporary storage location for the process information used by the Use Percent Optimizer

PROCESS, EQP_TYPE

This table is a temporary storage location for the result data for the Use Percent Optimizer

PROCESS, EQP_TYPE

This table is a temporary storage location for the run path information used by the Use Percent Optimizer

FACILITY, PROCESS_FAMILY, PROCESS_SUBFAMILY, TOOL, TIME_PERIOD

Table to store output of use percent optimizer solution for tool usage across process_subfamilies. The solution is how many units a tool should run of the goal remaining for each process_subfamily.

DEST_FACILITY, DEST_PRD, FACILITY, PRD, BANK

See comments in WFM_P_TOP_PRD_BANK_INFO_CUSTOM procedure.

This table allows the drop down lists in the WIP Flush application to be configurable

START_SHIFT, LOT, FACILITY, PRD, BANK

See comments in WF_APD_P_H_FLUSH view.