Results for “pa_percent_completes”

50+ results




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

Overview

PA_PERCENT_COMPLETES is a Projects (PA) module table owned by the PA schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the estimated percent completion for all levels of the work breakdown structure (WBS), providing a historical and current record of physical progress captured against tasks on a project. The table is central to progress-based revenue recognition, effort reporting, and project performance analysis, since Oracle Projects relies on its rows to derive percent-complete-driven accruals, billing, and reporting figures.

Because the table records percent completion over time, it functions as a time-stamped transactional store rather than a static reference. Its columns capture estimating dates, completion percentages, estimated and actual date ranges, publishing metadata, and descriptive attributes.

Applying the heuristic Data Vault classification mined from the foreign-key structure, PA_PERCENT_COMPLETES is best modeled as a link table. It associates multiple business entities — tasks, projects, project elements, project element versions, statuses, and parties — while its composite key (TASK_ID, DATE_COMPUTED) and unique surrogate PERCENT_COMPLETE_ID support satellite-style history attributes such as COMPLETED_PERCENTAGE and CURRENT_FLAG.

Key Information Stored

The table contains 45 documented columns. The most significant for integration and reporting are:

Common Use Cases and Queries

Typical scenarios include retrieving the current percent complete per task, reconciling historical progress entries, and feeding progress-based reporting or revenue workflows. A representative query is:

  • Current percent complete per task:
    SELECT ppc.PROJECT_ID, ppc.TASK_ID, ppc.COMPLETED_PERCENTAGE, ppc.DATE_COMPUTED
    FROM PA.PA_PERCENT_COMPLETES ppc
    WHERE ppc.CURRENT_FLAG = 'Y' AND ppc.TASK_ID = :task_id;
  • History for a project:
    SELECT ppc.TASK_ID, ppc.COMPLETED_PERCENTAGE, ppc.DATE_COMPUTED, ppc.STATUS_CODE
    FROM PA.PA_PERCENT_COMPLETES ppc
    WHERE ppc.PROJECT_ID = :project_id
    ORDER BY ppc.TASK_ID, ppc.DATE_COMPUTED DESC;
  • Joining to tasks for WBS context:
    SELECT t.TASK_NUMBER, ppc.COMPLETED_PERCENTAGE
    FROM PA.PA_PERCENT_COMPLETES ppc JOIN PA.PA_TASKS t ON t.TASK_ID = ppc.TASK_ID
    WHERE ppc.CURRENT_FLAG = 'Y';

Reporting often filters on PUBLISHED_FLAG or STATUS_CODE to isolate validated progress, and correlates DATE_COMPUTED with accounting periods for period-end analysis.

Related Objects

  • PA_TASKS — joined on PA_PERCENT_COMPLETES.TASK_ID = PA_TASKS.TASK_ID; supplies task and WBS detail.
  • PA_PROJECTS_ALL — joined on PROJECT_ID; the parent project definition.
  • PA_PROJ_ELEMENT_VERSIONS — joined on OBJECT_VERSION_ID; the specific element version the progress applies to.
  • PA_PROJ_ELEMENTS — joined on OBJECT_ID; the project element structure.
  • PA_PROJECT_STATUSES — joined on STATUS_CODE and PROGRESS_STATUS_CODE; supplies status descriptions.
  • HZ_PARTIES — joined on PUBLISHED_BY_PARTY_ID; identifies the party that published the progress entry.

These relationships make PA_PERCENT_COMPLETES a key integration point for project progress reporting, progressive revenue recognition, and reconciliation against the WBS and CBS hierarchies.