Search Results gmd_test_interval_plans




Overview
Explore in AI Chat

Overview

APPS.GMD_TEST_INTERVAL_PLANS_VL is a public, multi-lingual view in the Oracle E-Business Suite Process Manufacturing (formerly Oracle Process Manufacturing, OPM) schema. It exposes test interval plan definitions maintained within the Quality Management module and is intended for custom reporting and integration scenarios where read-only access to plan header data and translated plan names is required. The view is registered in FND Design Data as GMD.GMD_TEST_INTERVAL_PLANS_VL and carries a VALID status in both EBS 12.1.1 and 12.2.2. Because it is a "_VL" (multi-lingual) view, it joins the base entity table to its translation table and resolves the NAME column according to the session language, returning the appropriate translated value without requiring the caller to perform the join explicitly.

Underlying Base Objects

The view is defined over two documented base objects, both exposed in the APPS schema through synonyms:

  • GMD_TEST_INTERVAL_PLANS_B — the base (non-translated) table holding the plan definition itself, including identifiers, simulation dates, the delete/purge marker, descriptive flexfield columns, and the text code reference.
  • GMD_TEST_INTERVAL_PLANS_TL — the translation table holding language-specific plan names, keyed by the plan identifier and language.

The _VL view performs the outer/inner join between these two objects so that the NAME column reflects the translation matching the current language environment, while all structural columns are sourced from the _B table. All columns advertised by the view originate from the base entity; the translation contributes the name only.

Key Columns

  • ROW_ID (ROWID) — the physical row identifier of the underlying base table row.
  • TEST_INTERVAL_PLAN_ID (NUMBER) — the unique identifier of the test interval plan; this is the primary surrogate key and the value referenced by dependent plan-detail records.
  • NAME (VARCHAR2(80)) — the translated name of the test interval plan, resolved from the _TL table.
  • BASE_TEST_INTERVAL_PLAN_ID (NUMBER) — references the base plan from which a given plan version or copy is derived.
  • SIMULATION_START_DATE (DATE) — the start date used when the plan is applied in simulation mode.
  • DELETE_MARK (NUMBER) — indicator flagging whether the plan is marked for purge; queries should filter on this column to exclude logically deleted rows.
  • TEXT_CODE (NUMBER) — identifier linking the plan to its stored text/documentation.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE22 (VARCHAR2) — standard descriptive flexfield columns available for customer-extended attributes.

Common Use Cases and Queries

Typical uses include extracting plan masters for quality reporting, validating configuration during data migration, and joining plan headers to associated test interval detail rows. Because the view is multi-lingual, it is the preferred source whenever a user-facing plan name is required.

Listing active plans:

  • SELECT test_interval_plan_id, name, simulation_start_date FROM apps.gmd_test_interval_plans_vl WHERE delete_mark = 0 ORDER BY name;

Retrieving a specific plan by identifier:

  • SELECT test_interval_plan_id, name, base_test_interval_plan_id, simulation_start_date FROM apps.gmd_test_interval_plans_vl WHERE test_interval_plan_id = :plan_id;

Reporting on derived plans and flexfield extensions:

  • SELECT v.name, v.base_test_interval_plan_id, v.attribute_category, v.attribute1 FROM apps.gmd_test_interval_plans_vl v WHERE v.base_test_interval_plan_id IS NOT NULL AND v.delete_mark = 0;

In all cases, filtering on DELETE_MARK continues to be the recommended practice to avoid returning purged definitions.