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

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.