Results for “gmp_pdr_category_v”

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

Overview

GMP_PDR_CATEGORY_V is a database view owned by the APPS schema within Oracle E-Business Suite, belonging to the Process Manufacturing Process Planning (GMP) product family. Its documented purpose is to present a unique list of categories drawn from msc_item_categories for each organization within an instance. The view is classified as VALID in the ETRM metadata for both Oracle EBS 12.1.1 and 12.2.2, indicating that it is an active, supported database object rather than a deprecated or disabled artifact.

The view serves a specific reporting and integration role. Because item category assignments in EBS can span multiple organization contexts and may reference data flowing from Advanced Supply Chain Planning (MSC) staging structures, downstream consumers frequently require a deduplicated, instance-aware listing of category values. GMP_PDR_CATEGORY_V satisfies that need by collapsing the potentially repetitive category rows in msc_item_categories into distinct combinations of organization, source instance, category set, category name, and description. Its naming prefix, "PDR," aligns with process manufacturing planning deliverables that feed category reference data into planning and reporting layers.

Underlying Base Objects

The documented base object referenced by GMP_PDR_CATEGORY_V is MSC_ITEM_CATEGORIES, resolved in the APPS schema as a SYNONYM. This is the only base object recorded in the ETRM metadata. The view does not introduce joins to additional tables in its documented definition; it operates directly over MSC_ITEM_CATEGORIES, which is the supply chain planning table that stores item-to-category relationships and associated category descriptors.

Because the base table can contain redundant rows—particularly when data is loaded across multiple source instances or refreshed repeatedly by planning collections—the view applies a GROUP BY clause to its selected columns. This grouping is the mechanism that produces the "unique list" described in the object documentation. The relationship between the view and its base object is therefore one of aggregation and projection: MSC_ITEM_CATEGORIES holds the raw category-to-item detail, while GMP_PDR_CATEGORY_V exposes the distinct category dimension values at the organization and instance level.

Key Columns

• CATEGORY_NAME — The display name of the category as recorded in the planning category data; this is the primary human-readable identifier.
• DESCRIPTION — The descriptive text associated with the category, carried through the GROUP BY so that distinct descriptions appear as separate result rows.
• ORGANIZATION_ID — The inventory organization identifier, establishing the organizational scope of each category entry.
• SR_INSTANCE_ID — The source instance identifier, distinguishing category data originating from different planning or source systems.
• CATEGORY_SET_ID — The identifier of the category set (also known as a category set or flexible structure) to which the category belongs, providing the structural grouping context.

Together these five columns form the grouping key of the view. Any query that depends on uniqueness should treat the combination of all five columns as the effective primary key of the result set.

Common Use Cases and Queries

The view is typically used when a report or integration must enumerate available categories per organization without duplication, or when validating that category reference data has been collected correctly across source instances. A representative query retrieving all categories for a given organization is:

• SELECT CATEGORY_NAME, DESCRIPTION, CATEGORY_SET_ID FROM GMP_PDR_CATEGORY_V WHERE ORGANIZATION_ID = :org_id ORDER BY CATEGORY_NAME;
• SELECT ORGANIZATION_ID, CATEGORY_SET_ID, COUNT(*) FROM GMP_PDR_CATEGORY_V GROUP BY ORGANIZATION_ID, CATEGORY_SET_ID; — useful for auditing category counts per set and organization.
• SELECT DISTINCT SR_INSTANCE_ID FROM GMP_PDR_CATEGORY_V; — identifies the source instances contributing category data.
• SELECT * FROM GMP_PDR_CATEGORY_V WHERE CATEGORY_NAME LIKE 'FIN%'; — supports filters and lookups for planning or reporting screens.

Because the view is read-only and derived entirely from planning category data, it is best suited to reference, validation, and reporting workloads rather than transactional updates. Analysts should confirm that planning collections have populated MSC_ITEM_CATEGORIES before relying on the view's output.