Search Results process_cancel




Overview
Explore in AI Chat

Overview

EDR_PSIG_MSCA_PAGE_FLOW is an Oracle E-Business Suite PL/SQL package owned by the APPS schema that supports the electronic signature and approvals infrastructure of Oracle E-Records (formerly Oracle EDR, the E-Business Suite E-Records/e-Signature module). Its specific role is to manage the page-flow behavior of the Multi-Signature Consolidated Approval (MSCA) user interface, driving the signature process for approvers through successive pages of an approval flow and persisting the resulting responses into the ERES (Electronic Records and Electronic Signatures) tables.

The package is declared AUTHID CURRENT_USER, meaning it executes with the privileges of the invoking user rather than the definer, which is typical for packages that participate in a shared, security-sensitive approval framework. The ETRM/12.2.2 registration classifies the package under the "OTHER" API classification, indicating it is not part of the public, supported PL/SQL API surface. Its header comment, referencing EDRVMPFS.pls (version 120.1.12000000.1, dated 2007), confirms it is an internal implementation unit rather than a customer-facing interface. The procedures it exposes are documented explicitly as private, and the source header states that the procedures process the signature responses of approvers in the MSCA page flow and update the ERES tables accordingly.

The package is referenced by zero other packages in the documented metadata, reinforcing that it sits at the leaf of the MSCA call chain — invoked by the MSCA page-flow UI layer rather than by other PL/SQL units.

Key Procedures and Functions

  • PROCESS_RESPONSE — the principal worker procedure. It processes a single approver's signature response, accepting the event identifier, e-record identifier, approver user name, action code and meaning, signing sequence, and three parallel signature-parameter collections (names, values, and display names). It returns an error code and error message through OUT parameters. It is documented as a private procedure.
  • PROCESS_CANCEL — handles the CANCEL response within the page flow, unwinding or recording the cancellation of an in-progress signature action. Also documented as private.
  • PROCESS_MSCA_BLOCKED_ACTIVITY — manages the case in which an approver attempts an activity that is blocked within the MSCA flow (for example, an action disallowed at the current stage of the multi-signature sequence).
  • PROCESS_DEFER — supports deferral of an approval/signature action, allowing an approver to postpone a response rather than sign or reject immediately.
  • CLOSE_DOCUMENT — the procedure matching the user's search term "close_document". It determines the terminal state of the MSCA flow once all required signatures, cancellations, deferrals, or blocked activities have been resolved, closing the associated e-record so that the approval cycle is finalized and the ERES tables reflect completion.

All five procedures are private to the package's intended MSCA page-flow caller; the metadata does not publish parameter signatures for the latter four beyond what the header excerpt documents for PROCESS_RESPONSE.

Tables Accessed

  • EDR_ESIGNATURES — the core ERES signature table. PROCESS_RESPONSE and CLOSE_DOCUMENT read and update rows here to record approver actions (sign, reject, cancel, defer) and the signature parameters captured at signing time, guaranteeing a non-repudiable audit trail.
  • PLITBLM — a temporary/global PL/SQL table used by the package, accessed through an APPS synonym. It serves as the in-session work area for assembling and holding signature parameter values and page-flow state during a single invocation, rather than as a persistent business table.

Usage Notes

The package is invoked from the MSCA approval page-flow UI in Oracle E-Business Suite 12.1.1 and 12.2.2, typically through the OAF/E-Records signature region rendered to approvers. It is not registered as a concurrent program and is not intended for direct customer invocation; because the documented procedures are private, custom code should not call EDR_PSIG_MSCA_PAGE_FLOW directly. Customers extending MSCA behavior should use the supported E-Records/e-signature APIs instead. The AUTHID CURRENT_USER clause requires that the invoking user's privileges cover the referenced ERES tables, so any custom wrapper must execute in a context where those grants are available. Because the package is referenced by no other package, its lifetime and state are confined to the active page-flow session.