Search Results fa_lease_payment_items_u1

Overview

FA.FA_LEASE_PAYMENT_ITEMS is a transaction-level table in the Oracle E-Business Suite Fixed Assets (FA) module that stores the individual payment schedule amortization lines associated with capitalized lease contracts. It represents the intersection between lease payment schedules defined in FA_LEASES and the invoice or distribution detail that ultimately drives accounting entries for lease obligations. The table resides in the APPS_TS_TX_DATA tablespace with a PCT Free of 10, and its FND design data is registered as OFA.FA_LEASE_PAYMENT_ITEMS. In Oracle EBS 12.1.1 and 12.2.2, this table supports lease accounting workflows where scheduled payments are amortized, exported to downstream processes, and reconciled against payables invoices.

Based on the foreign key structure, the heuristic Data Vault classification is satellite-leaning. The table is keyed on LEASE_ID and PAYMENT_SCHEDULE_ID, both of which reference parent lease and schedule entities, and carries descriptive and transactional attributes such as invoice references, distribution code combinations, and export status. This positions the table as a satellite capturing the changing detail of lease payment amortization lines rather than a standalone hub or a pure link.

Key Information Stored

The unique index FA_LEASE_PAYMENT_ITEMS_U1 is defined on LEASE_ID, PAYMENT_SCHEDULE_ID, and SCHEDULE_AMORT_LINE_NUM. This three-column composite serves as the business-key candidate for the table; there is no single-column surrogate primary key documented. Key columns include:

• LEASE_ID — Foreign key to FA_LEASES; identifies the parent lease contract.
• PAYMENT_SCHEDULE_ID — Identifies the specific payment schedule version or stream within the lease.
• SCHEDULE_AMORT_LINE_NUM — Line number sequencing each amortization entry within a schedule.
• EXPORT_STATUS — Tracks whether the line has been exported to a downstream process such as Payables or the general ledger.
• LESSOR_ID and LESSOR_SITE_ID — Identify the lessor party and site used for payment processing.
• DIST_CODE_COMBINATION_ID — The distribution account used for accounting entries.
• INVOICE_ID, INVOICE_LINE_ID, and INVOICE_NUMBER — Reference the Payables invoice and line matched to the lease payment. INVOICE_LINE_ID has a documented foreign key to FTE_INVOICE_LINES.
• TERMS_ID — Payment terms applied to the lease line.
• REQUEST_ID — The concurrent program request that created or last processed the row.
• Standard audit columns: LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATED_BY, CREATION_DATE, and LAST_UPDATE_LOGIN.

Common Use Cases and Queries

Typical reporting scenarios include identifying lease payment lines not yet exported, reconciling lease amortization to Payables invoices, and auditing accounting distributions. A common query pattern selects all amortization lines for a given lease:

SELECT LEASE_ID, PAYMENT_SCHEDULE_ID, SCHEDULE_AMORT_LINE_NUM, EXPORT_STATUS, INVOICE_NUMBER, DIST_CODE_COMBINATION_ID FROM FA.FA_LEASE_PAYMENT_ITEMS WHERE LEASE_ID = :lease_id ORDER BY PAYMENT_SCHEDULE_ID, SCHEDULE_AMORT_LINE_NUM;

To find unexported lines awaiting processing:

SELECT * FROM FA.FA_LEASE_PAYMENT_ITEMS WHERE EXPORT_STATUS = 'NEW' OR EXPORT_STATUS IS NULL;

Joining to FA_LEASES on LEASE_ID provides lease-level context for reconciliation reports, while joining INVOICE_ID to AP_INVOICES_ALL supports payables matching analysis.

Related Objects

The most significant related objects based on the documented foreign keys and dependency data include:

• FA_LEASES — Parent lease master; joined on LEASE_ID.
• FTE_INVOICE_LINES — Invoice line detail; joined on INVOICE_LINE_ID.
• AP_INVOICES_ALL — Payables invoice header referenced via INVOICE_ID for invoice reconciliation.
• FA_LEASE_PAYMENT_SCHEDULES — Payment schedule parent referenced via PAYMENT_SCHEDULE_ID (implied by composite key).
• FA_LEASE_PAYMENT_ITEMS (APPS synonym) — The APPS-layer synonym through which the table is accessed from the application schema.
• OF A.FA_LEASE_PAYMENT_ITEMS — The FND design data registration supporting the underlying data model.

Because FA_LEASE_PAYMENT_ITEMS does not reference any database object beyond the documented foreign keys, its dependency footprint is primarily downstream, feeding lease accounting and payables integration processes.