Search Results pa_cc_bl_process




Overview
Explore in AI Chat

Overview

PA_CC_BL_PROCESS is a PL/SQL package body owned by the APPS schema in Oracle E-Business Suite releases 12.1.1 and 12.2.2. It belongs to the Oracle Projects (PA) module and supports the processing of cross-charge (CC) distribution and transfer-price calculations. In Oracle Projects, cross-charge functionality governs the allocation of costs between expenditure items when work is performed by one organization or project on behalf of another, generating transfer price and cost distribution entries accordingly. The status of the package body is VALID, and it depends on a compact but highly focused set of Oracle Projects and Oracle General Ledger objects. The documented API classification is "OTHER," indicating that it is an internal processing package rather than a formally published public API. ETRM documents five procedures within the package, and records that the package is referenced by two other database objects, confirming its role as a contributing component in a larger cross-charge processing framework rather than a top-level entry point.

Key Procedures and Functions

  • PA_BL_PR — The primary processing routine in the package body. It orchestrates the cross-charge distribution logic, applying transfer-price rules and producing the resulting distribution records. Its dependencies on PA_CC_UTILS, PA_CC_TRANSFER_PRICE, and PA_DEBUG indicate that it performs validation and utility work, derives transfer prices, and emits debug information during execution.
  • INITIALIZATION — Prepares the processing context before the main routine runs, including resolution of profile options via FND_PROFILE and the current operating unit via MO_GLOBAL, and access to ledger relationships and sets of books through GL_ALC_LEDGER_RSHIPS_V and GL_SETS_OF_BOOKS.
  • MASS_UPDATE — Performs bulk modification of existing cross-charge distribution lines. This procedure is used when distribution rows already exist and require adjustment as a set.
  • MASS_INSERT — Inserts cross-charge distribution lines in bulk, supporting the creation of large volumes of PA_CC_DIST_LINES_ALL records in a single pass.
  • MASS_DELETE — Removes cross-charge distribution lines in bulk, typically ahead of regeneration or during correction of prior processing.

The MASS_UPDATE, MASS_INSERT, and MASS_DELETE procedures operate collectively as a bulk maintenance layer over the distribution line tables, while PA_BL_PR serves as the business processing driver.

Tables Accessed

The package interacts with the core Oracle Projects cost and cross-charge tables through APPS synonyms. PA_CC_DIST_LINES_ALL, PA_CC_DIST_LINES, and PA_CC_DIST_LINES_S are the cross-charge distribution line tables that the package creates, modifies, and deletes. PA_CC_TRANSFER_PRICE provides transfer pricing information used during distribution generation. PA_COST_DISTRIBUTION_LINES_ALL holds the underlying cost distribution lines that form the basis for cross-charge activity. PA_EXPENDITURES_ALL, PA_EXPENDITURE_GROUPS_ALL, and PA_EXPENDITURE_ITEMS_ALL supply the expenditure data being processed, including expenditure groups and individual items. PA_IMPLEMENTATIONS_ALL is used to determine the configured Oracle Projects installation context. DUAL and PLITBLM appear as utility references. General Ledger dependencies GL_SETS_OF_BOOKS and GL_ALC_LEDGER_RSHIPS_V support ledger and accounting setup resolution, while MO_GLOBAL establishes the current operating unit for multi-organization access.

Usage Notes

PA_CC_BL_PROCESS is not intended for direct invocation by end users or external integrations. Because it is not referenced by any database object and is classified as OTHER, it is typically called from within Oracle Projects cross-charge processing flows, such as concurrent programs and internal package logic that generate or maintain cross-charge distributions. The MASS_* procedures may be invoked by bulk-processing concurrent requests or by custom code performing high-volume corrections under controlled conditions. Any custom usage should be preceded by review of the surrounding cross-charge processing sequence, since the package writes directly to distribution, expenditure, and cost distribution tables. As with all Oracle Projects data, changes should be executed within a supported maintenance window or in coordination with the standard cross-charge processing cycle to preserve data integrity.