Results for “project_cost_rate_type”

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

Overview

PA_BUDGET_LINES_M_UPG_DTRANGE is an internal Oracle Projects (PA) staging table owned by the PA schema. The ETRM metadata classifies its description simply as "INTERNAL," which is consistent with its role as a transient upgrade and migration staging structure rather than an end-user transaction table. The suffix "_M_UPG_DTRANGE" indicates that the table is used during the multi-organization upgrade path to hold budget-line date-range and resource-assignment data extracted and pre-processed before it is merged into the permanent PA_BUDGET_LINES structures. It exists in both Oracle EBS 12.1.1 and 12.2.2; the documented 12.2.2 physical schema contains 90 columns.

The heuristic Data Vault classification documented for this object is standalone. No parent references are recorded as foreign keys pointing outward; instead the table's own BUDGET_LINE_ID column references PA_BUDGET_LINES (i.e., PA_BUDGET_LINES is the recognized parent), which positions this as a satellite-like staging table attached to the budget-line hub. Because the classification is heuristic and the object is internal, it should be modeled as a load-dependent, upgrade-only satellite rather than a durable business entity.

Key Information Stored

Although 90 columns are documented, the functionally significant ones fall into identification, period/date range, costing, and multi-currency buckets:

• BUDGET_LINE_ID — foreign key to PA_BUDGET_LINES; the primary business link that ties each staged row back to its permanent budget line.
• RESOURCE_ASSIGNMENT_ID, RESOURCE_ASSIGNMENT_ID_RUP — identify the resource assignment being migrated; the _RUP variant supports the RUP (revenue upgrade) processing pass.
• BUDGET_VERSION_ID, BUDGET_VERSION_ID_RUP — the budget version context for the line and for the RUP pass.
• START_DATE, END_DATE, PERIOD_NAME — the date range the record covers, which is the reason the table is named "DTRANGE."
• QUANTITY, RAW_COST, BURDENED_COST, REVENUE — the core budgeted amounts and their associated *_SOURCE indicator columns (QUANTITY_SOURCE, RAW_COST_SOURCE, BURDENED_COST_SOURCE, REVENUE_SOURCE).
• CODE_COMBINATION_ID, CCID_GEN_STATUS_CODE, CCID_GEN_REJ_MESSAGE — accounting-flexfield generation state and rejection diagnostics.
• PROJECT_RAW_COST, PROJECT_BURDENED_COST, PROJECT_REVENUE along with TXN_RAW_COST, TXN_BURDENED_COST, TXN_REVENUE — project-currency and transaction-currency amounts.
• PROJFUNC_* and PROJECT_* rate, exchange-rate, and rate-date columns — the currency conversion metadata required to re-derive amounts.
• REQUEST_ID — the concurrent request that inserted the staging rows, essential for tracking an upgrade batch.
• LAST_UPDATE_DATE, CREATED_BY, LAST_UPDATED_BY, CREATION_DATE — standard audit columns.

No documented unique index is recorded in the metadata, so no surrogate primary key can be confirmed; BUDGET_LINE_ID combined with RESOURCE_ASSIGNMENT_ID and the date range is the practical business-key candidate.

Common Use Cases and Queries

Because the object is internal, typical access is diagnostic rather than transactional. DBAs and Oracle Projects upgrade consultants query it to reconcile staged versus final budget amounts and to investigate rejected code combinations:

SELECT budget_line_id, resource_assignment_id, period_name,
       quantity, raw_cost, burdened_cost, revenue,
       ccid_gen_status_code, ccid_gen_rej_message
FROM   pa.pa_budget_lines_m_upg_dtrange
WHERE  request_id = :request_id
ORDER  BY budget_line_id, start_date;

A second common pattern joins the staging table to PA_BUDGET_LINES to confirm that every staged BUDGET_LINE_ID was successfully merged, and to detect CCID generation failures where CCID_GEN_STATUS_CODE is non-zero. Reporting against this table is normally restricted to upgrade windows and should never be treated as a source for permanent budgetary reporting.

Related Objects

• PA_BUDGET_LINES — parent table; joined on BUDGET_LINE_ID. The merge target for this staging data.
• PA_BUDGET_VERSIONS — supplies the version context via BUDGET_VERSION_ID.
• PA_RESOURCE_ASSIGNMENTS — resource assignment master referenced by RESOURCE_ASSIGNMENT_ID.
• PA_PERIODS — period calendar used to interpret PERIOD_NAME.
• GL_CODE_COMBINATIONS — interpreted through CODE_COMBINATION_ID for accounting validation.
• FND_CONCURRENT_REQUESTS — correlated via REQUEST_ID to trace the upgrade batch.

In practice the table is populated and consumed exclusively by internal Oracle Projects upgrade and multi-organization migration programs; no supported public API is documented for it.