Search Results create_sum_lines

Overview

PSP_ENC_SUM_TRAN is the encumbrance summarization engine within the Oracle E-Business Suite payroll and labor distribution stack. Its principal business function is to initiate and execute the encumbrance summarization processes that consolidate transaction-level encumbrance detail into summarized lines suitable for General Ledger (GL) and Oracle Grants Management (GMS) integration. The package bridges payroll costing, project accounting, and grants encumbrance data, producing summarized encumbrance records and posting them to the GL interface. It coordinates control record processing, phase status tracking, and the movement of rejected lines to an archive table.

The package body carries a substantial history of bug fixes, reflected in global variables such as g_payroll_action_id (Bug 2030232), g_currency_code for the Quebec fix (Bug 2478000), g_susp_prob (Bug 2479579), g_insert_str (Bug 3233373), and g_dff_grouping_option (Bug 2908859). Precision handling for currencies is tracked through g_precision and g_ext_precision, while g_process_complete, g_sa_autopop, and g_suspense_failed support process-state and suspense validation logic.

Key Procedures and Functions

The package exposes twelve documented procedures and functions:

• ENC_SUM_TRANS — The main driver procedure that initiates encumbrance summarization and orchestrates the overall transaction flow.
• ENC_BATCH_BEGIN — Opens the encumbrance processing batch, establishing the control context for summarization.
• ENC_BATCH_END — Closes the encumbrance batch and finalizes processing state.
• INSERT_INTO_ENC_SUM_LINES — Inserts summarized encumbrance detail into the encumbrance summary lines structure.
• TR_TO_GL_INT — Transfers summarized encumbrance transactions to the General Ledger interface.
• GL_JE_SOURCE — Returns or resolves the journal entry source used for the GL posting.
• GL_JE_CAT — Returns or resolves the journal entry category applied to the generated GL records.
• ENC_TYPE — Determines the encumbrance type applied to the summarized transactions.
• GL_ENC_TIE_BACK — Performs tie-back validation between encumbrance summary data and GL balances.
• INSERT_INTO_GL_INT — Inserts encumbrance records directly into the GL interface tables.
• TR_TO_GMS_INT — Transfers summarized encumbrance transactions to the Grants Management interface.
• GMS_ENC_TIE_BACK — Performs tie-back validation specific to Grants Management encumbrance balances.

Supporting internal routines declared in the body include MOVE_REJ_LINES_TO_ARCH, CREATE_SUM_LINES, UPDATE_HIERARCHY_DATES, ADD_ST_WARNINGS, and LOG_ST_WARNINGS. These handle archival of rejected lines, summary line creation, hierarchy date maintenance, and warning collection and logging.

Tables Accessed

The package reads and writes the following documented tables through APPS synonyms:

• GL_ENCUMBRANCE_TYPES — Resolves the active encumbrance type definition.
• GL_INTERFACE, GL_INTERFACE_CONTROL, GL_INTERFACE_CONTROL_S, GL_JOURNAL_IMPORT_S — Target and control tables for loading summarized encumbrance data into General Ledger.
• GL_JE_CATEGORIES, GL_JE_SOURCES — Provide the journal category and source values used in the GL interface records.
• GMS_AWARDS_ALL, GMS_TRANSACTION_INTERFACE_ALL — Grants Management award and transaction interface data for grants encumbrance summarization.
• PA_PROJECTS_ALL, PA_TRANSACTION_INTERFACE_ALL — Project and project transaction detail feeding summarized encumbrance lines.
• PAY_ALL_PAYROLLS_F, PAY_ELEMENT_TYPES_F — Payroll and element type definitions used to associate encumbrances with payroll processing.
• HR_ALL_ORGANIZATION_UNITS, HR_ALL_ORGANIZATION_UNITS_TL — Organization unit data, including translated names, for expenditure organization identification.

Usage Notes

PSP_ENC_SUM_TRAN is invoked as part of the encumbrance summarization and GL/Grants integration flow rather than being called interactively. It is typically triggered by concurrent programs and by other packages in the payroll and labor distribution chain — the metadata records that the package is referenced by two other packages. It should be executed only within the supported concurrent processing context, since it depends on the control-record framework (g_control_rec_found) and batch begin/end bracketing. Custom code should not call the internal routines directly, as they assume an established control and batch state.