Search Results pn_payment_terms_all




Overview
Explore in AI Chat

Overview

The PN_PAYMENT_TERMS_ALL table is a core transactional entity within the Oracle E-Business Suite Property Manager (PN) module, serving as the central repository for all payment and billing terms defined for a lease. It is a multi-organization table, as indicated by the "_ALL" suffix, meaning it stores data partitioned by the ORG_ID column for multiple operating units. Its primary role is to define the financial obligations and schedules for lease agreements, linking the lease structure to the general ledger, customers, and vendors. This table is fundamental for generating invoices, processing receipts, and managing the complete financial lifecycle of a lease contract in both Oracle EBS 12.1.1 and 12.2.2.

Key Information Stored

The table's primary key is PAYMENT_TERM_ID, which uniquely identifies each payment term record. Critical columns establish the term's context and financial parameters. The LEASE_ID and LEASE_CHANGE_ID columns link the term to its specific lease agreement or amendment. Financial setup is defined by SET_OF_BOOKS_ID, CODE_COMBINATION_ID (the natural account for billing), and CURRENCY_CODE. The table also stores party information, including CUSTOMER_ID and CUSTOMER_SITE_USE_ID for tenant billing, or VENDOR_ID and VENDOR_SITE_ID for lessor payments. Other significant columns include TERM_TEMPLATE_ID for standardized term creation, and references to specific billing components like PERIOD_BILLREC_ID, OPEX_RECON_ID, and VAR_RENT_INV_ID.

Common Use Cases and Queries

A primary use case is generating financial reports for a lease portfolio, such as a schedule of future payment obligations. Analysts frequently query this table to validate billing setup before period-end close or to troubleshoot missing invoices. Common SQL patterns involve joining to lease and customer tables to produce actionable data.

  • Identifying Payment Terms for a Specific Lease: SELECT * FROM pn_payment_terms_all WHERE lease_id = <lease_id> ORDER BY start_date;
  • Reporting on Tenant Billing Terms: SELECT pt.payment_term_id, l.lease_num, hca.account_name, pt.currency_code, pt.code_combination_id FROM pn_payment_terms_all pt, pn_leases_all l, hz_cust_accounts hca WHERE pt.lease_id = l.lease_id AND pt.customer_id = hca.cust_account_id AND pt.org_id = <org_id>;
  • Auditing Setup Completeness: Queries often check for terms missing critical linkages, such as a code combination ID or customer site.

Related Objects

PN_PAYMENT_TERMS_ALL has extensive relationships across Property Manager and integrated EBS modules, as evidenced by its foreign keys. It is a parent table to several PN transactional entities, including PN_DISTRIBUTIONS_ALL, PN_ADJUSTMENT_SUMMARIES, and PN_INDEX_EXCLUDE_TERM_ALL via PAYMENT_TERM_ID. It is a child table referencing master data and transactional headers: