Results for “ptk_task_id”

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

Overview

PA_BUDGETARY_CONTROLS is a table in the Projects (PA) schema of Oracle E-Business Suite, present and valid in both 12.1.1 and 12.2.2. It stores the budgetary control levels that regulate how funds are reserved for project transactions. Each row defines a control configuration that determines whether funds checking and funds reservation are enforced for a given combination of project, task, budget type, and resource list member. This configuration drives the behavior of the budgetary control engine during transaction entry, ensuring that commitments and expenditures do not exceed authorized funding.

The table forms the policy layer of Oracle Projects budgetary control. Where transaction and funding tables capture actual amounts, PA_BUDGETARY_CONTROLS captures the rules that govern those amounts. Administrators maintain these records through the Budgetary Control setup in Oracle Projects, and the funds check process consults them at transaction validation time.

From a Data Vault modeling perspective, the metadata classifies this object heuristically as a link. That is consistent with its structure, since the table primarily associates multiple business entities — projects, tasks, budget types, and resource list members — rather than storing a single descriptive subject area. This should be treated as a modeling suggestion rather than an authoritative classification.

Key Information Stored

• BUDGETARY_CONTROLS_ID — The surrogate primary key, enforced by the PA_BUDGETARY_CONTROLS_PK constraint and the unique index PA_BUDGETARY_CONTROLS_U1. It uniquely identifies each budgetary control configuration record.
• PROJECT_ID — References PA_PROJECTS_ALL; the project to which the control configuration applies.
• TASK_ID — References PA_TASKS; narrows the control to a specific task within the project.
• TOP_TASK_ID — References PA_TOP_TASKS_IT; identifies the top task in the hierarchy for the control scope.
• BUDGET_TYPE_CODE — References PA_BUDGET_TYPES; specifies which budget type (for example, approved cost budget) the control level applies to.
• FUNDS_CONTROL_LEVEL_CODE — The core business attribute. It holds the control level that dictates how funds are reserved and checked for transactions, ranging from no control through advisory and absolute control.
• RESOURCE_LIST_MEMBER_ID — References PA_RESOURCE_LIST_MEMBERS; optionally restricts the control to a specific resource.
• PARENT_MEMBER_ID — Supports hierarchical resource list membership for parent-child control definitions.
• PPL_PROJECT_ID and PTK_TASK_ID — Additional foreign references to PA_PROJECTS_ALL and PA_TASKS respectively, supporting project and task relationships used by the budgetary control engine.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATED_BY, CREATION_DATE, LAST_UPDATE_LOGIN — Standard Oracle EBS audit columns that record who created and last modified each configuration and when.

The 13 documented columns combine one surrogate primary key, several foreign-key business-reference columns, one principal control attribute, and the standard audit stamp. The unique index on BUDGETARY_CONTROLS_ID confirms the surrogate key; the remaining reference columns act as business-key candidates for the scoped configuration.

Common Use Cases and Queries

Typical usage centers on reviewing and troubleshooting funds control behavior during transaction entry and on reporting control coverage across a project portfolio.

• Determine the configured control level for a specific project and task to explain why a transaction was or was not subjected to funds checking.
• Audit which projects have advisory versus absolute control, supporting governance and budget policy reviews.
• Reconcile budgetary control setup against budget types and resource lists after configuration changes.

A representative query retrieves control levels for a project:

• SELECT bc.budgetary_controls_id, bc.project_id, bc.task_id, bc.budget_type_code, bc.funds_control_level_code FROM pa.pa_budgetary_controls bc WHERE bc.project_id = :project_id;

Reporting scenarios include a portfolio-wide control inventory joining project names from PA_PROJECTS_ALL, and an exception report listing records with no resource list member for projects requiring resource-level control.

Related Objects

• PA_PROJECTS_ALL — Joined via PROJECT_ID and PPL_PROJECT_ID; supplies project identity and attributes.
• PA_TASKS — Joined via TASK_ID and PTK_TASK_ID; supplies task-level scope.
• PA_TOP_TASKS_IT — Joined via TOP_TASK_ID; identifies the top task hierarchy node.
• PA_BUDGET_TYPES — Joined via BUDGET_TYPE_CODE; defines the budget type subject to control.
• PA_RESOURCE_LIST_MEMBERS — Joined via RESOURCE_LIST_MEMBER_ID; restricts control to specific resources.
• PA_BUDGET_VERSIONS — Provides the budget versions against which controlled funds are measured.
• PA_FUNDS_CONTROL_LEVELS (control level lookup) — Supplies the valid values referenced by FUNDS_CONTROL_LEVEL_CODE.

These relationships confirm the table's role as a central link connecting project, task, budget type, and resource entities within the Oracle Projects budgetary control framework.