Results for “pa_role_profile_type”

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

Overview

APPS.PA_RES_PROFILES_V is a reporting and integration view in the Oracle E-Business Suite Projects (PA) module. It exposes resource role profile definitions maintained in the PA_ROLE_PROFILES base table, enriching each profile with descriptive meaning text and approval status information. In the context of Oracle EBS 12.1.1 and 12.2.2, the view is commonly referenced when users search for "pa_role_profile_type," since it surfaces the PROFILE_TYPE_CODE column alongside its decoded meaning sourced from the PA_ROLE_PROFILE_TYPE lookup. The view provides a denormalized, read-only presentation of role profiles that is suitable for reports, concurrent programs, and integration extracts without requiring joiners to reconstruct lookup and status relationships themselves. It is important to note that the view is not a transactional table; it is a queryable definition intended for consumption by forms logic, BI Publisher reports, and custom SQL.

Underlying Base Objects

The view is defined over three referenced base objects, as documented in the ETRM 12.2.2 metadata:

• PA_ROLE_PROFILES (SYNONYM) — the primary driver table containing each role profile record, including identifiers, dates, type code, resource linkage, and approval status.
• PA_LOOKUPS (VIEW) — supplies the human-readable meaning for the profile type code by matching LOOKUP_TYPE = 'PA_ROLE_PROFILE_TYPE'.
• PA_PROJECT_STATUSES (SYNONYM) — provides the project status name associated with the profile's approval status, filtered to STATUS_TYPE = 'ASGMT_APPRVL'.

The joins are enforced through equality conditions between PROFILE.PROFILE_TYPE_CODE and LOOKUP.LOOKUP_CODE, and between PROFILE.APPROVAL_STATUS_CODE and STATUS.PROJECT_STATUS_CODE, ensuring that only validly typed and status-approved profiles are returned.

Key Columns

The view exposes the following significant columns:

• PROFILE_ID — unique identifier of the role profile.
• PROFILE_NAME — display name of the profile.
• RESOURCE_ID — the resource associated with the profile, where applicable.
• PROFILE_TYPE_CODE — the role profile type classification (for example, the code used for "actual" profiles).
• MEANING — the decoded description of PROFILE_TYPE_CODE from the PA_ROLE_PROFILE_TYPE lookup.
• DESCRIPTION — free-text description of the profile.
• EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — the validity window for the profile.
• PROJECT_STATUS_CODE / PROJECT_STATUS_NAME — the approval status code and its descriptive name from PA_PROJECT_STATUSES.
• DECODE(...) — a computed flag column that returns 'Y' when an active profile of type 'ACTUAL' exists for the current SYSDATE, otherwise 'N'.

Common Use Cases and Queries

Typical usages include validating which role profiles are currently active, listing profiles by type meaning, and driving assignment approval workflows. A sample query follows:

SELECT profile_id,
       profile_name,
       resource_id,
       profile_type_code,
       meaning,
       effective_start_date,
       effective_end_date,
       project_status_name
  FROM apps.pa_res_profiles_v
 WHERE profile_type_code = 'ACTUAL'
   AND SYSDATE BETWEEN effective_start_date
                   AND NVL(effective_end_date, effective_start_date);

Because the view filters approval status through PA_PROJECT_STATUSES with STATUS_TYPE='ASGMT_APPRVL', consumers can rely on it as a pre-validated source of assignment approval status data, avoiding the need to re-implement lookup and status logic in downstream reporting.