Search Results top_task




Overview
Explore in AI Chat

Overview

PA_TRX_FUNDS_CHK_MAIN_V is a Projects (PA) module view owned by the APPS schema in Oracle EBS 12.1.1 and 12.2.2. It exposes the results of Oracle Projects budgetary control funds checking for project transaction packets. Each row represents a candidate accounting distribution originating from a PA_BC_PACKETS packet — for example, an expenditure item, a budget line, or a supplier cost adjustment — together with the outcome of the funds check performed against the controlling budget. The view is the primary reporting surface for diagnosing why a transaction was accepted, rejected, or held by budgetary controls, and it is commonly consumed by ETRM/audit reconciliation reports and by integrations that need to surface funds-check outcomes to feeder systems.

Underlying Base Objects

The view is defined over PA_BC_PACKETS (the budgetary control packet table, aliased BC and the driver of the result columns such as RESULT_CODE, RES_RESULT_CODE, and RES_GRP_RESULT_CODE). Lookups are resolved through the APPS PA_LOOKUPS view (L1, L2, L3) for status meanings, document types, and budget status codes. Project, task, and organization context come from PA_PROJECTS_ALL, PA_TASKS, PA_OPERATING_UNITS_V, and the PL/SQL function PA_EXPENDITURES_UTILS.GETORGTLNAME. Expenditure classification is joined from PA_EXPENDITURE_TYPES. Budget context is supplied by PA_BUDGET_VERSIONS, PA_BUDGET_TYPES, PA_BUDGET_ENTRY_METHODS, and PA_BUDGETARY_CONTROL_OPTIONS. Resource attribution uses PA_RESOURCES and PA_RESOURCE_LIST_MEMBERS, while MO_GLOBAL provides operating-unit (multi-org) context. The view does not store data; it is a read-only projection over these transactional and setup objects.

Key Columns

Common Use Cases and Queries

Typical uses include auditing failed funds checks, reconciling packets by funds effect, and feeding downstream reports. A common query filters on EFFECT_ON_FUNDS_CODE to isolate lines that consume or relieve funds:

  • SELECT PACKET_ID, PROJECT_ID, TASK_ID, EXPENDITURE_TYPE, EFFECT_ON_FUNDS_CODE, RESULT_CODE, AMOUNT, PERIOD_NAME FROM APPS.PA_TRX_FUNDS_CHK_MAIN_V WHERE EFFECT_ON_FUNDS_CODE = :p_code;
  • SELECT PROJECT, TASK, STATUS_MEANING, RESULT_CODE, SUM(AMOUNT) FROM APPS.PA_TRX_FUNDS_CHK_MAIN_V GROUP BY PROJECT, TASK, STATUS_MEANING, RESULT_CODE;

Because the view returns one row per packet distribution, it is well suited to drill-down reporting from the budgetary control workbench and to exception analysis, where rows carrying non-success RESULT_CODE values are examined alongside EFFECT_ON_FUNDS_CODE to explain control rejections.