Search Results p_time_period_id

Overview

PSP_SUM_TRANS is an Oracle E-Business Suite PL/SQL package owned by the APPS schema that supports the summary and transfer processing cycle for payroll and labor cost distribution within the Oracle Payroll and Oracle Project Costing integration flows. Its principal business function is to consolidate transaction detail into summary lines, apply the appropriate accounting and encumbrance attributes, and transfer those summarized amounts into the relevant Oracle General Ledger and Oracle Grants Management staging interfaces for downstream journal creation and award costing.

The package embodies the bridge between transactional cost collection and financial posting. It groups payroll or project expenditure data by time period, batch, business group, and set of books, converts it into General Ledger-ready journal interface rows, and provides tie-back and balance reconciliation utilities that allow implementers to validate that summarized amounts reconcile to source transactions. Because cost distribution is accounting-critical, the package also manages the batch lifecycle—marking the beginning and end of a summarization run—to ensure that partial or interrupted runs do not post incomplete journals.

Key Procedures and Functions

The documented API surface comprises seventeen procedures and functions:

• SUM_AND_TRANSFER — the primary driver that summarizes source payroll or project transactions and transfers the results to the target interfaces.
• MARK_BATCH_BEGIN and MARK_BATCH_END — delimit the start and completion of a summarization batch, establishing control boundaries around a run.
• CREATE_GL_SUM_LINES — constructs the summarized General Ledger lines derived from the source transactions.
• INSERT_INTO_SUMMARY_LINES — inserts an individual summarized line, including person, assignment, time period, accounting date, exchange rate type, code combination, project, task, award, amount, and debit/credit attributes.
• TRANSFER_TO_GL_INTERFACE and INSERT_INTO_GL_INTERFACE — move summarized amounts into the GL interface tables for journal import.
• GET_GL_JE_SOURCES and GET_GL_JE_CATEGORIES — retrieve valid journal source and category values used to label the generated journals.
• GET_ENCUM_TYPE_ID — resolves the encumbrance type identifier, which the user specifically searched for, from the General Ledger encumbrance type definitions so that summarized cost lines can be associated with the correct encumbrance classification.
• GL_TIE_BACK and GL_BALANCE_TRANSACTION — reconciliation utilities that verify summarized transactions tie back to the transferred GL balances.
• CREATE_GMS_SUM_LINES, TRANSFER_TO_GMS_INTERFACE, and GMS_TIE_BACK — equivalents for the Grants Management flow, producing and validating award-related interface rows.
• INSERT_INTO_PA_INTERFACE — writes summarized transactions into the Oracle Projects interface.
• SUPERCEDE_ER — handles superseding of existing encumbrance or expenditure records when reprocessing occurs.

Tables Accessed

The package reads and writes a well-defined set of interface and reference tables through APPS synonyms. It writes to GL_INTERFACE, GL_INTERFACE_CONTROL, and GL_INTERFACE_CONTROL_S to stage journal lines and control totals for Oracle General Ledger journal import. GL_JE_SOURCES and GL_JE_CATEGORIES provide the valid source and category values, while GL_JOURNAL_IMPORT_S supports import sequencing. GL_ENCUMBRANCE_TYPES supplies the encumbrance type lookup used by GET_ENCUM_TYPE_ID. For grants processing it writes to GMS_TRANSACTION_INTERFACE_ALL. Payroll reference data is read from PAY_ELEMENT_TYPES_F, PAY_ELEMENT_TYPE_RULES, and PAY_ELE_CLASSIFICATION_RULES, while HR_ALL_ORGANIZATION_UNITS and HR_ALL_ORGANIZATION_UNITS_TL supply organization information. Project data is validated against PA_PROJECTS_ALL and staged in PA_TRANSACTION_INTERFACE_ALL.

Usage Notes

PSP_SUM_TRANS is typically invoked by concurrent programs and internal cost distribution processes rather than directly from Oracle Forms. The standard entry point is SUM_AND_TRANSFER, which orchestration code calls with source type, source code, payroll, time period, batch, business group, and set of books parameters. Because the package is referenced by two other packages, customizations should call the packaged APIs rather than the underlying interface tables directly, preserving batch control and tie-back integrity. Implementers commonly trace GET_ENCUM_TYPE_ID when diagnosing encumbrance-related journal errors, confirming that the referenced GL_ENCUMBRANCE_TYPES entry exists and matches the transaction's encumbrance classification. All calls should observe the mark-batch begin and end protocol to avoid orphaned interface rows.