Search Results target_rlm_id
Overview
PA.PA_FP_CALC_AMT_TMP1_1 is a global temporary table owned by the PA (Projects) schema in Oracle E-Business Suite. It functions as a scratch/staging structure used during forecast and planning amount calculations, most notably within the Project Resource Management (PRM) and financial planning flows. Data inserted into the table is visible only to the session that populated it and is purged at transaction commit or termination, since the table is defined with a SYS$TRANSACTION duration. This makes it suitable for transient computation—intermediate rate-based, cost, and labor amount derivations—that feed downstream calculation engines rather than persisting as an entity.
From a Data Vault modeling perspective, the metadata heuristic classifies this object as standalone. It is important to note this is only a modeling suggestion derived from the absence of a strong, singular hub-like key and should not be treated as a canonical classification. The table has no documented primary key; its uniqueness is enforced only through nonunique indexes, and the records it holds are session-scoped and ephemeral.
Key Information Stored
The table spans 53 columns covering resource assignment, cost, rate, and organizational attributes. The most significant columns include:
- RESOURCE_ASSIGNMENT_ID, PROJECT_ID, TASK_ID, BUDGET_VERSION_ID, RESOURCE_LIST_MEMBER_ID — the core planning context identifying the resource assignment, project, task, budget version, and resource list member being evaluated.
- ORGANIZATION_ID, JOB_ID, PERSON_ID, PERSON_TYPE_CODE, PROJECT_ROLE_ID — the resource identity grouping (organization, job, person, and role).
- RATE_ORGANIZATION_ID, RATE_INCURRED_BY_ORGANZ_ID, RATE_OVERRIDE_TO_ORGANZ_ID, RATE_EXPENDITURE_ORG_ID — the rate/incurred-by organization context that is central to rate determination; this is the column family directly related to the user's search term rate_incurred_by_organz_id.
- RATE_JOB_ID, RATE_EXPENDITURE_TYPE, RATE_EXP_FUNC_CURR_CODE, RATE_BASED_FLAG — rate source, expenditure mapping, and functional currency.
- EXPENDITURE_TYPE, EXPENDITURE_CATEGORY, REVENUE_CATEGORY_CODE, INCURRED_BY_RES_FLAG, INCUR_BY_RES_CLASS_CODE, INCUR_BY_ROLE_ID — cost and incurrence classification attributes.
- TARGET_RLM_ID, TARGET_RES_ASG_ID, TOP_TASK_ID, MAPPED_FIN_TASK_ID — planning/target references used when the calculation is remapped to a target resource list member, assignment, or financial task.
No surrogate primary key is documented. Three nonunique indexes exist on TARGET_RES_ASG_ID (PA_FP_CALC_AMT_TMP1_N1), RESOURCE_ASSIGNMENT_ID (N2), and the composite MAPPED_FIN_TASK_ID/TARGET_RLM_ID (N3). These index columns are the strongest business-key candidates for joining back into the calculation output.
Common Use Cases and Queries
The typical usage pattern is to populate this temporary table during a forecasting or rate-calculation batch, join it to rate and resource master data, and derive amounts. A representative query identifies rows where the rate is incurred by a specific organization:
SELECT a.resource_assignment_id,
a.project_id,
a.task_id,
a.rate_organization_id,
a.rate_incurred_by_organz_id,
a.rate_job_id,
a.rate_expenditure_type
FROM pa.pa_fp_calc_amt_tmp1_1 a
WHERE a.rate_incurred_by_organz_id = :org_id
AND a.rate_based_flag = 'Y';
Other practical scenarios include reconciling target versus source assignments (joining TARGET_RES_ASG_ID to RESOURCE_ASSIGNMENT_ID), validating labor versus non-labor classification via TRACK_AS_LABOR_FLAG and RESOURCE_CLASS_CODE, and tracing forecast amounts by budget version and financial task. Because the table is transaction-duration, queries must run in the same session as the calculation process; external reporting should consume persisted results rather than this temporary structure.
Related Objects
Foreign key metadata relates this table to the following master objects:
- PA.PA_PROJECT_ROLE_TYPES — joined on PROJECT_ROLE_ID for role definitions.
- PA.PA_TOP_TASKS_IT — joined on TOP_TASK_ID for top-task hierarchy context.
Within the broader PRM calculation flow, this temporary table typically receives and feeds data alongside the resource assignment (PER/PRM) tables, rate and job/expenditure-type master data, and the planning/budget version structures referenced by its columns. It should be regarded as a transient computational artifact rather than a durable reporting table.
-
APPS.PA_FP_GEN_FCST_RMAP_PKG SQL Statements
12.1.1
-
APPS.PA_FP_GEN_FCST_RMAP_PKG SQL Statements
12.2.2
-
TABLE: PA.PA_FP_CALC_AMT_TMP1_1
12.2.2
owner:PA, object_type:TABLE, fnd_design_data:PA.PA_FP_CALC_AMT_TMP1_1, object_name:PA_FP_CALC_AMT_TMP1_1, status:VALID,
-
TABLE: PA.PA_FP_CALC_AMT_TMP1
12.1.1
owner:PA, object_type:TABLE, object_name:PA_FP_CALC_AMT_TMP1, status:VALID,
-
PACKAGE BODY: APPS.PA_FP_GEN_FCST_RMAP_PKG
12.1.1
-
PACKAGE BODY: APPS.PA_FP_GEN_FCST_RMAP_PKG
12.2.2
-
APPS.PA_FP_GEN_FCST_AMT_PUB SQL Statements
12.1.1
-
APPS.PA_FP_COMMITMENT_AMOUNTS SQL Statements
12.2.2
-
APPS.PA_FP_GEN_FCST_AMT_PUB SQL Statements
12.2.2
-
APPS.PA_FP_COMMITMENT_AMOUNTS SQL Statements
12.1.1
-
APPS.PA_FP_ORG_FCST_GEN_PUB SQL Statements
12.2.2
-
APPS.PA_FP_ORG_FCST_GEN_PUB SQL Statements
12.1.1
-
PACKAGE BODY: APPS.PA_FP_COMMITMENT_AMOUNTS
12.1.1
-
APPS.PA_FP_GEN_FCST_AMT_PUB1 SQL Statements
12.2.2
-
APPS.PA_FP_COPY_ACTUALS_PUB SQL Statements
12.2.2
-
PACKAGE BODY: APPS.PA_FP_COMMITMENT_AMOUNTS
12.2.2
-
APPS.PA_FP_GEN_FCST_AMT_PUB1 SQL Statements
12.1.1
-
APPS.PA_FP_GEN_FCST_RMAP_PKG dependencies on PA_FP_CALC_AMT_TMP1
12.1.1
-
APPS.PA_FP_ORG_FCST_GEN_PUB dependencies on PA_RESOURCE_LIST_MEMBERS
12.1.1
-
APPS.PA_FP_GEN_FCST_RMAP_PKG dependencies on PA_FP_CALC_AMT_TMP1
12.2.2
-
APPS.PA_FP_ORG_FCST_GEN_PUB dependencies on PA_RESOURCE_LIST_MEMBERS
12.2.2
-
APPS.PA_FP_COPY_ACTUALS_PUB dependencies on PA_FP_CALC_AMT_TMP1
12.2.2
-
APPS.PA_FP_GEN_FCST_AMT_PUB dependencies on PA_FP_PLANNING_RES_TMP1
12.1.1
-
APPS.PA_FP_GEN_FCST_AMT_PUB dependencies on PA_FP_PLANNING_RES_TMP1
12.2.2
-
APPS.PA_FP_COPY_ACTUALS_PUB dependencies on PA_TASKS
12.2.2
-
APPS.PA_FP_ORG_FCST_GEN_PUB dependencies on PA_TASKS
12.2.2
-
APPS.PA_FP_ORG_FCST_GEN_PUB dependencies on PA_TASKS
12.1.1
-
APPS.PA_FP_GEN_FCST_RMAP_PKG dependencies on PA_BUDGET_VERSIONS
12.1.1
-
APPS.PA_FP_GEN_FCST_RMAP_PKG dependencies on PA_BUDGET_VERSIONS
12.2.2
-
APPS.PA_FP_ORG_FCST_GEN_PUB dependencies on PA_RESOURCE_ASSIGNMENTS
12.1.1
-
APPS.PA_FP_ORG_FCST_GEN_PUB dependencies on PA_RESOURCE_ASSIGNMENTS
12.2.2
-
PACKAGE BODY: APPS.PA_FP_GEN_FCST_AMT_PUB
12.1.1
-
APPS.PA_FP_GEN_FCST_AMT_PUB dependencies on PA_FP_CALC_AMT_TMP1
12.1.1
-
PACKAGE BODY: APPS.PA_FP_GEN_FCST_AMT_PUB
12.2.2
-
APPS.PA_FP_GEN_FCST_RMAP_PKG dependencies on PA_RLMI_RBS_MAP_PUB
12.2.2
-
APPS.PA_FP_GEN_FCST_RMAP_PKG dependencies on PA_RLMI_RBS_MAP_PUB
12.1.1
-
APPS.PA_FP_GEN_FCST_AMT_PUB1 dependencies on PA_FP_CALC_AMT_TMP1
12.1.1
-
APPS.PA_FP_GEN_FCST_AMT_PUB1 dependencies on PA_FP_CALC_AMT_TMP1
12.2.2
-
APPS.PA_FP_GEN_FCST_RMAP_PKG dependencies on PA_PLSQL_DATATYPES
12.1.1
-
APPS.PA_FP_GEN_FCST_AMT_PUB dependencies on PA_FP_CALC_AMT_TMP1
12.2.2
-
APPS.PA_FP_GEN_FCST_RMAP_PKG dependencies on PA_PLSQL_DATATYPES
12.2.2
-
PACKAGE BODY: APPS.PA_FP_ORG_FCST_GEN_PUB
12.1.1
-
PACKAGE BODY: APPS.PA_FP_ORG_FCST_GEN_PUB
12.2.2
-
PACKAGE BODY: APPS.PA_FP_COPY_ACTUALS_PUB
12.2.2
-
APPS.PA_FP_COPY_ACTUALS_PUB dependencies on PA_RESOURCE_ASSIGNMENTS
12.2.2
-
PACKAGE BODY: APPS.PA_FP_GEN_FCST_AMT_PUB1
12.1.1
-
PACKAGE BODY: APPS.PA_FP_GEN_FCST_AMT_PUB1
12.2.2
-
eTRM - PA Tables and Views
12.2.2