Search Results pn_payment_items_all




Overview
Explore in AI Chat

Overview

The PN_PAYMENT_ITEMS_ALL table is a core data repository within the Oracle E-Business Suite Property Manager (PN) module, specifically for versions 12.1.1 and 12.2.2. It serves as the transactional foundation for lease payment and billing schedules. The table stores the individual line items that constitute a payment or billing schedule, linking financial obligations to specific lease terms, customers, and vendors. Its "ALL" suffix indicates it is a multi-organization enabled table, storing data across all operating units. The primary role of this table is to hold the detailed, scheduled payment and billing amounts, dates, and associated accounting and party information that drive the financial management of lease contracts.

Key Information Stored

The table's structure is defined by its primary and foreign keys, which reveal the critical data elements. The primary key, PAYMENT_ITEM_ID, uniquely identifies each scheduled item. Essential foreign key relationships define its core attributes: the PAYMENT_SCHEDULE_ID links the item to its parent schedule in PN_PAYMENT_SCHEDULES_ALL, and the PAYMENT_TERM_ID connects it to the specific lease term in PN_PAYMENT_TERMS_ALL. Financial context is provided by the SET_OF_BOOKS_ID (GL_SETS_OF_BOOKS) and CURRENCY_CODE (FND_CURRENCIES). Crucially, the table stores party information for both lessee (customer) and lessor (vendor) obligations through CUSTOMER_ID, CUSTOMER_SITE_USE_ID, VENDOR_ID, and VENDOR_SITE_ID columns, which reference Trading Community Architecture (HZ) and Purchasing (PO) tables. Other significant columns likely include scheduled amount, due date, and accounting date, forming the basis for invoice generation and journal entries.

Common Use Cases and Queries

This table is central to lease accounting operations and reporting. A primary use case is generating periodic billing or payment runs, where applications query for items where the due date falls within a specific period and the status is pending. It is also critical for reconciliation, aging analysis, and audit trails of lease-related receivables and payables. Common reporting queries involve joining to schedule and lease header tables to analyze payment streams. For example, to list all upcoming payment items for a specific lease, a query would join PN_PAYMENT_ITEMS_ALL to PN_PAYMENT_SCHEDULES_ALL and PN_LEASES_ALL. Another typical pattern is summarizing scheduled amounts by customer or vendor for cash flow forecasting. The table is also the target for adjustments, as indicated by its foreign key relationship with PN_ADJUSTMENT_DETAILS.

Related Objects

  • PN_PAYMENT_SCHEDULES_ALL: The direct parent table. Each payment item belongs to a payment schedule.
  • PN_PAYMENT_TERMS_ALL: Provides the contractual lease term details for the payment item.
  • PN_ADJUSTMENT_DETAILS: Child table that records any adjustments (credits, debits) applied to a specific payment item.
  • HZ_CUST_ACCOUNTS / PO_VENDORS: Provide the customer (lessee) and vendor (lessor) master data, respectively.
  • HZ_CUST_SITE_USES_ALL / PO_VENDOR_SITES_ALL: Provide the specific bill-to and ship-to site information for the involved parties.
  • GL_SETS_OF_BOOKS / FND_CURRENCIES: Define the accounting and currency context for the financial amounts.