Search Results funds_control_level_code




Overview
Explore in AI Chat

Overview

The PA_BUDGETARY_CONTROL_TASK_V view is a standard Oracle E-Business Suite database object owned by the APPS schema within the Projects (PA) product family. It serves as the base view for the Budgetary Controls form, specifically the Task block. In Oracle EBS 12.1.1 and 12.2.2, this view presents budgetary control settings at the task level, joining task descriptive information with the corresponding budgetary control configuration records. The presence of the FUNDS_CONTROL_LEVEL_CODE column, which is the term most frequently searched against this object, highlights its central role in exposing how funds control is applied to individual project tasks. The view is a read-only construct; it does not maintain data of its own but consolidates and exposes rows stored in the underlying budgetary control and task tables in a form suitable for form rendering, reporting, and integration.

Underlying Base Objects

The view is documented as being defined over two base objects, both referenced through synonyms in the APPS schema:

  • PA_BUDGETARY_CONTROLS (alias PABC) — the primary table holding budgetary control definitions, including the funds control level, budget type, and resource list member associations.
  • PA_TASKS (alias PAT) — the task master table providing task number and task name.

The join is performed on both TASK_ID and PROJECT_ID, ensuring that each budgetary control row is matched to the correct task within the correct project. The ROWID of the PA_BUDGETARY_CONTROLS record is exposed as ROW_ID, which supports form-based update semantics where the form block must reference the underlying base row. Because the view joins two tables, it effectively produces one row per budgetary control record that has a matching task.

Key Columns

The view exposes the following columns, each mapped to a specific business meaning:

  • ROW_ID — the ROWID of the underlying PA_BUDGETARY_CONTROLS row; used by the form for update and delete operations.
  • TASK_NUMBER and TASK_NAME — descriptive identifiers for the task from PA_TASKS.
  • PROJECT_ID and TASK_ID — the composite key linking the budgetary control record to its project and task.
  • BUDGETARY_CONTROLS_ID — the unique identifier of the budgetary control record.
  • FUNDS_CONTROL_LEVEL_CODE — indicates the level at which funds control is enforced or configured (for example, project, task, or resource level, depending on the code set values). This column is the primary attribute users search for when auditing or reporting on where funds checking applies.
  • BUDGET_TYPE_CODE — identifies the budget type associated with the control record.
  • RESOURCE_LIST_MEMBER_ID — references the resource list member to which the control applies, when resource-level control is configured.
  • Standard WHO columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN — providing audit trail information.

Common Use Cases and Queries

Typical uses include auditing funds control configuration, validating task-level budgetary controls after data migration, and driving custom reports or interfaces. A representative query is:

  • Listing all tasks with their funds control level: SELECT project_id, task_id, task_number, task_name, funds_control_level_code, budget_type_code FROM apps.pa_budgetary_control_task_v WHERE project_id = :project_id;
  • Auditing records where a specific funds control level is applied: SELECT * FROM apps.pa_budgetary_control_task_v WHERE funds_control_level_code = 'TASK';
  • Reviewing recently modified configurations: SELECT task_number, funds_control_level_code, last_updated_by, last_update_date FROM apps.pa_budgetary_control_task_v WHERE last_update_date > SYSDATE - 30;
  • Joining to project master data to enrich reports with project names.

Because the view enforces the join on both TASK_ID and PROJECT_ID, queries should always supply consistent project and task combinations to avoid cross-project anomalies. As with all APPS views, access should be granted through standard EBS responsibility and security mechanisms rather than direct grants.