Search Results pa_commitment_txns_v




Overview
Explore in AI Chat

Overview

PA_COMMITMENT_TXNS_V is a PL/SQL view owned by the APPS schema in Oracle E-Business Suite, classified under the JA (Asia/Pacific Localizations) product family. It exposes project-related commitment transactions — requisitions and purchase orders linked to projects and tasks — in a consolidated, reporting-ready format. Its role is to present commitment data that Project Accounting and Purchasing modules generate, unifying requisition distribution information with burdening logic and, in the case of the documented localizations, non-recoverable tax amounts computed by JAI_PA_COSTING_PKG.

The view is part of Oracle's Commitment Transaction framework used by Project Costing, Funds Control, and budgetary reporting. It appears during searches for "oracle_payables" because it draws on purchasing commitments that eventually flow into payables, invoices, and cost distribution. The Status is VALID and the object type is VIEW, meaning it is a stored definition that resolves to underlying project and purchasing tables at runtime.

Underlying Base Objects

According to the ETRM metadata for 12.2.2, PA_COMMITMENT_TXNS_V is defined over a set of synonyms, views, and PL/SQL packages. The principal synonyms are PJM_REQ_COMMITMENTS_V and PJM_PO_COMMITMENTS_V, which provide the requisition and purchase order commitment data respectively. Supporting views include PA_PROJ_REQ_DISTRIBUTIONS, PA_PROJ_PO_DISTRIBUTIONS, and PA_PROJ_AP_INV_DISTRIBUTIONS, which expose project-attributed distributions for requisitions, purchase orders, and AP invoice lines.

Logic is embedded via packages: PA_BURDEN_CMTS for burdened cost calculation, PA_CURRENCY and PA_MULTI_CURRENCY for currency handling, PA_TASK_UTILS and PA_UTILS4 for task resolution, PA_FUNDS_CONTROL_UTILS for funds checking, and PA_PJC_CWK_UTILS for constructed work-in-progress handling. AP_INVOICES_PKG links to Payables, while FND_PROFILE, HR_GENERAL, and HR_SECURITY provide profile options and security context. The JAI_PA_COSTING_PKG supplies the localizations-specific non-recoverable tax amount. CST_PROJMFG_CMT_VIEW is referenced for manufacturing commitment alignment.

Key Columns

The view exposes PROJECT_ID and TASK_ID to anchor each commitment to a project and task. REQ_NUMBER, REQ_DISTRIBUTION_ID, REQUISITION_HEADER_ID, and REQ_LINE identify the requisition and its distribution. VENDOR_ID and VENDOR_NAME identify the source supplier, while REQUESTOR_NAME and CREATION_DATE describe the originating document. EXPENDITURE_ITEM_DATE, EXPENDITURE_TYPE, EXPENDITURE_CATEGORY, and EXPENDITURE_ORGANIZATION_ID carry the costing attributes used by burdening and cost distribution. APPROVED_FLAG and NEED_BY_DATE indicate workflow status and timing.

Currency and amount columns include DENOM_CURRENCY_CODE and DENOM_AMOUNT, with AMOUNT computed as PPRD.AMOUNT plus the non-recoverable tax returned by JAI_PA_COSTING_PKG.GET_NONREC_TAX_AMOUNT. UNIT, UNIT_PRICE, and QUANTITY supply the originating measure. Burdening columns derive from PA_BURDEN_CMTS.GET_CMT_COMPILED_SET_ID and GET_CMT_BURDENED_COST. The literal 'ORACLE_PURCHASING' and 'R' identify the source application and document class. Numerous TO_NUMBER(NULL) and TO_DATE(NULL) columns placeholders preserve a fixed projection shape.

Common Use Cases and Queries

Typical uses include reconciling project commitments against approved requisitions and purchase orders, reviewing burdened versus unburdened commitment cost, and tracking non-recoverable tax for Asia/Pacific localization reporting. A representative query follows:

  • SELECT project_id, task_id, req_number, expenditure_type, expenditure_item_date, denom_currency_code, denom_amount FROM apps.pa_commitment_txns_v WHERE project_id = :p_project_id ORDER BY expenditure_item_date;
  • Commitment-by-vendor analysis: SELECT vendor_id, vendor_name, SUM(denom_amount) total_commit FROM apps.pa_commitment_txns_v GROUP BY vendor_id, vendor_name;
  • Approved commitment listing: SELECT req_number, req_line, expenditure_category, approved_flag, need_by_date FROM apps.pa_commitment_txns_v WHERE approved_flag = 'Y';
  • Task-level burdened cost: SELECT task_id, expenditure_type, SUM(amount), SUM(burdened_cost) FROM apps.pa_commitment_txns_v WHERE task_id = :p_task_id GROUP BY task_id, expenditure_type;

Because the view calls several packages at runtime, queries should filter by project, task, or date range to limit execution cost. Access requires the appropriate APPS or project security privileges, and results depend on profile options and HR security resolved through FND_PROFILE and HR_SECURITY.