Results for “pn_payment_terms_all”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

PN_PAYMENT_TERMS_ALL is the foundational transaction table within the Oracle Property Manager (PN) module. It stores the payment and billing terms that are defined against a lease, serving as the authoritative record from which recurring billing schedules, payment items, distributions, and receivables transactions are generated. In Oracle EBS 12.1.1 and 12.2.2, this multi-org table is owned by the PN schema and exposes an ORG_ID column for operating unit partitioning, consistent with other Property Manager transaction tables.

From a data modeling perspective, the object carries a 110-column physical profile dominated by descriptive and operational attributes. Its structure — a single surrogate key, extensive descriptive columns, and numerous foreign keys pointing to leases, customers, vendors, currencies, and accounting flexfields — reflects a satellite-leaning classification. Under a heuristic Data Vault interpretation, PN_PAYMENT_TERMS_ALL behaves as a satellite anchored to a lease/lease-change hub, with the surrogate key PAYMENT_TERM_ID functioning as the satellite's identifier rather than as an independent business key.

Key Information Stored

The primary key is enforced through PN_PAYMENT_TERMS_PK on the column PAYMENT_TERM_ID, and a unique index PN_PAYMENT_TERMS_U1 also covers PAYMENT_TERM_ID. No separate natural business key is documented, so PAYMENT_TERM_ID serves as both the surrogate and the documented unique identifier.

The most significant columns include:

• PAYMENT_TERM_ID — the surrogate primary key and the join key used by all dependent child tables.
• LEASE_ID and LEASE_CHANGE_ID — the lease and lease-change context to which the term belongs.
• PAYMENT_PURPOSE_CODE and PAYMENT_TERM_TYPE_CODE — classify the term (for example, rent, expense, or abatement).
• FREQUENCY_CODE, START_DATE, END_DATE, SCHEDULE_DAY, and TARGET_DATE — control the recurrence and timing of the payment schedule.
• ESTIMATED_AMOUNT and ACTUAL_AMOUNT — the expected versus realized monetary value of the term.
• CURRENCY_CODE and RATE — currency and exchange rate for multi-currency leases.
• CUSTOMER_ID and CUSTOMER_SITE_USE_ID — the billing party and site for customer-facing terms.
• VENDOR_ID and VENDOR_SITE_ID — the payee for landlord or expense-facing terms.
• CODE_COMBINATION_ID and SET_OF_BOOKS_ID — the accounting flexfield and ledger context.
• TERM_TEMPLATE_ID — links the term to the template used to generate it.
• STATUS and LEASE_STATUS — lifecycle state of the term.

Common Use Cases and Queries

Typical reporting scenarios include payment schedule extraction, lease abstraction, and reconciliation between contract terms and generated invoices or payables. A common pattern joins the terms to lease and customer data:

• Retrieve all active terms for a lease: SELECT payment_term_id, payment_purpose_code, frequency_code, estimated_amount FROM pn_payment_terms_all WHERE lease_id = :lease_id AND status = 'ACTIVE';
• Reconcile terms to generated billing records by joining on PAYMENT_TERM_ID against PN_DISTRIBUTIONS_ALL or PN_PAYMENT_ITEMS_ALL.
• Report customer billing exposure by joining CUSTOMER_ID to HZ_CUST_ACCOUNTS and aggregating ESTIMATED_AMOUNT by FREQUENCY_CODE.
• Audit term templates by grouping on TERM_TEMPLATE_ID to identify terms generated from standard templates versus manually entered terms.

Related Objects

The table participates in an extensive foreign-key web. Significant parents include PN_LEASES_ALL (LEASE_ID), PN_LEASE_CHANGES_ALL (LEASE_CHANGE_ID), PN_TERM_TEMPLATES_ALL (TERM_TEMPLATE_ID), HZ_CUST_ACCOUNTS (CUSTOMER_ID), HZ_CUST_SITE_USES_ALL (CUSTOMER_SITE_USE_ID), GL_CODE_COMBINATIONS (CODE_COMBINATION_ID), GL_SETS_OF_BOOKS_11I (SET_OF_BOOKS_ID), FND_CURRENCIES (CURRENCY_CODE), PO_VENDORS (VENDOR_ID), and PO_VENDOR_SITES_ALL (VENDOR_SITE_ID).

Significant children that reference PAYMENT_TERM_ID include PN_DISTRIBUTIONS_ALL, PN_PAYMENT_ITEMS_ALL, PN_PAYMENT_TERMS_HISTORY, PN_ADJUSTMENT_SUMMARIES, PN_LEASE_MILESTONES_ALL, PN_VAR_ABATEMENTS_ALL, PN_OPEX_EST_PAYMENTS_ALL, PN_INDEX_EXCLUDE_TERM_ALL, and PN_INDEX_LEASE_TERMS_ALL. These relationships make PN_PAYMENT_TERMS_ALL the central anchor for downstream billing, distribution, and reconciliations within Property Manager.