Search Results payment_purpose




Overview
Explore in AI Chat

Overview

The PN_TRX_LEASE_EXPENSE view is a reporting object in the Oracle E-Business Suite Property Manager (PN) module, owned by the APPS schema. It presents a denormalized, business-friendly projection of normalized lease payment expense data for leases classified as DIRECT. Rather than forcing report authors and integrators to join payment items, payment terms, leases, locations, lookups, and supplier tables manually, the view encapsulates those joins and exposes descriptive text values — lease numbers, supplier names, and lookup meanings — in place of raw foreign keys and codes.

The view is defined over PN_PAYMENT_ITEMS and filtered with the predicate ITEM.PAYMENT_ITEM_TYPE_LOOKUP_CODE = 'NORMALIZED', which restricts output to normalized payment items. Its principal role is to support expense reporting and downstream integration for direct leases, allowing a single query to return the payment item identifier alongside human-readable lease, supplier, and payment classification attributes. The PAYMENT_ITEM_ID column, which is the term the user searched for, is the primary identifying column of the view.

Underlying Base Objects

The documented base objects referenced by this view are:

Because the location join is an outer join, payment terms without an associated location still appear, with LOCATION_CODE returned as null.

Key Columns

  • PAYMENT_ITEM_ID — Unique identifier of the normalized payment item, sourced from PN_PAYMENT_ITEMS. This is the primary linkage key for expense transactions.
  • LEASE_NUMBER — Lease number from PN_LEASES_ALL.
  • LEASE_NAME — Descriptive lease name.
  • SUPPLIER_NAME — Vendor name from PO_VENDORS.
  • SUPPLIER_SITE — Vendor site code from PO_VENDOR_SITES_ALL.
  • PAYMENT_PURPOSE — Meaning of the payment purpose lookup (PN_PAYMENT_PURPOSE_TYPE).
  • PAYMENT_TYPE — Meaning of the payment term type lookup (PN_PAYMENT_TERM_TYPE).
  • LOCATION_CODE — Location code, null when no location is attached.

Common Use Cases and Queries

Typical uses include lease expense reporting, reconciliation of normalized payment items to suppliers and leases, and integration extracts keyed on PAYMENT_ITEM_ID. A representative query retrieving lease expense detail is:

SELECT payment_item_id, lease_number, lease_name, supplier_name, supplier_site, payment_purpose, payment_type, location_code FROM apps.pn_trx_lease_expense WHERE lease_number = :p_lease_number;

To target a specific payment item — the searched term — filter directly:

SELECT payment_item_id, lease_number, payment_type, payment_purpose FROM apps.pn_trx_lease_expense WHERE payment_item_id = :p_payment_item_id;

Aggregation by supplier and payment type is also common for spend analysis:

SELECT supplier_name, payment_type, COUNT(*) item_count FROM apps.pn_trx_lease_expense GROUP BY supplier_name, payment_type;

Because the view already resolves lookups and supplier joins, these queries avoid re-implementing the same joins and produce consistent, report-ready output.