Results for “project_organization”

50+ results




Overview
Explore in AI Chat

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

Overview

ICX_EDM_BUYER_SUP_PROJ_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the ICX (Oracle iProcurement) product. It is documented in ETRM as the "Project Information Summary View by Buyer / Supplier." Its purpose is to present a consolidated, de-normalized summary of purchasing activity broken down by buyer, supplier, and project, allowing iProcurement and downstream reporting tools to associate purchase order distributions with project accounting attributes without navigating the full transactional model.

The view carries a VALID status in both Oracle EBS 12.1.1 and 12.2.2. Because it is a view rather than a table, it stores no data of its own; it reads live from the purchasing and project accounting base objects at query time. Note that the defining query is a UNION of two branches: one driven from PA_PROJECTS_ALL for standard (non-template) projects, and one driven from PJM_SEIBAN_NUMBERS for Seiban-numbered projects. The two branches are aligned column-for-column so the result set remains consistent.

Underlying Base Objects

The documented base objects referenced by this view are:

  • PO_DISTRIBUTIONS (SYNONYM) — the core driver; each row is a purchase order distribution linking to a project and a PO header.
  • PO_HEADERS (SYNONYM) — supplies the buyer agent and vendor identifiers.
  • PO_VENDORS (VIEW) — provides the supplier name for the vendor on the header.
  • PA_PROJECTS_ALL (SYNONYM) — supplies project number, name, description, type, status, carrying-out organization, and dates for the standard branch.
  • PA_PROJECT_STATUSES (SYNONYM) — resolves the project status code to a descriptive status name.
  • PJM_SEIBAN_NUMBERS (SYNONYM) — alternative project source for the Seiban branch.
  • HR_ORGANIZATION_UNITS (VIEW) — resolves the organization identifier to an organization name.
  • PO_INQ_SV (PACKAGE) — used via PO_INQ_SV.GET_PERSON_NAME to return the buyer's display name.
  • HR_GENERAL and HR_SECURITY (PACKAGES) — supporting packages associated with the organizational and security model.

The joins use an outer join on PO_VENDORS (SUPP.VENDOR_ID (+) = HEAD.VENDOR_ID) and on HR_ORGANIZATION_UNITS in the Seiban branch, so records are retained even where a supplier or organization name is not yet available. The filter PROJ.TEMPLATE_FLAG != 'Y' excludes project templates from the standard branch.

Key Columns

The view exposes the following business-meaningful columns:

The dual SELECT lists also include placeholder NULL columns to keep the two UNION branches structurally identical; these carry no data in the corresponding branch.

Common Use Cases and Queries

This view is typically consumed to answer questions such as which buyers place project-related purchasing, which suppliers deliver against a given project, and how project activity is distributed across organizations — without querying PO_DISTRIBUTIONS, PO_HEADERS, and PA_PROJECTS_ALL directly. A representative query:

  • SELECT project_number, project_name, supplier_name, buyer_id FROM apps.icx_edm_buyer_sup_proj_v WHERE project_number = :p_project;
  • SELECT buyer_id, COUNT(DISTINCT project_id) FROM apps.icx_edm_buyer_sup_proj_v GROUP BY buyer_id;
  • SELECT organization_name, supplier_name, COUNT(*) FROM apps.icx_edm_buyer_sup_proj_v GROUP BY organization_name, supplier_name;

Because each row originates from a PO distribution, a single project may appear multiple times — once per distribution, per the DISTINCT projection over the joined set. Consumers should therefore aggregate when project- or supplier-level totals are required. As with all APPS reporting views, query execution is subject to the calling user's organization and project security.