Search Results gmd_test_interval_plans_b




Overview
Explore in AI Chat

Overview

GMD_TEST_INTERVAL_PLANS_B is the base table that stores test interval plans within the Oracle E-Business Suite Process Manufacturing Product Development module (GMD). It resides in the GMD schema and holds the header-level definition of a test interval plan — a reusable specification that governs how frequently quality or stability testing must recur for a given item, product, or storage condition. The "_B" suffix denotes the base (non-translated) table in Oracle's standard multi-language table pairing convention, confirming that this object holds the language-independent attributes of the plan while any translatable descriptive text would reside in a corresponding "_T" table.

Test interval plans drive downstream scheduling logic across Process Manufacturing. Each plan references a simulation start date and a base plan, and is broken into discrete periods (stored in the child table GMD_TEST_INTERVAL_PLAN_PERIODS). The plan can also be attached to storage plans through GMD_STORAGE_PLAN_DETAILS, linking test cadence to physical storage conditions.

The ETRM metadata classifies the object, using a heuristic Data Vault model, as a standalone entity — it functions effectively as a hub (or a small hub-and-satellite) since it holds the stable identity (TEST_INTERVAL_PLAN_ID) plus descriptive attributes, with no upward foreign-key dependencies on other GMD master tables. This classification is a modeling suggestion only; the physical schema remains a conventional EBS base table.

Key Information Stored

The table is documented with 42 physical columns. The most significant are:

  • TEST_INTERVAL_PLAN_ID — the surrogate primary key, defined by the index GMD_TEST_INTERVAL_PLANS_B_PK. This is the system-generated identifier used by all child and dependent tables.
  • NAME — the user-facing plan name. It is protected by the unique index GMD_TEST_INTERVAL_PLANS_B_U1, making it the primary business-key candidate and the natural identifier presented to users.
  • BASE_TEST_INTERVAL_PLAN_ID — a self-referencing attribute pointing back to a template or source plan from which the current plan was derived.
  • SIMULATION_START_DATE — the reference date from which interval periods are projected and simulated.
  • DELETE_MARK — the standard EBS soft-delete flag (0/1) used by the application to logically retire rows.
  • TEXT_CODE — a code field used to associate free-text or descriptive content with the plan.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE30 — the standard Oracle DFF (Descriptive Flexfield) columns, offering 30 configurable attributes for customer-specific extensions without schema change.
  • CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — the standard "WHO" audit columns maintained by Oracle Forms and concurrent programs.

The distinction matters: TEST_INTERVAL_PLAN_ID is a technical surrogate that is never exposed to end users, whereas NAME is the meaningful business identifier enforced as unique at the database level.

Common Use Cases and Queries

Typical applications include retrieving active plans for a quality specification, listing all periods belonging to a plan, and reporting which storage conditions are governed by a given plan.

Retrieve active plans, excluding soft-deleted rows:

  • SELECT TEST_INTERVAL_PLAN_ID, NAME, SIMULATION_START_DATE FROM GMD_TEST_INTERVAL_PLANS_B WHERE DELETE_MARK = 0;

Resolve a user-supplied plan name to its surrogate key:

  • SELECT TEST_INTERVAL_PLAN_ID FROM GMD_TEST_INTERVAL_PLANS_B WHERE NAME = :p_name;

Join to the period detail to build a full test schedule:

  • SELECT h.NAME, p.* FROM GMD_TEST_INTERVAL_PLANS_B h, GMD_TEST_INTERVAL_PLAN_PERIODS p WHERE h.TEST_INTERVAL_PLAN_ID = p.TEST_INTERVAL_PLAN_ID AND h.DELETE_MARK = 0 ORDER BY p.PERIOD_SEQUENCE;

Identify storage plans governed by each test plan:

  • SELECT s.*, h.NAME FROM GMD_STORAGE_PLAN_DETAILS s, GMD_TEST_INTERVAL_PLANS_B h WHERE s.TEST_INTERVAL_PLAN_ID = h.TEST_INTERVAL_PLAN_ID;

These patterns support quality assurance reporting, stability study setup, and reconciliation of plan definitions across organizations.

Related Objects

The foreign-key graph confirms two dependent children and one self-reference:

  • GMD_TEST_INTERVAL_PLAN_PERIODS — joins on TEST_INTERVAL_PLAN_ID; holds the ordered interval periods that define the plan's cadence.
  • GMD_STORAGE_PLAN_DETAILS — joins on TEST_INTERVAL_PLAN_ID; associates test plans with storage plan configurations.
  • GMD_TEST_INTERVAL_PLANS_B (self) — related via BASE_TEST_INTERVAL_PLAN_ID, linking a plan to the template it was copied from.

A corresponding translated table (conventionally GMD_TEST_INTERVAL_PLANS_T) and the standard GMD application APIs and concurrent programs that maintain test interval plans complete the object's functional neighborhood. Any purge or migration routine must delete child period rows before the parent header to respect referential integrity.