Search Results amendment_term

Overview

The APPS.PN_LEASE_CHANGES_V view is a reporting and integration object within the Oracle Property Manager (PN) module of Oracle E-Business Suite, available in releases 12.1.1 and 12.2.2. It presents lease amendment and change records — lease changes, amendments, renewals, terminations, and similar transactions — enriched with descriptive values resolved from Oracle lookup tables and Oracle Trading Community Architecture (TCA) entities. Rather than exposing raw foreign key identifiers alone, the view denormalizes those keys into human-readable meanings, transaction types, lease classifications, customer party names, and user names. This makes it suitable for operational reporting, lease administration inquiries, downstream data extracts, and integration interfaces where a flat, ready-to-consume record set is preferable to joining base tables directly.

Underlying Base Objects

The view is defined over a set of core Property Manager tables joined to lookup and reference sources. The primary change record is sourced from PN_LEASE_CHANGES_ALL, aliased LCHANGE. This is joined to PN_LEASES (aliased LEASE) to bring in lease-level attributes such as status, lease number, lease type, and class. PN_LEASE_TRANSACTIONS_ALL (aliased PLT) supplies the transaction type code associated with the change, while PN_LEASE_DETAILS_HISTORY is referenced within the view's underlying logic for historical lease detail context. FND_USER (aliased FNA and FNR) resolves the ABSTRACTED_BY_USER and RESPONSIBLE_USER identifiers into usernames. FND_LOOKUPS (aliased FLV, FLL, FLC) provides lookup meanings for transaction type, lease type, and lease class. HZ_PARTIES (aliased HZP) and HZ_CUST_ACCOUNTS (aliased HCA) supply customer party name and account number from TCA. FND_GLOBAL is referenced to support the standard WHO columns and environment context. Because the view does not restrict rows by operating unit, consumers should apply any required security or organizational filtering in their own queries.

Key Columns

Identity columns include LEASE_CHANGE_ID, LEASE_ID, LEASE_TRANSACTION_ID, and ROW_ID (the underlying row identifier). Descriptive identifiers include LEASE_CHANGE_NUMBER, LEASE_CHANGE_NAME, LEASE_NUMBER, and LEASE_NAME.

• ABSTRACTED_BY_USER_ID — the identifier of the user who abstracted the lease change, resolved by join to FND_USER as USER_ABSTRACTED. This is the column most directly related to the search term "abstracted_by_user_id".
• RESPONSIBLE_USER_ID / USER_RESPONSIBLE — the responsible user identifier and resolved username.
• CHANGE_TYPE_LOOKUP_CODE — the lookup code classifying the amendment or change.
• CHANGE_EXECUTION_DATE, CHANGE_COMMENCEMENT_DATE, CHANGE_TERMINATION_DATE — key dates defining the change's execution and effective term.
• AMENDMENT_TERM — a computed value derived as the inclusive day count between the commencement and termination dates.
• TRANSACTION_TYPE_CODE / TRANSACTION_TYPE — the raw transaction code and its lookup meaning.
• STATUS, LEASE_STATUS, LEASE_TYPE_CODE, LEASE_TYPE, LEASE_CLASS_CODE, LEASE_CLASS — lease-level state and classification attributes.
• CUSTOMER_ID, CUSTOMER_NAME, ACCOUNT_NUMBER — TCA customer party and account information.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 — the standard descriptive flexfield columns carried through from PN_LEASE_CHANGES_ALL.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — the standard WHO audit columns.

Common Use Cases and Queries

Typical uses include listing amendments per lease, reporting changes by transaction type or class, auditing which users abstracted changes, and extracting lease change data for integration. A representative query returning changes with their resolved types, classes, and the abstracting user is:

• SELECT lease_number, lease_name, lease_change_number, lease_change_name, transaction_type, lease_class, change_commencement_date, change_termination_date, amendment_term, user_abstracted, user_responsible FROM apps.pn_lease_changes_v WHERE lease_id = :p_lease_id ORDER BY change_commencement_date;
• SELECT user_abstracted, COUNT(*) FROM apps.pn_lease_changes_v GROUP BY user_abstracted;
• SELECT lease_number, customer_name, transaction_type, change_execution_date FROM apps.pn_lease_changes_v WHERE change_type_lookup_code = :p_change_type;

Because the view resolves lookups and user names, these queries avoid additional joins and return immediately meaningful results for reporting and validation.