A studio service
Campaign material planning workbench for SAP sponsor campaigns, expiry and supply risk on one screen.
SAP MRP and IBP are the planning engine. A contract manufacturer plans by sponsor campaign, with materials that expire, lots still in QC and suppliers that are the only qualified source. We build a planner workbench on top of SAP that shows demand by campaign and sponsor, nets only material that will still be in date and released in time, and flags which campaign a shortage would hit.

The facts behind this module
62%
“Of 163 drugs that went into shortage between 2013 and 2017, 62 percent went into shortage after supply disruptions occurred that were associated with manufacturing or product quality problems.”
21 CFR 211.184(c)
Records shall include “an individual inventory record of each component, drug product container, and closure and, for each component, a reconciliation of the use of each lot.”
21 CFR 211.82(b)
“Components, drug product containers, and closures shall be stored under quarantine until they have been tested or examined, whichever is appropriate, and released.”
Quoted from the sources linked. We add no estimates of our own.
What it looks like
Materials needed
38
Ready
31
In QC
4
Short
3
| Material | Required | Usable by date | Open order | Supplier risk | Status |
|---|---|---|---|---|---|
| Cell culture medium | 4,000 L | 2,500 L | 2,000 L due 9 Oct | Low | In QC |
| Filter capsule 0.2 µm | 60 pcs | 20 pcs | 40 pcs due 20 Oct | High | Short |
| Buffer salt | 120 kg | 300 kg | — | Low | Ready |
| Chromatography resin | 80 L | 80 L | — | High | Ready |
Interface concept with invented sample data, shown to illustrate the design. It is not a screenshot of a live system.
How it connects
SAP S/4HANA
- Batches, QM, EWM, planning
- Stays the system of record
- Core left standard, nothing changed inside
The app, in your tenancy
- SAP BTP, Azure or AWS, your region
- Audit trail, roles, single sign-on
- Read-only in a Pilot; write-back by agreement
People and plant systems
- Your teams, by role
- Sponsors, each to their own data
- MES, LIMS, QMS and logger platforms
SAP's clean-core rule, quoted: “Extensions must be developed using only released local or remote public SAP APIs, BAdIs, or ABAP RESTful application programming model business object (BO) extension points.” SAP PRESS, SAP S/4HANA Clean Core: Principles, Benefits, and Best Practices.
N° 01What SAP already covers
We start from SAP, not against it.
SAP MRP, MRP Live and IBP calculate requirements and offer machine-learning forecasting and Joule. This module adds the campaign-and-sponsor view and netting that accounts for expiry and release dates. This module is a side-by-side extension: it reads and writes SAP only through released APIs and leaves the core standard.
N° 02Where it helps
Four situations this module is built for.
01
Planning outside SAP
The campaign view, live from SAP, in place of a separate workbook.
02
Usable is not available
Netting only stock that is in date and expected to release before the batch.
03
Single-source surprises
Single-source and long-lead materials flagged with the campaigns they affect.
04
Which sponsor gets hurt?
Every shortage shown against the sponsor and campaign date.
N° 03What the module covers
Scope, in plain terms.
01
Campaign demand
Demand by sponsor campaign from the SAP schedule and recipes.
02
Expiry-aware netting
In-date, released and expected-release stock by date.
03
Risk view
Single-source, long-lead and short-dated materials.
04
Actions
Proposed changes sent to SAP as planned orders or purchase requisitions for a planner to confirm.
N° 04For each person in the decision
One page, six readers.
01
Supply chain lead
The scope above, three fixed-scope packages with prices, and a read-only Pilot you can run on one site before committing.
02
QA and validation
GAMP 5 Category 5 development documents, executed developer IQ/OQ evidence, Annex 11 and Part 11 controls in the GxP-ready package. You run and sign validation.
03
IT and your SAP team
Released SAP APIs only, no changes inside SAP, one least-privilege technical user, deployed in your own tenancy and region.
04
Sponsor-facing teams
Each sponsor sees only their own data, enforced in the data layer, with every access logged.
05
Procurement
Fixed scope and price per package, a written not-included list, and our vendor questionnaire answered in full on request.
06
Finance
The price shown is ours. SAP licences, including any SAP Digital Access for documents created in SAP, hosting and validation effort are yours and are listed as not included.
N° 05The Pilot, week by week
Eight to ten weeks, read-only from SAP.
01
Weeks 1–2: scope and access
Requirements workshop, the list of SAP APIs to be read, a technical user from your SAP team, and sample data agreed.
02
Weeks 3–5: build
The module built in your tenancy against your SAP test system, with a working demo every week.
03
Weeks 6–7: your data
Connected to the agreed SAP data, tested by your users, findings fixed.
04
Weeks 8–10: live on one site
Go-live for up to 25 users, a handover session, and a written decision paper for the Production package.
N° 06Your three options
Inside SAP, packaged, or beside SAP.
01
Customise inside SAP
Done by your SAP partner. SAP's clean-core rule limits extensions to released APIs and extension points, and each change follows your SAP change and validation process.
02
Buy a packaged product
A vendor's standard product and roadmap, with its own licence, validation package and integration to your SAP.
03
Build beside SAP (this page)
An app scoped to your process, in your tenancy, connected through released SAP APIs, with the source code and documentation handed to you.
N° 07AI assists
Where AI helps, and where a person decides.
Designed to the draft EU GMP Annex 22: predictive models are static, versioned and show their confidence; generative tools only draft for a person to confirm. No assist releases, rejects or ships a lot.
01
Real lead times
A static, versioned model learns each supplier's actual lead time from SAP history and shows it beside the master-data value, with confidence.
02
Shortage explanation
A draft plain-language explanation of why a campaign is at risk, for the planner to check.
N° 08Investment
Pilot, production, or GxP-ready.
Pilot
From $38,000
One site, read from SAP through released APIs, live in 8–10 weeks.
- Campaign demand and expiry-aware netting from SAP
- Supply-risk view
- Read-only connection to SAP S/4HANA (OData APIs and CDS views), no core changes
- Audit trail on every record, role-based access, SSO with your identity provider
- One site, up to 25 named users
- Not included: write-back to SAP, electronic signatures, validation documentation, SAP BTP licences
Production
From $64,000
Two-way with SAP and one more plant system, across sites.
- Everything in Pilot
- Proposals written back to SAP for planner confirmation
- LIMS release dates in the netting
- Two-way integration through SAP APIs or SAP Integration Suite, clean-core compliant
- Digital Access check with your SAP licence team before any write-back is switched on
- Up to three sites and 250 users
- 60 days of hypercare after go-live
- Not included: validation documentation, SAP or BTP licences (including any SAP Digital Access your contract requires for documents created in SAP), SAP-side configuration by your SAP partner
GxP-ready
From $96,000
Built and documented for GMP use.
- Everything in Production
- 21 CFR Part 11 / EU Annex 11 electronic signatures and record controls
- GAMP 5 Category 5 SDLC pack: URS trace matrix, FS/DS, code review records
- IQ/OQ scripts with executed developer evidence; change control for later releases
- Not included: validation execution and QA sign-off (your CSV team), hosting qualification, SAP licences
Before you buy
What you get
- An independent build that connects to SAP only through SAP's released APIs
- A read-only Pilot that creates nothing in SAP, so it carries no SAP licence exposure
- Delivery alongside your SAP partner and IT, who keep control of SAP itself
What we don’t do
- SAP licences, or SAP Digital Access for documents a two-way build creates in SAP
- Changes to your SAP configuration or custom code inside SAP
- SAP certification of the integration, unless you ask us to scope it in
DesignKompanie is an independent studio and is not affiliated with, endorsed by or a partner of SAP SE. SAP and SAP S/4HANA are trademarks of SAP SE.
N° 09Questions
The answers we give most often.
- Is this an MRP replacement?
- No. SAP MRP or IBP stays the planning engine and system of record. This is the campaign and sponsor view on top.
- How is it different from Joule in IBP?
- Joule assists inside IBP. This adds the contract-manufacturing view: campaigns, sponsors and release timing.
- Does it create orders automatically?
- It proposes; a planner confirms, and the order is created in SAP.
- Are you an SAP partner?
- No. We are an independent studio. We build beside SAP using its released APIs and work with your SAP partner, who stays responsible for SAP itself. If you need the integration certified by SAP, we scope that into the project.
N° 10Related
- Pharma supply chain apps for SAP S/4HANA
- Security, validation & your SAP partner
- Sponsor portal & client-owned material
- Cross-system batch genealogy
- Cold chain & excursion evidence
- Control tower across SAP, MES and LIMS
- GMP warehouse floor app for SAP
- Supplier CoA intake for SAP QM
- Sponsor quality notifications & approvals
- Tech transfer workspace
- AI assist layer
- Enterprise app development
Start your book
Planning the Campaign material planning for SAP build?
Tell us your sites, the systems you run and what has to change. You'll get a scoped plan and a fixed price within two business days.
