Search Results gmo_instr_instance_b




Overview
Explore in AI Chat

Overview

GMO_INSTR_INSTANCE_B is the instruction base table at execution time within the Oracle EBS Process Manufacturing module (GMO — Manufacturing Execution System for Process Manufacturing). It resides in the GMO schema and holds the runtime instance of production instructions that operators execute on the shop floor. Where instruction master data defines what should be done, GMO_INSTR_INSTANCE_B captures the specific instruction records generated and acknowledged during an actual production run, including acknowledgement state, operator confirmation, and task association.

From a Data Vault modeling perspective, the mined relationship data classifies this object heuristically as a standalone structure. In Data Vault terms, this suggests it behaves less like a pure hub or link anchored on shared business keys across the enterprise, and more like a self-contained artifact whose relationships are largely implicit through non-enforced references (such as instruction sets and tasks). The classification is a modeling suggestion only; the documented physical constraint is limited to a single primary key.

Key Information Stored

The table contains seventeen documented columns. The most operationally significant are:

The only documented unique index is the primary key on INSTRUCTION_ID; no separate business-key unique index is recorded in the ETRM metadata, meaning INSTR_NUMBER and INSTRUCTION_SET_ID plus INSTR_SEQ function as logical (non-enforced) identifying combinations.

Common Use Cases and Queries

Typical use cases include shop-floor execution monitoring, operator acknowledgement reporting, and reconciliation of instruction status against production completion. A frequent pattern retrieves all instances for a given instruction set in execution order:

  • SELECT instruction_id, instr_number, instr_seq, instr_status, operator_ackn FROM gmo.gmo_instr_instance_b WHERE instruction_set_id = :set_id ORDER BY instr_seq;
  • Tracking pending acknowledgements: SELECT task_id, task_ackn_status, task_ackn_date FROM gmo.gmo_instr_instance_b WHERE instr_status = :status AND task_ackn_status IS NULL;
  • Audit and throughput reporting by creation window using CREATION_DATE and CREATED_BY.
  • Joining task-level detail through TASK_ID to task execution tables for granular operator activity analysis.

Related Objects

The ETRM metadata documents this table as standalone, so enforced foreign keys are not listed. The following relationships are the most significant by naming and functional context:

  • GMO_INSTR_INSTANCE_TL — translation table keyed by INSTRUCTION_ID for language-specific instruction text.
  • Instruction set tables referenced through INSTRUCTION_SET_ID, defining the parent set of the instance.
  • Task execution tables referenced through TASK_ID, providing task definition and status.
  • GMO_INSTR_INSTANCE_TX or equivalent attribute/extension tables where instruction instance attributes are stored.
  • Batch and production execution tables that consume instruction instances to drive operator screens.
  • Task attribute tables joined via TASK_ATTRIBUTE_ID to resolve captured attribute values.

Because the vault classification is standalone, integration and reporting joins should be validated against instance data rather than relied upon as declarative constraints.