Results for “lease_number”

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

Overview

FA_LEASE_PAYMENT_ITEMS_V is an APPS-owned view in the Oracle E-Business Suite OFA (Oracle Assets) module, with validity status VALID in the ETRM repository. It presents lease payment schedule items — the individual amortization lines that make up a lease payment schedule — enriched with context from the parent lease, its amortization schedule, and the lessor vendor record. In EBS 12.1.1 and 12.2.2 the view functions as a denormalized reporting and integration layer over the FA_LEASE_PAYMENT_ITEMS base table, which stores the operational lease payment rows. Because it joins the lease, schedule, and vendor entities, it is the natural source for listings that must display payment amounts and dates alongside lease number, currency, lessor identity, and the distribution accounting flexfield. The DIST_CODE_COMBINATION_ID column is the join key that links each payment item to the GL code combination used when the item is accounted or invoiced, which is a frequent starting point for reconciliation queries between Oracle Assets lease data and Oracle Payables and General Ledger.

Underlying Base Objects

The ETRM metadata documents the following referenced objects: FA_LEASE_PAYMENT_ITEMS (SYNONYM), FA_LEASES (SYNONYM), FA_AMORT_SCHEDULES (SYNONYM), PO_VENDORS (VIEW), and PO_VENDOR_SITES_ALL (VIEW); the FND_GLOBAL package is also referenced. The view text confirms this composition. FA_LEASE_PAYMENT_ITEMS is the driving table (aliased FLPI), supplying the payment item identity, export status, lessor site, distribution code combination, invoice attributes, request ID, and terms ID. FA_LEASES (FL) supplies LEASE_NUMBER and CURRENCY_CODE. FA_AMORT_SCHEDULES (FAS) supplies PAYMENT_AMOUNT and PAYMENT_DATE, matched on payment schedule ID and amortization line number. PO_VENDOR_SITES_ALL (PVS) resolves LESSOR_SITE_ID to vendor site code and vendor ID, and PO_VENDORS (PV) supplies LESSOR_NAME and LESSOR_NUM. Note that the vendor objects are themselves views in this release, and FND_GLOBAL is referenced for session context in the underlying definition.

Key Columns

• ROW_ID — ROWID of the underlying FA_LEASE_PAYMENT_ITEMS row.
• LEASE_ID, LEASE_NUMBER — Identifier and user-facing number of the parent lease.
• PAYMENT_SCHEDULE_ID, SCHEDULE_AMORT_LINE_NUM — Payment schedule and line that uniquely locate the item.
• PAYMENT_AMOUNT, PAYMENT_DATE — Amount and due date sourced from FA_AMORT_SCHEDULES.
• DIST_CODE_COMBINATION_ID — GL code combination assigned to the payment item; central to accounting reconciliation.
• EXPORT_STATUS — Indicates whether the item has been exported or transferred.
• LESSOR_SITE_ID, LESSOR_SITE_NAME, LESSOR_ID, LESSOR_NAME, LESSOR_NUM — Lessor vendor site and vendor identifiers from the PO views.
• INVOICE_ID, INVOICE_NUMBER, INVOICE_LINE_ID — Payables invoice linkage when the item has been invoiced.
• CURRENCY_CODE — Lease currency.
• Audit columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATED_BY, CREATION_DATE, LAST_UPDATE_LOGIN, REQUEST_ID, TERMS_ID.

Common Use Cases and Queries

The most common requirement triggered by the DIST_CODE_COMBINATION_ID column is resolving a payment item to its GL account. A representative query lists lease payments with their lessor, amount, and distribution combination:

• Payment listing by lease — SELECT lease_number, schedule_amort_line_num, payment_date, payment_amount, currency_code FROM fa_lease_payment_items_v WHERE lease_number = :lease_number ORDER BY payment_date;
• Distribution lookup — SELECT lease_number, payment_amount, dist_code_combination_id FROM fa_lease_payment_items_v WHERE dist_code_combination_id IS NOT NULL;
• Lessor exposure — SELECT lessor_num, lessor_name, lessor_site_name, SUM(payment_amount) FROM fa_lease_payment_items_v GROUP BY lessor_num, lessor_name, lessor_site_name;
• Invoice reconciliation — SELECT lease_number, invoice_number, invoice_line_id, export_status FROM fa_lease_payment_items_v WHERE invoice_id IS NOT NULL;
• Unaccounted items — SELECT * FROM fa_lease_payment_items_v WHERE dist_code_combination_id IS NULL;

Because the view joins vendor and schedule objects, queries should be filtered by lease or by date range to limit the join cost against the PO vendor views.