Oracle
Send documents from Oracle business processes for signature and return the signed result.
Integrations
WQ3 with SAP
Connect SAP business processes to WQ3 signing workflows.
Typical workflows
Procurement documents.
Sales contracts.
Employee documents.
Related
API
A REST API to create documents, add signers, send for signature and download signed copies.
Discuss an SAP integration.
Integrations are scoped per agreement. Tell us about your environment.
How the integration works
A document is sent from SAP to WQ3, signers sign from a secure link, and the signed copy and each signer's status flow back to SAP automatically.
Send
Create a signing request from inside SAP through the WQ3 API.
Sign
Each party signs at the level set for them: electronic, remote or token.
Return
Real-time status updates, with the sealed file and completion certificate saved to the same record.
What we need from you
Your SAP version, the documents to connect, your current approval flow and a technical contact. Each integration is scoped by agreement with your team.
Define the boundary between approval and signing
Start by identifying when an SAP document is ready for signature, rather than simply ready for internal review. Specify which approvals must be complete, who confirms the signing parties, and which version represents the final agreement. This separates an internal business decision from the parties signing the document.
WQ3 locks documents once they are sent, so resolve edits before that handoff. Establish a procedure for content changes discovered after sending, including how a replacement document should be distinguished in the SAP record. Also agree what counts as completion for your team: receiving the signed result, for example, rather than merely sending the request.
Build a signing policy around participant roles
Translate your contracting policy into explicit signing requirements for each participant. Electronic signature can suit everyday agreements, while remote signing or token signing can be selected for formal or high-value contracts. WQ3 allows different levels for different signers within the same document, so participants need not share one requirement.
Treat identity verification as a separate decision from signature level. Where your policy requires proof of the account holder’s identity, the eKYC account-verification add-on can accompany any of the three levels. Review these choices with legal and business owners before implementation so that SAP-originated requests reflect the needs of the document and its participants.
Plan for a record that reviewers can understand
Define what a future reviewer will need to connect an SAP transaction with the document that was signed. Your integration plan should address the originating record reference, final signed copy, completion certificate and accompanying audit trail. The aim is to preserve context, not simply keep a file detached from its business transaction.
For review outside SAP, WQ3 provides a public verification page accessible through a QR code or reference without an account. Comparing the file’s SHA-256 fingerprint with the stored fingerprint reveals changes. Decide how reviewers should use that check alongside the signer names, signature levels and timestamps shown in the record.
Agree acceptance criteria before rollout
Use a representative document and its SAP record to build a practical acceptance checklist. Check that the intended version is sent, the correct participants receive the intended signing requirements, and the returned result is associated with the originating record. Review what users need to distinguish an outstanding request from a completed document.
Include data handling and internal review in that checklist rather than leaving them until implementation is finished. Consider which information is necessary for signing and who needs access to the resulting records. Any required handling of failures, reconciliation or resubmission should be documented in the agreed integration scope, not assumed to be available.
Start your first signing journey today.
Create your WQ3 account, or talk to us about your organization’s requirements.
Frequently asked questions
Does SAP approval replace a signature?+
Treat them as separate steps: define internal approvals independently from the signatures required from the document’s parties.
Is eKYC a fourth signing level?+
No. It is an account-verification add-on that can accompany electronic signature, remote signing or token signing.
Can a document be edited after sending?+
Documents are locked once sent. Agree a procedure for changes and replacement documents before rollout.
Can a reviewer verify a file without a WQ3 account?+
Yes. The public check page uses a QR code or reference to support verification without an account.
Does connecting SAP alone establish legal validity?+
No. Under Egyptian E-Signature Law No. 15 of 2004, legal validity depends on meeting the applicable conditions, not simply connecting systems.