Search Results account_class_pay




Overview
Explore in AI Chat

Overview

PN_DISTRIBUTIONS_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, belonging to the PN (Property Manager) product family. It exposes distribution records maintained by the Property Manager module, which governs leases, lease payment terms, billing schedules, and the allocation of charges across general ledger accounts. The view is documented as VALID in both Oracle EBS 12.1.1 and 12.2.2, and its definition is a direct, unfiltered projection of the PN_DISTRIBUTIONS base table. No joins, unions, or aggregation logic are applied; the view exists primarily to provide a stable, read-friendly interface for reporting, integration, and custom development against distribution data.

Because the underlying entity stores row data in a multi-organization (multi-org) context, the view also carries ORG_ID, making it suitable for operating-unit-scoped queries and for consumption by tools such as Oracle Reports, BI Publisher, OBIEE, or external integration layers that require a consistent read interface over the Property Manager distribution tables.

Underlying Base Objects

The documented base object referenced by this view is PN_DISTRIBUTIONS, accessed through a SYNONYM. The view text confirms the mapping: every column is sourced from the alias PDIST, which resolves to PN_DISTRIBUTIONS. No other tables are joined. Consequently, the view is a one-to-one reflection of the base table: every row in PN_DISTRIBUTIONS produces exactly one row in PN_DISTRIBUTIONS_V, and row volume is identical between the two objects.

The ROW_ID column is a notable artifact of this design. It is derived from PDIST.ROWID, the physical Oracle row identifier of the base table record. This provides a stable technical key for the row but means the value is not portable across database reorganization operations, such as export/import, table moves, or partition maintenance that changes row physical locations.

Key Columns

Common Use Cases and Queries

Typical scenarios include reviewing distribution splits for a lease, validating payment term assignments, reconciling distributions to GL accounts, and extracting data for custom reports or interfaces. The following query lists distributions within a specific operating unit:

  • SELECT distribution_id, payment_term_id, percentage, line_number, account_id, account_class FROM pn_distributions_v WHERE org_id = :p_org_id ORDER BY line_number;
  • SELECT d.distribution_id, d.account_id, d.percentage FROM pn_distributions_v d WHERE d.payment_term_id = :p_payment_term_id;

Because the view applies no filtering, callers should always constrain queries by ORG_ID where multi-org data separation is required, and should treat ROW_ID as a session-bound technical identifier rather than a persistent business key.