Results for “billable_raw_cost_itd”

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

Overview

The PJM_PROJECT_PROJ_SUMMARY_V view is an APPS-owned database object in Oracle E-Business Suite, belonging to the Project Manufacturing (PJM) product family. Its documented purpose is to expose project summary information for Web Inquiry, consolidating descriptive project attributes together with financial rollups so that inquiry forms, HTML-based dashboards, and reporting layers can display a complete project snapshot without joining the underlying Project Accounting tables directly.

The view is marked VALID in the ETRM repository and is present in both 12.1.1 and 12.2.2 environments, though the underlying 12.1.1 table structure differs from 12.2.x where the HR_ALL_ORGANIZATION_UNITS_TL synonym replaces the older organization views. The view is read-only and query-oriented; no DML is supported against it. It is typically referenced by project status inquiry pages and by users searching for related metadata such as the pa_project_status_controls table, which governs which status transitions are permitted for a project.

Underlying Base Objects

The view text is defined over the following documented base objects:

• PA_PROJECTS_ALL — the master project table supplying project_id, segment1, name, description, dates, project_type, org_id, and carrying_out_organization_id.
• PA_PROJECT_STATUSES — provides PROJECT_STATUS_NAME used to render the human-readable status of the project.
• PA_PROJECT_STATUS_CONTROLS — defines status transition controls referenced by status validation logic; not directly projected but linked through project status handling.
• PA_PROJECT_TYPES_ALL — supplies PROJECT_TYPE_CLASS_CODE used to classify the project (e.g., contract, indirect).
• PA_PROJECT_PLAYERS and PER_ALL_PEOPLE_F — provide the project manager's person_id and full name.
• PA_PROJECT_ACCUM_ACTUALS, PA_PROJECT_ACCUM_BUDGETS, PA_PROJECT_ACCUM_COMMITMENTS, and PA_PROJECT_ACCUM_HEADERS — supply the PTD, YTD, and ITD revenue, burdened cost, and base revenue figures that drive the profitability calculations.
• HR_ALL_ORGANIZATION_UNITS_TL — resolves the operating unit and carrying-out organization names.
• PA_RPT_UTILS and PA_SECURITY — packages used at runtime for reporting utilities and security-based row filtering.
• PA_BUDGET_TYPES — supports budget-type lookups used in the summary calculations.

Key Columns

• PROJECT_ID, SEGMENT1, NAME, DESCRIPTION — primary project identifiers.
• START_DATE, COMPLETION_DATE, CLOSED_DATE — lifecycle dates.
• PERSON_ID, FULL_NAME — project manager details.
• PROJECT_STATUS_NAME — status text sourced from PA_PROJECT_STATUSES.
• PM_PRODUCT_CODE, PM_PROJECT_REFERENCE — Project Manufacturing identifiers.
• CARRYING_OUT_ORGANIZATION_ID and organization names — the executing and owning organizations.
• PROJECT_TYPE, PROJECT_TYPE_CLASS_CODE — classification attributes.
• ORG_ID — operating unit for multi-org security.
• Formatted financial columns — REVENUE_PTD, BURDENED_COST_PTD, margin PTD, REVENUE_YTD, BURDENED_COST_YTD, margin YTD, REVENUE_ITD, BURDENED_COST_ITD, margin ITD, and the associated margin percentages. Values are rounded and rendered with the format mask FM999G999G999G999G999G990.
• BASE_REVENUE_TOT3 — total funded/base revenue for backlog computation.

Common Use Cases and Queries

The view supports project status inquiry screens, project margin dashboards, and ad hoc reporting where cross-period revenue versus cost is required for manufacturing projects. A representative query is:

SELECT project_id, segment1, name, project_status_name, revenue_ytd, burdened_cost_ytd
FROM apps.pjm_project_proj_summary_v
WHERE org_id = :p_org_id
ORDER BY segment1;

Because it joins several accumulation tables, the view is best queried with restrictive predicates on PROJECT_ID or SEGMENT1. Where transaction-level detail is required, the underlying PA_PROJECT_ACCUM_* tables should be joined directly rather than expanding this view.