Search Results etc_cost_pc

Overview

The APPS.PA_ASSGN_COST_EFFORT_V view is a public Oracle E-Business Suite database object owned by the APPS schema and registered in the Applications FND design data under PA (Projects). It exposes a consolidated, assignment-level picture of cost and effort across the planning, actual, and estimate-to-complete (ETC) dimensions of a project. The view is defined as an internal (non-updatable) view, and its status is reported as VALID in the reviewed ETRM metadata for 12.1.1 and 12.2.2.

Functionally, the view joins the workplan task assignment structure to progress rollup and project element version data, so that a single row returns the cost and effort figures associated with a specific project/task assignment combination. This makes it relevant to reporting and integration scenarios in Oracle Projects that require cost and effort values at the resource assignment level rather than at the raw transaction level. Because the view includes a column named ETC_COST_TC — the user search term "etc_cost_tc" matches this column name — it is commonly encountered by developers and analysts building ETC or forecast-related extracts.

The ETRM metadata carries the standard Oracle restriction notice: the object is for internal use only, and Oracle Corporation does not support direct access to application data through it except from standard Oracle Applications programs. Consequently, custom read-only queries are possible but unsupported, and any integration should anticipate a schema or definition change across patches.

Underlying Base Objects

The view is not a simple projection over a single table. Per the documented dependency list, it references the following objects in the APPS schema:

• PA_TASK_ASGMTS_V (view) — the assignment-level source, supplying the project, task, and resource assignment identifiers.
• PA_PROJ_ELEMENT_VERSIONS and PA_PROJ_ELEM_VER_STRUCTURE — project element version and structure data used to resolve task and structure versions.
• PA_PROJ_WORKPLAN_ATTR — workplan attributes associated with the assignment.
• PA_PROGRESS_ROLLUP — progress rollup records linked through the PROGRESS_ROLLUP_ID column.
• PA_FP_FCST_GEN_AMT_UTILS, PA_PROGRESS_UTILS, and PA_TASK_ASSIGNMENT_UTILS — PL/SQL packages whose functions are invoked to derive cost and effort amounts.

These dependencies explain why the view surfaces both version identifiers (TASK_VERSION_ID, STRUCTURE_VERSION_ID, BUDGET_VERSION_ID) and computed amount columns. The amount figures, including the ETC and actual values expressed in transaction currency (TC) and project currency (PC), are produced through the packaged utility logic rather than being stored directly on a single base table.

Key Columns

The view returns NUMBER(15) keys, DATE range columns, and measure columns. The principal keys are PROJECT_ID, TASK_ID, TASK_VERSION_ID, STRUCTURE_VERSION_ID, RESOURCE_LIST_MEMBER_ID, RESOURCE_ASSIGNMENT_ID, BUDGET_VERSION_ID, and PROGRESS_ROLLUP_ID. Scheduling context is provided by ACTUAL_START_DATE, ACTUAL_FINISH_DATE, ESTIMATED_START_DATE, and ESTIMATED_FINISH_DATE.

• PLANNED_COST, PLANNED_RAWCOST, PLANNED_EFFORT — planned cost, raw cost, and effort for the assignment.
• ACTUAL_COST_TC, ACTUAL_RAWCOST_TC — actual cost and raw cost in transaction currency.
• ETC_COST_TC, ETC_RAWCOST_TC — estimate-to-complete cost and raw cost in transaction currency; these are the columns associated with the search term "etc_cost_tc."
• ACTUAL_EFFORT, ETC_EFFORT — actual and remaining effort quantities.
• ACTUAL_COST_PC, ACTUAL_RAWCOST_PC, ETC_COST_PC, ETC_RAWCOST_PC — the same actual and ETC measures expressed in project currency.

Common Use Cases and Queries

Typical scenarios include extracting assignment-level cost and effort for project performance reporting, reconciling actual versus ETC values, and feeding downstream forecasting or dashboard solutions. A basic extract selecting the ETC cost columns follows:

• SELECT project_id, task_id, resource_assignment_id, etc_cost_tc, etc_rawcost_tc, etc_effort FROM apps.pa_assgn_cost_effort_v;
• SELECT project_id, resource_assignment_id, actual_cost_tc, etc_cost_tc, (actual_cost_tc + etc_cost_tc) total_at_completion FROM apps.pa_assgn_cost_effort_v WHERE project_id = :project_id;
• SELECT project_id, task_id, etc_cost_tc, etc_cost_pc FROM apps.pa_assgn_cost_effort_v WHERE etc_cost_tc IS NOT NULL ORDER BY project_id, task_id;

Queries should be restricted by PROJECT_ID where possible to limit the cost of the packaged function calls underlying the view, and results should be validated against Oracle Projects standard reports before use in unsupported custom reporting or integration.