Search Results term_normalize_flag

Overview

PN_PAYMENT_ITEMS_V is an Oracle E-Business Suite 12.1.1 / 12.2.2 reporting view owned by the APPS schema within the PN – Property Manager product. It presents payment items associated with property leases, consolidating the transactional payment item record from PN_PAYMENT_ITEMS with descriptive lookup meanings, vendor and customer party details, payment term attributes, and site-use location information. Rather than exposing raw foreign-key identifiers alone, the view resolves many of them into human-readable values through joins to FND_LOOKUPS, FND_LOOKUP_VALUES, HZ_CUST_ACCOUNTS_ALL, HZ_CUST_SITE_USES_ALL, HZ_PARTIES, PO_VENDORS, PO_VENDOR_SITES_ALL, and PN_PAY_GROUP_RULES. This makes the view well suited for ad-hoc reporting, lease payment reconciliation, and integration extracts where consumers require labeled attributes instead of coded lookups. The presence of the standard WHO columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) and the ROW_ID column confirms it is a conventional EBS reporting view supporting both informational queries and potential programmatic access.

Underlying Base Objects

The documented base objects referenced by the view include the following. The primary transactional source is PN_PAYMENT_ITEMS (PN_PAYMENT_ITEMS synonym), which supplies payment amounts, dates, currency, and lookup codes. PN_PAYMENT_TERMS_ALL and PN_LEASES_ALL provide payment term and lease context. PN_PAY_GROUP_RULES supplies the invoice grouping rule description. Descriptive lookups are resolved via FND_LOOKUPS and FND_LOOKUP_VALUES, joined to translate PAYMENT_ITEM_TYPE_LOOKUP_CODE and related codes into displayed meanings. Trading partner data is drawn from HZ_CUST_ACCOUNTS_ALL, HZ_CUST_SITE_USES_ALL, and HZ_PARTIES for customer attributes, and PO_VENDORS and PO_VENDOR_SITES_ALL for supplier attributes. FND_GLOBAL is referenced, typically for session or responsibility context. The view therefore sits logically between the raw PN_PAYMENT_ITEMS table and presentation-layer reporting requirements.

Key Columns

• PAYMENT_ITEM_ID / PAYMENT_ITEM_TYPE_LOOKUP_CODE – Primary identifier and the lookup code describing the nature of the payment item; the code is joined to FND_LOOKUP_VALUES.
• DUE_DATE, SET_OF_BOOKS_ID, CURRENCY_CODE, RATE – Scheduling and accounting context for the payment item.
• PAYMENT_TERM_ID / PAYMENT_SCHEDULE_ID – Links to payment terms and schedules.
• VENDOR_ID, VENDOR_SITE_ID, CUSTOMER_ID, CUSTOMER_SITE_USE_ID – Foreign keys resolving to VENDOR_NAME, VENDOR_NUMBER, VENDOR_SITE, CUSTOMER_NAME, CUSTOMER_NUMBER, and site-use locations.
• ACTUAL_AMOUNT, ESTIMATED_AMOUNT, ACCOUNTED_AMOUNT, ACCOUNTED_DATE – Financial measures central to reconciliation.
• TRANSFERRED_TO_AP_FLAG / AP_INVOICE_NUM – Indicates whether the item was transferred to Payables and the resulting invoice reference.
• PAYMENT_PURPOSE / PAYMENT_TERM_TYPE – Lookup meanings supplied by the FLV/FLV1 join aliases.
• ONE_TIME, TERM_NORMALIZE_FLAG, CODE_COMBINATION_ID – Derived from PN_PAYMENT_TERMS_ALL to describe term behaviour.
• INV_GROUP_NAME, GROUPING_RULE_ID – Invoice grouping rule context.
• ADJ_START_DATE, ADJ_END_DATE, LAST_ADJUSTMENT_TYPE_CODE – Adjustment window and last adjustment type for the item.
• ATTRIBUTE_CATEGORY and descriptive-flex columns – Exposes descriptive flexfield segments.

Common Use Cases and Queries

Typical scenarios include extracting lease payment items for a given set of books or period, reconciling actual versus estimated amounts, and identifying items not yet transferred to Payables. For example, to list payment items by purpose and party, a query such as:

SELECT payment_item_id, due_date, payment_item_type_lookup_code, payment_purpose, actual_amount, estimated_amount, vendor_name, customer_name FROM apps.pn_payment_items_v WHERE set_of_books_id = :p_sob ORDER BY due_date;

Developers frequently search on PAYMENT_ITEM_TYPE_LOOKUP_CODE to filter by item classification; the view’s join to FND_LOOKUP_VALUES ensures the corresponding meaning is available without secondary lookups. A reconciliation query might compare TERM_ACTUAL_AMOUNT and TERM_ESTIMATED_AMOUNT against ACTUAL_AMOUNT and ESTIMATED_AMOUNT, while a Payables-transfer check would filter on TRANSFERRED_TO_AP_FLAG = 'N' and inspect AP_INVOICE_NUM for items already interfaced.