Search Results pn_payment_items




Overview
Explore in AI Chat

Overview

APPS.PN_XLA_EXTRACT_LINES_V is a reporting and integration view in Oracle E-Business Suite that exposes payment item distribution lines from Oracle Payables/Payments in a Subledger Accounting (XLA) extraction format. It is one of a family of PN_XLA_EXTRACT_*_V views that supply "extract lines" — the granular data that the Subledger Accounting engine and downstream reporting consume when accounting events are generated from Payments (application ID 240). The view presents each qualifying distribution line of a payment item together with its associated XLA event identifier, ledger, currency, and conversion-date information, effectively flattening the accounting model into a single denormalized row set.

The name follows the XLA extraction naming convention, indicating that the view is intended to serve as a data source for subledger journal line extraction, reconciliation, and audit reporting rather than for transactional entry. It is owned by the APPS schema and is typically queried by reporting tools (Oracle Reports, BI Publisher, OBIEE) and by custom integration programs that need to move payment accounting data into a general ledger or data warehouse.

Underlying Base Objects

The view is defined over four referenced objects, each accessed through an APPS synonym:

  • PN_PAYMENT_ITEMS — the payment item header/line table holding amounts, currency, and accounting dates.
  • PN_PAYMENT_ITEM_DIST_ALL — the payment item distributions table holding accounted and entered amounts per accounting class and code combination.
  • XLA_EVENTS — Subledger Accounting events, providing the event identifier.
  • XLA_TRANSACTION_ENTITIES — XLA transaction entities, linking the source document to its accounting event.

The joins are the defining characteristic of the view: PN_PAYMENT_ITEMS.PAYMENT_ITEM_ID equates to PN_PAYMENT_ITEM_DIST_ALL.PAYMENT_ITEM_ID, and the XLA linkage is established by XLA_TRANSACTION_ENTITIES.SOURCE_ID_INT_1 = PN_PAYMENT_ITEMS.PAYMENT_ITEM_ID joined to XLA_EVENTS.ENTITY_ID = XLA_TRANSACTION_ENTITIES.ENTITY_ID. The filter XLA_EVENTS.APPLICATION_ID = 240 restricts results to the Payments application, ensuring that only payment-sourced accounting events are returned. This join path also explains the empirical relationship users observe when they search for "pn_payment_items": the view is the accounting-aware projection of that base table.

Key Columns

Common Use Cases and Queries

Typical uses include reconciling payment distributions to subledger journal entries, extracting payment accounting data for a general ledger interface, and auditing currency and ledger assignment on payment items. The consistent pattern is to filter by EVENT_ID, LEDGER_ID, CONVERSION_DATE, or DISTRIBUTION_TYPE.

Example — retrieve extract lines for a specific XLA event:

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

Example — summarize accounted amounts by ledger and currency for a period:

  • SELECT ledger_id, currency_code, distribution_type, SUM(accounted_amount) total_accounted, SUM(entered_amount) total_entered
  • FROM apps.pn_xla_extract_lines_v
  • WHERE conversion_date BETWEEN :p_start AND :p_end
  • GROUP BY ledger_id, currency_code, distribution_type;

Because CONVERSION_RATE and CONVERSION_RATE_TYPE are always null and ACCOUNTED_AMOUNT is zero-defaulted, consumers should treat the view as a line-level extract requiring external rate lookup rather than a self-contained currency translation source. Queries should also be bounded by event, ledger, or date to avoid the cost of scanning the underlying XLA tables.