Results for “lease_termination_date”
50+ results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
PN_LEASE_DETAILS_V is a seeded Oracle E-Business Suite database view owned by the APPS schema and shipped as a VALID object within the PN (Property Manager) product module. It consolidates lease header attributes from PN_LEASES_ALL with the finer-grained lease detail records held in PN_LEASE_DETAILS, and enriches that data with the responsible user's login name and the descriptive name of the associated payment grouping rule. In Oracle EBS 12.1.1 and 12.2.2 this view serves as a denormalized reporting and integration surface for lease-level information, allowing concurrent programs, custom reports, Oracle Discoverer worksheets, and interface extracts to retrieve lease terms, financial account assignments, descriptive flexfield values, and audit columns without repeatedly coding the multi-table joins. Because the view already resolves the FND_USER and PN_PAY_GROUP_RULES lookups, it reduces the risk of duplicated or inconsistent join logic across downstream artifacts while preserving the standard PN data model.
Underlying Base Objects
The view is defined over four documented base objects, exposed through APPS synonyms:
- PN_LEASE_DETAILS (PLD) — the driving detail table; supplies lease detail identifiers, dates, accounts, grouping rule and term template references, DFF attributes, and audit columns.
- PN_LEASES_ALL (PNL) — the lease header table; joined on LEASE_ID to supply lease name, lease number, lease status, and the payment term proration rule. This is an _ALL table, so it is partitioned by ORG_ID.
- FND_USER (FNR) — joined on USER_ID = PLD.RESPONSIBLE_USER to resolve the responsible user's login name.
- PN_PAY_GROUP_RULES (PPGR) — outer-joined (GROUPING_RULE_ID (+)) on the grouping rule, so detail rows are retained even when no grouping rule is assigned.
All joins are effectively inner joins except the grouping rule, which is optional. The view therefore returns one row per lease detail record that has a matching lease and responsible user.
Key Columns
- LEASE_DETAIL_ID, LEASE_ID, LEASE_CHANGE_ID — primary keys linking to detail, header, and change records.
- LEASE_NAME, LEASE_NUMBER, LEASE_STATUS — identifying and lifecycle attributes sourced from PN_LEASES_ALL.
- RESPONSIBLE_USER_ID, USER_NAME — the internal user identifier and the resolved FND_USER login name.
- LEASE_EXECUTION_DATE, LEASE_COMMENCEMENT_DATE, LEASE_TERMINATION_DATE, LEASE_EXTENSION_END_DATE — key lease dates.
- LEASE_TERM — a derived value computed as TRUNC(NVL(termination, SYSDATE)) minus TRUNC(NVL(commencement, SYSDATE)) plus one, giving the inclusive lease term in days.
- EXPENSE_ACCOUNT_ID, ACCRUAL_ACCOUNT_ID, RECEIVABLE_ACCOUNT_ID — account assignments for expense, accrual, and receivable postings.
- TERM_TEMPLATE_ID, GROUPING_RULE_ID, PAYMENT_TERM_PRORATION_RULE — billing and term configuration references.
- ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 — the descriptive flexfield segments carried from the detail table.
- ORG_ID — the operating unit, enabling multi-org (MOAC) security filtering.
- Audit columns — CREATION_DATE/BY, LAST_UPDATE_DATE/BY, and LAST_UPDATE_LOGIN.
Common Use Cases and Queries
Typical scenarios include lease register reporting, responsible-user workload analysis, lease term/expiry tracking, and account assignment extracts. All queries should observe multi-org security by filtering on ORG_ID.
- List active leases with responsible party and remaining term for a given operating unit.
- Report leases approaching termination or extension dates.
- Extract account assignments for financial reconciliation.
- Read DFF attribute values without joining the detail table directly.
Illustrative query:
SELECT lease_number, lease_name, lease_status, user_name, lease_commencement_date, lease_termination_date, lease_term, org_id FROM apps.pn_lease_details_v WHERE org_id = :p_org_id AND lease_status = 'ACTIVE' ORDER BY lease_termination_date;
Because the view already resolves the user and grouping rule, no additional joins are required; simply add predicates on ORG_ID and lease status to scope the result set.
-
View: PN_LEASE_DETAILS_V 12.1.1
APPS.PN_LEASE_DETAILS_V·↳ FND_USER·↳ PN_LEASES_ALL·↳ PN_LEASE_DETAILS·Explore PN module →
-
View: PN_LEASES_V 12.2.2
APPS.PN_LEASES_V·↳ FND_GLOBAL·↳ FND_LOOKUPS·↳ FND_USER·Explore PN module →
-
PN_SPACE_UTIL_LEASE_ITF Interface Table.
-
PN_MILESTONES_ITF Interface Table.
-
PN_MILESTONES_ITF Interface Table.
-
PN_SPACE_ASSIGN_LEASE_ITF Interface Table.
-
Table: PN_LEASE_OPTIONS_ITF 12.2.2
PN_LEASE_OPTIONS_ITF Interface Table.
-
Lease dates and accounting information
-
View: PN_LEASE_DETAILS_V 12.2.2
APPS.PN_LEASE_DETAILS_V·↳ FND_USER·↳ PN_LEASES_ALL·↳ PN_LEASE_DETAILS·Explore PN module →
-
APPS.PN_LEASE_DETAILS_HISTORY_V·↳ FND_USER·↳ PN_LEASES_ALL·↳ PN_LEASE_DETAILS·Explore PN module →
-
View: PN_VAR_RENTS_V 12.2.2
Form view used to input variable rent agreement related information.
APPS.PN_VAR_RENTS_V·↳ FND_GLOBAL·↳ FND_LOOKUPS·↳ FND_USER·Explore PN module →
-
This table is used to create the RXi Rent Increase Account Detail Report
-
View: PN_VAR_RENTS_V 12.1.1
Form view used to input variable rent agreement related information.
APPS.PN_VAR_RENTS_V·↳ FND_GLOBAL·↳ FND_LOOKUPS·↳ FND_USER·Explore PN module →
-
PN_SPACE_UTIL_LEASE_ITF Interface Table.
-
This table is used to create the RXi Rent Increase Account Detail Report
-
This table is used to create the RXi Rent Increase Summary Report
-
PN_SPACE_ASSIGN_LEASE_ITF Interface Table.
-
PN_RENT_ROLL_LEASE_EXP_ITF Interface Table.
-
Lease dates and accounting information
-
View: PN_INDEX_LEASES_V 12.1.1
Form view for table PN_INDEX_LEASES_ALL
APPS.PN_INDEX_LEASES_V·↳ FND_GLOBAL·↳ FND_LOOKUPS·↳ FND_USER·Explore PN module →
-
Track changes to the lease details data elements
-
Track changes to the lease details data elements
-
View: PN_LEASES_V 12.1.1
APPS.PN_LEASES_V·↳ FND_GLOBAL·↳ FND_LOOKUPS·↳ FND_USER·Explore PN module →
-
APPS.PN_LEASE_DETAILS_HISTORY_V·↳ FND_USER·↳ PN_LEASES_ALL·↳ PN_LEASE_DETAILS·Explore PN module →
-
This table is used to create the RXi Rent Increase Detail Report
-
This table is used to create the RXi Rent Increase Summary Report
-
View: PN_INDEX_LEASES_V 12.2.2
Form view for table PN_INDEX_LEASES_ALL
APPS.PN_INDEX_LEASES_V·↳ FND_GLOBAL·↳ FND_LOOKUPS·↳ FND_USER·Explore PN module →
-
PN_RENT_ROLL_LEASE_EXP_ITF Interface Table.
-
Table: PN_LEASE_OPTIONS_ITF 12.1.1
PN_LEASE_OPTIONS_ITF Interface Table.
-
This table is used to create the RXi Rent Increase Detail Report
-
VIEW: PN.PN_MILESTONES_ITF# 12.2.2