Results for “instruction_process_id”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

GMO_INSTR_APPR_DEFN_T is a table in the GMO schema supporting Oracle Manufacturing Execution System for Process Manufacturing (MES for Process Manufacturing) in Oracle E-Business Suite 12.1.1 and 12.2.2. It defines the approval requirement structure for process instructions, capturing which roles are responsible for approving an instruction at each step in a defined approval sequence. Because process manufacturing instructions frequently require multi-level sign-off—typically spanning supervisory, quality, and production-control roles—this table stores the ordered definition of those approval stages rather than the resulting approval transactions.

Rows are scoped to a specific instruction and its instruction process. The ownership of the record is therefore best understood as a definitional artifact: it describes the expected approval path before any approval action occurs. Following the heuristic Data Vault classification provided in the metadata, GMO_INSTR_APPR_DEFN_T is modeled as a standalone table. It does not function as a hub or a link in the strict Data Vault sense, but its composite business key (INSTRUCTION_PROCESS_ID, INSTRUCTION_ID, APPROVER_SEQ) can be treated as a natural business key candidate for satellite-style modeling if the definition is versioned or historized.

Key Information Stored

The table contains ten documented columns. The three columns forming the primary key—INSTRUCTION_PROCESS_ID, INSTRUCTION_ID, and APPROVER_SEQ—constitute the unique identifier of each definition record and together satisfy the GMO_INSTR_APPR_DEFN_T_PK unique index. APPROVER_SEQ is the sequence number that orders approval steps within an instruction process; it is the column most commonly referenced by users searching for "approver_seq" and determines the order in which approvers are expected to act.

• INSTRUCTION_ID — Identifies the process instruction to which the approval definition belongs. Part of the composite primary key.
• INSTRUCTION_PROCESS_ID — Identifies the instruction process (or process step) scope for the approval definition. Part of the composite primary key.
• APPROVER_SEQ — The ordinal sequence of the approval step. Together with the two identifiers above, it forms the unique business-key candidate and primary key.
• ROLE_NAME — The role expected to act as approver at the given sequence position.
• ROLE_COUNT — The number (or count) of role holders required to complete approval at that step, supporting parallel or quorum-style approvals.
• CREATION_DATE, CREATED_BY — Standard audit columns recording when and by whom the definition row was created.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard audit columns recording the most recent modification to the definition row.

The surrogate-style identity here is the composite key itself; there is no separate single-column surrogate documented. The unique index on (INSTRUCTION_PROCESS_ID, INSTRUCTION_ID, APPROVER_SEQ) is the authoritative business-key candidate.

Common Use Cases and Queries

Typical use cases include retrieving the ordered approval path for a given instruction, validating that every required approval sequence is defined, and reporting on which roles are responsible for sign-off. A representative query retrieves the approval chain for a specific instruction:

• SELECT approver_seq, role_name, role_count FROM gmo.gmo_instr_appr_defn_t WHERE instruction_id = :instruction_id AND instruction_process_id = :process_id ORDER BY approver_seq;
• Determining the next expected approver after a given step by filtering APPROVER_SEQ > :current_seq and ordering ascending.
• Reporting on role workload by aggregating ROLE_COUNT grouped by ROLE_NAME across all instruction definitions.
• Auditing definition changes using CREATION_DATE and LAST_UPDATE_DATE to detect configuration changes to approval paths.

Related Objects

Because the table is classified as standalone, no foreign-key child tables are documented. Related objects are therefore inferred from the shared instruction and process identifiers used by the broader GMO instruction model.

• GMO_INSTRUCTION_HEADERS / instruction master tables — joined on INSTRUCTION_ID to resolve the instruction being approved.
• Instruction process definition tables in GMO — joined on INSTRUCTION_PROCESS_ID to scope the approval sequence to a process step.
• Approval transaction or history tables in GMO — relate via INSTRUCTION_ID, INSTRUCTION_PROCESS_ID, and APPROVER_SEQ to compare required versus actual approvals.
• FND_ROLES / workflow role definitions — resolve ROLE_NAME to the EBS role used for approval routing.
• Approval workflow and notification APIs — consume the sequenced definition to generate approval tasks and notifications.

These relationships should be confirmed against the deployed schema in each environment, since the documented metadata for GMO_INSTR_APPR_DEFN_T exposes only the primary key and column list.