Search Results resource_email_address




Overview
Explore in AI Chat

Overview

APPS.PA_NOMINATE_RESOURCE_LOV_V is an internal Oracle E-Business Suite database view owned by the APPS schema, registered under FND Design Data as PA.PA_NOMINATE_RESOURCE_LOV_V, and marked VALID in both 12.1.1 and 12.2.2 environments. The view is a list-of-values (LOV) source used by the Oracle Projects nomination workflow — the process by which project managers nominate resources (people or organizations) to assignments against project requirements. It presents a denormalized, security-filtered row per nominatable resource, combining person attributes, organization attributes, assignment dates, supervisor information, and email address into a single queryable structure.

The view's role in reporting and integration is secondary to its operational role. Because it is designated "Oracle Internal Use Only" in the ETRM documentation, Oracle Corporation does not support direct customer access to this object except through standard Oracle Applications programs. Customers and integrators may query it for read-only reporting purposes, but should treat its column list and predicate logic as subject to change during patching. The column naming and the presence of RESOURCE_EMAIL_ADDRESS directly satisfy the common search term "resource_email_address," which surfaces the view's email attribute for downstream notification, integration, and directory-style reporting needs.

Underlying Base Objects

The view is defined over a documented set of base objects spanning the Oracle Human Resources and Oracle Projects schemas. The ETRM dependency list identifies: HR_ALL_ORGANIZATION_UNITS (synonym), HR_GENERAL (package), HR_PERSON_NAME (package), HR_SECURITY (package), PA_ALL_ORGANIZATIONS (synonym), PA_LOOKUPS (view), PER_ASSIGNMENTS_F (view), PER_ASSIGNMENT_STATUS_TYPES (synonym), PER_JOB_EXTRA_INFO (synonym), and PER_PEOPLE_F (view).

The core person and assignment data is drawn from the date-tracked PER_PEOPLE_F and PER_ASSIGNMENTS_F views, which supply resource identity, person type, supervisor, and assignment effective dates. PER_ASSIGNMENT_STATUS_TYPES and PER_JOB_EXTRA_INFO contribute status and job-related qualification attributes. Organization context comes from HR_ALL_ORGANIZATION_UNITS and the Projects-specific PA_ALL_ORGANIZATIONS, allowing the LOV to distinguish resources by owning organization. PA_LOOKUPS provides decoded lookup values, while the HR_SECURITY and HR_GENERAL packages enforce security profiles and derive person/organization names respectively. HR_PERSON_NAME resolves formatted person names from PER_PEOPLE_F attributes. The view is not referenced by any other database object, confirming its position as a terminal presentation layer rather than a building block.

Key Columns

  • RESOURCE_SOURCE_ID (NUMBER, 10) — Surrogate identifier of the resource source record; typically the person or organization party identifier used by the nomination flow.
  • RESOURCE_NAME (VARCHAR2, 240) — Display name of the nominatable resource, resolved through HR_PERSON_NAME or organization naming logic.
  • RESOURCE_NUMBER (VARCHAR2, 30) — Employee number, applicant number, or equivalent resource reference.
  • RESOURCE_ORGANIZATION_ID / RESOURCE_ORGANIZATION_NAME — Owning organization identifier and its decoded name, sourced from HR_ALL_ORGANIZATION_UNITS and PA_ALL_ORGANIZATIONS.
  • ASSIGNMENT_START_DATE / ASSIGNMENT_END_DATE — Effective date boundaries of the resource's assignment, enabling date-aware LOV filtering.
  • SUPERVISOR_ID (NUMBER, 10) — Supervisor person identifier for the resource, useful for approval routing and hierarchy reporting.
  • PERSON_TYPE (VARCHAR2, 80) — Employee, contingent worker, or other person type classification.
  • RESOURCE_EMAIL_ADDRESS (VARCHAR2, 240) — The documented email address attribute of the resource; this is the column matching the user's search term.

Common Use Cases and Queries

Typical uses include resource directory reporting, nomination validation extracts, and populating email notifications for assignment candidates. The following query retrieves the email and identity attributes for all nominatable resources:

SELECT RESOURCE_SOURCE_ID, RESOURCE_NAME, RESOURCE_NUMBER,
  RESOURCE_ORGANIZATION_NAME, PERSON_TYPE, RESOURCE_EMAIL_ADDRESS
  FROM APPS.PA_NOMINATE_RESOURCE_LOV_V;

To filter by organization and email presence:

SELECT RESOURCE_NAME, RESOURCE_NUMBER, RESOURCE_EMAIL_ADDRESS
  FROM APPS.PA_NOMINATE_RESOURCE_LOV_V
  WHERE RESOURCE_ORGANIZATION_ID = :org_id
    AND RESOURCE_EMAIL_ADDRESS IS NOT NULL;

For date-effective filtering of active nominations:

SELECT RESOURCE_NAME, ASSIGNMENT_START_DATE, ASSIGNMENT_END_DATE
  FROM APPS.PA_NOMINATE_RESOURCE_LOV_V
  WHERE TRUNC(SYSDATE) BETWEEN ASSIGNMENT_START_DATE AND NVL(ASSIGNMENT_END_DATE, SYSDATE);

Because HR_SECURITY participates in the view definition, results are constrained by the HR security profile of the querying user, so the same query may return different row sets for different responsibilities.