Search Results buyer_name




Overview
Explore in AI Chat

Overview

APPS.GMP_PDR_BUYER_V is a reporting view in Oracle E-Business Suite that exposes the distinct set of buyer assignments held against system items. It is defined as a grouped projection over MSC_SYSTEM_ITEMS, filtering out any row where the buyer identifier is null. The view therefore functions as a lightweight buyer reference list rather than a transactional supply chain object, and it is typically consumed by planning, sourcing, and procurement reporting that must resolve a buyer_id to a buyer name within a specific organizational and planning context.

Because the view is owned by APPS and is built directly on an MSC synonym, it belongs to the Advanced Supply Chain Planning / Demand Planning data model rather than to the Purchasing (PO) or Process Manufacturing (GMP) base tables, despite the GMP_ prefix. In EBS 12.1.1 and 12.2.2 the definition is identical, and the view remains a read-only convenience layer intended to spare report developers from writing the DISTINCT logic themselves.

Underlying Base Objects

The view is defined over a single base object, MSC_SYSTEM_ITEMS, referenced through a synonym. MSC_SYSTEM_ITEMS is the planning system's item master, holding item, organization, instance, plan, and sourcing attributes collected from source instances for planning purposes. GMP_PDR_BUYER_V does not join to any other table; it simply groups and filters that source.

  • Source object: MSC_SYSTEM_ITEMS (SYNONYM)
  • Definition: 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
  • Effect: all five projected columns participate in the GROUP BY, so the result is the set of unique buyer / organization / instance / plan combinations present in the planning item master.

Key Columns

  • BUYER_ID — The internal identifier of the buyer. This is the column most frequently searched, and it is the filter predicate of the view: rows with a null BUYER_ID are excluded entirely.
  • BUYER_NAME — The display name of the buyer. Because it is included in the GROUP BY, a single buyer_id can theoretically appear under more than one name if the source data is inconsistent.
  • ORGANIZATION_ID — The inventory organization to which the buyer assignment applies.
  • SR_INSTANCE_ID — The source system instance identifier, distinguishing records collected from different source applications.
  • PLAN_ID — The planning plan with which the item record is associated, allowing the same item and buyer to be reported separately per plan.

Common Use Cases and Queries

Typical usage is validation or lookup: confirming which buyers exist for an organization, populating a buyer parameter list of values, or joining planning results back to a buyer name. A simple lookup by buyer follows.

SELECT buyer_name, buyer_id, organization_id, sr_instance_id, plan_id FROM apps.gmp_pdr_buyer_v WHERE buyer_id = :p_buyer_id;

To list all buyers for a specific organization and plan:

SELECT buyer_name, buyer_id FROM apps.gmp_pdr_buyer_v WHERE organization_id = :p_org_id AND plan_id = :p_plan_id ORDER BY buyer_name;

To produce a distinct buyer list across instances, the caller can further aggregate, for example SELECT DISTINCT buyer_id, buyer_name FROM apps.gmp_pdr_buyer_v. Because MSC_SYSTEM_ITEMS is a planning staging object, results reflect the most recent planning collection rather than live purchasing setup; where current, authoritative buyer information is required, the Purchasing buyers table should be used instead. Query performance benefits from filtering on organization_id, sr_instance_id, or plan_id, since these predicates reduce the grouped set before aggregation.