Search Results pa_expenditemadjactivities

Overview

PA_PURGE_COSTING is an Oracle EBS Projects (PA) schema package owned by APPS that supports the purge of costing and expenditure data from the project accounting tables. In Oracle Projects, purging is the process by which historical, summarized, or otherwise unnecessary transactional records are permanently removed from the operational costing tables once their accounting and reporting life cycle has completed. The package serves as the costing-specific worker component of the broader PA_PURGE infrastructure, performing the physical deletion of rows from expenditure, cost distribution, cross-charge distribution, and their associated denormalized and multi-reporting-currency (MRC) counterparts. It is classified as an OTHER API, meaning it is not a public, supported integration interface intended for direct customer invocation; instead it is designed to be called by Oracle Projects purge processes.

Key Procedures and Functions

The package exposes fifteen documented procedures, each targeting a specific costing table or logical group of tables:

• PA_COSTING_MAIN_PURGE — the primary driver procedure that coordinates the overall costing purge by invoking the subordinate purge routines.
• PA_COSTDISTLINES — removes cost distribution line records.
• PA_CCDISTLINES — removes cross-charge distribution line records.
• PA_EXPENDITURECOMMENTS — purges expenditure comment records.
• PA_EXPENDITEMADJACTIVITIES — purges expenditure item adjustment activity records.
• PA_EIDENORM — purges the denormalized expenditure item table used for reporting performance.
• PA_EXPENDITUREHISTORY — purges expenditure history rows.
• PA_EXPENDITUREITEMS — purges the base expenditure item records.
• PA_EXPITEMSSRCPURGE and PA_EXPITEMSDESTPURGE — handle purge on the source and destination sides of inter-project or cross-charge expenditure item transfers.
• PA_ROUTINGS1 — supports purge of routing-related costing data.
• PA_EXPENDITURES1 — purges expenditure header/interface records.
• PA_MRCEXPENDITUREITEMS, PA_MRCCOSTDISTLINES, and PA_MRCCCDISTLINES — purge the MRC shadow tables that store reporting-currency equivalents of expenditure items, cost distribution lines, and cross-charge distribution lines respectively.

Tables Accessed

The package operates across the core Oracle Projects costing tables through APPS synonyms. Base tables include PA_EXPENDITURES_ALL, PA_EXPENDITURE_ITEMS_ALL, PA_EXPENDITURE_COMMENTS, PA_EXPENDITURE_HISTORY, PA_EXPEND_ITEM_ADJ_ACTIVITIES, and its sequence PA_EXPEND_ITEM_ADJ_ACT_S, plus PA_COST_DISTRIBUTION_LINES_ALL and PA_CC_DIST_LINES_ALL. Denormalized data is handled through PA_EI_DENORM. Multi-reporting-currency mirrors are addressed via PA_EXPENDITURES_AR, PA_EXPENDITURE_ITEMS_AR, PA_COST_DIST_LINES_AR, PA_CC_DIST_LINES_AR, PA_EI_DENORM_AR, and PA_EXP_COMMENTS_AR. The _AR tables hold reporting-currency amounts, so they must be purged in lockstep with their base tables to avoid orphaned MRC rows.

Usage Notes

PA_PURGE_COSTING is invoked indirectly by the PA_PURGE package, which is the documented caller, and it also appears within its own dependency list. In practice, purging is driven from the Oracle Projects Purge concurrent program (for example, the Purge Projects / Purge Expenditures programs), which validates prerequisites such as closed accounting periods and fully accounted and interface-processed expenditure items before allowing deletion. Because the package is undocumented as a public API and its procedures manipulate high-volume transactional tables directly, custom code should never call it in place of supported Oracle APIs such as the expenditure adjustment or cost distribution APIs. Direct invocation bypasses the validation, security, and audit logic enforced by the standard purge flow and risks data corruption, broken foreign-key relationships, and invalid accounting balances. Administrators should ensure complete backups and confirm that no open commitments, unbilled receivables, or unprocessed interface lines remain before permitting a purge run in either 12.1.1 or 12.2.2.