Search Results psp_enc_line_types




Overview
Explore in AI Chat

Overview

PSP_ENC_UPDATE_LINES is an Oracle E-Business Suite 12.1.1 and 12.2.2 PL/SQL package body owned by the APPS schema and classified as OTHER within the ETRM repository. It belongs to the Payroll/Encumbrance processing family (PSP prefix) and supports the maintenance and reconciliation of encumbrance lines associated with payroll activity. The package operates against line types supplied by the caller through the p_enc_line_type parameter — the term that corresponds to the user search "psp_enc_line_types" — and is scoped by payroll, business group, and set of books identifiers.

The package header comment ($Header: PSPENUPB.pls 120.3 2006/02/22) indicates the body has been maintained across multiple bug fixes (references to bugs 2143723, 2259310, 3434626, 3684930, and 3953230 appear in the source). It declares a global g_request_id defaulted from fnd_global.conc_request_id, evidencing that the package is designed for concurrent program execution, and a g_liquidate_flag global introduced for liquidation handling. In the supplied excerpt many procedure bodies are stubbed with NULL, so the documented interface (procedure names and signature shape) is the authoritative reference.

Key Procedures and Functions

  • UPDATE_ENC_LINES — The primary driver procedure. It carries the standard concurrent program OUT parameters (errbuf, retcode) alongside payroll, encumbrance line type, business group, and set of books inputs, and performs the core encumbrance line update logic.
  • VERIFY_CHANGES — Validates the pending changes for a given payroll/line type/business group/set of books combination before they are committed. The p_enc_line_type parameter was added specifically for bug 2143723, confirming line type sensitivity in verification.
  • MOVE_QKUPD_REC_TO_HIST — Moves Quick Update staging records into the history table, retaining an audit trail of processed encumbrance line corrections. It returns a status through p_return_status.
  • CLEANUP_ON_SUCCESS — Removes transient data after a successful run, including handling of p_invalid_suspense records, so the staging area is left clean.
  • BACKTRACK — Documented in the ETRM metadata as a package procedure; it supports reversal/recovery of prior processing steps within the same payroll/line type context.
  • ROLLBACK_REJECTED_ASG — Rolls back assignments that were rejected during group processing. Its parameters include payroll, action type, GMS batch name, accepted/rejected group IDs, run ID, business group, and set of books, indicating integration with group (GMS) batch processing.

Tables Accessed

The excerpt explicitly references PSP_ENC_CONTROLS, which the package queries through the cursor c_unsummarized_lines to identify controls with action_code = 'N' for a given payroll. This table functions as the control/staging registry that governs which encumbrance lines require summarization or update. The ETRM metadata lists no additional tables referenced via APPS synonyms for this body. Given the procedure names (MOVE_QKUPD_REC_TO_HIST, CLEANUP_ON_SUCCESS), the package is expected to read and write Quick Update staging and history tables within the PSP encumbrance schema, but those specific names are not confirmed by the supplied metadata.

Usage Notes

Because g_request_id is initialized from fnd_global.conc_request_id and UPDATE_ENC_LINES exposes the standard errbuf/retcode concurrent program signature, the package is intended for invocation from an Oracle EBS concurrent program rather than interactively. Typical call paths include a concurrent program registered against UPDATE_ENC_LINES, with VERIFY_CHANGES, MOVE_QKUPD_REC_TO_HIST, and CLEANUP_ON_SUCCESS called in sequence within the same run to validate, archive, and clean up. ROLLBACK_REJECTED_ASG and BACKTRACK provide exception-handling paths invoked when group processing is rejected or a prior step must be reversed. Custom code should call the procedures in the order defined by the concurrent program and should not assume the stub bodies shown in the excerpt reflect runtime behavior; the ETRM metadata indicates 0 packages reference this package, so it is a top-level entry point rather than a shared utility.