Search Results pn_contact_assignments




Overview
Explore in AI Chat

Overview

APPS.PN_CONTACT_ASSIGNMENTS_V is a reporting and integration view in the Oracle E-Business Suite Property Manager (PN) module. It presents contact assignment records that link company site contacts to leases, together with the descriptive names and lookup meanings required to interpret those records without additional joins. The view predates and complements the Oracle Lease and Finance Management data model, and its definition is stable across EBS 12.1.1 and 12.2.2, since it depends on core PN tables and the standard FND lookups infrastructure rather than on version-specific features.

The view joins five base objects to resolve raw foreign keys into business-friendly values: company name, site name, lease role meaning, and contact name. Because it filters on pca.lease_id IS NOT NULL, it exposes only contact assignments that are tied to a lease, omitting site-level assignments that carry no lease reference. This makes it the preferred source for lease-centric contact reporting and for downstream integrations that need a single denormalized row per lease contact assignment.

Underlying Base Objects

The documented referenced objects are FND_GLOBAL (package), FND_LOOKUPS (view), PN_COMPANIES_ALL, PN_COMPANY_SITES_ALL, PN_CONTACTS_ALL, and PN_CONTACT_ASSIGNMENTS (all synonyms). The driving table is PN_CONTACT_ASSIGNMENTS (aliased PCA), joined to PN_COMPANY_SITES_ALL (PCS) on company_site_id, to PN_COMPANIES_ALL (PNC) on company_id, and to FND_LOOKUPS (FLV) on lookup_code = pcs.lease_role_type with lookup_type = 'PN_LEASE_ROLE_TYPE'. PN_CONTACTS_ALL (CON) is outer-joined to PCS on company_site_id and to primary_flag = 'Y', which resolves the primary contact for the site. FND_GLOBAL supplies the session context for organization and security derivation used elsewhere in the module.

Key Columns

Common Use Cases and Queries

Typical scenarios include reporting lease contacts by role, extracting lease/contact combinations for data warehousing, and validating primary contact coverage per company site. The following query lists lease contacts with their roles:

  • SELECT lease_id, company_name, site_name, lease_role, contact_name FROM apps.pn_contact_assignments_v WHERE lease_id = :p_lease_id;
  • SELECT company_id, COUNT(*) FROM apps.pn_contact_assignments_v GROUP BY company_id ORDER BY 2 DESC;
  • SELECT a.* FROM apps.pn_contact_assignments_v a WHERE a.org_id = :p_org_id AND a.status = 'A';

Before querying in a multi-org context, ensure the correct ORG_ID predicate is applied. Because the view exposes ROWID from PN_CONTACT_ASSIGNMENTS, it can also be used in updatable-view scenarios, though direct DML against the base table is preferable for controlled maintenance.