Search Results pn_lease_type




Overview
Explore in AI Chat

Overview

APPS.PN_LEASE_CHANGES_V is a reporting view in the Oracle Property Manager (PN) module of Oracle E-Business Suite, available in releases 12.1.1 and 12.2.2. It presents lease change (amendment) records from the lease change transaction infrastructure and enriches them with descriptive attributes drawn from the parent lease, lease transaction, and reference lookup tables. The view is intended for inquiry, reporting, and integration purposes rather than transactional data entry; all DML is performed against the underlying _ALL tables.

Its role is to denormalize lease amendment data into a single, human-readable result set. Rather than joining PN_LEASE_CHANGES_ALL to PN_LEASES, PN_LEASE_TRANSACTIONS_ALL, HZ_PARTIES, and FND_LOOKUPS manually, consumers can query one view to obtain lease numbers, customer names, lookup meanings, and computed amendment terms. The view sits within the standard multi-org model, exposing ORG_ID from the parent lease.

Underlying Base Objects

The view is defined over the following documented objects:

  • PN_LEASE_CHANGES_ALL (synonym) — the driving table, supplying lease change identity, numbering, responsible and abstracted users, execution/commencement/termination dates, change type lookup code, and the DFF attribute columns.
  • PN_LEASES (synonym) — the parent lease, supplying lease number, name, status, lease_status, lease_type_code, lease_class_code, location, customer, and ORG_ID.
  • PN_LEASE_TRANSACTIONS_ALL (synonym) — joined via LEASE_TRANSACTION_ID to supply TRANSACTION_TYPE_CODE.
  • PN_LEASE_DETAILS_HISTORY (synonym) — referenced as PDH, supplying LEASE_STATUS used with NVL against the lease status.
  • FND_USER (synonym) — two aliases (FNA, FNR) resolve the abstracted_by and responsible_user IDs to user names.
  • FND_LOOKUPS (view) — aliases FLV, FLL, and FLC resolve transaction type, lease type, and lease class lookup codes to their meanings.
  • HZ_PARTIES and HZ_CUST_ACCOUNTS (synonyms) — supply customer name and account number.
  • FND_GLOBAL (package) — referenced for session/org context functions.

Key Columns

The view exposes ROWID as ROW_ID and the lease change primary key LEASE_CHANGE_ID, alongside LEASE_ID and LEASE_TRANSACTION_ID. Identification columns include LEASE_CHANGE_NUMBER and LEASE_CHANGE_NAME. Audit columns cover CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN.

Personnel columns pair IDs with resolved names: ABSTRACTED_BY_USER_ID / USER_ABSTRACTED and RESPONSIBLE_USER_ID / USER_RESPONSIBLE. Dates include CHANGE_EXECUTION_DATE, CHANGE_COMMENCEMENT_DATE, and CHANGE_TERMINATION_DATE, with the derived AMENDMENT_TERM computed as TRUNC(change_termination_date) - TRUNC(change_commencement_date) + 1.

Descriptive columns include CHANGE_TYPE_LOOKUP_CODE, TRANSACTION_TYPE_CODE and TRANSACTION_TYPE (meaning), LEASE_NUMBER, LEASE_NAME, LEASE_TYPE_CODE and LEASE_TYPE (meaning from FND_LOOKUPS), LEASE_CLASS_CODE and LEASE_CLASS, STATUS, LEASE_STATUS (NVL of history over lease status), CUSTOMER_NAME, CUSTOMER_NUMBER, LOCATION_ID, CUSTOMER_ID, and ORG_ID. Fifteen DFF columns (ATTRIBUTE_CATEGORY and ATTRIBUTE1–15) are also surfaced.

Common Use Cases and Queries

Typical uses include amendment registers, lease change date tracking, customer-facing lease activity reports, and interface extracts that require resolved lookup meanings.

List all changes for a lease:

  • SELECT lease_change_number, lease_change_name, transaction_type, lease_type, change_commencement_date, change_termination_date, amendment_term FROM apps.pn_lease_changes_v WHERE lease_number = :lease_num ORDER BY change_commencement_date;

Filter by the lease type the user searched for ("pn_lease_type"), which maps to LEASE_TYPE_CODE / LEASE_TYPE:

  • SELECT lease_number, lease_name, lease_type_code, lease_type, lease_change_name FROM apps.pn_lease_changes_v WHERE lease_type_code = :p_lease_type_code;

Restrict by operating unit and responsible user:

  • SELECT lease_number, lease_change_number, user_responsible, change_execution_date FROM apps.pn_lease_changes_v WHERE org_id = :p_org_id AND user_responsible = :p_user ORDER BY change_execution_date DESC;

Because the view already resolves users and lookups, it is well suited to concurrent program extracts and BI Publisher reports where additional joins would otherwise duplicate this logic.