Search Results parent_bc_packet_id




Overview
Explore in AI Chat

Overview

PA_BC_COMMITMENTS is a single-organization view within the Oracle EBS Projects (PA) module that exposes burden cost commitment and encumbrance data used by the Project Burdening and Commitment Cost processes. It presents transaction-level detail for commitment amounts, burdened totals, transfer status, and the associated accounting identifiers (CCIDs) generated when commitment costs are compiled and later relieved against actual expenditures. The view is central to the flow that moves supplier commitments and encumbrances through the Projects subledger into General Ledger.

The view is documented as Not implemented in this database, meaning the compiled definition is derived rather than stored in the sample environment from which the ETRM metadata was captured. Its defining characteristic is the ORG_ID predicate applied at the end of the view text, which performs a multi-organization security filter using USERENV('CLIENT_INFO') truncated to ten characters. This mechanism restricts rows to the operating unit (ORG_ID) currently set in the user session, converting the underlying multi-org table into a single-org presentation suitable for reporting and concurrent processing.

Underlying Base Objects

The ETRM metadata documents no base objects for this view, but the SELECT text unambiguously identifies the source as PA_BC_COMMITMENTS_ALL. The _ALL suffix indicates a multi-organization table that carries ORG_ID and is secured by the standard multi-org partition logic. PA_BC_COMMITMENTS is therefore a filtered projection of PA_BC_COMMITMENTS_ALL, exposing the same column list while applying the client-info ORG_ID restriction at runtime. Process EX_PROCESS — a unique key involving BC_COMMITMENT_ID, BC_PACKET_ID, PARENT_BC_PACKET_ID, PACKET_ID, and PROCESS_EXP_ITEM_ID — identifies individual rows within the table.

Key Columns

The column list is broad and supports both transactional and accounting processing. The COMPILED_MULTIPLIER column, the term the user searched for, is the factor applied to the commitment raw amount to derive the burdened commitment amount during compilation. It sits alongside COMM_TOT_RAW_AMT, COMM_TOT_BD_AMT, COMM_RAW_AMT_RELIEVED, and COMM_BD_AMT_RELIEVED, which together track raw and burdened commitment totals and their relieved portions. Other notable columns include:

Common Use Cases and Queries

The view supports reconciliation of commitment and burden amounts, analysis of transfer status, and investigation of the multiplier applied during burdens compilation. A typical query examining the compiled multiplier against the raw and burdened totals is:

  • Burden reconciliation: SELECT BC_COMMITMENT_ID, PROJECT_ID, TASK_ID, EXPENDITURE_TYPE, COMM_TOT_RAW_AMT, COMPILED_MULTIPLIER, COMM_TOT_BD_AMT, COMM_RAW_AMT_RELIEVED, COMM_BD_AMT_RELIEVED FROM PA_BC_COMMITMENTS WHERE PROJECT_ID = :p_project_id ORDER BY BC_COMMITMENT_ID;
  • Transfer status review: SELECT PACKET_ID, TRANSFER_STATUS_CODE, COMM_TRANSFER_REJ_REASON, PROJ_TRANSFER_REJ_REASON, COUNT(*) FROM PA_BC_COMMITMENTS GROUP BY PACKET_ID, TRANSFER_STATUS_CODE, COMM_TRANSFER_REJ_REASON, PROJ_TRANSFER_REJ_REASON;
  • Period accounting detail: SELECT PERIOD_NAME, GL_DATE, TXN_CCID, ENTERED_DR, ENTERED_CR, ACCOUNTED_DR, ACCOUNTED_CR FROM PA_BC_COMMITMENTS WHERE PERIOD_NAME = :p_period AND SET_OF_BOOKS_ID = :p_sob;
  • Unrelieved burdened commitments: SELECT BC_COMMITMENT_ID, COMM_TOT_BD_AMT - COMM_BD_AMT_RELIEVED AS BALANCE FROM PA_BC_COMMITMENTS WHERE ACTUAL_FLAG = 'C' AND COMM_TOT_BD_AMT <> COMM_BD_AMT_RELIEVED;

Because the view enforces ORG_ID filtering through CLIENT_INFO, reports must ensure the correct operating unit is initialized in the session before querying, otherwise rows may be excluded or unexpectedly included.