Search Results gmo_instr_instance_vl




Overview
Explore in AI Chat

Overview

GMO_INSTR_INSTANCE_VL is a multilingual (VL) view owned by the APPS schema in Oracle E-Business Suite, registered as VALID. It belongs to the GMO product family — Oracle Manufacturing Execution System for Process Manufacturing — and exposes instruction instance data used by process manufacturing execution workflows. In EBS 12.1.1 and 12.2.2 the view presents a translated, user-facing projection of instruction instances, combining language-independent attributes with the translated instruction text, comments, and task label. Because it resolves the current session language through USERENV('LANG'), it is the appropriate object for reporting and integration layers that must display instruction content in the operator's own language rather than the base-language text stored in the underlying tables. The view is read-only and is typically consumed by concurrent programs, Oracle Reports, OAF/ADF pages, and custom SQL extracts that surface shop-floor instruction status, acknowledgement state, and task labeling.

Underlying Base Objects

The view is defined over two documented base objects, both exposed to APPS as synonyms:

The join is an inner join on INSTRUCTION_ID between the two tables, filtered by T.LANGUAGE = USERENV('LANG'). Consequently, a row is returned only when a translation record exists for the session language. The view text selects B.ROWID as ROW_ID and carries audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) from the base table. The documented referenced objects confirm the dependency on GMO_INSTR_INSTANCE_B and GMO_INSTR_INSTANCE_TL exclusively.

Key Columns

  • ROW_ID — the ROWID of the base-table row, useful for direct row identification.
  • INSTRUCTION_ID — primary key linking the base and translation records; the join key of the view.
  • INSTRUCTION_SET_ID, INSTR_SEQ — identify the parent instruction set and the sequence position of the instruction within it.
  • INSTR_NUMBER, INSTR_STATUS — the instruction's business number and its current status.
  • TASK_ID, TASK_ATTRIBUTE, TASK_ATTRIBUTE_ID, TASK_LABEL — the associated task and its label; TASK_LABEL is drawn from the translation table.
  • TASK_ACKN_DATE, TASK_ACKN_STATUS, OPERATOR_ACKN — task-level acknowledgement timestamp, status, and operator acknowledgement flag.
  • INSTR_ACKN_TYPE, INSTRUCTION_TEXT, COMMENTS — acknowledgement type plus the translated instruction body and comments.
  • Audit columns — creation and last-update metadata inherited from the base table.

Since the user search term was "task_label," TASK_LABEL is the column of principal interest: it is sourced from GMO_INSTR_INSTANCE_TL and is therefore returned in the session language.

Common Use Cases and Queries

Typical scenarios include generating shop-floor instruction listings, tracking acknowledgement completion by task, and extracting translated instruction text for integration with MES or label-printing routines.

SELECT instr_number,
       instr_status,
       task_label,
       task_ackn_status,
       operator_ackn
FROM   apps.gmo_instr_instance_vl
WHERE  task_ackn_status = 'PENDING'
ORDER  BY instruction_id;

To retrieve translated instruction content for a specific set:

SELECT instr_seq,
       task_label,
       instruction_text,
       comments
FROM   apps.gmo_instr_instance_vl
WHERE  instruction_set_id = :p_set_id
ORDER  BY instr_seq;

Because the view filters on USERENV('LANG'), callers receive rows only where a matching translation exists; reports intended to show all instructions regardless of translation must query the base and translation tables directly. All access should be granted through APPS with the standard EBS responsibility and security model applied.