Search Results create_burden_expenditure_item

Overview

APPS.PA_BURDEN_COSTING is the core PL/SQL package body responsible for Oracle EBS Project Accounting burden (indirect cost) processing. It calculates, distributes, and records burdened cost amounts for expenditure items, commitments, and cost distribution lines within Oracle Projects. In the context of Oracle EBS 12.1.1 and 12.2.2, this package is central to the Burden Costing process, invoked when indirect costs must be applied to raw costs according to compiled multiplier schedules and cost base definitions. It is an internal, non-public API classified as OTHER in the ETRM metadata, meaning it is invoked by other Oracle Projects processes rather than published as a formally supported customer-facing API.

The package maintains session-level context through a set of setter/getter procedures and functions, tracking the current project, current burden summary run, and the sponsored project flag. These state markers allow downstream procedures to operate on the correct project and batch without repeated parameter propagation, an approach also aligned with performance optimizations introduced through various bug fixes referenced in the source header.

Key Procedures and Functions

• SET_CURRENT_PROJECT_ID / GET_CURRENT_PROJECT_ID — store and retrieve the project ID currently being processed, using the PA_PROJECTS_ALL.PROJECT_ID type.
• SET_CURRENT_RUN_ID / GET_CURRENT_RUN_ID — store and retrieve the burden summary run ID (based on PA_COST_DISTRIBUTION_LINES_ALL.BURDEN_SUM_SOURCE_RUN_ID), enabling procedures to correlate burden activity with a specific batch.
• SET_CURRENT_SPONSORED_FLAG / GET_CURRENT_SPONSORED_FLAG — manage the sponsored project indicator derived via PA_GMS_API.IS_SPONSORED_PROJECT, supporting grants-related burdening rules.
• CREATE_BURDEN_EXPENDITURE_ITEM — the principal procedure (matching the user's search term) that creates the burdened expenditure item records resulting from burden calculation.
• CREATE_BURDEN_CMT_TRANSACTION — creates burden commitment transactions, extending burdening logic to commitment accounting.
• INSBURDENAUDIT — inserts audit records tracking burden cost distribution activity.
• POPULATE_GTEMP — loads data into the temporary/global temporary holding structures used during processing (e.g., PA_EI_CDL_CM_GTEMP).
• UPDATE_GTEMP — updates the temporary structures after processing before final persistence.

Tables Accessed

The package reads and writes against a set of Project Accounting tables accessed through APPS synonyms. PA_COST_DISTRIBUTION_LINES_ALL and PA_COST_DISTRIBUTION_LINES hold distributed cost lines and burden source run information. PA_EXPENDITURE_ITEMS_ALL, PA_EXPENDITURES, and PA_EXPENDITURES_ALL store expenditure and burden expenditure item records. PA_PROJECTS_ALL supplies project attributes, and GMS_AWARD_DISTRIBUTIONS supports grants-related burdening. PA_COMPILED_MULTIPLIERS provides the burden multiplier rates, while PA_COST_BASE_COST_CODES and PA_COST_BASE_EXP_TYPES define burden bases. PA_BURDEN_SUM_RUN_S tracks burden summarization runs. PA_COMMITMENT_TXNS and PA_COMMITMENT_TXNS_S support commitment burdening, PA_AUD_COST_DIST_LINES captures audit detail, and PA_EI_CDL_CM_GTEMP serves as the temporary staging table for expenditure item, cost distribution line, and commitment data.

Usage Notes

PA_BURDEN_COSTING is not intended for direct customer invocation. It is called internally by Oracle Projects concurrent programs and processes such as the Burden Costing process, and is referenced by six other packages within the Oracle Projects schema. Customizations should avoid direct calls; instead, they should rely on supported public APIs. The setter/getter pattern requires that context (project, run ID, sponsored flag) be established before the creation and temp-table procedures execute, and the temporary staging procedures must run in the correct sequence—populate, process, then update—to preserve data integrity. The presence of the PA_RPT_BTC_SRC_RESRC profile option reference indicates that burden source/resource behavior can be configured at the site level.