Results for “pn_landlord_services”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

APPS.PN_LANDLORD_SERVICES_V is a reporting and inquiry view within the Oracle E-Business Suite Property Manager (PN) module. It exposes landlord service obligations associated with real estate leases, presenting the base transaction data in a denormalized, user-readable form. The view joins the landlord services table to the FND_LOOKUPS view so that internal lookup codes are translated into their descriptive meanings, and to PN_COMPANIES_ALL so that the name of the party responsible for the obligation is available directly on each row. Because it is defined as a view rather than a table, it carries no independent storage and reflects the current state of the underlying records at query time. Typical consumers are Property Manager forms, Oracle Reports outputs, Discoverer workbooks, and custom concurrent programs that extract lease obligation data for reconciliation, audit, or interface to external property management systems.

Underlying Base Objects

The view is defined over four documented objects. PN_LANDLORD_SERVICES (referenced through the PN_LANDLORD_SERVICES synonym) is the driving table holding one row per landlord service obligation; it supplies all identifying, date, status, and descriptive flexfield columns. FND_LOOKUPS is joined three times, each aliased separately, to resolve the service type, the responsibility type, and the financial responsibility party from their lookup codes. PN_COMPANIES_ALL is joined by COMPANY_ID to return the responsibility provider name. FND_GLOBAL is referenced as a package, typically to supply session context such as ORG_ID for multi-organization filtering. All three lookup joins and the company join are outer joins, so a landlord service row is still returned even when no matching lookup or company record exists; in that case the meaning columns come back null.

Key Columns

• landlord_service_id — primary key of the underlying obligation record.
• lease_id, lease_change_id — the lease and any associated change order to which the service obligation belongs.
• service_type_lookup_code / service_type — the stored lookup code and its decoded meaning from the PN_LANDLORD_SERVICE_TYPE lookup type.
• responsibility_code / responsibility_type — the stored code and decoded meaning from the PN_OBLIGATION_RESP_TYPE lookup.
• financial_resp_party_code / financial_resp_party — stored code and decoded meaning from the PN_OBLIGATION_FIN_RESP_PARTY lookup.
• company_id / responsibility_prov_name — the responsible company identifier and its name from PN_COMPANIES_ALL.
• start_date, end_date, status — effective period and lifecycle status of the obligation.
• obligation_num, obligation_reference, obligation_comments — the obligation number (used in the view's ORDER BY), free-text reference, and comments.
• financial_pct_resp, responsibility_maint, common_area_resp — financial percentage responsibility, maintenance responsibility, and common area responsibility flags.
• attribute_category and attribute1 through attribute15 — the descriptive flexfield context and segment values.
• row_id, org_id — the physical row identifier and the multi-organization identifier, along with the standard WHO audit columns (creation_date, created_by, last_update_date, last_updated_by, last_update_login).

Common Use Cases and Queries

The view is most often queried to list active landlord obligations for a given lease, or to report obligations grouped by service type and responsible party. Because the obligation number is a character column ordered via TO_NUMBER, it is advisable to apply the same numeric ordering when replicating the view's sort behavior. A typical inquiry is:

SELECT lease_id, obligation_num, service_type,
       responsibility_type, financial_resp_party,
       responsibility_prov_name, start_date, end_date,
       financial_pct_resp, status
FROM   apps.pn_landlord_services_v
WHERE  org_id = :p_org_id
AND    status = 'ACTIVE'
ORDER  BY TO_NUMBER(obligation_num);

Additional uses include joining the view back to PN_LEASES_ALL to enrich lease-level reporting, filtering on service_type to isolate a specific obligation category, and using the descriptive flexfield attributes to surface client-specific data in custom reports. The user's search for "Landmark / Address Line 3" most likely reflects a client-specific descriptive flexfield segment or a location attribute stored in attribute1 through attribute15, rather than a standard column of the view, so such values should be located through the attribute_category and attribute columns described above.