Results for “notification_lead_time”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

GMD_STABILITY_STUDIES_VL is a multilingual (ML) style database view owned by the APPS schema in Oracle E-Business Suite. It belongs to the GMD product family — Process Manufacturing Product Development — and is classified as a VALID object in both Release 12.1.1 and 12.2.2. The view presents stability study records maintained by process manufacturers to track how a product's quality attributes behave over time under defined storage conditions. Stability studies are central to regulated industries such as pharmaceuticals, food, and chemicals, where shelf-life justification and re-test intervals must be documented and auditable.

Functionally, the view exposes the full set of descriptive and administrative columns from the stability study base table, joined with the translated description text for the session language. Because the "_VL" suffix denotes a view that combines a base ("_B") table with its translation ("_TL") table, consumers of this view receive both language-independent attributes and the language-specific description in a single flattened result set. This makes it suitable for reporting, Oracle Discoverer workbooks, BI Publisher data templates, and custom integrations that need human-readable study descriptions without performing their own translation joins.

Underlying Base Objects

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

• GMD_STABILITY_STUDIES_B — the base table holding language-independent stability study data, aliased as B in the view text.
• GMD_STABILITY_STUDIES_TL — the translation table holding language-dependent text, aliased as T, which supplies the DESCRIPTION column.

The join condition is B.SS_ID = T.SS_ID combined with the language filter T.LANGUAGE = USERENV('LANG'). This restricts the result to the description matching the language of the current database session, ensuring each stability study appears once with an appropriate localized description. The B.ROWID is exposed as ROW_ID, a common EBS convention that allows the view to act as an updateable or identifiable row source in Oracle Forms and similar frameworks.

Key Columns

The view exposes a broad set of columns, the most significant of which include:

• SS_ID — the unique identifier of the stability study, and the join key between the base and translation tables.
• SS_NO — the user-visible stability study number.
• DESCRIPTION — the translated, language-specific study description sourced from the _TL table.
• STATUS — the current lifecycle state of the study.
• ORGANIZATION_ID, INVENTORY_ITEM_ID, REVISION — identify the item and organization the study concerns.
• STORAGE_SPEC_ID, STORAGE_PLAN_ID, BASE_SPEC_ID — references to related specification and storage plan records.
• LAB_ORGANIZATION_ID — the laboratory organization responsible for testing.
• SCHEDULED_START_DATE, SCHEDULED_END_DATE, REVISED_START_DATE, REVISED_END_DATE, ACTUAL_START_DATE, ACTUAL_END_DATE — the scheduled, revised, and actual timelines of the study.
• RECOMMENDED_SHELF_LIFE, RECOMMENDED_SHELF_LIFE_UNIT — the derived shelf-life recommendation.
• NOTIFICATION_LEAD_TIME(_UNIT), TESTING_GRACE_PERIOD(_UNIT) — operational planning attributes.
• OWNER, TEXT_CODE, DELETE_MARK — ownership, descriptive flexfield context, and soft-delete indicator.
• MATERIAL_SOURCES_CNT, STORAGE_CONDITIONS_CNT, PACKAGES_CNT — denormalized counters summarizing related child records.
• ATTRIBUTE1 … ATTRIBUTE30 and ATTRIBUTE_CATEGORY — the descriptive flexfield segments.
• Standard WHO columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN.

Common Use Cases and Queries

Typical uses include building stability study reports, feeding external LIMS or quality systems, and supporting audit queries. A representative query listing active studies for an item is:

• SELECT ss_no, description, status, recommended_shelf_life, recommended_shelf_life_unit, actual_start_date, actual_end_date FROM apps.gmd_stability_studies_vl WHERE inventory_item_id = :item_id AND organization_id = :org_id AND NVL(delete_mark,0) = 0 ORDER BY ss_no;
• To review testing timelines: SELECT ss_no, description, scheduled_start_date, revised_start_date, actual_start_date, notification_lead_time, testing_grace_period FROM apps.gmd_stability_studies_vl WHERE status = :status;
• To inspect flexfield or related-record counts: SELECT ss_no, attribute_category, attribute1, attribute2, material_sources_cnt, storage_conditions_cnt, packages_cnt FROM apps.gmd_stability_studies_vl WHERE ss_id = :ss_id;

Because DELETE_MARK indicates soft-deleted rows, most operational queries should filter on it. The language predicate is applied internally by the view, so no additional translation join is required by the caller.