GA · Shipped ECC & S/4HANA FDA 21 CFR Part 11

SAP ↔ DocuSign:
Sign POs in hours, not days.

When an SAP release strategy triggers, Forged fires a DocuSign envelope to the right signer. The signed response writes back to SAP — release code set, PO status updated, audit trail closed. No Basis ticket. No printed PDFs. No chasing approvers on Slack.

Get Fixed-Price Quote See how it works
$10K Standard · 3–4 week delivery · Source & runbook delivered
How it works

Seven steps. One release code.

The whole cycle is triggered by a standard SAP release strategy — no custom transaction, no user-facing portal. Your approvers get an email. SAP gets a signed release. That's it.

  1. SAP

    PO created

    Standard ME21N or batch. Release strategy evaluated by ABAP release group.

  2. Forged

    BAdI fires callback

    ZIF_FI_DS_CALLBACK resolves signer from ZTDS_SIGNER_MAP config.

  3. DocuSign

    Envelope sent

    Template populated with PO number, line items, vendor, total. Signer notified by email.

  4. Signer

    Approver signs

    One click from email. Mobile-friendly. Part 11-compliant signature captured.

  5. DocuSign

    Webhook fired

    Connect event hits /sap/bc/docusign_cb — the ICF endpoint Forged registers.

  6. Forged

    Callback validated

    Signature verified, PO looked up, release code resolved from envelope metadata.

  7. SAP

    Release set

    PO status updated. Signed PDF attached as DMS doc. Audit trail closed.

Pricing

Two tiers. Both fixed price.

Standard ships the core flow above. Premium adds Forged Stream async middleware, release-strategy setup in SAP, a Goods Receipt safety block, a live monitoring dashboard, on-site training, and 30-day hypercare.

Standard

$10,000 one-time

Right for single release strategy, ≤ 50 POs/day, one DocuSign account.

  • 5-phase Forged deploy — discover → validate → deploy → verify → sync
  • Works with existing release strategies wired end-to-end
  • DocuSign template mapped to PO fields
  • Idempotent callback via ICF webhook + polling fallback
  • Hurl smoke tests in CI
  • Runbook + source delivered to your repo
  • Knowledge transfer session with your SAP team
Get Standard quote
Most common

Premium

$18,000 one-time

Right for multi-tier release groups, > 50 POs/day, or when you need guaranteed delivery and a live monitoring dashboard.

  • Everything in Standard, plus —
  • Forged Stream async middleware — guaranteed delivery, DLQs, event replay
  • Release strategy configuration — multi-level approval chains set up in SAP
  • Goods Receipt safety block — BAdI-enforced until PO is formally released
  • Real-time monitoring dashboard — pending signers, stale envelopes, alerts
  • 2-day on-site training — SAP team + business users
  • 30-day hypercare — priority response, config adjustments
Get Premium quote

Variable surcharges: SmartForm complexity (+$1K moderate, +$2.5K heavy custom layout) · PI/PO middleware routing (+$2K). Maximum stack: +$4.5K. Your exact number is fixed after forged discover — no surprises mid-project.

Compliance & security

Your audit team will actually like this.

Every step is logged to SAP's standard change document tables plus Forged's structured event log. Signed PDFs are attached to the PO as DMS documents. Nothing leaves SAP that didn't start there.

21 CFR Part 11

Validated signature capture, tamper-evident audit trail, and full signer identity binding. Evidence pack shipped with Premium.

SOX / J-SOX

Release strategy enforced by SAP itself — Forged doesn't bypass it, we orchestrate it. Segregation of duties preserved.

OAuth 2.0 JWT

DocuSign auth via JWT grant — no long-lived passwords. Keys rotated via standard Basis procedures.

On-premise SAP

No BTP, no cloud connector, no middleman. Forged CLI runs on your network; ABAP runs in your system.

Signed webhooks

DocuSign Connect HMAC verified in ABAP before any SAP write happens. Replay protection included.

Customer owns the code

Delivered to your Git repo. No license, no phone home, no vendor lock-in. Source in every tier.

Deploy demo

Watch it install.

From a fresh machine against a sandbox system — 47 seconds end-to-end.

forged — docusign deploy
FAQ

Answers, not sales language.

Does this work on ECC 6.0, or only S/4HANA?
Both. The ABAP packages ship with conditional logic for ECC 6.0 (EhP5+) and S/4HANA up through 2025 FAA. NPL 7.52 sandbox systems are supported for dev/QA. forged discover auto-detects your version during the first run.
Do we need SAP BTP or PI/PO?
No. Forged runs entirely on-premise — the CLI talks to your SAP system via the ADT REST API, and signed webhooks come back through a standard ICF endpoint. Forged Stream (Premium) is an optional async worker that runs in your cloud, not SAP's.
How does signer substitution work for out-of-office approvers?
Out of the box, SAP release strategies route to the approver assigned to the release code. For OOO coverage, most clients either update the signer mapping in ZFI_DS_SIGNERS before the approver leaves, or use DocuSign's built-in delegation feature. Date-bounded substitution logic with a dedicated ABAP table is not in Standard or Premium by default — it's a common add-on we can scope during discovery (typically half a day of work).
What happens if DocuSign is down when a PO is released?
Premium queues the envelope in Forged Stream with retry-safe delivery (exponential backoff, DLQ after 5 failures). Standard logs the failure to ZTDS_LOG and exposes it via forged log tail — your team can re-fire manually with one command.
What does the code handoff actually include?
Every Forged project ships: ABAP transport (.zip), ClientProfile.json, runbook.md (generated), Hurl smoke tests, deploy CLI config, and a docs/ directory with architecture diagrams. Delivered to your Git repo on day one of hypercare.
Is this GxP / 21 CFR Part 11 compliant?
DocuSign's Part 11 module provides the validated signature capture itself — that's on DocuSign regardless of which package you buy. Forged binds the signed artefact to the SAP change document trail on both tiers, so the PO's audit history reflects who signed and when. If you need a formal evidence pack (IQ/OQ scripts, audit-trail extracts, signer identity verification records), we scope that as a custom add-on — it's not bundled into Standard or Premium by default.
Can we see the source before we buy?
Standard and Premium customers own the source. For prospects, we do a live forged discover demo in the 30-minute intro call — you see the CLI, the generated ClientProfile, and a walkthrough of the ABAP strategy pattern. No NDA required.
What's not included?
Licensing for DocuSign itself (you bring your own account). SAP Basis transport ownership. Custom approval workflows beyond multi-level release (scoped separately). Training beyond the runbook walkthrough.

Ready to see forged discover on your system?

30-minute call. We'll run discover against your sandbox and walk through the ClientProfile it generates. If the mapping doesn't look right, the call is free.

Book a Demo Email Nate

Fixed price · 3–4 week delivery · Source code & runbook delivered