Search Results gmd_test_interval_plans_vl




Overview
Explore in AI Chat

Overview

GMD_TEST_INTERVAL_PLANS_VL is an Oracle E-Business Suite (EBS) view owned by the APPS schema and classified as VALID in both 12.1.1 and 12.2.2. It belongs to the GMD product family, identified as Process Manufacturing Product Development. The view functions as a Multi-Lingual (ML) view for the GMD_TEST_INTERVAL_PLANS entity, exposing translated and base-table data through a single queryable interface. Test interval plans are used in process manufacturing product development to define the cadence and schedule at which stability or quality tests are performed against products or specifications over a simulation timeline.

The _VL suffix signals that the view joins a language-independent base table with a translation table so that users retrieve descriptions in their own session language. It supports reporting, concurrent program logic, forms, and integrations that require a denormalized, language-resolved representation of test interval plan definitions without requiring callers to perform the ML join manually.

Underlying Base Objects

Per the ETRM metadata, GMD_TEST_INTERVAL_PLANS_VL is defined over two documented base objects, both referenced through public synonyms:

The view text performs an inner join between the two tables on TEST_INTERVAL_PLAN_ID, filtered by T.LANGUAGE = USERENV('LANG'). Because of this filter, only the row matching the caller's current language session is returned for each plan. The view aliases the base table as B and the translation table as T, projecting B.ROWID as ROW_ID along with all descriptive and attribute columns from B, and DESCRIPTION from T.

Key Columns

The view exposes the following notable columns:

  • ROW_ID — the ROWID of the underlying base-table row; useful for row-level addressing and certain Forms/DML constructs.
  • TEST_INTERVAL_PLAN_ID — the primary key linking base and translation records.
  • NAME — the language-independent plan name.
  • BASE_TEST_INTERVAL_PLAN_ID — reference to a source/base plan from which the current plan may be derived or copied.
  • SIMULATION_START_DATE — the date from which interval simulation begins.
  • DELETE_MARK — soft-delete indicator (0 = active, 1 = logically deleted).
  • TEXT_CODE — reference to translated text segments in the standard Oracle text repository.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE30 — the standard Oracle DFF (descriptive flexfield) columns for user-defined extensions.
  • CREATION_DATE, CREATED_BY, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns.
  • DESCRIPTION — the language-specific descriptive text sourced from the TL table, resolved via USERENV('LANG').

Common Use Cases and Queries

Typical usage centers on retrieving active test interval plans with translated descriptions for reporting, validation, or integration. Because the view already applies the ML join and language filter, callers should not re-join the TL table.

Base query retrieving all active plans:

  • SELECT TEST_INTERVAL_PLAN_ID, NAME, DESCRIPTION, SIMULATION_START_DATE FROM APPS.GMD_TEST_INTERVAL_PLANS_VL WHERE DELETE_MARK = 0;

Lookup for a specific plan by identifier or name:

  • SELECT TEST_INTERVAL_PLAN_ID, NAME, DESCRIPTION FROM APPS.GMD_TEST_INTERVAL_PLANS_VL WHERE NAME = :p_name;
  • SELECT * FROM APPS.GMD_TEST_INTERVAL_PLANS_VL WHERE TEST_INTERVAL_PLAN_ID = :p_id;

Reports and concurrent programs commonly select NAME and DESCRIPTION for display, while attribute columns support customer-specific DFF reporting. Integration extracts frequently use TEST_INTERVAL_PLAN_ID as the key and filter on DELETE_MARK and LAST_UPDATE_DATE for incremental pulls. Query performance depends on valid indexes on TEST_INTERVAL_PLAN_ID in both underlying tables and the correct session language being set.