Results for “pm_product”

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

Overview

PA_RPT_PROJECT_ATTRIBUTES is a reporting view owned by the APPS schema in Oracle E-Business Suite Projects (PA). It presents a consolidated, denormalized projection of project master data drawn from PA_PROJECTS_ALL and several supporting reference tables, together with derived reporting attributes produced by the PA_RPT_UTILS package. The view is intended for operational and analytical reporting rather than transaction processing, and its status is documented as VALID in ETRM.

The view is notable for embedding row-level security and status filtering directly in its definition. Records are restricted through PA_SECURITY.ALLOW_QUERY(PPA.PROJECT_ID) = 'Y', and template projects are excluded by the predicate PPA.TEMPLATE_FLAG = 'N'. Only project statuses associated with the STATUS_REPORTING action code in PA_PROJECT_STATUS_CONTROLS are returned, which aligns the view with project status reporting rather than the full lifecycle. The presence of PM_PRODUCT_CODE and PM_PROJECT_REFERENCE makes the view particularly relevant to searches referencing "pm_product", since these columns carry the Oracle Product Management product code and the corresponding project reference for a project.

Underlying Base Objects

The documented base objects are PA_PROJECTS_ALL (the primary source of project attributes), PA_PROJECT_TYPES, PA_PROJECT_STATUSES, PA_PROJECT_STATUS_CONTROLS, HR_ORGANIZATION_UNITS, HR_ALL_ORGANIZATION_UNITS, and the PL/SQL packages PA_RPT_UTILS, PA_SECURITY, HR_GENERAL, and HR_SECURITY. Most table references resolve through APPS synonyms.

• PA_PROJECTS_ALL supplies PROJECT_ID, NAME, SEGMENT1, START_DATE, COMPLETION_DATE, CLOSED_DATE, PM_PRODUCT_CODE, PM_PROJECT_REFERENCE, CARRYING_OUT_ORGANIZATION_ID, PROJECT_TYPE, and ORG_ID.
• PA_PROJECT_TYPES joins on PROJECT_TYPE and ORG_ID to provide PROJECT_TYPE_CLASS_CODE.
• PA_PROJECT_STATUSES provides the PROJECT_STATUS_NAME, while PA_PROJECT_STATUS_CONTROLS supplies ENABLED_FLAG and enforces the STATUS_REPORTING action filter.
• HR_ORGANIZATION_UNITS provides the carrying-out organization name, and HR_ALL_ORGANIZATION_UNITS supplies the operating unit name via an outer join on ORG_ID.
• PA_RPT_UTILS supplies the report classification and key member derivations; PA_SECURITY enforces query access.

Key Columns

• PROJECT_ID: Primary key of the project, used for joins and security evaluation.
• PROJECT_NUMBER (SEGMENT1) / PROJECT_NAME: User-facing project identifiers.
• PROJECT_STATUS: Descriptive status name resolved from PA_PROJECT_STATUSES.
• START_DATE, COMPLETION_DATE, CLOSED_DATE: Standard project milestone dates.
• PM_PRODUCT: The product code (PM_PRODUCT_CODE) associated with the project.
• PM_PROJECT_REFERENCE: The reference value linking the project to the product context.
• PROJECT_ORGANIZA...: The carrying-out organization name derived from HR_ORGANIZATION_UNITS.
• Report class and key member columns: Three paired columns producing the configured report class category and its value, plus three paired columns for role type and key member, all derived via PA_RPT_UTILS.
• ENABLED_FLAG: Status reporting enablement indicator from PA_PROJECT_STATUS_CONTROLS.

Common Use Cases and Queries

Typical uses include project status reporting, product-to-project cross-reference analysis, and organization-level project inventories. The PM_PRODUCT and PM_PROJECT_REFERENCE columns support reconciliation between project data and product management reporting.

A representative query, filtered on the documented product column:

• SELECT project_id, project_number, project_name, project_status, pm_product, pm_project_reference FROM apps.pa_rpt_project_attributes WHERE pm_product = :product_code ORDER BY project_number;
• SELECT project_status, COUNT(*) FROM apps.pa_rpt_project_attributes GROUP BY project_status ORDER BY project_status;
• SELECT project_id, project_name, start_date, completion_date FROM apps.pa_rpt_project_attributes WHERE org_id = :org_id AND enabled_flag = 'Y';

Because the view enforces PA_SECURITY.ALLOW_QUERY, results are automatically limited to projects the querying user is authorized to see. For bulk reporting, joining this view to PA_TASKS or PA_EXPENDITURES on PROJECT_ID allows attribute-level enrichment while retaining the security and status filters applied by the view definition.