Search Results cleanup_batch_details

Overview

PSP_SUM_ADJ is an Oracle E-Business Suite PL/SQL package owned by the APPS schema that supports the summarization and adjustment of payroll-related cost transactions for transfer into Oracle General Ledger and Oracle Grants Management. In the 12.1.1 and 12.2.2 releases the package serves as the bridge between Oracle Payroll and Oracle Projects cost collection on one side, and the subledger accounting destinations (GL_INTERFACE and the GMS transaction interface) on the other. The package name reflects its two-fold purpose: summary creation of aggregate cost lines, and adjustment processing of those summarized amounts prior to transfer.

The package is invoked most commonly from concurrent programs that transfer payroll summarized costs and adjustments. It encapsulates batch-oriented processing so that a run can be marked at its beginning, its detail lines generated, transferred, tied back, and finally cleaned up. The header revision (PSPADSTS.pls, 120.1) indicates the package is a long-standing payroll-to-GL integration component rather than a recent API.

Key Procedures and Functions

The 18 documented programs fall into several functional groups.

• SUM_TRANSFER_ADJ — top-level driver that executes the summarization and adjustment transfer for a given adjustment summary batch, business group, and set of books.
• MARK_BATCH_BEGIN / MARK_BATCH_END — bookend procedures that mark the start and completion of a batch run, providing run-level control and status tracking.
• CREATE_GL_SUM_LINES / CREATE_GMS_SUM_LINES — build summarized cost lines destined for General Ledger and for Grants Management respectively.
• INSERT_INTO_SUMMARY_LINES — inserts individual summarized lines, capturing person, assignment, time period, effective and accounting dates, exchange rate type, source type and code, set of books, GL code combination, project, expenditure organization, expenditure type, task, award, amount, Dr/Cr flag, status code, interface batch name, payroll control, business group, and descriptive flexfield attributes.
• TRANSFER_TO_GL_INTERFACE / INSERT_INTO_GL_INTERFACE — populate the GL_INTERFACE table for journal import, using the GL_JE_SOURCES and GL_JE_CATEGORIES lookups.
• TRANSFER_TO_GMS_INTERFACE / INSERT_INTO_PA_INTERFACE — feed Grants Management and Oracle Projects interfaces with the summarized cost detail.
• GET_GL_JE_SOURCES / GET_GL_JE_CATEGORIES — retrieve valid journal source and category values used when writing GL interface rows.
• GL_TIE_BACK / GMS_TIE_BACK — reconcile the summarized source amounts to the amounts written to the respective interfaces.
• GL_BALANCE_TRANSACTION — validates that debits and credits balance before the interface is written.
• CHECK_INTERFACE_STATUS / GET_THE_BATCH_DETAILS / CLEANUP_BATCH_DETAILS — inspect interface processing status, retrieve batch detail for reporting or reprocessing, and purge batch artifacts after successful completion.

Tables Accessed

The package predominantly writes to and reads from GL_INTERFACE, GL_INTERFACE_CONTROL, and GL_INTERFACE_CONTROL_S, which carry journal import data and their control records, and GL_JOURNAL_IMPORT_S for journal import reference. GL_JE_SOURCES and GL_JE_CATEGORIES provide the valid source and category values applied to interface rows. On the Grants side it references GMS_AWARD_DISTRIBUTIONS and GMS_TRANSACTION_INTERFACE_ALL. Payroll and Projects source data comes from PAY_ELEMENT_TYPES_F, PA_EXPENDITURES_ALL, PA_EXPENDITURE_GROUPS_ALL, PA_EXPENDITURE_ITEMS_ALL, and PA_PROJECTS_ALL. Organization information is resolved through HR_ALL_ORGANIZATION_UNITS and HR_ALL_ORGANIZATION_UNITS_TL. All access is via APPS synonyms.

Usage Notes

PSP_SUM_ADJ is not a public API in the conventional sense; its procedures are normally invoked indirectly through the concurrent programs that perform payroll summary and adjustment transfers. The SUM_TRANSFER_ADJ driver is the intended entry point, with MARK_BATCH_BEGIN and MARK_BATCH_END wrapping execution. Custom code should avoid writing to GL_INTERFACE directly when this package already provides validated insertion and tie-back logic. Because the package is documented as API classification OTHER, no stability guarantee exists for its internal procedures, and callers should revalidate behavior when applying 12.2.2 patches. The batch cleanup routine should be scheduled after downstream journal import and GMS interface processing confirm success, so that interface rows are not purged before they are consumed.