Results for “adj_element_id”

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

Overview

PA_FP_ADJ_ELEMENTS is a Projects (PA) module table owned by the PA schema in Oracle E-Business Suite 12.1.1 and 12.2.2. Per the ETRM documentation, it stores denormalized header information for Plan Adjustments. It functions as a supporting transactional structure within the project forecasting and planning framework, capturing the descriptive header attributes associated with adjustments made to a project plan or budget version. In the documented ETRM 12.2.2 schema, the table is VALID and contains 12 columns.

From a Data Vault modeling perspective, the mined foreign key structure classifies PA_FP_ADJ_ELEMENTS heuristically as a link. This reflects its role as an associative structure that connects a project, a task, a budget version, and a resource assignment into a single adjustment record, rather than acting as an independent hub key or a pure descriptive satellite. Practitioners modeling this data in a warehouse may treat it as a link table whose grain is one row per plan adjustment element, with surrounding descriptive columns behaving satellite-like.

Key Information Stored

The 12 documented columns capture the identity, relationships, and audit metadata of each adjustment header record. The most important ones are:

• ADJ_ELEMENT_ID — the surrogate primary key. It is the sole column of the unique index PA_FP_ADJ_ELEMENTS_U1, making it the documented business-key candidate and the join anchor for child records.
• PROJECT_ID — foreign key to PA_PROJECTS_ALL, identifying the project against which the plan adjustment applies.
• TASK_ID — foreign key to PA_TASKS, narrowing the adjustment to a specific task or work breakdown structure element.
• BUDGET_VERSION_ID — foreign key to PA_BUDGET_VERSIONS, tying the adjustment to a particular budget or forecast version.
• RESOURCE_ASSIGNMENT_ID — foreign key to PA_RESOURCE_ASSIGNMENTS, associating the adjustment with a specific resource assignment line.
• ADJUSTMENT_REASON_CODE — a code classifying the business reason for the adjustment.
• ADJUSTMENT_COMMENTS — free-text narrative explaining the adjustment.
• Audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN, which support Who columns and concurrency handling. (Note that the documented listing includes five audit columns; LAST_UPDATE_LOGIN and the surrounding four satisfy the standard EBS audit pattern.)

Common Use Cases and Queries

Typical usage centers on reporting and reconciling plan adjustments by project, task, budget version, and resource. A common pattern joins the adjustment header to its parent project and task to produce a readable adjustment register:

• Adjustment detail by project: join PA_FP_ADJ_ELEMENTS to PA_PROJECTS_ALL on PROJECT_ID to retrieve the project name and number.
• Adjustment detail by task: join to PA_TASKS on TASK_ID for the task name and WBS context.
• Version-scoped analysis: filter on BUDGET_VERSION_ID against PA_BUDGET_VERSIONS to compare adjustments across forecast versions.
• Resource-level tracing: join to PA_RESOURCE_ASSIGNMENTS on RESOURCE_ASSIGNMENT_ID to reconcile adjustments to specific resource lines.
• Reason code trending: aggregate ADJUSTMENT_REASON_CODE counts to identify the most frequent adjustment drivers.

A representative query retrieves the adjustment header with project and task context:

SELECT a.ADJ_ELEMENT_ID, p.SEGMENT1 project_number, t.TASK_NAME, a.ADJUSTMENT_REASON_CODE
FROM PA_FP_ADJ_ELEMENTS a, PA_PROJECTS_ALL p, PA_TASKS t
WHERE a.PROJECT_ID = p.PROJECT_ID AND a.TASK_ID = t.TASK_ID;

Related Objects

The foreign key relationships documented in ETRM identify the principal related objects that PA_FP_ADJ_ELEMENTS depends upon:

• PA_PROJECTS_ALL — joined via PROJECT_ID; the master project definition.
• PA_TASKS — joined via TASK_ID; the task/WBS structure.
• PA_BUDGET_VERSIONS — joined via BUDGET_VERSION_ID; the budget/forecast version master.
• PA_RESOURCE_ASSIGNMENTS — joined via RESOURCE_ASSIGNMENT_ID; the resource assignment lines.

In addition, the PA schema typically exposes plan adjustment data through concurrent programs and planning UI pages that read this table, so reporting and integration efforts should treat it as a dependent child of the four master objects above rather than an entry point.