Results for “buyer_name”

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

Overview

The GMP_PDR_BUYER_V view is a reporting and integration object owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It belongs to the GMP product family, Process Manufacturing Process Planning, which forms part of the broader Advanced Supply Chain Planning (ASCP) and process manufacturing planning stack. The view is documented as VALID in the ETRM metadata, confirming that it is compiled and available for query at runtime.

The purpose of the view is to expose a unique, de-duplicated list of buyers sourced from the planning data maintained in MSC_SYSTEM_ITEMS, scoped to each organization, source instance, and plan. Because planner-facing applications and reports frequently need to enumerate buyers independently of the item rows that reference them, GMP_PDR_BUYER_V provides a convenient, pre-aggregated access point. Rather than scanning the full item master for every buyer lookup, downstream consumers can query this view to obtain the distinct buyer identifiers and names that are actually referenced in a given planning context. This makes it well suited to value lists, report parameters, and integration extracts where a buyer list is required.

Underlying Base Objects

The view is defined over a single documented base object: MSC_SYSTEM_ITEMS, accessed through a synonym within the APPS schema. MSC_SYSTEM_ITEMS is the planning-side item master that stores item attributes as collected and maintained by the MSC (Advanced Supply Chain Planning) modules, including planning-relevant organizational assignments and buyer references.

The view text is a straightforward projection and grouping over this table:

• SELECT BUYER_NAME, BUYER_ID, ORGANIZATION_ID, SR_INSTANCE_ID, PLAN_ID FROM MSC_SYSTEM_ITEMS WHERE BUYER_ID IS NOT NULL GROUP BY ORGANIZATION_ID, SR_INSTANCE_ID, PLAN_ID, BUYER_NAME, BUYER_ID

Two characteristics follow from this definition. First, the WHERE BUYER_ID IS NOT NULL predicate restricts output to items that have an assigned buyer, which is why the result represents buyers in active planning use rather than every defined buyer. Second, the GROUP BY clause collapses the multiplicity of item rows that can share the same buyer within an organization, instance, and plan combination into a single distinct row, producing the "unique list of buyers" described in the metadata. Because the view is read-only and contains no joins beyond the underlying table, it inherits the access and performance profile of MSC_SYSTEM_ITEMS.

Key Columns

• BUYER_NAME — The display name of the buyer. This is the column most frequently returned to end users and the direct target of searches such as "buyer_name".
• BUYER_ID — The unique identifier of the buyer. Used as the join key to buyer/employee reference data and as the filter that excludes unassigned items.
• ORGANIZATION_ID — The inventory/planning organization to which the buyer reference applies. The same buyer can appear once per organization.
• SR_INSTANCE_ID — The source instance identifier, distinguishing data collected from different source systems or instances.
• PLAN_ID — The plan identifier. A buyer may appear multiple times across plans, so this column must typically be constrained to obtain plan-specific results.

Common Use Cases and Queries

Typical scenarios include populating buyer selection lists on custom planning reports, validating buyer assignments during data conversion, and extracting buyer master data for integration or downstream analytics. Because the view is already aggregated, it is well suited to parameter-driven lookups.

Retrieve all distinct buyers for a plan and organization:

• SELECT BUYER_NAME, BUYER_ID FROM APPS.GMP_PDR_BUYER_V WHERE PLAN_ID = :p_plan_id AND ORGANIZATION_ID = :p_org_id ORDER BY BUYER_NAME;

Find a specific buyer by name, matching the original search intent:

• SELECT BUYER_ID, BUYER_NAME, ORGANIZATION_ID FROM APPS.GMP_PDR_BUYER_V WHERE UPPER(BUYER_NAME) LIKE UPPER('%' || :p_buyer_name || '%');

Enumerate buyers across all plans in a source instance:

• SELECT DISTINCT BUYER_NAME, BUYER_ID FROM APPS.GMP_PDR_BUYER_V WHERE SR_INSTANCE_ID = :p_instance_id;

For best performance, always constrain the query by PLAN_ID, ORGANIZATION_ID, or SR_INSTANCE_ID where possible, since the view reflects the full planning item population and unconstrained queries can return large result sets.