Search Results post_signature_error




Overview
Explore in AI Chat

Overview

The APPS.EDR_PSIG_MSCA_PAGE_FLOW package body is a component of the Oracle E-Business Suite electronic signature (E-Signature) infrastructure, delivered within the EDR (Electronic Document Research/eRecords) product family. Its overarching business function is to process and finalize signature-related page flow events during the electronic signature capture sequence. Within Oracle EBS, electronic signatures are required for regulatory compliance such as 21 CFR Part 11, and this package governs what happens when a signer submits, defers, cancels, or is blocked while signing a record. The package is classified as an OTHER API, meaning it is not a public, supported interface but an internal component invoked by the E-Signature framework itself. A notable implementation characteristic is that PROCESS_RESPONSE is declared with PRAGMA AUTONOMOUS_TRANSACTION, allowing signature status updates to be committed independently of the caller's transaction — an important design choice for ensuring signature evidence is preserved even if the surrounding transaction rolls back.

Key Procedures and Functions

  • PROCESS_RESPONSE — The central routine for processing a signer's response. It validates signature sequencing against EDR_ESIGNATURES, raising an out-of-sequence exception when the submitted sequence does not match the minimum pending sequence. It iterates over signature parameter name/value arrays, resolves the signer type code and meaning, and drives finalization of the signature action. Error handling is returned through output error code and message parameters, and internal exceptions include POST_SIGNATURE_ERROR, EDR_PSIG_DOC_ERR, and EDR_PSIG_OUT_OF_SEQUENCE.
  • PROCESS_CANCEL — Handles the cancellation path when a signer aborts the signing process, updating the corresponding signature records so that the signature is not left in a pending state.
  • PROCESS_MSCA_BLOCKED_ACTIVITY — The routine most relevant to the searched term. It manages the scenario in which an activity is blocked by the Multi-Signature/Certificate Authority (MSCA) flow, ensuring the workflow and signature status remain consistent when a signing action cannot proceed.
  • PROCESS_DEFER — Supports deferral of a signature, allowing a signer to postpone signing while the record remains within an acceptable signature state.
  • CLOSE_DOCUMENT — Finalizes the document once all required signatures have been captured, marking the signing cycle complete.

Tables Accessed

The package references two documented tables through APPS synonyms. EDR_ESIGNATURES is the primary evidence and state table, storing signature sequence, signature status (such as PENDING), signer identity, and related signature attributes; it is queried in PROCESS_RESPONSE to determine the next expected signer and is updated as signatures are processed, cancelled, or deferred. The reference to PLITBLM, an EBS-supplied PL/SQL table type used for multi-value parameter handling, indicates that the package passes collections of signature parameters between procedures, consistent with the FND_TABLE_OF_VARCHAR2_255 parameters and the internal EDR_PSIG.params_table structure used to hold parameter name/value pairs.

Usage Notes

This package is not intended for direct invocation by custom code, as indicated by its OTHER API classification and its zero inbound package references — it is driven by the E-Signature page flow and MSCA signer interface, typically reached through the EBS Forms-based signature capture screens and the associated workflow action history. The autonomous transaction in PROCESS_RESPONSE means signature outcomes commit immediately, so developers analysing transaction behaviour must account for this independent commit. Because no other package references it, changes to this object should be treated as internal to the EDR E-Signature framework. The presence of PROCESS_MSCA_BLOCKED_ACTIVITY confirms the package participates in MSCA-related blocking scenarios, and any investigation of blocked-activity errors should begin with the signature status rows in EDR_ESIGNATURES for the affected event.