Search Results pn_lease_transactions_v




Overview
Explore in AI Chat

Overview

PN_LEASE_TRANSACTIONS_V is a view owned by the APPS schema in Oracle E-Business Suite, defined within the Property Manager (PN) product module. The view presents lease transaction records enriched with descriptive lookup values and user information, providing a denormalized perspective on lease change activity. Its primary role is to support reporting and integration scenarios in which lease transactions must be presented with human-readable transaction type descriptions rather than raw lookup codes.

The view is particularly relevant to users searching for transaction_type_code, since it exposes the underlying lease transaction type as a column named TRANSACTION_TYPE_CODE, translated per row into a display meaning through the TRANSACTION_TYPE column. Querying this view therefore allows both the coded and descriptive forms to be retrieved from a single source, eliminating the need for consumers to join to FND_LOOKUPS and FND_USER manually.

Underlying Base Objects

The view is defined over several documented objects. The principal transactional source is PN_LEASE_TRANSACTIONS, aliased LTRX, which supplies the core lease transaction identifier, lease and location references, transaction type code, date effective, audit columns, and ORG_ID. It is joined to PN_LEASE_CHANGES_ALL (alias LCHANGE) on LEASE_TRANSACTION_ID to obtain the LEASE_CHANGE_ID, distinguishing between the transaction header record and the associated lease change record.

The transaction type code is translated by joining FND_LOOKUPS (alias FLV) where LOOKUP_CODE equals the transaction type and LOOKUP_TYPE equals 'PN_LEASE_CHANGE_TYPE'. The creator's user name is obtained from FND_USER (alias FNC) matched on USER_ID to CREATED_BY. A reference to FND_GLOBAL is also documented, consistent with ORG_ID being sourced from the operating unit context. The joins are inner joins, so only transactions with a matching lease change, a valid PN_LEASE_CHANGE_TYPE lookup, and a resolvable creating user are returned.

Key Columns

  • LEASE_TRANSACTION_ID — Primary surrogate identifier for the lease transaction, and the join key to PN_LEASE_CHANGES_ALL.
  • LEASE_ID — Reference to the lease to which the transaction belongs.
  • LOCATION_ID — Identifier of the location associated with the transaction.
  • TRANSACTION_TYPE_CODE — The raw lease transaction type code stored on PN_LEASE_TRANSACTIONS; the lookup code expected to exist under LOOKUP_TYPE 'PN_LEASE_CHANGE_TYPE'.
  • TRANSACTION_TYPE — The FND_LOOKUPS MEANING corresponding to TRANSACTION_TYPE_CODE, providing the descriptive transaction type.
  • DATE_EFFECTIVE — The effective date of the transaction.
  • LEASE_CHANGE_ID — Identifier of the associated lease change record.
  • CREATED_BY, CREATED_BY_NAME — The creating user identifier and the resolved FND_USER user name.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, LAST_UPDATE_LOGIN — Standard audit columns.
  • ORG_ID — Operating unit identifier for multi-organization security.
  • ROW_ID — The ROWID of the underlying transaction row.

Common Use Cases and Queries

Typical use cases include lease change reporting, workload analysis by creating user, and integration extracts that require both coded and descriptive transaction types. Because the view already performs the lookup and user joins, standard queries remain concise:

  • Listing transactions for a lease: SELECT lease_transaction_id, lease_id, transaction_type_code, transaction_type, date_effective FROM pn_lease_transactions_v WHERE lease_id = :p_lease_id ORDER BY date_effective;
  • Filtering on a specific type using the code: SELECT * FROM pn_lease_transactions_v WHERE transaction_type_code = :p_type_code;
  • Filtering on the descriptive meaning: SELECT * FROM pn_lease_transactions_v WHERE transaction_type = :p_meaning;
  • Auditing creations by user within an operating unit: SELECT created_by_name, COUNT(*) FROM pn_lease_transactions_v WHERE org_id = :p_org_id GROUP BY created_by_name;

Note that inner joins restrict results to transactions having a valid lookup and resolvable user. For exhaustive transaction listings, querying PN_LEASE_TRANSACTIONS directly with outer joins may be preferable.