Search Results gmd_ss_storage_package_pk

Overview

GMD_SS_STORAGE_PACKAGE is a table in the GMD schema belonging to the Oracle Process Manufacturing Product Development module (GMD). Its documented description identifies it as the "Stability Study Variant Storage Package" table. In this role, the object records the storage and packaging configuration associated with stability study variants in process manufacturing. Stability studies track how formulated products behave over time under defined conditions; the storage package record captures the physical packaging item, the quantity, and the unit of measure in which a variant is handled during such studies.

The ETRM data vault classification derived heuristically from the foreign-key structure is standalone. In modeling terms, this suggests the table can be treated as a standalone entity rather than a strict hub, link, or satellite within a data vault construct, because no inbound or outbound FK relationships were mined from the documented structure. It is also notable that the table carries a wide descriptive-attribute block (ATTRIBUTE1 through ATTRIBUTE30), a pattern typical of OPM (Oracle Process Manufacturing) tables that support customer-specific extension columns.

The documented physical schema reflects Owner GMD with 49 columns. Access to this object should follow the standard security and audit model applied to GMD application tables, and it is marked Oracle proprietary and confidential.

Key Information Stored

The table is anchored by its surrogate primary key, GMD_SS_STORAGE_PACKAGE_PK, defined on the column PACKAGE_ID. This is the only documented unique index and therefore the sole business-key candidate; other columns are descriptive or foreign-key-style references without a documented unique constraint.

• PACKAGE_ID — Surrogate primary key uniquely identifying each storage package record.
• PACKAGE_NAME — Human-readable name or label of the storage package.
• FORMULA_ID — Reference to the formula associated with the stability study variant.
• ITEM_ID / INVENTORY_ITEM_ID — References to the inventory item representing the packaging or stored material.
• ORGANIZATION_ID — Organization owning the package record.
• QUANTITY / QUANTITY_UOM / UOM — Packaged or stored quantity and its unit of measure.
• TEXT_CODE — Code value used for descriptive or lookup text.
• REVISION — Revision identifier for the package or formulation context.
• MIGRATED_IND — Indicator denoting records migrated from a prior system.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE30 — A flexible descriptive-attribute block for implementation-specific extensions.
• DELETE_MARK — Soft-delete flag used to logically deactivate rows.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard audit columns recording who created and last modified each row.

Common Use Cases and Queries

Typical reporting scenarios include listing all storage packages for a given formula, retrieving package details for an inventory item within an organization, and identifying migrated records for data-conversion validation. A representative query joining the package to its formula context might select PACKAGE_ID, PACKAGE_NAME, FORMULA_ID, QUANTITY, and UOM filtered by FORMULA_ID. To isolate active records, queries should exclude rows where DELETE_MARK is set. Migration audits commonly filter on MIGRATED_IND. Because the primary key is on PACKAGE_ID, point lookups by that column are the most efficient access path; queries on FORMULA_ID or ITEM_ID benefit from indexes if present in the implementation.

Related Objects

The documented metadata indicates this object is standalone, so no foreign-key joins were mined. Related objects that logically connect through the columns present in the schema include:

• GMD_FORMULAS — joined via FORMULA_ID to obtain formula details.
• GMD_STABILITY_STUDY and its variant tables — the parent study context for storage packages.
• MTL_SYSTEM_ITEMS_B — joined via ITEM_ID or INVENTORY_ITEM_ID for item descriptions.
• MTL_PARAMETERS / ORG_ORGANIZATION_DEFINITIONS — joined via ORGANIZATION_ID for organization context.
• GMD_SS_* variant tables — sibling stability study entities that share the study structure.
• FND_LOOKUPS / standard UOM tables — referenced through UOM and TEXT_CODE values.

Because the object is documented as standalone, implementers should confirm actual relational dependencies in their instance rather than assuming the joins above are enforced by database constraints.