Search Results export_currency_code

Overview

PN_EXP_PAYMENT_ITEMS_V is an APPS-owned reporting view within the PN – Property Manager product family (leases and property management). It presents a unified, denormalized perspective of payment items that are candidates for export to Oracle Payables (AP), and, in parallel column structures, to Oracle Receivables (AR). The view is defined as an export-oriented reporting layer rather than a transactional entity; it does not itself store data but projects attributes from several PN payment, schedule, term, and distribution tables together with descriptive lookups and vendor information. The view is documented as VALID in ETRM 12.2.2 and is referenced in Oracle EBS 12.1.1 and 12.2.2 environments.

The view is significant because it exposes both AP-centric columns (VENDOR_ID, VENDOR_SITE_ID, AP_INVOICE_NUM) and placeholder AR-centric columns populated with TO_NUMBER(NULL) and TO_CHAR(NULL), reflecting the dual-direction export design of Property Manager payment processing. Its PAYMENT_TERM_TYPE_CODE column, sourced from PN_PAYMENT_TERMS_ALL, is the attribute most commonly queried when users analyze how payment terms drive the timing and classification of lease payment items.

Underlying Base Objects

The view is defined over the following documented base objects: PO_VENDORS (VIEW), FND_LOOKUPS (VIEW), PN_LEASES_ALL (SYNONYM), PN_PAYMENT_SCHEDULES_ALL (SYNONYM), PN_PAYMENT_TERMS_ALL (SYNONYM), PN_PAYMENT_ITEMS (SYNONYM), PN_DISTRIBUTIONS_ALL (SYNONYM), and PN_PAY_GROUP_RULES (SYNONYM). Documented metadata also references FND_GLOBAL (PACKAGE), PNP_UTIL_FUNC (PACKAGE), HZ_CUST_ACCOUNTS (SYNONYM), HZ_PARTIES (SYNONYM), and DUAL (SYNONYM) as objects involved in the wider view definition.

• PN_PAYMENT_ITEMS (PNPI) is the primary driving table, supplying amounts, flags, dates, currency, and identifiers.
• PN_PAYMENT_SCHEDULES_ALL (PNPS) supplies SCHEDULE_DATE and PERIOD_NAME.
• PN_PAYMENT_TERMS_ALL (PNPT) supplies PAYMENT_TERM_TYPE_CODE, PAYMENT_PURPOSE_CODE, and CODE_COMBINATION_ID.
• PN_LEASES_ALL (PNL) supplies LEASE_ID, LEASE_NAME, and LEASE_NUMBER.
• PN_DISTRIBUTIONS_ALL (PD) contributes the reconciliation liability account (REC_LIA_ACCOUNT_ID).
• PN_PAY_GROUP_RULES (PNGR) contributes the invoice group name.
• PO_VENDORS (POV) and FND_LOOKUPS (aliased twice) resolve vendor names and lookup meanings.

Key Columns

• PAYMENT_TERM_TYPE_CODE – Classification of the payment term associated with the item, sourced from PN_PAYMENT_TERMS_ALL.
• PAYMENT_PURPOSE, PAYMENT_TYPE, PAYMENT_PURPOSE_CODE – Decoded from FND_LOOKUPS using lookup types such as PN_PAYMENT_PURPOSE_TYPE.
• ACTUAL_AMOUNT, ESTIMATED_AMOUNT, EXPORT_CURRENCY_AMOUNT, RATE – Monetary values, with export currency conversion.
• EXPORT_TO_AP_FLAG, TRANSFERRED_TO_AP_FLAG – Status indicators controlling AP export.
• VENDOR_ID, VENDOR_SITE_ID, VENDOR_NAME, AP_INVOICE_NUM – Payables-side party and document references.
• LEASE_ID, LEASE_NAME, LEASE_NUMBER, PAYMENT_SCHEDULE_ID – Lease context keys.
• ORG_ID, SET_OF_BOOKS_ID, CURRENCY_CODE – Multi-org and ledger context.

Common Use Cases and Queries

The view is typically used to report payment items pending AP export, to reconcile lease payment schedules to AP invoices, and to analyze how payment terms influence item classification.

• Listing items awaiting AP export by lease.
• Aggregating amounts by payment term type code.
• Reconciling exported items to AP invoice numbers.

Example query filtering by payment term type code:

SELECT lease_number, payment_schedule_id, payment_term_type_code,
      payment_purpose, actual_amount, currency_code, due_date
 FROM apps.pn_exp_payment_items_v
 WHERE payment_term_type_code = :p_term_type
   AND org_id = :p_org_id
 ORDER BY lease_number, due_date;

Example query for items pending AP export:

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