Search Results task_attribute_id




Overview

GMO_INSTR_DEFN_VL is a language-dependent (VL suffix) view owned by the APPS schema in Oracle E-Business Suite. It belongs to the GMO product family — Manufacturing Execution System for Process Manufacturing — and presents instruction definition records used to drive task-level instructions on the shop floor. The view joins the base table GMO_INSTR_DEFN_B, which stores language-independent attributes, to the translation table GMO_INSTR_DEFN_TL, which stores language-specific descriptive text, filtering translations by the session language via USERENV('LANG'). Status is VALID in both 12.1.1 and 12.2.2.

Its role is to provide a single, current-language representation of instruction definitions for reporting, forms, and integration. Because the VL view resolves translation at query time, consumers avoid hard-coding language joins, making it a standard read interface for concurrent programs, OAF pages, and outbound interfaces that must reflect the logged-in user's language.

Underlying Base Objects

The ETRM metadata documents two referenced base objects, both accessed through synonyms: GMO_INSTR_DEFN_B and GMO_INSTR_DEFN_TL. The view text confirms an inner join between them on INSTRUCTION_ID, restricted by T.LANGUAGE = USERENV('LANG'). This is the canonical MLS (Multi-Language Support) pattern in EBS: a _B table holding transactional and foreign-key columns shared across languages, and a _TL table holding the translated columns (INSTRUCTION_TEXT and TASK_LABEL). The view also exposes B.ROWID ROW_ID, aligning it with the standard VL contract that provides a row identifier for Framework-based (OAF) consumption.

Key Columns

  • ROW_ID – B.ROWID from the base table, used by the OA Framework for row identification.
  • INSTRUCTION_ID – Primary key linking base and translation rows.
  • INSTRUCTION_SET_ID – Groups related instructions into a set.
  • INSTR_SEQ – Sequence of the instruction within its set.
  • TASK_ID – Task with which the instruction is associated.
  • TASK_ATTRIBUTE_ID, TASK_ATTRIBUTE – The task attribute context (code and identifier) to which the instruction applies.
  • INSTR_ACKN_TYPE – Acknowledgement type controlling how the operator must confirm the instruction.
  • INSTR_NUMBER – Numbering for the instruction.
  • INSTRUCTION_TEXT – Translated instruction text from GMO_INSTR_DEFN_TL.
  • TASK_LABEL – Translated task label from GMO_INSTR_DEFN_TL.
  • CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN – Standard EBS audit columns sourced from the base table.

Common Use Cases and Queries

The view is commonly used to retrieve instructions sequenced for a task set, to display operator-facing instruction text in the current language, and to feed integration extracts where TASK_ATTRIBUTE and its ID drive downstream logic. The searched term "task_attribute" maps directly to the TASK_ATTRIBUTE / TASK_ATTRIBUTE_ID pair exposed here.

Retrieve all instructions in a current-language context:

SELECT instruction_id, instruction_set_id, instr_seq,
       task_id, task_attribute_id, task_attribute,
       instr_ackn_type, instruction_text, task_label
FROM   apps.gmo_instr_defn_vl
ORDER  BY instruction_set_id, instr_seq;

Filter by task attribute:

SELECT task_id, task_attribute_id, task_attribute, instruction_text
FROM   apps.gmo_instr_defn_vl
WHERE  task_attribute_id = :p_task_attribute_id;

Join to base details for auditing:

SELECT v.instr_number, v.task_attribute, v.instruction_text,
       b.created_by, b.creation_date
FROM   apps.gmo_instr_defn_vl v, apps.gmo_instr_defn_b b
WHERE  v.instruction_id = b.instruction_id
AND    v.task_id = :p_task_id;

Because translation resolution depends on USERENV('LANG'), results differ by session language; reports requiring a specific locale should seed the NLS_LANG or language context accordingly.