Search Results validated_complete_date

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

Overview

WF_DIG_SIGS is a table owned by the APPLSYS schema within Oracle E-Business Suite, listed under the FND – Application Object Library product. Its documented description identifies it as the "digital signatures table." In practice, WF_DIG_SIGS stores the outcomes of Oracle Workflow digital signature operations, recording the binding between a signed object, the certificate used to sign it, the resulting signature payload, and the lifecycle of request, signing, verification, and error handling. It therefore acts as an audit and persistence layer for electronic signature activity driven by Oracle Workflow signature policies.

The table carries a heuristic Data Vault classification of "standalone," mined from its foreign key structure. As a modeling suggestion, this implies WF_DIG_SIGS is neither a pure hub, link, nor satellite, but a self-contained transactional record whose relationships to certificates and security groups are captured through its own foreign keys rather than through dedicated link tables. The primary key is defined as WF_DIG_SIGS_PK on the SIG_ID column, and the documented physical schema in ETRM 12.2.2 shows 19 columns with two unique indexes (SYS_IL0000241120C00007$$ and SYS_IL0000241120C00008$$) associated with LOB segments.

Key Information Stored

The surrogate primary key is SIG_ID, which uniquely identifies each signature record. Among the most significant business columns are:

• CERT_ID — references WF_DIG_CERTS, identifying the digital certificate used.
• SECURITY_GROUP_ID — references FND_SECURITY_GROUPS, scoping the record by security group.
• SIG_POLICY — the digital signature policy governing the operation.
• SIG_FLAVOR — the signature flavor/type applied.
• SIG_OBJ_TYPE and SIG_OBJ_ID — the type and identifier of the signed object.
• PLAINTEXT — the source content that was signed.
• SIGNATURE — the resulting digital signature value; both PLAINTEXT and SIGNATURE are the large-object columns typically associated with the two documented unique LOB indexes.
• REQUESTED_SIGNER_TYPE and REQUESTED_SIGNER_ID — the signer requested for the operation.
• STATUS — the current state of the signature request.
• CREATION_DATE, SIGNED_DATE, VERIFIED_DATE, LAST_VALIDATION_ATTEMPT, and VALIDATED_COMPLETE_DATE — the audit timestamps tracking the request, signing, verification, and validation lifecycle.
• ERRBUF and ERRSTACK — error message and stack information captured when an operation fails.

Common Use Cases and Queries

Typical uses include auditing who signed what and when, verifying signature validity, and diagnosing signature-processing failures. A representative query joining the certificate and security group dimensions follows:

• SELECT s.SIG_ID, s.SIG_OBJ_TYPE, s.SIG_OBJ_ID, s.STATUS, s.SIGNED_DATE, c.CERT_ID FROM WF_DIG_SIGS s JOIN WF_DIG_CERTS c ON s.CERT_ID = c.CERT_ID WHERE s.STATUS = 'SIGNED';
• Filtering by SECURITY_GROUP_ID to isolate signatures within a specific operating scope.
• Reporting on ERRSTACK and ERRBUF for records where signing or verification failed.
• Audit extracts comparing CREATION_DATE against SIGNED_DATE and VALIDATED_COMPLETE_DATE to measure turnaround and validation status.

Related Objects

• WF_DIG_CERTS — referenced by WF_DIG_SIGS.CERT_ID; holds the certificate definitions used for signing.
• FND_SECURITY_GROUPS — referenced by WF_DIG_SIGS.SECURITY_GROUP_ID; defines the security group context of each record.
• WF_DIG_SIGS_PK — the primary key constraint on SIG_ID.
• APPLSYS.WF_DIG_SIGS — the fully qualified table referenced from custom SQL and views.

Because the metadata classifies the table as standalone, dependent objects are primarily these foreign key targets and the primary key constraint rather than a broader set of link tables.