Search Results pn_payment_term_type




Overview
Explore in AI Chat

Overview

APPS.PN_TRX_LEASE_EXPENSE is a reporting view in the Oracle E-Business Suite Property Manager module. It presents lease payment expense information by joining normalized payment items to their governing payment terms, lease headers, locations, suppliers, and lookup-based code translations. The view is designed to expose lease-related expense lines in a business-friendly, denormalized format suitable for financial reporting, reconciliation, and downstream integration.

The view restricts output in several important ways. Only leases with a lease class code of 'DIRECT' are returned, and only payment items whose payment item type lookup code is 'NORMALIZED'. This means the view is scoped to direct leases and normalized (recurring or scheduled) payment items, excluding other lease classifications and non-normalized items. The presence of FND_GLOBAL in the documented base objects indicates that the view may rely on session context, such as the current organization or user, for multi-org or security filtering.

The user search term "pn_payment_term_type" corresponds directly to the PN_PAYMENT_TERM_TYPE lookup type referenced in the view definition, which supplies the human-readable PAYMENT_TYPE meaning. This is a common entry point for users seeking to understand or filter lease payment types.

Underlying Base Objects

The view is defined over the following documented base objects:

  • PN_PAYMENT_ITEMS — the primary source of payment item records; joined on payment_term_id.
  • PN_PAYMENT_TERMS_ALL — provides payment term details including lease_id, vendor, vendor site, location, payment term type code, and payment purpose code.
  • PN_LEASES_ALL — supplies lease header attributes (lease number, name, class code).
  • PN_LOCATIONS_ALL — supplies the location code; joined with an outer join (+) on location_id, so terms without a location still appear.
  • FND_LOOKUPS — referenced twice, once for PN_PAYMENT_TERM_TYPE and once for PN_PAYMENT_PURPOSE_TYPE, to translate lookup codes into meanings.
  • PO_VENDORS and PO_VENDOR_SITES_ALL — provide supplier name and supplier site code.
  • FND_GLOBAL — a package typically used for session or organization context.

The joins follow a straightforward relational path: payment items link to payment terms, which link to leases, locations, lookups, and suppliers.

Key Columns

  • PAYMENT_ITEM_ID — unique identifier of the payment item.
  • 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.
  • PAYMENT_PURPOSE — decoded meaning of the payment purpose code (PN_PAYMENT_PURPOSE_TYPE).
  • PAYMENT_TYPE — decoded meaning of the payment term type code (PN_PAYMENT_TERM_TYPE), directly relevant to the "pn_payment_term_type" search.
  • LOCATION_CODE — location code from PN_LOCATIONS_ALL; may be null due to the outer join.

Common Use Cases and Queries

Typical uses include lease expense reporting, supplier payment analysis, and filtering by payment type. A simple query retrieving normalized direct lease expense lines is:

SELECT lease_number, lease_name, supplier_name, supplier_site, payment_purpose, payment_type, location_code
FROM apps.pn_trx_lease_expense
WHERE payment_type = 'Advance Payment';

To group expenses by supplier and payment type:

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

Because the view already decodes lookups and filters to direct leases with normalized items, it is well suited for ad hoc reporting and integration extracts without requiring knowledge of the underlying Property Manager schema.