Search Results po_distributions_print




Overview
Explore in AI Chat

Overview

PO_DISTRIBUTIONS_PRINT is an APPS-owned reporting view in the Oracle Purchasing (PO) module, catalogued in ETRM with the description marker "- Retrofitted." It is a denormalized, print-oriented projection of the distribution-level records held in PO_DISTRIBUTIONS, enriched with the delivering person's full name resolved from the HR person tables. Its primary role is to supply the data set consumed by Oracle Purchasing distribution printing and related distribution reports, where a human-readable requestor or deliver-to name is required alongside the accounting, requisition, and destination attributes of each distribution.

The view is significant in the context of Oracle EBS 12.1.1 and 12.2.2 because its definition embeds a truncation of SYSDATE against the PER_PEOPLE_F date-tracked effective range and a subquery against FINANCIALS_SYSTEM_PARAMETERS. This makes the view date-sensitive and business-group-sensitive, and it is a frequent subject of retrofitting or client-extension copy during upgrades and multi-org deployments.

Underlying Base Objects

The documented base objects for the view are:

  • PO_DISTRIBUTIONS (SYNONYM) — the driving distribution table, supplying quantity, requisition, destination, DFF attribute, and key identifier columns.
  • PER_PEOPLE_F (VIEW) — the HR date-tracked person view, supplying FULL_NAME.
  • FINANCIALS_SYSTEM_PARAMETERS (SYNONYM) — used in a MAX(BUSINESS_GROUP_ID) subquery to scope the effective person record.
  • HR_GENERAL, HR_PERSON_NAME, and HR_SECURITY (PACKAGES) — HR infrastructure referenced by the person name and security logic.

PO_DISTRIBUTIONS and PER_PEOPLE_F are outer-joined: the predicate POD.DELIVER_TO_PERSON_ID = PPF.PERSON_ID (+) ensures distributions without a resolvable deliver-to person are still returned. The person row is accepted only when its BUSINESS_GROUP_ID matches the maximum configured in FINANCIALS_SYSTEM_PARAMETERS and the current truncation of SYSDATE falls between its effective start and end dates; otherwise the PPF.PERSON_ID IS NULL branch preserves the distribution row with a null name.

Key Columns

Common Use Cases and Queries

The view is typically used in distribution print programs, charge-account reconciliations, and custom reports requiring requestor names. A basic query follows:

SELECT requestor_name, requisition_number, charge_account_id, quantity_ordered
FROM apps.po_distributions_print
WHERE po_header_id = :p_header_id;

A requestor-oriented lookup, matching the original search, might read:

SELECT DISTINCT requestor_id, requestor_name
FROM apps.po_distributions_print
WHERE org_id = :p_org_id
ORDER BY requestor_name;

Because REQUESTOR_NAME resolves via SYSDATE and FINANCIALS_SYSTEM_PARAMETERS, results depend on the reporting date and the set of books configuration; queries intended for historical reporting should account for this behavior. In 12.1.1 and 12.2.2 the object remains an APPS view over the same base tables, with 12.2.x Online Patching considerations applying to any custom objects layered on top of it.