Search Results pn_location_contact_assign_v




Overview
Explore in AI Chat

Overview

The APPS.PN_LOCATION_CONTACT_ASSIGN_V view is a reporting and integration object within the Oracle E-Business Suite Property Manager (PN) module. It consolidates contact assignment records that are tied to a specific property location rather than to a lease. The defining filter of the view is the predicate PCA.LOCATION_ID IS NOT NULL AND PCA.LEASE_ID IS NULL, meaning it exposes only those contact assignments associated with a location. This makes it the location-oriented counterpart to lease-oriented contact assignment reporting.

The view is registered in the ETRM metadata with a status of VALID and is owned by the APPS schema. Its primary role is to support inquiry, reporting, and downstream integration scenarios where an implementer or application needs contact-to-location relationships enriched with the company name, company site name, and a decoded lease role description. The view resolves the raw lookup code stored on the company site into a human-readable meaning, which simplifies report generation and removes the need for callers to join the lookup table themselves.

Underlying Base Objects

The view is defined over four base objects plus a lookup table. The documented referenced objects are PN_CONTACT_ASSIGNMENTS (SYNONYM), PN_COMPANIES_ALL (SYNONYM), PN_COMPANY_SITES_ALL (SYNONYM), FND_LOOKUPS (VIEW), and FND_GLOBAL (PACKAGE).

  • PN_CONTACT_ASSIGNMENTS (PCA) — the driving table holding the contact assignment transaction rows, including location, company, and site references.
  • PN_COMPANIES_ALL (PNC) — supplies the company master record and its NAME.
  • PN_COMPANY_SITES_ALL (PCS) — supplies the company site name and the LEASE_ROLE_TYPE lookup code.
  • FND_LOOKUPS (FLV) — decodes LEASE_ROLE_TYPE using lookup type PN_LEASE_ROLE_TYPE.
  • FND_GLOBAL — the standard EBS package referenced in the view text, typically for session context such as ORG_ID.

Joins are enforced on COMPANY_SITE_ID, COMPANY_ID, and on the lookup code/type pair. The relation is effectively a location-scoped projection of contact assignment data joined to company and site masters.

Key Columns

Common Use Cases and Queries

A frequent scenario is finding location contacts filtered by the role type that a user searched for, lease_role_type. Because the code and its decoded meaning are both exposed, users can filter either way.

  • List all location contact assignments for a given location or company.
  • Report assignments grouped by LEASE_ROLE for the property portfolio.
  • Export company/site contact relationships to an integration file.

Sample query:

SELECT contact_assignment_id,
       company_name,
       site_name,
       lease_role_type,
       lease_role,
       location_id,
       status
FROM   apps.pn_location_contact_assign_v
WHERE  lease_role_type = 'TENANT'
AND    org_id = :p_org_id
ORDER  BY company_name, site_name;

To resolve the full set of available role codes, query FND_LOOKUPS with LOOKUP_TYPE = 'PN_LEASE_ROLE_TYPE'.