Search Results gmd_test_interval_plan_periods




Overview
Explore in AI Chat

Overview

GMD_TEST_INTERVAL_PLAN_PERIODS is a table in the GMD schema, owned by the Oracle Process Manufacturing Product Development module (GMD). It stores the individual period definitions that make up a test interval plan, which is used to schedule stability testing and product-quality sampling at defined points in time relative to a batch or material start date. Each row represents a single named period within a parent test interval plan, defining when that period occurs and how it should be treated during plan execution.

In Oracle EBS 12.1.1 and 12.2.2 the table is documented as VALID and physically comprises 48 columns. It carries no documented child foreign keys, and its heuristic Data Vault classification, mined from the FK structure, is standalone — meaning it is best modeled as a satellite-like structure anchored to its parent plan rather than as a central hub or a link between independent business entities.

Key Information Stored

The table's surrogate primary key is PERIOD_ID, enforced by the GMD_TEST_INT_PLAN_PERIODS_PK index. A second unique index, GMD_TEST_INT_PLAN_PERIODS_U1, covers TEST_INTERVAL_PLAN_ID and NAME and serves as the documented business-key candidate — within a given plan, period names must be unique.

  • PERIOD_ID — surrogate primary key uniquely identifying each period row.
  • TEST_INTERVAL_PLAN_ID — foreign key to GMD_TEST_INTERVAL_PLANS_B; identifies the parent plan to which the period belongs.
  • NAME — the user-defined label for the period, part of the unique business key.
  • YEARS_FROM_START, MONTHS_FROM_START, WEEKS_FROM_START, DAYS_FROM_START, HOURS_FROM_START — offset components that express when the period occurs relative to the plan's start reference.
  • SIMULATED_DATE — the computed or simulated calendar date for the period, typically derived from the offsets.
  • FROM_BASE — flag indicating whether the offset is measured from the plan base rather than another reference.
  • EXCLUDE — flag marking a period to be skipped during plan generation or sampling.
  • TEXT_CODE — a code value used to categorise or qualify the period.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE30 — the standard Oracle descriptive-flexfield columns (31 total) for extension data.
  • CREATION_DATE, CREATED_BY, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — who-created/who-updated audit columns maintained automatically by the application.

Common Use Cases and Queries

Typical usage covers retrieving all periods for a plan, auditing period scheduling, and reporting on sampling coverage. A basic listing for a plan is:

  • SELECT period_id, name, months_from_start, days_from_start, simulated_date, exclude FROM gmd.gmd_test_interval_plan_periods WHERE test_interval_plan_id = :plan_id ORDER BY name;
  • Filtering active periods: add AND NVL(exclude,'N') = 'N' to exclude skipped periods.
  • Joining to the parent plan to resolve names, for example joining TEST_INTERVAL_PLAN_ID to GMD_TEST_INTERVAL_PLANS_B.
  • Reporting the flexfield attributes, selecting ATTRIBUTE_CATEGORY and the relevant ATTRIBUTEn column, when the installation extends the period definition.
  • Investigating duplicate business keys by grouping on TEST_INTERVAL_PLAN_ID and NAME.

Related Objects

The dominant relationship is the parent plan via the documented foreign key.

  • GMD_TEST_INTERVAL_PLANS_B — parent table; joined on GMD_TEST_INTERVAL_PLAN_PERIODS.TEST_INTERVAL_PLAN_ID = GMD_TEST_INTERVAL_PLANS_B.TEST_INTERVAL_PLAN_ID.
  • GMD_TEST_INTERVAL_PLANS_TL — translated plan names, joined through the base plan.
  • GMD_TEST_INTERVAL_PLAN_PERIODS itself is indexed by PK and by the U1 business key.
  • Related GMD quality and stability objects that consume plan periods for sampling, such as GMD_SPEC_TESTS and stability-study tables, are typically reached through the parent plan.

No child foreign keys are documented, confirming the standalone classification and indicating the table is a dependent satellite of the test interval plan.