Results for “document_not_found”

2 results




AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

EDR_PSIG is the core PL/SQL package body of the Oracle E-Business Suite Electronic Records and Signature (ERES) framework, delivered under the APPS schema. Its primary business function is to manage the lifecycle of electronic records ("e-records") and the electronic signatures applied to them, satisfying regulatory requirements such as FDA 21 CFR Part 11, EU Annex 11, and similar good-practice mandates. The package creates, opens, updates, and closes signature-controlled documents; it records signature intents and results; it captures document-level and signature-level parameters; and it produces the printable output associated with signed records.

The package is classified as OTHER (not a public open interface), reflecting its role as an internal engine invoked by other EBS modules rather than a documented integration API. It is referenced by twelve other packages and therefore sits deep in the dependency tree of the EDR product family. The package header carries the version marker $Header: EDRPSIGB.pls 120.4 2011/03/31, indicating sustained maintenance through several bug fixes, including corrections for timezone validation and child e-record counting.

Key Procedures and Functions

The package exposes twenty-eight documented procedures and functions. Their responsibilities group as follows:

VERIFY_TIMEZONE compares the database server timezone from FND_TIMEZONES.GET_SERVER_TIMEZONE_CODE against the profile option EDR_SERVER_TIMEZONE, raising EDR_PSIG_TIMEZONE_ERROR when they diverge or when either value is null.

Tables Accessed

The package reads and writes the following APPS synonyms:

Usage Notes

EDR_PSIG is normally invoked indirectly. EBS forms and OA framework pages that present signature-controlled transactions call these procedures to open a document before data entry and to close it after commit; concurrent programs invoke it to finalize, print, or archive signed records. Custom code should call the package through the documented procedure names rather than querying the underlying tables, because the procedures enforce timezone validation, status transitions, and audit shadow-table writes that maintain regulatory compliance. Because the package is not a public API, customers should validate inter-version behavior between 12.1.1 and 12.2.2, where profile and message definitions (EDR_SERVER_TIMEZONE, EDR_PSIG_TIMEZONE_ERROR) must be present for VERIFY_TIMEZONE to succeed.