Search Results mark_extracted_cdl_rows

Overview

PJI_FM_EXTR is a PL/SQL package in the APPS schema that belongs to the Oracle Projects suite, specifically the Project Financial Management (PJI) module. Its name denotes a "Financial Management Extraction" component, and its role is to identify eligible transaction rows in the Projects tables and stage or mark them for transfer to a downstream extraction staging area. In Oracle EBS 12.1.1 and 12.2.2, the package is catalogued with an API classification of OTHER and is documented in the ETRM as VALID, indicating that the compiled package and body exist and are usable in the instance. The package supports the extraction side of Project revenue and cost processing by selecting batches of transactions — expenditures, cost distribution lines, draft revenues, draft invoices, and customer revenue distribution lines — and by flagging those rows once they have been extracted. The package is internally self-referencing (APPS.PJI_FM_EXTR references APPS.PJI_FM_EXTR) and is referenced by the companion package PJI_FM_SUM_EXTR, which indicates that the extraction and summarization processes cooperate in the same batch-oriented flow. Dependency metadata shows PJI_FM_EXTR resides on top of SYS.STANDARD and therefore relies only on the PL/SQL runtime rather than external PL/SQL library packages.

Key Procedures and Functions

The documented interface contains 26 procedures and functions, organized around extraction of a batch followed by post-extraction marking of the affected rows.

EXTRACT_BATCH_FND and EXTRACT_BATCH_DREV extract batches for funding and draft revenue processing respectively, each paired with MARK_EXTRACTED_FND_ROWS / MARK_EXTRACTED_FND_ROWS_PRE / MARK_EXTRACTED_FND_ROWS_POST and the equivalent DREV marking routines.
EXTRACT_BATCH_CDL_CRDL_FULL, EXTRACT_BATCH_ERDL_FULL, EXTRACT_BATCH_CDL_ROWIDS, EXTRACT_BATCH_CRDL_ROWIDS, EXTRACT_BATCH_ERDL_ROWIDS, and EXTRACT_BATCH_CDL_AND_CRDL handle cost distribution lines (CDL) and customer revenue distribution lines (CRDL), including full-row and ROWID-based variants.
MARK_EXTRACTED_CDL_ROWS_PRE, MARK_EXTRACTED_CDL_ROWS, and MARK_EXTRACTED_CDL_ROWS_POST form the pre/extract/post marking sequence for CDL rows.
EXTRACT_BATCH_ERDL and EXTRACT_BATCH_DINV cover expense revenue distribution lines and draft invoices, with MARK_EXTRACTED_DINV_ROWS completing the draft invoice marking stage.

The "_PRE" and "_POST" suffixes indicate that marking is performed in phases, allowing the extraction routine to run between them.

Tables Accessed

Through APPS synonyms the package reads and updates the core Project Financial Management tables: PA_EXPENDITURES_ALL and PA_EXPENDITURE_ITEMS_ALL (expenditure batches), PA_EXPENDITURE_TYPES, PA_COST_DISTRIBUTION_LINES_ALL (cost distribution extraction), PA_CUST_REV_DIST_LINES_ALL and PA_CUST_EVENT_RDL_ALL (customer revenue distribution), PA_DRAFT_REVENUES_ALL and PA_DRAFT_INVOICES_ALL with PA_DRAFT_INVOICE_ITEMS (draft revenue and invoice extraction), PA_EVENTS and PA_EVENT_TYPES (event-driven revenue), PA_AGREEMENTS_ALL, PA_IMPLEMENTATIONS_ALL, AR_PAYMENT_SCHEDULES_ALL for receivables linkage, and GL_PERIODS for accounting period validation. These tables are the authoritative sources for the rows that the extraction batch routines select and mark.

Usage Notes

PJI_FM_EXTR is not an end-user API; it is invoked by Project Financial Management batch programs and by its companion summarization package PJI_FM_SUM_EXTR. Typical invocations occur during concurrent program runs that extract project cost and revenue data for transfer, and it may be called by custom extensions that need to reproduce the standard extraction and marking sequence. Because marker procedures modify rows in the Projects tables, the package should be executed only through the supported batch flow or with extreme care in custom code, honoring the pre/extract/post ordering documented in the procedure names.