Search Results mtl_grades_vl




Overview
Explore in AI Chat

Overview

MTL_GRADES_VL is a seeded, read-only view owned by the APPS schema within the Oracle Inventory (INV) module of Oracle E-Business Suite. It is classified in the E-Business Suite Technical Reference Manual (ETRM) as the "Grade Code View" and carries a VALID status in both the 12.1.1 and 12.2.2 releases. The object presents a translated, language-aware representation of inventory grade codes — the quality or condition classifications that can be associated with lots and material within Oracle Inventory. Because Oracle EBS stores translatable descriptive text in a separate "_TL" table and language-independent attributes in a "_B" table, this view exists to join the two so that consumers retrieve grade records with the description resolved to the session's language, without needing to write the join themselves. In reporting and integration contexts, MTL_GRADES_VL functions as the canonical, user-facing source for grade code data: Oracle Forms, OAF pages, and concurrent programs use it, and it is the recommended object for custom reports, BI Publisher data models, and interface extracts that need grade descriptions. The "_VL" suffix conventionally denotes a "value list" or translated view in the EBS schema design pattern.

Underlying Base Objects

According to the documented view text, MTL_GRADES_VL is defined over two base objects, both exposed through APPS synonyms:

  • MTL_GRADES_B — the base table holding all language-independent columns, including GRADE_CODE and the descriptive flexfield (DFF) attribute columns.
  • MTL_GRADES_TL — the translation table holding language-specific DESCRIPTION values.

The two tables are joined on GRADE_CODE, with the translation table additionally filtered by T.LANGUAGE = USERENV('LANG'), which restricts rows to the language of the current database session. The view selects B.ROWID as ROW_ID, then projects GRADE_CODE and DESCRIPTION from the translation table side together with DISABLE_FLAG, the standard WHO audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN), and the full set of thirty descriptive flexfield attribute columns (ATTRIBUTE1 through ATTRIBUTE30) plus ATTRIBUTE_CATEGORY from the base table.

Key Columns

  • ROW_ID — the ROWID of the underlying MTL_GRADES_B row, used by EBS Forms for row identification and update coordination.
  • GRADE_CODE — the primary business key and internal identifier for the grade; the column on which the two base tables are joined.
  • DESCRIPTION — the language-specific, user-visible grade description sourced from MTL_GRADES_TL.
  • DISABLE_FLAG — indicates whether the grade code is active or disabled; disabled grades should generally be excluded from transactional validation lists.
  • CREATION_DATE / CREATED_BY / LAST_UPDATE_DATE / LAST_UPDATED_BY / LAST_UPDATE_LOGIN — the standard WHO audit columns, useful for data lineage, change tracking, and audit reporting.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE30 — the descriptive flexfield segments defined on grade codes, exposing any customer-configured grade attributes.

Common Use Cases and Queries

Typical scenarios include validating a grade code entered on an inventory transaction, populating a grade selection list in a custom form or OAF page, extracting grade master data for a warehouse or quality system, and joining grade descriptions onto lot or on-hand query results. A basic lookup of active grades can be written as:

  • SELECT grade_code, description FROM apps.mtl_grades_vl WHERE disable_flag = 'N' ORDER BY grade_code;
  • SELECT g.grade_code, g.description, g.last_update_date FROM apps.mtl_grades_vl g WHERE g.grade_code = :p_grade_code;
  • SELECT m.lot_number, m.grade_code, g.description FROM apps.mtl_lot_numbers m, apps.mtl_grades_vl g WHERE m.grade_code = g.grade_code(+) AND m.inventory_item_id = :p_item_id;

Because the view is read-only and translation-aware, it should be queried rather than modified; DML on grade codes must be directed to the base tables or performed through the Oracle Inventory setup forms, which maintain the underlying records consistently.