Search Results edr_erecords_s

Overview

EDR_PSIG_RULE is a core PL/SQL package body in the Oracle E-Business Suite EDR (Electronic Records / Electronic Signature) module, deployed in the APPS schema and valid on both 12.1.1 and 12.2.2. Its business purpose is to evaluate and enforce the signing and signature rules that govern electronic records. In regulated environments subject to 21 CFR Part 11 and similar mandates, the package determines whether a given electronic record requires one or more electronic signatures, which signatories are eligible, and under what routing or approval conditions those signatures must be captured. It therefore acts as the rule-evaluation engine sitting between the EDR record model and the Oracle Approvals Management (AME) and Workflow engines, translating configured signature policies into runtime decisions that drive the e-signature lifecycle for records such as change orders, quality records, and other controlled documents.

Key Procedures and Functions

The documented interface exposes a single program unit, PSIG_RULE. Consistent with its name and with the package's dependency on AME_ENGINE, AME_CALLING_APPS and AME_UTIL, PSIG_RULE is the entry point that resolves the applicable signature rule for an electronic record and determines the required approval or signature flow. It evaluates the record context against configured AME transaction and rule definitions, and returns or applies the resulting signature requirement so that the EDR signing layer can enforce it. The procedure operates as the glue between EDR's own rule storage (EDR_PSIG_RULE) and the AME rule engine, invoking the engine on behalf of the calling application and handling the outcome within the EDR signing process. No further program units are documented for this package body.

Tables Accessed

The package references a broad set of objects, all via APPS synonyms. EDR-record tables form the transactional core: EDR_ERECORDS and its sequence EDR_ERECORDS_S hold electronic records, while EDR_ERECORD_ID_TEMP supplies record identifiers during processing. Signature data is read from or written to EDR_ESIGNATURES and EDR_ESIGNATURES_S. EDR_REDLINE_TRANS_DATA supports redline/change tracking associated with signed content, and EDR_FINAL_XML_GT is used in the generation or validation of the final XML representation of records. Workflow-related tables — WF_EVENTS, WF_EVENT_SUBSCRIPTIONS, and WF_PARAMETER_LIST_T — plus WF_EVENT_T are used for event publication and parameter passing. AME_CALLING_APPS registers the calling application context with the AME engine. Additional lookups against FND_APPLICATION resolve application metadata, and DBMS_LOB and DUAL appear in standard utility operations.

Usage Notes

EDR_PSIG_RULE is not referenced by any other database object, indicating that it is invoked at runtime rather than compiled into dependent packages. It is typically called from the EDR electronic records and e-signature UI flows, from EDR workflow or event subscription handlers (as suggested by the WF_* dependencies), and from related EDR packages such as EDR_PSIG, EDR_ESIGNATURES and EDR_ERES_EVENT_PVT. Signature rule evaluation occurs whenever a record transitions to a state requiring signature — for example, on submission for approval, on signature capture, or on a Workflow business event that fires an EDR subscription. Custom code extending EDR should call this package only through its documented PSIG_RULE entry point rather than referencing internal logic, and should rely on the AME engine being correctly configured with the EDR transaction type and its rule definitions. Administrators modifying signature policies should validate them against this package's evaluation path, since misconfigured AME rules will surface here as failed or incomplete signature requirement resolution.