Results for “parent_assignment_id”

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

Overview

PA_PROJ_PERIODS_DENORM is a denormalized projection of period-by-period amounts held against project and resource-assignment structures within the Oracle Projects (PA) module. Where transactional project data is ordinarily stored in a normalized, row-per-period fashion, this table pivots that data into a wide, single-row-per-key layout with 52 discrete period amount columns (PERIOD_AMOUNT1 through PERIOD_AMOUNT52), alongside preceding, succeeding, and prior period aggregates. The table exists to accelerate the retrieval of time-phased planning, budgeting, forecasting, and cost figures without repeatedly aggregating the underlying detail. The set of periods referenced is governed by the period profile defined in the PA_PROJ_PERIOD_PROFILES entity.

The table is owned by the PA schema and is classified as VALID in a 12.1.1 / 12.2.2 environment. It carries 73 documented columns in the ETRM 12.2.2 physical schema. Based on the foreign-key topology mined from the metadata, the heuristic Data Vault classification is link: the table resolves relationships between projects, budget versions, resource assignments, forecast elements, and amount types, rather than acting as a pure reference hub or a descriptive satellite. This classification is offered as a modeling suggestion and reflects the object's role in joining independent business keys.

Key Information Stored

The table's most significant columns fall into four groups: keys, classification attributes, time-phased amounts, and audit fields.

• PROJECT_ID — foreign key to PA_PROJECTS_ALL; the project against which periods are measured.
• BUDGET_VERSION_ID — foreign key to PA_BUDGET_VERSIONS; isolates amounts to a specific budget version.
• RESOURCE_ASSIGNMENT_ID and PARENT_ASSIGNMENT_ID — foreign keys to PA_RESOURCE_ASSIGNMENTS, supporting assignment-level and rolled-up hierarchies.
• OBJECT_ID and OBJECT_TYPE_CODE — polymorphic reference resolving to PA_RESOURCE_ASSIGNMENTS or PA_ORG_FCST_ELEMENTS depending on object type.
• AMOUNT_TYPE_ID and AMOUNT_SUBTYPE_ID — foreign keys to PA_AMOUNT_TYPES_B, with denormalized code counterparts AMOUNT_TYPE_CODE and AMOUNT_SUBTYPE_CODE.
• PERIOD_PROFILE_ID — links to the period profile governing which periods the PERIOD_AMOUNTn columns represent.
• CURRENCY_TYPE and CURRENCY_CODE — indicate whether amounts are project, functional, or another currency basis.
• PERIOD_AMOUNT1 … PERIOD_AMOUNT52 — the pivoted period values; the denormalized core of the table.
• PRECEDING_PERIODS_AMOUNT, SUCCEEDING_PERIODS_AMOUNT, PRIOR_PERIOD_AMOUNT — pre-aggregated boundary totals.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — standard EBS audit columns.

No explicit surrogate primary key is documented in the supplied metadata; the likely business-key candidates are the composite of PROJECT_ID, BUDGET_VERSION_ID, RESOURCE_ASSIGNMENT_ID or OBJECT_ID, PERIOD_PROFILE_ID, AMOUNT_TYPE_ID, AMOUNT_SUBTYPE_ID, and CURRENCY_CODE.

Common Use Cases and Queries

Typical usage centers on reporting period spread for budgets, forecasts, and cost, and on comparing planned versus actual by period. A representative query retrieves first-quarter amounts for a project's budget version and amount type:

• Join PROJECT_ID to PA_PROJECTS_ALL and BUDGET_VERSION_ID to PA_BUDGET_VERSIONS to report budget phasing by period.
• Aggregate PERIOD_AMOUNT1 through PERIOD_AMOUNT12 for fiscal-year roll-ups, using CURRENCY_CODE to control conversion.
• Filter on AMOUNT_TYPE_CODE and AMOUNT_SUBTYPE_CODE to isolate cost, revenue, or burden components.
• Use PRECEDING_PERIODS_AMOUNT and SUCCEEDING_PERIODS_AMOUNT for cumulative-to-date reporting without window functions.
• Drive forecasting extracts by selecting RESOURCE_ASSIGNMENT_ID and OBJECT_TYPE_CODE to reconcile assignment-level and forecast-element-level figures.

Because PERIOD_AMOUNTn columns are positional, reporting logic must resolve the underlying period profile first, typically through PERIOD_PROFILE_ID, before labelling columns with actual period names.

Related Objects

• PA_PROJECTS_ALL — joined on PROJECT_ID; supplies project attributes.
• PA_BUDGET_VERSIONS — joined on BUDGET_VERSION_ID; defines the budget context.
• PA_RESOURCE_ASSIGNMENTS — joined on RESOURCE_ASSIGNMENT_ID, OBJECT_ID, and PARENT_ASSIGNMENT_ID.
• PA_ORG_FCST_ELEMENTS — joined on OBJECT_ID for organizational forecast elements.
• PA_AMOUNT_TYPES_B — joined on AMOUNT_TYPE_ID and AMOUNT_SUBTYPE_ID for amount classification.
• PA_PROJ_PERIOD_PROFILES — referenced through PERIOD_PROFILE_ID; governs the period calendar used.