Results for “lease_execution_date”

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

Overview

The PN_LEASE_DETAILS_ALL table is a core transaction table within the Oracle Property Manager (PN) module of Oracle E-Business Suite. It stores lease dates and accounting information associated with lease agreements, capturing the financial and temporal attributes that drive accrual, payment, and accounting entries for leased properties. In Oracle EBS 12.1.1 and 12.2.2, this table sits at the intersection of lease administration and subledger accounting, feeding the Property Manager accounting engine with the account distributions, dates, and responsible parties needed to generate journal entries through Subledger Accounting (SLA).

Based on the foreign key topology extracted from the ETRM metadata, this object is heuristic-classified as satellite-leaning in a Data Vault modeling sense. It functions as a descriptive satellite tied primarily to PN_LEASES_ALL (via LEASE_ID), carrying the time-variant and context-specific detail attributes rather than serving as a hub of business keys or a pure link between entities. The presence of a corresponding history table, PN_LEASE_DETAILS_HISTORY, reinforces this interpretation, as satellite structures typically maintain historical versions of the descriptive attributes.

Key Information Stored

The table contains 36 documented columns. The most significant are:

• LEASE_DETAIL_ID — Surrogate primary key (PN_LEASE_DETAILS_PK) and the unique index candidate (PN_LEASE_DETAILS_U1). It uniquely identifies each lease detail row.
• LEASE_ID — Foreign key to PN_LEASES_ALL, tying the detail record to its parent lease agreement.
• LEASE_CHANGE_ID — Foreign key to PN_LEASE_CHANGES_ALL, linking the detail to a specific lease change or amendment transaction.
• RESPONSIBLE_USER — Foreign key to FND_USER, identifying the individual accountable for the lease detail.
• EXPENSE_ACCOUNT_ID — Foreign key to GL_CODE_COMBINATIONS, the expense account used in accounting distributions.
• ACCRUAL_ACCOUNT_ID — The accrual account for lease liability recognition.
• RECEIVABLE_ACCOUNT_ID — The receivable account applied where lease recovery or billing applies.
• LEASE_COMMENCEMENT_DATE — Start date of the lease term.
• LEASE_TERMINATION_DATE — End date of the lease term.
• LEASE_EXECUTION_DATE — Date the lease was executed.
• LEASE_EXTENSION_END_DATE — End date of an exercised lease extension.
• TERM_TEMPLATE_ID — Foreign key to PN_TERM_TEMPLATES_ALL, defining the term structure applied.
• SEND_ENTRIES — Flag controlling whether accounting entries are transferred to the general ledger.
• GROUPING_RULE_ID — Identifier governing how lease details are grouped for accounting.
• ORG_ID — Operating unit identifier, enforcing multi-org data segregation.

The standard WHO columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) and the 15 ATTRIBUTE flex columns (ATTRIBUTE_CATEGORY, ATTRIBUTE1–15) are also present for audit and descriptive flexibility.

Common Use Cases and Queries

Typical reporting and integration scenarios include extracting lease detail records for a given lease, verifying accounting account assignments, and auditing lease term dates for expirations and extensions. A representative query joining the parent lease and expense account might read:

SELECT d.lease_detail_id, d.lease_id, l.lease_number, d.lease_commencement_date, d.lease_termination_date, g.concatenated_segments expense_account
FROM pn_lease_details_all d, pn_leases_all l, gl_code_combinations_kfv g
WHERE d.lease_id = l.lease_id
AND d.expense_account_id = g.code_combination_id
AND d.org_id = :p_org_id;

Other use cases include reconciliation of lease accruals against GL balances, reporting on leases nearing termination or extension, and identifying details flagged for entry submission (SEND_ENTRIES). Reporting tools such as Oracle BI Publisher, Discoverer, and custom concurrent programs routinely query this table.

Related Objects

• PN_LEASES_ALL — Parent lease master; joined on LEASE_ID.
• PN_LEASE_CHANGES_ALL — Lease change transactions; joined on LEASE_CHANGE_ID.
• PN_LEASE_DETAILS_HISTORY — Historical versions; references LEASE_DETAIL_ID.
• PN_TERM_TEMPLATES_ALL — Term templates; joined on TERM_TEMPLATE_ID.
• GL_CODE_COMBINATIONS — Account validation and distribution source.
• FND_USER — Responsible user information.
• Subledger Accounting (XLA) events — Consume lease details to create accounting.

Collectively, these relationships position PN_LEASE_DETAILS_ALL as the principal descriptive and accounting-detail satellite for lease agreements in Oracle Property Manager.