Search Results r_funds_control_level_code

Overview

PA_TRX_FUNDS_CHK_DET_V is an APPS-owned database view within the Oracle E-Business Suite Projects (PA) module, delivered with status VALID in both release 12.1.1 and 12.2.2. The view presents transaction-level budgetary control detail — the funds-check outcome for each budgetary control packet processed by Oracle Project Budgetary Control. Its name reflects its purpose: Project Accounting (PA), transaction (TRX), funds check (FUNDS_CHK), detail (DET), view (V).

Functionally, the view exposes the detail rows generated when budgetary control funds checks are executed against commitments, obligations, and actual transactions, together with the derived balances used to evaluate the results. Each row carries both the raw packet information and a set of NVL-protected balance figures, so consumers can reconcile the funds-check result code with the underlying budget, commitment, and actual amounts. This makes it a reporting and diagnostic object rather than a transactional entry point; it is not designed for direct DML.

Underlying Base Objects

The view is defined principally over PA_BC_PACKETS, the budgetary control packets table that stores the individual funds-check records. Several attributes reference supporting configuration and control setup: PA_BUDGETARY_CONTROL_OPTIONS (budgetary control flags and thresholds), PA_BUDGET_ENTRY_METHODS, PA_BUDGET_VERSIONS, and PA_PROJECTS_ALL, PA_TASKS, and PA_OPERATING_UNITS_V for project, task, and operating unit context. Lookup code meanings are resolved through PA_LOOKUPS, and the funds control logic itself derives from the PA_FUNDS_CONTROL_UTILS package. MO_GLOBAL provides multi-org (operating unit) security context.

Key Columns

• PACKET_ID, BC_PACKET_ID, PARENT_BC_PACKET_ID — identify the budgetary control packet and its hierarchy; REQUEST_ID links the rows to the concurrent process that generated them.
• PROJECT_ID, TASK_ID, TOP_TASK_ID, BUD_TASK_ID — project and task attribution, including the top task and budgeted task used for control-level evaluation.
• ACTUAL_FLAG, STATUS_CODE, RESULT_CODE, PROJECT_RESULT_CODE, EFFECT_ON_FUNDS_CODE — classify the transaction and record the pass/fail outcome of the funds check.
• BUDGET_CCID, SET_OF_BOOKS_ID, PERIOD_NAME, PERIOD_YEAR, PERIOD_NUM — accounting and set-of-books context for the checked amounts.
• ACCOUNTED_DR/CR, ENTERED_DR/CR, PROJECT_BUDGET_POSTED, PROJECT_ENC_POSTED/APPROVED, PROJECT_ACTUAL_POSTED/APPROVED — the balance components; the derived commitment and actual columns net the entered amount according to ACTUAL_FLAG.
• R_/RG_/T_/TT_/P_FUNDS_CONTROL_LEVEL_CODE — control levels applied at resource, resource group, task, top task, and project.

Common Use Cases and Queries

Typical uses include reconciling failed funds checks, auditing commitment and actual balances by project or task, and feeding custom budgetary control dashboards. A representative query:

SELECT p.PROJECT_NUMBER, d.TASK_ID, d.STATUS_CODE, d.RESULT_CODE,
       d.EFFECT_ON_FUNDS_CODE,
       d.PROJECT_ENC_POSTED, d.PROJECT_ACTUAL_POSTED
FROM   APPS.PA_TRX_FUNDS_CHK_DET_V d,
       APPS.PA_PROJECTS_ALL p
WHERE  d.PROJECT_ID = p.PROJECT_ID
AND    d.PROJECT_RESULT_CODE = 'F'
AND    d.PERIOD_NAME = :period;

Join to PA_TASKS for task descriptions and constrain by SET_OF_BOOKS_ID or operating unit where MO_GLOBAL is active. Because results are derived at request time, always filter on REQUEST_ID or a date/period range rather than scanning the view unfiltered.