Results for “pa_fp_calc_amt_tmp1_1”

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

Overview

PA_FP_CALC_AMT_TMP1_1 is a temporary calculation table in the Oracle Projects (PA) module, belonging to the schema PA. It supports the Forecast Planning (FP) and Project Resource Management calculation engine. The table stores intermediate results generated when Oracle Projects computes forecasted amounts, staffing requirements, and resource assignment data during planning and budgeting cycles. The "_TMP" naming convention indicates that the object is populated and consumed during a processing run rather than holding permanent transactional data, and the trailing "_1" suffix suggests it is one of a set of parallel or partitioned working tables used to improve processing throughput in large implementations.

In heuristic Data Vault terms, the metadata classifies this object as standalone. This classification reflects the mined foreign key structure, which shows only two outbound references and no identified inbound dependencies within the ETRM model. As a modeling suggestion, however, the wide set of descriptive attributes (cost, rate, resource, task, and organization context) is more consistent with a satellite pattern anchored to a resource-assignment or budget-version hub. The absence of declared dependent relationships indicates that the object is intentionally decoupled: it is a self-contained scratch area whose rows are joined back to the permanent Project Resource Management tables by the program that populates them.

Key Information Stored

The documented physical schema contains 53 columns. The most significant columns and their roles are:

• PROJECT_ID, TASK_ID, TOP_TASK_ID — identify the project and the task or top-level work breakdown structure element against which the calculated amount is computed. TOP_TASK_ID carries a foreign key to PA_TOP_TASKS_IT.
• RESOURCE_ASSIGNMENT_ID, TARGET_RES_ASG_ID, TARGET_RLM_ID — tie the row to the resource assignment being planned, along with the target assignment and resource list member used for comparison.
• RESOURCE_LIST_MEMBER_ID, RESOURCE_ASSIGNMENT_TYPE, RESOURCE_CLASS_CODE, RES_TYPE_CODE, FC_RES_TYPE_CODE — describe the resource being staffed and the forecast resource type supplied by the planning engine.
• PERSON_ID, JOB_ID, ORGANIZATION_ID, PROJECT_ROLE_ID, NAMED_ROLE — capture the named person, role, job, and organization context. PROJECT_ROLE_ID references PA_PROJECT_ROLE_TYPES, making it a principal business-join candidate.
• BUDGET_VERSION_ID — identifies the budget or forecast version under which the calculation was performed, allowing the same project to carry rows for multiple versions.
• PLANNING_START_DATE, PLANNING_END_DATE — define the date range over which the planned amount applies.
• BILLABLE_PERCENT, COST_IND_COMPILED_SET_ID, EXPENDITURE_TYPE, EXPENDITURE_CATEGORY, REVENUE_CATEGORY_CODE — carry the cost and revenue classification and billability assumptions used in the amount derivation.
• UNIT_OF_MEASURE, NON_LABOR_RESOURCE, INVENTORY_ITEM_ID, BOM_RESOURCE_ID — support non-labor and material resources, including inventory items and bills of material resources.
• RATE_JOB_ID, RATE_ORGANIZATION_ID, RATE_EXPENDITURE_TYPE, RATE_BASED_FLAG — record the rate-determining attributes applied when the amount was calculated.
• ETC_METHOD_CODE — indicates the estimate-to-complete method applied.

No surrogate primary key or unique index is documented in the ETRM metadata. The likely business-key candidate is the combination of PROJECT_ID, TASK_ID, RESOURCE_ASSIGNMENT_ID, and BUDGET_VERSION_ID, which would uniquely identify a calculated row within a planning run.

Common Use Cases and Queries

The table is queried primarily for diagnostics of forecast planning output, for reconciliation between planned and actual staffing, and for reconciliation of amounts by resource class or expenditure category. A typical query joins the temporary rows back to the permanent assignment tables:

• Reconcile planned amounts by project and task within a budget version: SELECT project_id, task_id, SUM(billable_percent) FROM pa_fp_calc_amt_tmp1_1 WHERE budget_version_id = :ver GROUP BY project_id, task_id.
• Inspect the resource mix generated for a planning run by grouping on res_type_code, resource_class_code, and track_as_labor_flag to separate labor from non-labor forecasts.
• Join to PA_PROJECT_ROLE_TYPES on project_role_id to validate that staffing assumptions match the defined role types.
• Compare the temporary output against the target assignment columns (target_rlm_id, target_res_asg_id) to detect staffing gaps between requested and calculated resources.

Because the object is a temporary table, queries are most meaningful during and immediately after a planning execution. Operators should treat its contents as transient and re-runnable.

Related Objects

• PA_PROJECT_ROLE_TYPES — referenced by PROJECT_ROLE_ID on the temporary table; supplies role definitions used in the calculation.
• PA_TOP_TASKS_IT — referenced by TOP_TASK_ID; provides the top-level task structure against which amounts roll up.
• PA_PROJECTS_ALL / PA_TASKS — provide the project and task master data joined via PROJECT_ID and TASK_ID.
• PA_BUDGET_VERSIONS — the version master keyed by BUDGET_VERSION_ID.
• PA_PROJECT_ASSIGNMENTS / PA_PROJECT_RESOURCES — the permanent assignment and resource objects whose planning output this table mirrors.
• PA_EXPENDITURE_TYPES and PA_EXPENDITURE_CATEGORIES — supply classification for the expenditure type and category columns.
• PA_RESOURCE_LIST_MEMBERS — the resource list master referenced by RESOURCE_LIST_MEMBER_ID.
• PER_ALL_PEOPLE_F and HR_ALL_ORGANIZATION_UNITS — the person and organization masters used for the person and organization columns.