Results for “signature_overriding_comments”

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

Overview

EDR_ESIGNATURES is the core transactional table within the EDR (E-Records) product module of Oracle E-Business Suite, responsible for storing electronic signature records captured against business events and transactions. In release 12.1.1 and 12.2.2, the table resides in the EDR schema and holds a status of VALID. Its role is to persist the evidence trail associated with Oracle eSignatures, allowing organizations to demonstrate regulatory compliance under frameworks such as 21 CFR Part 11, SOX, and internal change-control policies.

From a data-modeling perspective, the ETRM metadata heuristically classifies EDR_ESIGNATURES as satellite-leaning. This classification reflects the table's position as a detail-bearing structure that captures descriptive attributes and audit context around a signature event, rather than acting as a pure hub of distinct business keys or a link resolving many-to-many relationships. Modelers should treat the table as a provider of point-in-time descriptive state attached to signature and event entities.

Key Information Stored

The table contains 15 documented columns. The surrogate primary key is SIGNATURE_ID, which is also the sole business-key candidate, enforced by the unique index EDR_ESIGNATURES_U1. This column also carries a foreign key relationship to CZ_SIGNATURES, linking each e-signature record to its underlying signature configuration.

The remaining columns capture the identity, timing, and contextual detail of each signing action:

• EVENT_ID and EVENT_NAME — identify the business event or transaction against which the signature was applied.
• EVIDENCE_STORE_ID — references the evidence store that archives the signed record artifact.
• USER_NAME — the signer, foreign-keyed to FND_USER, providing the authenticated identity responsible for the signature.
• SIGNATURE_SEQUENCE and SIGNATURE_TYPE — define ordering and the category of signature applied (for example, approval, review, or witness).
• SIGNATURE_TIMESTAMP and SIGNATURE_TIMEZONE — establish the authoritative signing time and its timezone context.
• SIGNATURE_STATUS — the disposition of the signature (such as signed, rejected, or cancelled).
• SIGNATURE_REASON_CODE, SIGNER_COMMENTS, and SIGNATURE_OVERRIDING_COMMENTS — capture the justification, signer remarks, and any supervisory override narrative.
• ORIGINAL_RECIPIENT and ADHOC_STATUS — record the intended recipient and the state of ad hoc signing workflows.

Common Use Cases and Queries

Typical scenarios include audit reporting of who signed what and when, reconciliation of signature events against workflow approvals, and investigation of overrides or rejected signatures. A representative query joins the table to FND_USER to resolve signer detail:

• SELECT e.SIGNATURE_ID, e.EVENT_NAME, e.USER_NAME, e.SIGNATURE_TIMESTAMP, e.SIGNATURE_STATUS FROM EDR.EDR_ESIGNATURES e WHERE e.SIGNATURE_TIMESTAMP >= :p_from_date ORDER BY e.SIGNATURE_TIMESTAMP DESC;
• To enumerate all signatures on a given event: SELECT SIGNATURE_SEQUENCE, USER_NAME, SIGNATURE_TYPE, SIGNATURE_STATUS FROM EDR.EDR_ESIGNATURES WHERE EVENT_ID = :p_event_id ORDER BY SIGNATURE_SEQUENCE;
• To surface overrides for compliance review, filter on non-null SIGNATURE_OVERRIDING_COMMENTS or specific SIGNATURE_REASON_CODE values.

Because the table is satellite-leaning, reporting should join outward to hub and link structures (events, signatures, users) rather than treating this table alone as a complete dimensional source.

Related Objects

The following objects are most significant to EDR_ESIGNATURES based on documented foreign-key relationships and module context:

• FND_USER — joined via EDR_ESIGNATURES.USER_NAME = FND_USER.USER_NAME to resolve signer identity.
• CZ_SIGNATURES — joined via EDR_ESIGNATURES.SIGNATURE_ID = CZ_SIGNATURES.SIGNATURE_ID to obtain signature configuration metadata.
• EDR_ESIGNATURES_U1 — the unique index enforcing the SIGNATURE_ID business key.
• Evidence store and event-related EDR tables referenced through EVIDENCE_STORE_ID and EVENT_ID, which complete the signature evidence chain.
• Oracle eSignatures setup and API structures within the EDR module that consume these records for approval and audit processing.