Search Results location_alias




Overview
Explore in AI Chat

Overview

APPS.PN_TRX_LEASE_REVENUE is a reporting view within the Oracle Property Manager (PN) module of Oracle E-Business Suite, shipped in releases 12.1.1 and 12.2.2. It exposes lease revenue and payment term information for real estate leases in a flattened, denormalized form that is convenient for reporting, extraction, and integration. The view is owned by the APPS schema, is registered in FND Design Data as PN.PN_TRX_LEASE_REVENUE, and carries a VALID status in the ETRM documentation.

The view type is documented as a multi-org view. It therefore restricts returned rows to the operating unit of the current session, relying on the standard FND_GLOBAL package context. This behavior means reports and integrations must run in the context of the correct operating unit or set the client_info environment variables appropriately; data belonging to other operating units is filtered out automatically. The view is primarily used by Oracle Property Manager lease billing and revenue reporting, and by custom extracts that need lease, customer, location, and payment term attributes in a single record.

Underlying Base Objects

The documented dependencies of APPS.PN_TRX_LEASE_REVENUE span several schemas within EBS:

The presence of HZ and PN synonyms indicates the view joins lease administration data (PN) with customer master data (HZ). No Oracle-provided business logic beyond these joins is documented in the metadata.

Key Columns

  • PAYMENT_ITEM_ID — NUMBER. Primary identifier of a payment or billing item row, populated from the PN_PAYMENT_ITEMS_S sequence.
  • LEASE_NUMBER — VARCHAR2(30). Unique lease identifier. Populated manually, or automatically via PN_LEASES_NUM_S when the profile option "PN: Automatic Lease Number Generation" is set to Yes.
  • LEASE_NAME — VARCHAR2(50). Descriptive name of the lease.
  • CUSTOMER_NAME — VARCHAR2(240). Party name of the customer associated with the lease.
  • CUSTOMER_SITE — VARCHAR2(40). Site use identifier for the customer's bill-to or lease site.
  • PAYMENT_PURPOSE — VARCHAR2(80). Purpose of the term, such as rent, operating expense, or insurance.
  • PAYMENT_TYPE — VARCHAR2(80). Term type, such as base, escalation, or pre-payment.
  • LOCATION_CODE — VARCHAR2(90). Unique hierarchical location identifier generated from the location_alias entered by the user. Buildings, floors, and offices are each classified and combined; for example, building alias 3OP yields 3OP, a floor alias -02 yields 3OP-2, and an office alias -201 yields 3OP-02-201.

Common Use Cases and Queries

Typical uses include lease revenue reconciliations, rent roll and billing extracts, and interfaces that push lease transactions into external accounting or analytics systems. Because the LOCATION_CODE column is derived from location_alias, users searching for "location_alias" often query this view to resolve user-entered aliases to the generated codes.

A basic select restricting to the current operating unit:

  • SELECT lease_number, lease_name, customer_name, payment_purpose, payment_type, location_code FROM apps.pn_trx_lease_revenue WHERE location_code LIKE '3OP%';

A join back to PN_PAYMENT_ITEMS to retrieve the underlying transaction detail by PAYMENT_ITEM_ID:

  • SELECT r.lease_number, r.location_code, p.payment_item_id, p.amount FROM apps.pn_trx_lease_revenue r, apps.pn_payment_items p WHERE r.payment_item_id = p.payment_item_id;

Users should remember that without an operating unit context, the multi-org predicate may return no rows, so initialization via FND_GLOBAL or the standard report runtime is required.