Results for “status_reporting”

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

Overview

APPS.PA_RPT_PROJECT_ATTRIBUTES is a reporting view in Oracle EBS Projects (PA) that exposes project master attributes alongside status, classification, and key-member information. It is purpose-built to support Oracle Projects reporting and integration scenarios, particularly the Project Status Inquiry and related status reporting functionality. The view consolidates data drawn from project definitions, project types, statuses, status controls, and organization hierarchies, and it enriches the result set through Oracle Projects report utility functions.

A distinguishing characteristic is its status-reporting filter: the view joins to PA_PROJECT_STATUS_CONTROLS and restricts output to rows where the status control action code equals STATUS_REPORTING. This means only projects whose current status permits or requires status reporting are returned, making the view a targeted data source rather than a general-purpose project listing. Template projects are also excluded through the predicate ppa.template_flag = 'N', and row-level project security is enforced by PA_SECURITY.ALLOW_QUERY, so only projects the querying user is authorized to see are exposed.

Underlying Base Objects

The view is defined over several documented base objects, joined as follows:

• PA_PROJECTS_ALL — primary project source (project_id, name, segment1, dates, type, organization).
• PA_PROJECT_TYPES — supplies project_type_class_code, joined on project_type and org_id.
• PA_PROJECT_STATUSES — supplies the descriptive project_status_name.
• PA_PROJECT_STATUS_CONTROLS — supplies the enabled flag and drives the STATUS_REPORTING filter.
• HR_ORGANIZATION_UNITS — the carrying-out organization name (POU1).
• HR_ALL_ORGANIZATION_UNITS — the operating unit name (POU2), outer-joined on org_id.
• PA_RPT_UTILS (package) — functions returning report class category, project classification, role type, and key-member values.
• PA_SECURITY (package) — ALLOW_QUERY security predicate.
• HR_GENERAL / HR_SECURITY — supporting organization and security routines referenced through the package dependencies.

Key Columns

• PROJECT_ID, NAME, SEGMENT1 — unique identifier and the project number/name.
• PROJECT_STATUS_NAME — decoded status label for reporting.
• START_DATE, COMPLETION_DATE, CLOSED_DATE — key project lifecycle dates.
• PM_PRODUCT_CODE, PM_PROJECT_REFERENCE — linkage to Oracle Project Management.
• CARRYING_OUT_ORGANIZATION_ID (and POU1.NAME) — owning execution organization.
• PROJECT_TYPE, PROJECT_TYPE_CLASS_CODE — type identifier and its classification.
• ORG_ID (and POU2.NAME) — operating unit context.
• RPT_CLASS_CATEGORY / RPT_CLASS columns — three slots of project classification and category derived via PA_RPT_UTILS.
• RPT_ROLE_TYPE / key-member columns — three slots of role type and key member derived via PA_RPT_UTILS.
• ENABLED_FLAG — from PA_PROJECT_STATUS_CONTROLS, indicating whether the status control is active.

Common Use Cases and Queries

The view is commonly queried to obtain a status-reporting-eligible project list with classifications and key members pre-resolved. A typical query:

• SELECT project_id, segment1, name, project_status_name, start_date FROM apps.pa_rpt_project_attributes WHERE org_id = :p_org_id;
• Filtering by status: WHERE project_status_name = 'APPROVED';
• Class-driven reporting: SELECT name, rpt_class_category1, rpt_class1 FROM apps.pa_rpt_project_attributes;

Because security and status-reporting eligibility are embedded in the view definition, it is well suited to custom operational reports, status dashboards, and integrations that must respect project security and active status-reporting controls without replicating those predicates in application code.