Search Results tr_to_gms_int




Overview

PSP_ENC_SUM_TRAN is an Oracle EBS public package owned by APPS that supports encumbrance summarization and transfer for Oracle Payroll costing within the Oracle Grants and Financials architecture. It is classified as OTHER within the ETRM metadata repository. The package is defined with AUTHID CURRENT_USER, meaning its SQL executes under the privileges of the calling user rather than the definer. It maintains global package state variables including g_run_id, g_error_api_path, g_business_group_id, and g_set_of_books_id, which are set at runtime to carry context across procedure calls within a processing run.

In the EBS 12.1.1 and 12.2.2 environments, the package acts as a bridge between payroll costing results and the General Ledger encumbrance model, and between payroll results and Oracle Grants Management. It supports the end-to-end flow of payroll encumbrance data from batch creation through summarization and final transfer to GL or GMS interfaces.

Key Procedures and Functions

The package exposes twelve documented procedures. These include:

  • ENC_SUM_TRANS — the primary driver procedure that orchestrates the summarization and transfer of payroll encumbrance transactions for a given payroll action, business group, and set of books.
  • ENC_BATCH_BEGIN — marks the beginning of an encumbrance processing batch for a payroll action, establishing batch context and returning a status.
  • ENC_BATCH_END — closes the encumbrance batch, performing any finalization needed at the conclusion of processing.
  • INSERT_INTO_ENC_SUM_LINES — inserts summarized encumbrance lines, populating the encumbrance summary with payroll, person, assignment, GL code combination, project, award, and descriptive flexfield attributes introduced for bug fix 2908859.
  • TR_TO_GL_INT — transfers summarized encumbrance data into the GL interface tables for journal import.
  • GL_JE_SOURCE — retrieves or resolves the GL journal source used for encumbrance entries.
  • GL_JE_CAT — retrieves or resolves the GL journal category for encumbrance entries.
  • ENC_TYPE — resolves the encumbrance type used for the entries.
  • GL_ENC_TIE_BACK — performs tie-back validation between GL encumbrance results and source data.
  • INSERT_INTO_GL_INT — writes records into the GL interface tables.
  • TR_TO_GMS_INT — transfers summarized encumbrance data to the Oracle Grants Management interface.
  • GMS_ENC_TIE_BACK — performs tie-back reconciliation for Grants Management encumbrance data.

The header also contains a commented-out procedure, CREATE_GL_ENC_SUM_LINES, indicating it was superseded or disabled in the shipped version (120.3, dated 2006).

Tables Accessed

The package reads and writes several documented tables via APPS synonyms. GL_INTERFACE, GL_INTERFACE_CONTROL, and GL_INTERFACE_CONTROL_S are used when transferring and controlling journal import of encumbrance entries. GL_JE_SOURCES, GL_JE_CATEGORIES, GL_JOURNAL_IMPORT_S, and GL_ENCUMBRANCE_TYPES provide the reference and control data needed to build valid GL journal entries. On the Grants side, GMS_TRANSACTION_INTERFACE_ALL receives transferred records, while GMS_AWARDS_ALL supplies award validation. HR_ALL_ORGANIZATION_UNITS and HR_ALL_ORGANIZATION_UNITS_TL resolve expenditure organizations. Payroll context is sourced from PAY_ALL_PAYROLLS_F and PAY_ELEMENT_TYPES_F. Project and transaction data come from PA_PROJECTS_ALL and PA_TRANSACTION_INTERFACE_ALL.

Usage Notes

PSP_ENC_SUM_TRAN is typically invoked from Oracle Payroll costing and encumbrance concurrent programs rather than directly from forms. The payroll action ID passed into ENC_SUM_TRANS ties the package to a specific payroll run. The package is also referenced by two other packages in the ETRM metadata, indicating it is called programmatically within the payroll-to-GL encumbrance chain. Customizations should call the procedures in sequence (batch begin, summarization, insert, transfer to GL or GMS, tie-back, batch end) and honor the NOCOPY OUT parameters for error buffer, return code, and status. Because it is AUTHID CURRENT_USER, appropriate grants must be in place for the calling schema.