Results for “pa_budget_entry_methods”

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

Overview

PA_BUDGET_ENTRY_METHODS is a Projects (PA) module reference table that stores implementation-defined methods for entering project budgets in Oracle E-Business Suite 12.1.1 and 12.2.2. Each row defines a named budget entry method — for example an entry method that governs whether budgets are captured at cost or revenue, at raw or burdened amounts, and whether quantity and time-phased detail is required. Because budget entry methods are configuration data referenced by project types and budget versions, the table acts as a controlled lookup rather than a transactional store. Under the heuristic Data Vault classification supplied in the metadata, PA_BUDGET_ENTRY_METHODS is identified as a hub: its single-column primary key, BUDGET_ENTRY_METHOD_CODE, is a stable business key referenced by multiple dependent tables. This classification is offered as a modeling suggestion for warehouse or integration design, not as a physical constraint of the EBS schema.

Key Information Stored

The table is owned by the PA schema and, in the documented 12.2.2 physical schema, contains 36 columns. The most significant include:

• BUDGET_ENTRY_METHOD_CODE — the primary key (PA_BUDGET_ENTRY_METHODS_PK) and the business key referenced by all foreign keys. It also forms the leading column of unique index PA_BUDGET_ENTRY_METHODS_U1 (with ZD_EDITION_NAME).
• BUDGET_ENTRY_METHOD — the user-facing name of the method; forms unique index PA_BUDGET_ENTRY_METHODS_U2 (with ZD_EDITION_NAME).
• ENTRY_LEVEL_CODE and CATEGORIZATION_CODE — control the level at which budget amounts are entered (for example project, task, or resource) and whether entry is categorized.
• COST_QUANTITY_FLAG, RAW_COST_FLAG, BURDENED_COST_FLAG — determine whether cost quantities, raw costs, and burdened costs may be budgeted under this method.
• REV_QUANTITY_FLAG, REVENUE_FLAG — determine whether revenue quantities and revenue amounts may be budgeted.
• TIME_PHASED_TYPE_CODE — indicates the time-phasing behavior expected for budgets entered with this method.
• START_DATE_ACTIVE, END_DATE_ACTIVE, PREDEFINED_FLAG — dating and provenance controls; PREDEFINED_FLAG distinguishes Oracle-delivered methods from customer-defined ones.
• DESCRIPTION, ATTRIBUTE_CATEGORY, ATTRIBUTE1–ATTRIBUTE15 — descriptive text and the standard EBS flexfield (DDF) columns for extensibility.
• ZD_EDITION_NAME — the edition discriminator used by the 12.2 Online Patching (adop) architecture; it appears in both unique indexes and separates editions of the same logical row.
• Standard WHO columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN.

Common Use Cases and Queries

Typical scenarios include validating which budget entry methods are enabled, reporting the project types configured to use a given method, and reconciling budget versions to their entry method. A representative query joins the lookup to project types:

• SELECT pt.project_type, pt.cost_budget_entry_method_code, pt.rev_budget_entry_method_code FROM pa_project_types_all pt WHERE pt.cost_budget_entry_method_code = :code;
• SELECT bv.budget_version_name, bv.budget_entry_method_code FROM pa_budget_versions bv WHERE bv.budget_entry_method_code = :code;
• SELECT budget_entry_method_code, budget_entry_method, start_date_active, end_date_active FROM pa_budget_entry_methods WHERE NVL(end_date_active, SYSDATE+1) > SYSDATE;
• SELECT bem.budget_entry_method_code, bem.entry_level_code, bem.cost_quantity_flag, bem.raw_cost_flag, bem.burdened_cost_flag, bem.revenue_flag FROM pa_budget_entry_methods bem WHERE bem.burdened_cost_flag = 'Y';

These patterns support configuration audits, migration validation, and reporting on budgeting options available to a project type.

Related Objects

The foreign key metadata identifies the principal dependents of this hub table:

• PA_PROJECT_TYPES_ALL — references BUDGET_ENTRY_METHOD_CODE through COST_BUDGET_ENTRY_METHOD_CODE and REV_BUDGET_ENTRY_METHOD_CODE, governing the cost and revenue budget entry behaviour of each project type.
• PA_BUDGET_VERSIONS — references BUDGET_ENTRY_METHOD_CODE to record the method under which a specific budget version was entered.
• GMS_BUDGET_VERSIONS — the Grants Management counterpart to PA_BUDGET_VERSIONS, also referencing BUDGET_ENTRY_METHOD_CODE.
• PA_FP_UPGRADE_AUDIT — references the table twice, via BASIS_COST_BEM and BASIS_REV_BEM, capturing the cost and revenue budget entry method basis used during Federal/upgrade processing.

These relationships establish PA_BUDGET_ENTRY_METHODS as a central configuration reference whose codes must exist before project types, budget versions, or grants budget versions can be created or upgraded.