Results for “project_category”

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

Overview

PA_XC_PROJECT_DETAILS_V is a Projects (PA) module reporting view in Oracle E-Business Suite 12.1.1 and 12.2.2 whose documented purpose is "View All Project Details." It consolidates project header information, the current project manager, progress report content, workflow routing attributes, and progress-status lookup values into a single denormalized row per project. The view is not implemented as a stored database object in every environment; the ETRM metadata records it as "Not implemented in this database," which means it must be created from its view text where a deployment depends on it. Its primary role is read-only presentation — supplying data surfaces, concurrent extracts, and custom inquiries rather than serving as a transactional object. Because it exposes the PROGRESS_ISSUES column, it is frequently located by searches such as "progress_issues," reflecting its use for tracking outstanding project delivery issues captured in progress reports.

Underlying Base Objects

The view is defined over seven documented base objects. PA_PROJECTS_ALL supplies the project header (identifier, number, name, description, dates, and descriptive flexfield segments). HZ_PARTIES is joined twice: once as the carrying-out organization and once, via an outer join, as the project manager's party record. PA_PROJECT_PLAYERS provides the project manager assignment, constrained to the PROJECT MANAGER role and limited by the active start and end dates against the current date. FND_USER resolves the manager's application user account through an outer join on CUSTOMER_ID. PA_PROJ_PROGRESS_REPORTS provides the progress report content at the project level, restricted by PPR.TASK_ID = 0. PA_LOOKUPS supplies the decoded progress status, constrained to LOOKUP_TYPE = 'PA_XC_PROGRESS_STATUS'. All manager-related joins are outer joins (denoted by the (+) operator), so a project without an active manager still returns a row, with placeholder values of −999 supplied by NVL for the manager party, name, and user identifiers. The join to the progress reports table is an inner join, so only projects having at least one project-level progress report are returned.

Key Columns

• PROJECT_ID, PROJECT_NUMBER, PROJECT_NAME, DESCRIPTION — core project identification and descriptive text.
• START_DATE, END_DATE — the project's start and completion dates mapped from START_DATE and COMPLETION_DATE.
• COMPANY_ID, COMPANY_NAME — the carrying-out organization party.
• PROJECT_MANAGER_ID, PROJECT_MANAGER_NAME — the current manager's party identifiers, defaulted to −999 when absent.
• PROJECT_MANAGER_USER_ID, PROJECT_MANAGER_USER_NAME — the manager's FND_USER account.
• PROGRESS_STATUS_CODE, PROGRESS_STATUS, TAG, PREDEFINED_FLAG-like lookup values — the code and decoded meaning from PA_LOOKUPS for PA_XC_PROGRESS_STATUS.
• PROGRESS_ASOF_DATE, PROGRESS_COMMENT, PROGRESS_REPORT — reporting date, short and long progress narrative text.
• PROGRESS_ISSUES — the issues narrative captured on the progress report, the element most often targeted by the "progress_issues" search pattern.
• WF_STATUS_CODE, WF_ITEM_TYPE, WF_ITEM_KEY, WF_PROCESS — Oracle Workflow routing attributes associated with the progress report.
• REPORTING_CLASSIFICATION, PROJECT_CATEGORY — descriptive flexfield attributes (ATTRIBUTE1, ATTRIBUTE2) reported as classification and category.

Common Use Cases and Queries

Typical uses include reporting outstanding project issues, producing project status dashboards, and extracting workflow-linked progress data. To list projects with open issues and their manager:

SELECT project_number, project_name, project_manager_name, progress_status, progress_asof_date, progress_issues FROM pa_xc_project_details_v WHERE progress_issues IS NOT NULL;

To restrict to a specific manager or date window:

SELECT project_number, project_name, progress_status, progress_issues FROM pa_xc_project_details_v WHERE project_manager_name = :p_mgr AND progress_asof_date BETWEEN :p_from AND :p_to ORDER BY progress_asof_date DESC;

To isolate workflow-pending reports, filter on WF_STATUS_CODE IS NOT NULL. Because only current, active manager assignments are returned and the manager joins are outer, downstream logic must treat the −999 sentinel as "no manager assigned." Given the view is not always implemented, deployments should verify its existence before referencing it in custom concurrent programs or BI Publisher data templates.