Results for “pn_job_title”

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

Overview

APPS.PN_CONTACTS_V is a reporting and integration view in Oracle E-Business Suite that exposes contact records maintained in the Oracle Projects/Property Manager contact model. The view is owned by the APPS schema and is documented for both release 12.1.1 and 12.2.2. It presents a denormalized, read-friendly projection of the PN_CONTACTS base entity, joining it to the FND_LOOKUPS lookup view so that the job title code stored on each contact is accompanied by its descriptive meaning. This makes the view particularly suitable for reporting, extracts, concurrent program output, and inbound/outbound interface queries where a human-readable job title is required alongside the contact attributes.

Because the object is a view rather than a table, it carries no independent storage; all reads resolve through the PN_CONTACTS synonym and the FND_LOOKUPS view at runtime. The view is defined with an outer join to FND_LOOKUPS, which preserves contact rows even when no matching PN_JOB_TITLE lookup exists.

Underlying Base Objects

The documented base objects referenced by APPS.PN_CONTACTS_V are:

• PN_CONTACTS (SYNONYM) — the primary source of contact data. The synonym resolves to the underlying PN_CONTACTS table that stores contact records with their company site association, personal details, status, and descriptive flexfield attributes.
• FND_LOOKUPS (VIEW) — the lookup source used to resolve the job title code into a descriptive meaning. The join is driven by LOOKUP_TYPE = 'PN_JOB_TITLE' matched to the contact's JOB_TITLE value.
• FND_GLOBAL (PACKAGE) — referenced as part of the view's dependency set, consistent with the ORG_ID column exposed in the projection and the standard Oracle EBS multi-org security model.

The join condition in the view text is expressed as an outer join (indicated by the (+) operator on the FND_LOOKUPS side), ensuring that contacts lacking a valid or active lookup entry are still returned, with a null job title meaning.

Key Columns

The view exposes the contact key and identifying attributes, audit columns, and flexfield segments:

• ROW_ID — the ROWID of the underlying PN_CONTACTS row, useful for direct row identification and updates within EBS.
• CONTACT_ID — the unique primary key of the contact record.
• COMPANY_SITE_ID — the company site to which the contact is associated, linking contacts to the site/party hierarchy.
• STATUS — the active/inactive state of the contact.
• LAST_NAME, FIRST_NAME, JOB_TITLE — the personal and professional identification of the contact; JOB_TITLE holds the lookup code.
• JOB_TITLE_MEANING — the descriptive meaning of JOB_TITLE resolved from FND_LOOKUPS for lookup type PN_JOB_TITLE.
• MAIL_STOP, EMAIL_ADDRESS, PRIMARY_FLAG — contact communication details and the indicator of the primary contact for the site.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — the descriptive flexfield context and segment values, enabling client-specific extensions to be reported directly.
• ORG_ID — the operating unit/organization identifier supporting multi-org restricted queries.
• Audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN, providing standard WHO tracking.

Common Use Cases and Queries

The view is commonly used to list site contacts with their job titles for reporting and integration. Because ORGANIZATION_ID is not part of it, multi-org filtering is typically applied externally via org_id.

A basic listing of active primary contacts with their job titles:

• SELECT contact_id, first_name, last_name, job_title, job_title_meaning, email_address, company_site_id FROM apps.pn_contacts_v WHERE status = 'A' AND primary_flag = 'Y';

Joining to a site or project entity to produce a contact roster for a given operating unit:

• SELECT c.last_name, c.first_name, c.job_title_meaning, c.email_address FROM apps.pn_contacts_v c WHERE c.org_id = :p_org_id ORDER BY c.last_name, c.first_name;

Flexfield-based extracts can select attribute_category and the attribute segments directly, and the presence of row_id supports targeted correction scripts. Because FND_LOOKUPS is outer-joined, a query filtered on job_title_meaning will exclude contacts whose lookup value is missing; querying on JOB_TITLE code instead avoids that loss.