Search Results mrc_row_count

Overview

APPS.PA_PURGE_ICIP is an Oracle Projects archive-and-purge utility responsible for removing intercompany and draft invoice data from the Oracle E-Business Suite Projects schema after it has been retained for the required period. The package belongs to the broader Oracle Projects purge architecture, in which purge requests are driven by a purge batch identifier, a project identifier, a purge release code, and a transaction cut-off date. Its header comment identifies the module revision as PAICIPPB.pls (version 120.6), indicating a long-lived component of the Projects code line.

The central business purpose is to selectively archive rows into shadow archive tables and then delete the corresponding operational rows. The package is written to process data in commit-sized increments so that high-volume purges do not exhaust rollback segments or hold excessive locks on the Projects tables. It also contains multi-reporting-currency (MRC) awareness, which is directly relevant to the user query term "mrc_row_count": internal counters such as the MRC insert and delete counters track how many MRC-related rows were archived or purged during a processing loop, and the MRC flag governs whether MRC handling is engaged.

Key Procedures and Functions

• PA_DRAFTINVDETAILS — The primary private procedure. It archives and purges data from PA_DRAFT_INVOICE_DETAILS_ALL. It accepts a purge batch identifier, project identifier, purge release, transaction-to date, archive flag, and commit size, and returns an error stack, error stage, and error code. When the archive flag is 'Y', rows are first inserted into the archive table PA_DRAFT_INV_DETS_AR and are subsequently deleted. The procedure operates in a LOOP, resetting its record-insert and record-delete counters on each pass, and it halves the effective commit size before performing archive inserts so that the combined archive-plus-delete volume per iteration stays within the batch's intended commit footprint. MRC insert and delete counters are maintained alongside the standard counters.
• PA_MC_DRAFTINVOICEDETAILS — The multi-currency counterpart procedure, invoked to apply the same archive-and-purge treatment to the MRC shadow rows that correspond to the draft invoice detail records processed by PA_DRAFTINVDETAILS. Separation of the MRC logic into a distinct procedure allows the purge routine to be skipped entirely when the MRC flag is 'N', which avoids unnecessary work in installations that do not enable multiple reporting currencies.

Both procedures follow the Oracle error-handling convention of carrying an error stack, error stage, and numeric error code, allowing the calling purge driver to record diagnostic context for each failed batch.

Tables Accessed

• PA_DRAFT_INVOICE_DETAILS_ALL — The principal operational table purged by PA_DRAFTINVDETAILS; rows are read, archived, and then deleted.
• PA_DRAFT_INV_DETS_AR — The archive table receiving rows copied from PA_DRAFT_INVOICE_DETAILS_ALL before deletion, keyed by purge batch, purge release, and purge project.
• PA_DRAFT_INVOICES_ALL — The draft invoice header table, referenced in support of the detail-level purge so that invoice structures remain consistent.
• PA_EXPENDITURE_ITEMS_ALL — Project expenditure items associated with the purged draft invoice details.
• PA_TASKS — Project task definitions referenced for validation and relationship integrity during purge processing.

Usage Notes

PA_PURGE_ICIP is not intended for direct invocation by end users. It is called by the Oracle Projects purge concurrent program infrastructure, and the ETRM metadata records that it is referenced by one other package, which supplies the purge batch and project context. The commit size is normally derived from the utility constant pa_utils2.arpur_mrc_commit_size rather than being supplied arbitrarily, so custom callers should preserve that derivation to avoid oversized transactions. Debug tracing is emitted through pa_debug.debug, and this trace should be enabled when diagnosing purge runs because the error stack carries the stage markers that identify the failing table. In EBS 12.1.1 and 12.2.2 the package remains an APPS-owned, non-public API; custom code should invoke it only through the supported purge framework rather than calling the private procedures directly.