Results for “fund_control_level_res”

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

Overview

PA.PA_BUDGETARY_CONTROL_OPTIONS is a Projects (PA) module configuration table that stores the default budgetary control levels and time intervals applied to project budgets. It defines how Oracle Projects enforces budgetary control for a given project and budget type combination, encompassing fund control levels, boundary handling, amount types, encumbrance integration, and year-end rollover behaviour. In Oracle EBS 12.1.1 and 12.2.2 the table carries a VALID status and resides in the PA schema, where it is consulted by the budgetary control validation engine during budget entry, baseline, and adjustment transactions.

From a Data Vault modelling perspective, the FK-derived heuristic classifies this object as a link, reflecting its role as an associative structure binding project and budget type entities to a set of control configuration attributes. Analysts building a warehouse layer should treat it accordingly, as a relationship record rather than an independent hub or descriptive satellite.

Key Information Stored

The primary key is PA_BUDGETARY_CONTROL_OPT_PK, defined on the composite business key (PROJECT_ID, BUDGET_TYPE_CODE). A second unique index, PA_BDGTRY_CONTROL_OPTS_U1, spans (PROJECT_ID, BUDGET_TYPE_CODE, PROJECT_TYPE, PROJECT_TYPE_ORG_ID), indicating that budgetary control options may also be defined at the project type and project type organization level for defaults. There is no single surrogate key column; the table is keyed natively by these business attributes.

• PROJECT_ID — the project to which the budgetary control options apply, referencing PA_PROJECTS_ALL.
• BUDGET_TYPE_CODE — the budget type (for example, Approved Cost Budget) for which the options are configured, referencing PA_BUDGET_TYPES.
• PROJECT_TYPE and PROJECT_TYPE_ORG_ID — the project type and project type organization used when the record serves as a template default rather than a project-specific override.
• BDGT_CNTRL_FLAG — indicates whether budgetary control is enabled for the project and budget type combination.
• FUND_CONTROL_LEVEL_PROJECT, FUND_CONTROL_LEVEL_TASK, FUND_CONTROL_LEVEL_RES_GRP, FUND_CONTROL_LEVEL_RES — the fund control levels defined across project, task, resource group, and resource dimensions.
• BOUNDARY_CODE — controls how the budgetary control boundary is treated at rollup.
• BALANCE_TYPE and AMOUNT_TYPE — the balance and amount categories against which control is enforced.
• ENCUMBRANCE_TYPE_ID — the GL encumbrance type used when budgetary control integrates with encumbrance accounting, referencing GL_ENCUMBRANCE_TYPES.
• GL_BUDGET_VERSION_ID and EXTERNAL_BUDGET_CODE — linkage to the General Ledger budget version and external budget identifier.
• YR_END_ROLLOVER_FLAG, YR_END_ROLLOVER_YEAR, YR_END_ROLLOVER_AMOUNT, YR_END_ROLLOVER_MESSAGE — year-end rollover configuration and messaging.
• Audit columns LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN, and REQUEST_ID.

Common Use Cases and Queries

A frequent requirement is to report which projects have budgetary control enabled and at what level. A representative query joins the options table to the project master:

• Identifying projects with budgetary control active: SELECT p.segment1, o.budget_type_code, o.bdgt_cntrl_flag FROM pa_project_budgetary_control_options o, pa_projects_all p WHERE o.project_id = p.project_id AND o.bdgt_cntrl_flag = 'Y';
• Auditing fund control levels configured across project, task, resource group, and resource columns to confirm policy compliance.
• Verifying encumbrance integration by joining ENCUMBRANCE_TYPE_ID to GL_ENCUMBRANCE_TYPES.
• Reviewing year-end rollover behaviour for budgeting cycles and reconciling rollover messages produced during the rollover process.
• Reconstructing project type defaults by filtering on PROJECT_TYPE and PROJECT_TYPE_ORG_ID when PROJECT_ID is null.
• Change-tracking extracts using LAST_UPDATE_DATE and LAST_UPDATED_BY for SOX or configuration audit reporting.

Related Objects

• PA_PROJECTS_ALL — joined on PROJECT_ID and additionally on PPL_PROJECT_ID, supplying project identity and attributes.
• PA_BUDGET_TYPES — joined on BUDGET_TYPE_CODE, providing budget type descriptions and validation.
• GL_ENCUMBRANCE_TYPES — joined on ENCUMBRANCE_TYPE_ID, resolving the encumbrance type used for fund checking.
• GL_BUDGET_VERSIONS — referenced through GL_BUDGET_VERSION_ID for the associated GL budget version.
• PA_BUDGET_VERSIONS and PA_BUDGET_LINES — the budgetary control engine uses the options defined here to validate budget version and line entries against configured control levels.
• Oracle Projects budgetary control validation APIs and the Funds Checker process, which read these options when processing expenditure and commitments.

Because the table governs the enforcement thresholds for project funds checking, changes to rows in PA_BUDGETARY_CONTROL_OPTIONS should be treated as controlled configuration and reconciled carefully against any downstream reporting or integration that relies on budgetary control status.