Results for “pn_payment_term_type”

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

Overview

APPS.PN_EXP_PAYMENT_ITEMS_V is a reporting view in Oracle Property Manager (PN) exposed within the APPS schema. It presents payment items, payment terms, payment schedules, lease information, and vendor details in a single flattened structure intended for extraction, reconciliation, and external integration. In Oracle EBS 12.1.1 and 12.2.2, the view serves as the primary interface for transferring Property Manager payment obligations into Oracle Payables and, where relevant, Oracle Receivables, as indicated by its export_to_ap_flag, transferred_to_ap_flag, and companion AR-oriented columns. Because the underlying PN_EXP_PAYMENT_ITEMS package and related objects are not part of the public API surface, this view is the documented means by which implementers and analysts access payment item data without querying base tables directly. It supports compliance with the lease accounting and payment distribution requirements typical of Property Manager implementations.

Underlying Base Objects

The documented base objects referenced by this view include PN_DISTRIBUTIONS_ALL, PN_LEASES_ALL, PN_PAYMENT_ITEMS, PN_PAYMENT_SCHEDULES_ALL, PN_PAYMENT_TERMS_ALL, PN_PAY_GROUP_RULES, FND_LOOKUPS, PO_VENDORS, and the packages FND_GLOBAL and PNP_UTIL_FUNC. Synonyms such as HZ_CUST_ACCOUNTS, HZ_PARTIES, and DUAL are also listed, reflecting the view's capability to resolve both vendor and customer parties. The join structure links payment items (PN_PAYMENT_ITEMS) to payment terms (PN_PAYMENT_TERMS_ALL), schedules (PN_PAYMENT_SCHEDULES_ALL), leases (PN_LEASES_ALL), distributions (PN_DISTRIBUTIONS_ALL), and grouping rules (PN_PAY_GROUP_RULES). Lookups in FND_LOOKUPS decode PN_PAYMENT_PURPOSE_TYPE and PN_PAYMENT_TERM_TYPE into descriptive meanings.

Key Columns

• payment_item_id, payment_schedule_id, payment_term_id, lease_id — primary identifiers for reconciliation and joins to base tables.
• export_to_ap_flag, transferred_to_ap_flag, export_to_ar_flag, transferred_to_ar_flag — integration status flags governing transfer to Payables and Receivables.
• vendor_id, vendor_site_id, vendor_name, ap_invoice_num — supplier-side payment identifiers.
• actual_amount, estimated_amount, export_currency_amount, currency_code, export_currency_code, rate — monetary and currency conversion data.
• due_date, schedule_date, period_name — payment timing and GL period reference.
• set_of_books_id, org_id — ledger and operating unit context, essential for multi-org reporting.
• rec_lia_account_id (aliased from pd.account_id) — the receivable liability account identifier sourced from PN_DISTRIBUTIONS_ALL, used for accounting and reconciliation of scheduled payment distributions.
• payment_purpose, payment_type, payment_purpose_code, payment_term_type_code — lookup-derived descriptive categories.

Common Use Cases and Queries

The view supports reconciliation of Property Manager obligations to Payables invoices, audit of payment purpose and term classification, and analysis of receivable liability postings by ledger. A typical query retrieving payment items with their receivable liability account is:

SELECT payment_item_id, lease_num, vendor_name,
       payment_purpose, payment_type, due_date,
       actual_amount, currency_code, rec_lia_account_id
FROM   apps.pn_exp_payment_items_v
WHERE  org_id = :p_org_id
AND    due_date BETWEEN :p_from AND :p_to;

To identify items pending transfer to Payables:

SELECT payment_item_id, lease_num, ap_invoice_num, actual_amount
FROM   apps.pn_exp_payment_items_v
WHERE  export_to_ap_flag = 'Y'
AND    transferred_to_ap_flag = 'N';

Because the view references FND_GLOBAL, PNP_UTIL_FUNC, and multi-org context, queries should generally be filtered by org_id and run under a valid application responsibility to ensure correct operating unit security and ledger resolution.