Search Results res_result_code




Overview
Explore in AI Chat

Overview

APPS.PA_TRX_FUNDS_CHK_DET_V is a reporting view in Oracle E-Business Suite (EBS) Release 12.1.1 and 12.2.2 that exposes the detail rows produced when Oracle Project Budgetary Controls and Funds Checking processes evaluate project transactions. The view is built directly on PA_BUDGETARY_CONTROL_OPTIONS and the budgetary control staging structure referenced as PA_BC_PACKETS, and it presents both the controlling (accounting) amounts and the funds-availability amounts computed against a project's budget, encumbrances, and actuals. Its primary role is to support Funds Checking inquiry and reporting: it allows users and integrators to trace, per transaction distribution, whether a given expenditure, requisition, purchase order, or journal source transaction passed or failed the funds check and why.

Because the view is layered over the budgetary control packet data rather than a single base table, it functions as a consolidated, denormalized read model. Its columns align with the Funds Check Results and budgetary control inquiry screens delivered by Oracle Projects, and the presence of the transactional identifiers (rowid, request_id, document_header_id, document_distribution_id) makes it suitable for joining back to source transactions in subledger and general ledger contexts.

Underlying Base Objects

The documented referenced objects include the following:

  • PA_BC_PACKETS (synonym) — the core budgetary control packet/detail structure supplying most columns, aliased as bc in the view definition.
  • PA_BUDGETARY_CONTROL_OPTIONS (synonym) — budgetary control configuration per project/operating unit, governing whether funds checking is enabled and its thresholds.
  • PA_BUDGET_ENTRY_METHODS, PA_BUDGET_VERSIONS — budget entry methodology and the specific budget version against which funds checking is performed (budget_version_id).
  • PA_PROJECTS_ALL, PA_TASKS — project and task (including top task) definition, also used indirectly through the PA_OPERATING_UNITS_V and PA_LOOKUPS views for descriptive decoding.
  • PA_FUNDS_CONTROL_UTILS (package) and MO_GLOBAL (package) — supporting PL/SQL for funds control logic and multi-org (operating unit / set of books) security.

These objects together provide the project, task, resource, budget version, and multi-organization context required to interpret each funds-check detail row.

Key Columns

  • bc.rowid, packet_id, bc_packet_id, parent_bc_packet_id, request_id — identify the packet and the concurrent request that generated the funds-check detail.
  • project_id, task_id, top_task_id, bud_task_id, resource_list_member_id, parent_resource_id — the project/task/resource dimension of the checked transaction.
  • budget_ccid, expenditure_type, expenditure_item_date, expenditure_organization_id, actual_flag — accounting and expenditure attributes; actual_flag distinguishes encumbrance ('E') from actual ('A') transactions.
  • set_of_books_id, je_category_name, je_source_name, period_name, period_year, period_num, document_header_id, document_distribution_id, gl_row_number — general ledger and source-document references for drill-down.
  • accounted_dr, accounted_cr, entered_dr, entered_cr — amounts; the view applies NVL(...,0) to produce safe numeric values.
  • effect_on_funds_code, result_code, project_result_code — the funds-check outcome, including the task_result_code the user searched for; these codes indicate whether the transaction passed, failed, or had no impact, at project and task level.
  • r_funds_control_level_code, rg_funds_control_level_code, t_funds_control_level_code, tt_funds_control_level_code, p_funds_control_level_code — the funds control level applied at resource, resource group, task, top task, and project levels.
  • project_budget_posted, project_enc_posted, project_enc_approved, project_actual_posted, project_actual_approved and their top_task equivalents — the available balances against which funds are checked.

Common Use Cases and Queries

The view is typically queried to diagnose failed funds checks and to report available funds by project/task.

  • Locate failed checks for a project or request.
  • Reconcile budget, encumbrance, and actual balances by project and top task.
  • Drill from a funds-check row to a GL distribution using document_header_id and document_distribution_id.

Sample query:

SELECT request_id, project_id, task_id, top_task_id,
       effect_on_funds_code, result_code, project_result_code,
       accounted_dr, accounted_cr,
       project_budget_posted, project_enc_posted
 FROM apps.pa_trx_funds_chk_det_v
 WHERE project_id = :p_project_id
   AND result_code <> 'S';

Filtering on result_code and effect_on_funds_code isolates exceptions, while joins to PA_PROJECTS_ALL and PA_TASKS supply project and task names for reporting.