Search Results verify_changes

Overview

PSP_ENC_UPDATE_LINES is an Oracle Application Object Library package owned by the APPS schema within the Oracle E-Business Suite environment. It forms part of the payroll cost encumbrance processing infrastructure, supporting the flow of payroll information into the general ledger where commitment accounting is enabled. The package header carries a source version marker of 115.20 dated 2004/03/04, and its API classification in the ETRM metadata is OTHER, indicating that it is not published as a formally supported public API but rather serves as an internal processing engine invoked by higher-level payroll encumbrance concurrent programs.

Its central business function is to maintain and reconcile the encumbrance lines that Oracle Payroll generates in Oracle General Ledger. When payroll costing and encumbrance accounting are configured, estimated labor costs are reserved against budget as encumbrances prior to actual payment. The package carries out the incremental update of those encumbrance lines, validates that the changes posted are consistent with the underlying payroll run data, and performs the housekeeping necessary for a restartable (resubmittable) update process when errors interrupt the flow.

Key Procedures and Functions

• UPDATE_ENC_LINES — The primary entry point for the concurrent program of the same purpose. It drives the update of encumbrance lines for a given payroll, encumbrance line type, business group, and set of books, returning the standard concurrent manager error buffer and return code.
• VERIFY_CHANGES — Validates the changes applied to encumbrance lines during the update, scoped by payroll, business group, set of books, and encumbrance line type. The encumbrance line type parameter was added to address bug 2143723.
• MOVE_QKUPD_REC_TO_HIST — Moves qualifying processed records into a history structure, supporting the restartable update encumbrance process enhancement and returning a status indicator.
• CLEANUP_ON_SUCCESS — Removes transient working records once the update completes successfully, with awareness of an invalid suspense indicator and a return status.
• BACKTRACK — Documented as a function in the metadata, though it appears commented out in the package source in favor of enhanced restart logic. It was originally intended to determine whether a prior processing period could be revisited based on a time period and encumbrance line type.
• ROLLBACK_REJECTED_ASG — Handles rejected assignment groups, reversing changes associated with a rejected group identifier and restoring the corresponding accepted group, based on payroll, action type, GMS batch name, run, business group, and set of books.

The package also declares a global error path variable used to locate the failing API during error handling.

Tables Accessed

The ETRM metadata for this package does not enumerate the specific underlying tables or APPS synonyms referenced. Functionally, the package operates across the payroll encumbrance working and history tables that store qualifying update records, rejected assignment groups, and suspense entries produced by the payroll-to-general-ledger encumbrance flow. All access is performed through APPS synonyms under AUTHID CURRENT_USER, meaning execution privileges and object resolution are evaluated against the calling user rather than the package owner.

Usage Notes

PSP_ENC_UPDATE_LINES is not referenced by any other documented package in the ETRM repository, confirming its position as an execution-level component invoked directly by the Oracle Payroll concurrent program for updating encumbrances rather than as a library consumed by custom code. In Oracle EBS 12.1.1 and 12.2.2, it is invoked when the Update Encumbrance process is submitted from the Payroll or Costing responsibility, or restarted following an interruption. Because it is classified as OTHER and is not a published API, customizations should not call its procedures directly; integrations requiring encumbrance creation or adjustment should use the supported payroll costing and general ledger interfaces. The presence of the cleanup, history-move, and rollback procedures reflects the designed restartability of the process, allowing a failed run to be corrected and resubmitted without manual data remediation.