Search Results pn_payment_purpose_type




Overview
Explore in AI Chat

Overview

APPS.PN_PAYMENT_ITEMS_V is a reporting and integration view in Oracle E-Business Suite (EBS) Release 12.1.1 and 12.2.2 that consolidates payment item records used by the Property Manager (PN) module, most commonly in the context of lease and payment management. The view joins the base payment item table with payment terms, grouping rules, vendor, customer, and lookup data to present a denormalized, human-readable result set. It is typically consumed by concurrent reports, Oracle Discoverer workbooks, custom SQL reports, and outbound interfaces that require payment scheduling data enriched with descriptive names rather than internal identifiers. The view is owned by the APPS schema and is treated as a read-only object for reporting purposes.

Underlying Base Objects

The view is defined over the following documented base objects:

  • PN_PAYMENT_ITEMS — the primary table, aliased as pitem, supplying payment item detail such as amounts, dates, currency, and adjustment attributes.
  • PN_PAYMENT_TERMS_ALL — aliased as pterm, supplying term-level attributes including frequency code, normalization flag, and code combination.
  • PN_PAY_GROUP_RULES — aliased as ppgr, providing the invoice grouping rule name.
  • PN_LEASES_ALL — referenced for lease-level context such as the lease indicator.
  • PO_VENDORS and PO_VENDOR_SITES_ALL — aliased as pov and povs, supplying vendor name, vendor number (segment1), and vendor site code.
  • HZ_CUST_ACCOUNTS_ALL, HZ_CUST_SITE_USES_ALL, and HZ_PARTIES — supplying customer account number, customer site use, and party name.
  • FND_LOOKUPS and FND_LOOKUP_VALUES — aliased as flv and flv1, providing lookup meanings such as payment_purpose and payment_term_type.
  • FND_GLOBAL — the standard package used to derive session context such as organization and user information.

The view therefore functions as a single-source presentation layer over the transactional PN payment item model, replacing raw lookup codes with meaningful descriptions.

Key Columns

  • payment_item_id — primary key of the underlying payment item record.
  • payment_item_type_lookup_code — classifies the payment item (for example, payment or receipt).
  • due_date, accounted_date, adj_start_date, adj_end_date — scheduling and adjustment dates for the item.
  • actual_amount, estimated_amount, accounted_amount — monetary values at item and term level.
  • currency_code and rate — transaction currency and conversion rate.
  • payment_purpose — descriptive meaning derived via FND_LOOKUP_VALUES; this is the column surfaced when users search for "pn_payment_purpose_type," as the lookup that feeds it.
  • payment_term_type — lookup meaning for the associated payment term.
  • vendor_name, vendor_number, vendor_site, customer_name, customer_number — party identification for payment or receipt processing.
  • inv_group_name — the invoice grouping rule name from PN_PAY_GROUP_RULES.
  • transferred_to_ap_flag, ap_invoice_num — indicate whether the item was passed to Payables and its resulting invoice number.
  • term_normalize_flag and one_time — DECODE-derived indicators for term behavior.

Common Use Cases and Queries

This view is commonly used to extract payment schedules for lease contracts, to reconcile payment items transferred to Payables, and to report payment purpose by vendor or customer. A typical query retrieves scheduled payments with their descriptive purpose and term type:

  • SELECT payment_item_id, due_date, vendor_name, currency_code, actual_amount, payment_purpose, payment_term_type FROM apps.pn_payment_items_v WHERE transferred_to_ap_flag = 'N' ORDER BY due_date;
  • Reporting received or paid amounts by grouping rule using inv_group_name and accounted_amount.
  • Reconciling items already interfaced to Payables by filtering on ap_invoice_num IS NOT NULL.
  • Filtering by payment_purpose to analyze lease payments by purpose category, which is derived from the lookup underlying "pn_payment_purpose_type."

Because the view embeds FND_LOOKUPS resolutions at execution time, users must ensure the correct language and lookup configuration are in place when running reports, as the payment_purpose and payment_term_type values reflect the active lookup meanings in the session.