Results for “pn_payment_items_all”

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

Overview

PN_PAYMENT_ITEMS_ALL is a Property Manager (PN) transactional table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores the individual payment and billing items associated with a payment or a billing schedule. In the context of Oracle Property Manager, the table acts as the operational ledger for scheduled cash flows tied to leases — including recurring rent, operating expense adjustments, and other periodic obligations. Each row represents a discrete payment or billing line that can be reported, transferred to Oracle Payables (AP) for disbursement, or transferred to Oracle Receivables (AR) for customer invoicing.

From a data modeling perspective, the heuristic Data Vault classification derived from the foreign key structure is satellite-leaning. This suggests the table behaves primarily as a descriptive satellite attached to hub or link structures such as lease, payment schedule, and party relationships, rather than as an independent hub. The surrogate primary key, PN_PAYMENT_ITEMS_PK on PAYMENT_ITEM_ID, uniquely identifies each item, and the unique index PN_PAYMENT_ITEMS_U1 confirms PAYMENT_ITEM_ID as the sole documented business-key candidate.

Key Information Stored

The table contains 58 documented columns. The most operationally significant include the following:

• PAYMENT_ITEM_ID — surrogate primary key and unique business-key candidate; the unique identifier of each payment or billing item.
• PAYMENT_SCHEDULE_ID — foreign key to PN_PAYMENT_SCHEDULES_ALL; identifies the parent schedule to which the item belongs.
• PAYMENT_TERM_ID — foreign key to PN_PAYMENT_TERMS_ALL; captures the payment terms applicable to the item.
• DUE_DATE — the date on which the payment or billing item falls due.
• PAYMENT_ITEM_TYPE_LOOKUP_CODE — classifies the item (e.g., recurring rent, adjustment, billing).
• ACTUAL_AMOUNT and ESTIMATED_AMOUNT — the confirmed and anticipated monetary values of the item.
• ACCOUNTED_AMOUNT and ACCOUNTED_DATE — the amount and date recorded for accounting (subledger) purposes.
• SET_OF_BOOKS_ID — foreign key to GL_SETS_OF_BOOKS_11I; identifies the ledger of record.
• CURRENCY_CODE and EXPORT_CURRENCY_CODE — functional and export currencies, both referencing FND_CURRENCIES; RATE carries the conversion rate.
• VENDOR_ID / VENDOR_SITE_ID — supplier references for payable items, keyed to PO_VENDORS and PO_VENDOR_SITES_ALL.
• CUSTOMER_ID / CUSTOMER_SITE_USE_ID / CUST_SHIP_SITE_ID — party and site references for receivable items, keyed to HZ_CUST_ACCOUNTS and HZ_CUST_SITE_USES_ALL.
• EXPORT_TO_AP_FLAG / TRANSFERRED_TO_AP_FLAG and EXPORT_TO_AR_FLAG / TRANSFERRED_TO_AR_FLAG — control flags governing downstream transfer to Payables and Receivables.
• ORG_ID — the operating unit, supporting multi-org security and reporting.
• XLA_EVENT_ID and GROUPING_RULE_ID — subledger accounting and grouping references.

Common Use Cases and Queries

Typical scenarios include payables-generation reports for lease payments due in a period, receivables-generation reports for billing schedules, accounting reconciliation against XLA events, and audit of transfer status to AP or AR.

Sample query — pending payable items due in a period:

• SELECT payment_item_id, payment_schedule_id, due_date, actual_amount, currency_code, vendor_id, org_id FROM pn_payment_items_all WHERE org_id = :org_id AND transferred_to_ap_flag = 'N' AND due_date BETWEEN :from_date AND :to_date;

Sample query — reconciliation of accounted amounts by ledger:

• SELECT set_of_books_id, SUM(actual_amount) actual, SUM(accounted_amount) accounted FROM pn_payment_items_all WHERE accounted_date BETWEEN :start_date AND :end_date GROUP BY set_of_books_id;

These patterns support period-close, cash-flow forecasting, and integration monitoring between Property Manager and the financial subledgers.

Related Objects

The most significant relationships are:

• PN_PAYMENT_SCHEDULES_ALL — parent schedule via PAYMENT_SCHEDULE_ID; the primary driver of item generation.
• PN_PAYMENT_TERMS_ALL — terms applied via PAYMENT_TERM_ID.
• PN_ADJUSTMENT_DETAILS — references Payment items via PAYMENT_ITEM_ID; stores adjustment details applied to items.
• PN_PAYMENT_ITEMS_EFC — extension/currency table keyed on PAYMENT_ITEM_ID.
• HZ_CUST_ACCOUNTS / HZ_CUST_SITE_USES_ALL — customer and site references for billing items (CUSTOMER_ID, CUSTOMER_SITE_USE_ID, CUST_SHIP_SITE_ID).
• PO_VENDORS / PO_VENDOR_SITES_ALL — supplier references for payable items.
• GL_SETS_OF_BOOKS_11I — ledger context via SET_OF_BOOKS_ID.
• FND_CURRENCIES — currency definitions for CURRENCY_CODE and EXPORT_CURRENCY_CODE.

Legacy views RA_CUSTOMERS and RA_SITE_USES_ALL also reference CUSTOMER_ID and CUSTOMER_SITE_USE_ID, reflecting backward compatibility with earlier Receivables data models. Together these objects anchor PN_PAYMENT_ITEMS_ALL firmly within the lease accounting and financial integration fabric of Oracle Property Manager.