Search Results open_document

Overview

APPS.EDR_EVIDENCESTORE_PUB is the public PL/SQL interface for the Oracle E-Business Suite Evidence Store, a component of the Oracle E-Records (EDR) product. Its role is to create, populate, sign, and retrieve electronic records — referred to as evidence documents — that capture the transactional proof required by regulatory regimes such as 21 CFR Part 11, Sarbanes-Oxley, and similar compliance frameworks. The package header carries the version marker $Header: EDRPEVRS.pls 120.0.12000000.1 2007/01/18 and is annotated in the ETRM repository as scope public, product EDR, lifecycle active, category BUSINESS_ENTITY EDR_EVIDENCE_STORE, with a display name of "E-records Evidence Store APIs." Its reference documentation is Oracle Metalink note 268669.1, the Oracle E-Records API User's Guide. Any application or custom code that must place a signable, auditable document into the E-Records evidence store does so through this single, supported entry point.

Key Procedures and Functions

The package exposes twelve documented procedures, organized around the lifecycle of an evidence document:

• OPEN_DOCUMENT — creates a document instance for signature, allowing signatures to be associated before the document is closed.
• CHANGE_DOCUMENTSTATUS — updates the status of an existing document, moving it along its controlled lifecycle.
• UPDATE_DOCUMENT — modifies document content or attributes after creation.
• POST_DOCUMENTPARAMETERS — writes parameter values associated with a document, supplying the structured metadata that accompanies the e-record.
• CLOSE_DOCUMENT — finalizes a document instance, closing it for further modification before or after signature.
• CANCEL_DOCUMENT — cancels a document that will not complete its normal lifecycle.
• REQUEST_SIGNATURE — initiates the signature workflow, driving the request to the designated signer.
• POST_SIGNATURE — records signature data returned by the signing process against the document.
• POST_SIGNATUREPARAMETERS — stores parameter values that qualify a captured signature.
• GET_DOCUMENTDETAILS — retrieves the details of a stored document instance.
• GET_SIGNATUREDETAILS — retrieves the details of signatures captured against a document.
• CAPTURE_SIGNATURE — captures signature information into the evidence store.

The header also declares two public collection types, Params_tbl_type and Signature_tbl_type, used to pass parameter and signature data as PL/SQL tables indexed by BINARY_INTEGER. Each API follows the standard EBS PL/SQL convention, carrying an API version argument together with the return status and message count/data out parameters.

Tables Accessed

The package operates against two core E-Records tables, accessed through APPS synonyms:

• EDR_PSIG_DOCUMENTS — the master table of evidence document instances. It is written by OPEN_DOCUMENT, UPDATE_DOCUMENT, CHANGE_DOCUMENTSTATUS, CLOSE_DOCUMENT, and CANCEL_DOCUMENT, and read by GET_DOCUMENTDETAILS.
• EDR_PSIG_DETAILS — the detail table holding individual signature and parameter records. It is written by POST_SIGNATURE, POST_SIGNATUREPARAMETERS, POST_DOCUMENTPARAMETERS, and CAPTURE_SIGNATURE, and read by GET_SIGNATUREDETAILS.
• PLITBLM — the standard EBS PL/SQL table-to-index utility used for bulk binding of rows.

Usage Notes

EDR_EVIDENCESTORE_PUB is invoked by Oracle application modules and by customer extensions whenever a business event must generate a compliant e-record. E-Records-enabled flows in Order Management, Purchasing, Payables, and similar products call these APIs to open a document when a transaction is initiated, post the relevant parameters, request and capture the signature, and close the document once the signing workflow completes. Because the package is classified PUB and is referenced by five other packages, it is the supported integration surface; custom code should call it rather than writing to EDR_PSIG_DOCUMENTS and EDR_PSIG_DETAILS directly, so that signature and audit semantics are preserved. The APIs are equally usable from forms-based logic, concurrent program PL/SQL, or external integration code, and callers must honor the standard EBS API conventions — passing the API version, checking x_return_status for FND_API.G_RET_STS_SUCCESS, and harvesting messages via FND_MSG_PUB when an error is returned.