Results for “pn_xla_extract_headers_v”

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

Overview

The view PN_XLA_EXTRACT_HEADERS_V is owned by the APPS schema and belongs to the PN (Property Manager) product family. It presents a denormalized, reporting-oriented projection of lease payment terms, enriched with descriptive lookup meanings and human-readable business identifiers, and joined to the Subledger Accounting (XLA) event model. Because it is a view rather than a table, it exposes no persistent storage of its own; it is intended for consumption by reports, extracts, and integration interfaces that must reconcile Property Manager lease obligations with their corresponding accounting events.

The view is primarily relevant in the context of Oracle E-Business Suite Release 12 subledger accounting, where Property Manager transactions are captured as XLA events. By surfacing lease, customer, supplier, property, item, and event data in a single flat structure, the view supports downstream extraction patterns — for example, feeding a data warehouse or a customer-defined accounting engine — without requiring the caller to reassemble the underlying normalized relationships.

Underlying Base Objects

The documented metadata identifies the following referenced base objects:

• PN_LEASES_ALL — supplies the lease header, lease name, and lease number.
• PN_PAYMENT_TERMS_ALL — the central driver, supplying location, customer, supplier, site use, attribute, and term references.
• PN_PAYMENT_ITEMS — supplies payment item identifiers and item-level descriptive flexfield attributes.
• PN_LOCATIONS_ALL and PN_PROPERTIES_ALL — provide location codes and property code/name.
• HZ_CUST_ACCOUNTS_ALL, HZ_CUST_SITE_USES_ALL, and HZ_PARTIES — provide trading-partner customer identity, party name, and site information.
• PO_VENDORS and PO_VENDOR_SITES_ALL — provide supplier name and supplier site code.
• FND_LOOKUPS — converts coded lookup values into meanings for lease class, payment purpose, payment type, and payment term frequency.
• XLA_EVENTS and XLA_TRANSACTION_ENTITIES — link the term to its accounting event.
• FND_GLOBAL — the standard EBS package used for session context (for example, USER_ID and RESP_ID).

Several of these are exposed as synonyms, reflecting the standard APPS-layer access pattern in Release 12.

Key Columns

The columns most frequently referenced in extracts include:

• LEASE_CLASS, LEASE_NAME, LEASE_NUMBER — lease identification and classification.
• CUSTOMER_ACCOUNT_ID — sourced from TERM.CUSTOMER_ID; the customer account identifier against which lease receivables are recognized.
• CUSTOMER_NAME, CUSTOMER_SITE, CUSTOMER_SITE_ID — customer party and site detail.
• SUPPLIER_ID, SUPPLIER_SITE_ID, SUPPLIER_NAME, SUPPLIER_SITE — supplier identification for payment-side processing.
• PAYMENT_ITEM_ID, PAYMENT_TERM_ID, PAYMENT_PURPOSE, PAYMENT_TYPE, PAYMENT_TERM_FREQUENCY — the payment obligation being extracted.
• LOCATION_ID, LOCATION_CODE, PROPERTY_CODE, PROPERTY_NAME — the leased premises.
• EVENT_ID — the XLA event identifier used to tie the row to subledger accounting.
• Term and item ATTRIBUTE_CATEGORY and ATTRIBUTE1…15 — descriptive flexfield values carried through for user-defined reporting.

Common Use Cases and Queries

A typical use is locating the customer account associated with a lease payment term, which is precisely the pattern that surfaces when searching on customer_account_id:

• SELECT lease_number, customer_account_id, customer_name, payment_type FROM pn_xla_extract_headers_v WHERE customer_account_id = :cust_id;
• SELECT event_id, lease_number, supplier_id, payment_term_id FROM pn_xla_extract_headers_v WHERE event_id = :event_id;

Because the view already resolves lookup meanings, it is also well suited to frequency and purpose analysis:

• SELECT payment_purpose, payment_term_frequency, COUNT(*) FROM pn_xla_extract_headers_v GROUP BY payment_purpose, payment_term_frequency;

When using the view, note that it is not filtered by operating unit or ledger, so callers should apply their own security predicates on location_id or customer_account_id as required. It is also advisable to restrict extracts by event_id or lease scope to avoid full-table scans across the lease population.