Search Results erecords_enabled

Overview

APPS.PO_ERECORDS_PVT is a private PL/SQL package body in the Oracle E-Business Suite Procurement module that bridges Oracle Purchasing workflow notifications with the Oracle eRecords (electronic records and electronic signatures) framework. Its primary business function is to capture legally binding electronic signature evidence against documents and approvals processed through the purchasing workflow, and to communicate back to the eRecords product layer through acknowledgement handling. The package is classified as PVT (private) in ETRM, meaning its APIs are not intended for direct third-party invocation; they are consumed internally by Oracle-owned packages and workflow components. The header references $Header: POXVEVRB.pls, and the revision history dates the code to 2003, which is consistent with the period in which eSignature and eRecords functionality was introduced into the EBS workflow stack. In both 12.1.1 and 12.2.2 the package resides in the APPS schema and is delivered as part of the standard Purchasing code line; 12.2.2 does not materially change the package's role, though 12.2.x deployments frequently rely on Online Patching, so the package body may be recompiled during patching cycles and its editioning context is managed by ADOP.

Key Procedures and Functions

The ETRM metadata documents three procedures or functions in this package:

• CAPTURE_SIGNATURE — The principal entry point of the package. It calls the APIs supplied by the eRecords product team in order to persist signature details. Based on the documented inline comments, it accepts standard Apps API parameters (API version, message list initialisation, and commit flag), the source signature XML, document, and document format, requester and source platform indicators, an eSignature event name and event key, a workflow notification identifier, post-document and post-signature parameter tables, the signer's user name and original recipient, an overriding comment, the evidence store identifier, and the user response. It returns the standard Apps return status and message count/data, together with the generated document id and signature id.
• SEND_ACKN — Sends an acknowledgement, returning a confirmation or status indicator to the calling workflow or eRecords component after a signature capture operation has been attempted or completed.
• ERECORDS_ENABLED — A function that determines whether eRecords/eSignature processing is currently enabled for the calling context, allowing upstream workflow logic to bypass signature capture entirely when the feature has not been configured.

Tables Accessed

The ETRM metadata records a single referenced table via APPS synonyms: PLITBLM. PLITBLM is the standard Oracle Applications message table used by FND_MSG_PUB and the Apps API messaging framework. PO_ERECORDS_PVT uses it indirectly to accumulate and retrieve error and diagnostic messages generated when signature capture fails or when acknowledgement processing encounters exceptions. No purchasing transactional tables or eRecords evidence tables are directly declared as dependencies in the documented metadata, indicating that persistence of signature data is delegated to the eRecords product APIs invoked within CAPTURE_SIGNATURE rather than being performed by this package itself.

Usage Notes

PO_ERECORDS_PVT is invoked indirectly. In a typical configuration, an Oracle Purchasing workflow notification such as a document approval or a buyer response is routed through the eSignature-enabled notification path; when the responder signs, the Oracle Workflow eSignature activity calls into PO_ERECORDS_PVT.CAPTURE_SIGNATURE so the signature and its supporting evidence are handed to the eRecords APIs. SEND_ACKN is used to acknowledge the outcome back to the requesting component. ERECORDS_ENABLED is the gate that callers check before attempting any signature capture, which is why a search on "erecords_enabled" surfaces this package. Because the package is private, custom code should not call it directly; integrators should use the supported public eRecords APIs and let the standard workflow call this package internally. Three other packages reference it in this release.