Search Results capture_signature

Overview

PO_ERECORDS_PVT is an Oracle E-Business Suite private PL/SQL package owned by APPS that provides the backend interface between Oracle Purchasing and the eRecords (Electronic Records) product. Its purpose is to persist electronic signature evidence and acknowledgement data captured during procurement business transactions so that a tamper-evident record of who signed, approved, or acknowledged a document is retained in the eRecords evidence store. The package was originally introduced under the Oracle Procurement module header POXVEVRS.pls (version 115.1, dated 2003) and remains present in both 12.1.1 and 12.2.2 code lines.

Because it is declared AUTHID CURRENT_USER, it executes with the privileges of the calling schema rather than the definer, which is consistent with its role as a private (PVT) API intended to be called from inside Oracle Purchasing rather than directly by external clients.

Key Procedures and Functions

• CAPTURE_SIGNATURE — The principal entry point for storing signature details. It accepts the signature XML and the signed document along with their format, requester, event name and key, workflow notification identifier, and supporting parameter tables for both the document and the signature. It calls the APIs supplied by the eRecords product team to write the signature into the evidence store and returns the generated document identifier, signature identifier, and standard FND_API return status, message count, and message data.
• SEND_ACKN — Creates an acknowledgement against an existing eRecord in the evidence store, recording whether the underlying business transaction completed successfully. It accepts the eRecord identifier, the transaction status, an acknowledgement author and note, and an autonomous-commit flag defaulting to FND_API.G_FALSE, and returns the standard FND_API status triplet.
• ERECORDS_ENABLED — A control function used to determine whether the eRecords patch has been applied and the feature is active, allowing callers to skip signature and acknowledgement processing when eRecords is not installed.

Tables Accessed

The only table documented against this package through APPS synonyms is PLITBLM. In Oracle EBS this is the PL/SQL interface table used by the Applications Technology stack for bulk DML processing on partitioned or interface data, and here it supports the internal data handling performed while building the parameters and evidence payload before it is passed to the eRecords APIs. The actual signature and document content is not persisted directly by this package into Purchasing tables; it is handed to the external eRecords evidence store through the called APIs. Documented table usage is therefore deliberately narrow, and any dependency on additional Purchasing or workflow tables is not part of the published metadata.

Usage Notes

PO_ERECORDS_PVT is a private API and is referenced by three other packages, indicating that it is invoked indirectly by Oracle Purchasing workflow and approval logic rather than by end users. Typical invocation paths are the Purchasing document approval and signature flows, where a workflow notification identifier and event key are available to identify the transaction, and where the caller has already resolved the requester and user name. Note that ERECORDS_ENABLED should be checked before calling CAPTURE_SIGNATURE, since signature capture is meaningful only when the eRecords patch is applied.

Because parameter names and signatures are documented in the package specification, custom code that must integrate with eRecords-based signing should call the public Purchasing APIs that wrap this package rather than invoking PO_ERECORDS_PVT directly; direct calls risk breakage across 12.1.1 and 12.2.2 release levels and bypass the intended validation performed by the purchasing layer.