Search Results pn_xla_extract_lines_v




Overview
Explore in AI Chat

Overview

PN_XLA_EXTRACT_LINES_V is an APPS-owned database view in Oracle E-Business Suite, belonging to the Property Manager (PN) product family. It exposes property payment distribution data in a format aligned with the Subledger Accounting (XLA) extract requirements, making it a bridge between Property Manager payment structures and the accounting events generated for the general ledger. Because the view derives amounts from both a payment item and its associated distributions, it presents a prorated financial picture suitable for reporting, reconciliation, and downstream accounting integration.

The view is valid and is populated from the PN payment model, essentially flattening the relationship between payment items, payment terms, and their accounting distributions into a single accounting-oriented projection. The DISTRIBUTION_TYPE column in particular draws the user's search interest: it is sourced directly from PN_DISTRIBUTIONS and identifies the accounting class of each distribution line, enabling reports to distinguish between the principal, tax, fee, or other accounting components of a property payment.

Underlying Base Objects

The view is defined over several core objects: PN_PAYMENT_ITEMS, PN_PAYMENT_TERMS_ALL, PN_DISTRIBUTIONS_ALL, XLA_EVENTS, and XLA_TRANSACTION_ENTITIES. The documented ETRM metadata lists the referenced base objects as PN_PAYMENT_ITEMS, PN_PAYMENT_ITEM_DIST_ALL, XLA_EVENTS, and XLA_TRANSACTION_ENTITIES (each appearing as synonyms), reflecting the joins used to assemble the projection.

The joins are structurally important. Payment terms are matched to both the payment item and the distribution on PAYMENT_TERM_ID. Only payment items with a PAYMENT_ITEM_TYPE_LOOKUP_CODE of 'NORMALIZED' are included, which restricts the view to normalized payment records. The link to XLA is made through XLA_TRANSACTION_ENTITIES, where SOURCE_ID_INT_1 equals the payment item identifier, and then to XLA_EVENTS via ENTITY_ID, filtered to APPLICATION_ID = 240 (the Property Manager application). This chain anchors each accounting line to its originating subledger event.

Key Columns

  • ACCOUNTED_AMOUNT — The payment item's accounted amount multiplied by the distribution percentage, yielding the prorated accounted value for each line.
  • ENTERED_AMOUNT — The export currency amount similarly prorated by distribution percentage.
  • CODE_COMBINATION_ID — The accounting flexfield combination taken from the distribution's ACCOUNT_ID.
  • DISTRIBUTION_TYPE — Derived from the distribution's ACCOUNT_CLASS, indicating the accounting classification of the line.
  • CONVERSION_DATE / CONVERSION_RATE / CONVERSION_RATE_TYPE — Set from the accounted date; rate and rate type are returned as NULL in this view.
  • CURRENCY_CODE — The export currency code of the payment item.
  • LEDGER_ID — The set of books from the payment term record.
  • EVENT_ID — The XLA event identifier linking the line to its subledger accounting event.
  • LINE_NUMBER — The distribution line number, preserving ordering within the payment.

Common Use Cases and Queries

Typical uses include property payment reconciliation, subledger-to-GL tie-outs, and auditing of accounting distributions by type. A common query filters or groups by DISTRIBUTION_TYPE, since the user specifically searched on that term:

  • Reporting total accounted amounts per ledger and currency.
  • Listing all lines for a given XLA EVENT_ID.
  • Analyzing the composition of a payment by DISTRIBUTION_TYPE.

Sample SQL:

SELECT event_id, line_number, distribution_type, code_combination_id, accounted_amount, entered_amount, currency_code, ledger_id FROM apps.pn_xla_extract_lines_v WHERE distribution_type = :p_type ORDER BY event_id, line_number;

Because the view applies a percentage-based proration, consumers should ensure they aggregate at the correct grain (event plus line) to avoid double counting across terms or items.