Search Results gmo_instr_appr_defn_t




Overview
Explore in AI Chat

Overview

The GMO_INSTR_APPR_DEFN_T table is a core data object within the Manufacturing Execution System for Process Manufacturing (GMO) module of Oracle E-Business Suite (EBS) releases 12.1.1 and 12.2.2. It serves as the transactional repository for defining the approval hierarchy and sequence for instructions within a manufacturing process. This table is fundamental to enforcing workflow and quality control by storing the structured list of approvers required to authorize a specific instruction before it can be executed on the shop floor. Its role is to ensure that process instructions follow a defined, auditable chain of approval, which is critical in regulated process manufacturing environments.

Key Information Stored

The table's structure is designed to uniquely identify each approver within the context of an instruction and its overarching process. The primary key is a composite of three columns, which together define a unique approval step. The INSTRUCTION_PROCESS_ID links to the overall manufacturing process. The INSTRUCTION_ID identifies the specific instruction within that process requiring approval. The APPROVER_SEQ is a numeric column that defines the sequential order in which the approver is positioned within the approval chain for that instruction. While the provided metadata specifies the primary key columns, typical related data stored would include the approver's user or role identifier (e.g., EMPLOYEE_ID), approval action codes, and status flags, though these specific column names are inferred from standard EBS patterns and the table's purpose.

Common Use Cases and Queries

This table is primarily accessed to drive approval workflow logic and for audit reporting. A common operational use case is retrieving the next pending approver for an instruction to route a notification. For reporting, queries often join this table to instruction header and employee tables to generate approval history or pending approval lists. Sample SQL patterns include retrieving the full approval chain for an instruction or finding instructions stuck at a specific approver sequence.

  • Retrieve the approval sequence for a specific instruction: SELECT APPROVER_SEQ, [APPROVER_ID] FROM GMO.GMO_INSTR_APPR_DEFN_T WHERE INSTRUCTION_PROCESS_ID = :p_process_id AND INSTRUCTION_ID = :p_instr_id ORDER BY APPROVER_SEQ;
  • Identify the next approver in sequence: SELECT MIN(APPROVER_SEQ) FROM GMO.GMO_INSTR_APPR_DEFN_T WHERE INSTRUCTION_PROCESS_ID = :p_process_id AND INSTRUCTION_ID = :p_instr_id AND [APPROVAL_STATUS] = 'PENDING';

Related Objects

The GMO_INSTR_APPR_DEFN_T table is central to the instruction approval workflow. Its primary key (INSTRUCTION_PROCESS_ID, INSTRUCTION_ID, APPROVER_SEQ) is likely referenced by foreign keys in related transactional or history tables. Based on standard GMO schema design, key related objects include:

  • GMO_INSTRUCTION_HEADER or similar: The INSTRUCTION_PROCESS_ID and INSTRUCTION_ID columns in GMO_INSTR_APPR_DEFN_T typically form a foreign key relationship to the primary key of an instruction header table, which defines the master record for the instruction itself.
  • GMO_INSTR_APPR_HISTORY_T or a status table: A history or status table would likely store the actual approval transactions, referencing the definition in GMO_INSTR_APPR_DEFN_T via its primary key columns to track which approver (sequence) acted and when.
  • FND_USER / PER_ALL_PEOPLE_F: The table will contain a foreign key (e.g., APPROVER_ID) to the core EBS tables defining users or employees to identify the individual responsible for each approval sequence step.