Results for “per_budget_elements”

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

Overview

The PER_BUDGET_ELEMENTS table resides in the HR schema and belongs to the PER (Human Resources) product family in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the combinations of organization, grade, job, and position that define detailed budget values within the workforce budgeting feature of Oracle HRMS. Each row represents a distinct budgeting element against which budget amounts are captured and compared to actual workforce costs.

From a dimensional modeling perspective, the FK structure suggests a satellite-leaning classification for this table. It carries descriptive and qualifying attributes tied to a budget version, rather than acting as a standalone hub of business keys or a pure intersection/link table. The presence of audit columns, request/program tracking columns, and multiple optional dimension references reinforces this satellite interpretation.

Key Information Stored

The table contains 19 documented columns. The surrogate primary key is BUDGET_ELEMENT_ID, enforced through the PER_BUDGET_ELEMENTS_PK unique index. No separate business-key unique index is documented beyond this primary key.

• BUDGET_ELEMENT_ID — Surrogate primary key uniquely identifying each budget element row.
• BUDGET_VERSION_ID — Foreign key to PER_BUDGET_VERSIONS, tying the element to a specific budget version.
• BUSINESS_GROUP_ID — Foreign key to HR_ALL_ORGANIZATION_UNITS, identifying the business group context.
• ORGANIZATION_ID — Foreign key to HR_ALL_ORGANIZATION_UNITS, identifying the organization dimension of the element.
• GRADE_ID — Foreign key to PER_GRADES, capturing the grade dimension.
• JOB_ID — Foreign key to PER_JOBS, capturing the job dimension.
• POSITION_ID — Foreign key to PER_ALL_POSITIONS, capturing the position dimension.
• TRAINING_PLAN_ID and TRAINING_PLAN_MEMBER_ID — Optional foreign keys to OTA training plan tables.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — Concurrent program tracking columns populated on insert or update.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE — Standard WHO audit columns.
• EVENT_ID — Business event reference column.

Common Use Cases and Queries

Typical usage centers on budget versus actual workforce reporting, where users decompose budget amounts by organizational and classification dimensions. A common query joins budget values to their defining elements and concurrency context.

• Budget vs. actual by organization/grade: Join PER_BUDGET_ELEMENTS to PER_BUDGET_VALUES on BUDGET_ELEMENT_ID, then to HR_ALL_ORGANIZATION_UNITS, PER_GRADES, and PER_JOBS to present the amounts against descriptive labels.
• Version-level detail extraction: Filter by BUDGET_VERSION_ID to report all elements belonging to a specific budget version.
• Concurrent program auditing: Query REQUEST_ID and PROGRAM_ID to trace which process created or modified budget element records.
• Training-related budgeting: Use TRAINING_PLAN_ID and TRAINING_PLAN_MEMBER_ID where budget alignment with training plans is required.

Sample pattern: SELECT e.budget_element_id, e.organization_id, e.grade_id, v.budget_value FROM per_budget_elements e JOIN per_budget_values v ON e.budget_element_id = v.budget_element_id WHERE e.budget_version_id = :v_version_id.

Related Objects

The following tables participate in the most significant FK relationships with PER_BUDGET_ELEMENTS:

• PER_BUDGET_VALUES — References BUDGET_ELEMENT_ID; the primary child table holding actual budget amounts.
• PER_BUDGET_VERSIONS — Parent via BUDGET_VERSION_ID.
• HR_ALL_ORGANIZATION_UNITS — Parent via BUSINESS_GROUP_ID and ORGANIZATION_ID.
• PER_GRADES — Parent via GRADE_ID.
• PER_JOBS — Parent via JOB_ID.
• PER_ALL_POSITIONS — Parent via POSITION_ID.
• OTA_TRAINING_PLANS and OTA_TRAINING_PLAN_MEMBERS — Parents via TRAINING_PLAN_ID and TRAINING_PLAN_MEMBER_ID.