Recipe compliance for SAP S/4HANA — without the data maintenance.
SAP's native Compliance Check works — if your team is willing to maintain every constraint on every substance, for every market, forever. Prodeen plugs into your existing SAP recipes and runs the regulatory review for you. The verdict lands back on the Recipe page in SAP. No constraint tables. No custom BAdIs.
Why SAP's native compliance check keeps falling behind
SAP S/4HANA ships with a Compliance Check inside Recipe Development. The engine runs, but it has no built-in regulatory knowledge — it only checks what your team has had time to model. As the rate of regulatory change accelerates, the gap between what's loaded into SAP and what each market actually requires keeps widening.
Every constraint is yours to maintain
Allergens, diets, nutrients, GMOs, religious certificates — each has its own Fiori app and must be populated on every substance. Your team owns the substance master end-to-end, and SAP ships no regulatory content with it.
Every new rule is a development ticket
New regulations don't slot in through configuration. They require ABAP development, transports, and regression testing — handled by IT on whatever cycle they can manage, while regulatory affairs waits.
"Your system administrator can only define new rules by implementing Business Add-Ins (BAdIs)." — SAP Help PortalInherited values are silently skipped
The engine cannot resolve regulatory properties inherited through composition — a real blind spot for any recipe built from multi-tier substances. The check passes; the risk doesn't go away.
"Inherited characteristic values cannot be checked." — SAP Help PortalOne engine, one system, no outside intelligence
The compliance check is internal to PLM. There is no inbound API to receive an external verdict — so any regulatory intelligence sitting outside SAP has nowhere to land, and the gap stays open.
Regulatory affairs depends on IT for every change
The chain of dependency is long: regulatory reads the change, translates it into a constraint structure, raises a ticket, IT specs the BAdI, develops, tests, transports. Every step is a delay.
Compliance status drifts away from reality
The product passes the check in SAP. It may still be non-compliant in three markets the team hasn't had time to model. The audit surfaces the gap — usually after launch.
Bring the regulatory engine to your recipes — not the other way around.
Prodeen is a regulatory-intelligence platform built for food, beverage, cosmetics, and personal-care manufacturers. We maintain the substance properties, market rules, ingredient restrictions, and labelling thresholds across hundreds of jurisdictions — and we plug into SAP so the verdict lands exactly where your team already works.
What changes for your team
- The regulatory rulebook moves out of your SAP master data and into a platform Prodeen keeps current.
- New regulations are available as soon as Prodeen publishes them — no BAdI, no transport, no IT ticket.
- Recipes and specifications stay in SAP. Prodeen reads them via standard OData; nothing is duplicated.
- The verdict appears directly on the Recipe and Product Specification page — visible to the SAP users who already work there.
- Every verdict is timestamped and cited to the source regulation, article, and effective date.
- Per-market output: "Compliant in DE, blocked in FR for ingredient X, conditional in IT pending PCN."
What changes when the regulatory engine isn't your team's homework
Most of the hard work in product compliance isn't reading regulations — it's keeping a thousand small rules current across every market you sell into. Prodeen takes that work off the table.
Market coverage out of the box
Every check returns a per-jurisdiction verdict — not "compliant" or "not compliant" against whatever subset of markets you've had time to model.
Faster product approvals
Hours instead of weeks to confirm whether a new recipe is launchable in each market — because the regulatory intelligence is ready before the recipe is.
Audit-ready evidence
Every verdict carries a citation to the regulation, article, and effective date — the trail auditors look for, generated automatically.
Catch what the native check can't
Inherited characteristic values, multi-tier substance composition, market-specific nuances — all resolved by Prodeen, not silently skipped.
Clean core preserved
No Z-tables of regulatory constraints. No custom BAdIs. No modifications to standard SAP objects. The integration uses released APIs only.
One source of truth, one workflow
Your team continues to work in SAP. Prodeen is invisible to recipe developers — the verdict simply appears on the object page they already use.
Native SAP Compliance Check vs Prodeen + SAP
Prodeen doesn't replace SAP — it replaces the regulatory-content modelling work. Internal product-quality limits can stay in SAP's native check. The regulatory rules — where the maintenance burden is highest — move to Prodeen.
Regulatory content maintained by Prodeen
We keep the rulebook current across hundreds of jurisdictions. Your team focuses on decisions, not data entry.
New rules go live as soon as Prodeen publishes them
Zero customer work. Regulatory affairs is no longer gated by an IT release cycle.
Full-composition resolution
Prodeen walks the substance tree end to end. Nothing is silently skipped — the verdict reflects the real recipe.
Verdict on the Recipe page itself
A Key User custom field on the Recipe / Specification, plus the full cited report attached. Your team sees it where they already work.
Citation on every verdict
Regulation, article, effective date — every time. The audit trail your quality and regulatory teams need.
Days to first verdict, not months
Connect, point at recipes, get verdicts back the same week. The regulatory intelligence is already in place.
How the integration works
A thin server-to-server integration. Prodeen calls your SAP tenant on behalf of your organisation, using standard, released SAP APIs. No middleware mandate, no modifications to standard objects, no clean-core compromise. The full architecture is available on request — this is the summary.
Recipe created or updated
An SAP user creates or changes a recipe in Manage Recipes. SAP emits a CloudEvent (or Prodeen picks it up on the next change-tracking sweep).
Prodeen reads from SAP
Header, formula items, and substance composition pulled via released OData services. CAS, INCI, E-numbers and analytical composition flow into Prodeen.
Market-by-market review
Prodeen runs the recipe against the regulations active for each target market, returning a verdict per jurisdiction with cited source articles.
Verdict back in SAP
Status field on the Recipe / Specification object page; full report attached for audit. SAP users see the result where they already work.
What stays in SAP
- Recipes & specifications remain the source of truth.
- Prodeen reads via
API_RECIPE_HEADER_AND_FORMULAandAPI_SPECIFICATION_DOCUMENT_HDR_SRV. - Writeback via Key User custom field (
YY1_ProdeenComplianceStatus) plus an attached report viaAPI_CV_ATTACHMENT_SRV. - No Z-tables of regulatory constraints. No modifications to standard objects.
Authentication & connectivity
- OAuth 2.0 Client Credentials by default — Communication Arrangement scoped to the minimum services needed.
- mTLS / X.509 for customers with mature PKI — no shared secret.
- SAML Bearer available where end-user attribution is required.
- SAP Cloud Connector + BTP Destination for tenants that aren't internet-reachable.
Editions supported
- S/4HANA Cloud Public Edition — Communication Arrangements with the relevant
SAP_COM_*scenarios. - S/4HANA Private Edition (RISE-hosted) — same released services, activated by Basis.
- S/4HANA on-premise — same released services, plus Z-CDS / RAP options where richer data is needed.
Event-driven triggers
- SAP Cloud Application Event Hub — CloudEvents 1.0 webhook to Prodeen.
- SAP Event Mesh / Advanced Event Mesh — for Private Edition / on-premise via Enterprise Event Enablement.
- OData polling on
LastChangeDateTimeas a reliable reconciliation sweep, available everywhere. - SAP Integration Suite (CPI iFlow) supported where the customer already uses it as middleware.
Who this is for
The same integration delivers two different outcomes — depending on which side of the table you're on.
For Regulatory & Compliance leaders
- Stop maintaining the rulebook. Prodeen keeps regulatory content current — you focus on decisions, not data entry.
- Catch what SAP can't. Inherited values, late-breaking regulations, market-specific nuances — covered.
- Audit-ready evidence. Every verdict timestamped and cited to a primary source.
- Faster product approvals. Hours instead of weeks to confirm market launchability.
For SAP, IT & Digital Transformation leads
- Clean core. No ABAP, no Z-tables of regulatory constraints, no modifications.
- Released APIs only. The exact services SAP publishes — nothing exotic.
- Works in your edition. Cloud Public, Private Edition, on-premise — including SAP Cloud Connector deployments.
- Standard auth. OAuth 2.0 by default; mTLS, SAML Bearer, and Basic Auth all supported.
Frequently asked questions
The questions SAP architects, regulatory leads, and procurement teams ask in early conversations.
Do we have to abandon SAP's native compliance check?
No. Constraints that genuinely belong in your master data — internal product-quality limits, recipe-engineering rules — can stay in SAP's native engine. Prodeen takes over the regulatory rules, where the maintenance burden is highest. The two coexist on the same recipe.
What data leaves SAP?
Recipe header, formula items, and substance composition are read via released SAP OData APIs — the exact data your team already exposes through standard inbound services. No SAP master data is duplicated in Prodeen. The verdict and a cited report are written back to the Recipe or Product Specification.
Does it work with our S/4HANA edition?
Yes — for S/4HANA Cloud Public Edition, Private Edition (including RISE-hosted), and on-premise. The integration uses the same released OData services across all three, with edition-specific authentication and connectivity (OAuth, mTLS, SAP Cloud Connector). The full per-edition implementation guide is available on request.
Is this clean-core compatible?
Yes. We use released SAP APIs only and write the verdict via the Key User Custom Fields and Logic app (or, on Private Edition, an equivalent CDS view with a RAP service binding). No modifications to standard SAP objects, no Z-tables of regulatory content, no BAdI development.
How does Prodeen know when a recipe changes?
Three options, used together for reliability: (1) SAP Cloud Application Event Hub or SAP Event Mesh push CloudEvents to Prodeen when a recipe is created or updated; (2) SAP Integration Suite (CPI) as middleware where the customer already uses it; (3) an OData polling sweep on LastChangeDateTime as a reconciliation safety net. Most deployments combine an event-driven primary channel with a polling sweep.
How long does the integration take to stand up?
Days, not months. The standard pattern is: customer creates a Communication Arrangement and issues OAuth credentials → Prodeen connects and starts reading recipes → first verdict back in SAP within the same week. The bulk of "implementation time" in legacy compliance projects goes into modelling rules and substances — Prodeen brings that pre-built.
See it on your own SAP recipes
We'll connect to a sandbox tenant, point Prodeen at a handful of representative recipes, and show you the per-market verdict back in SAP — usually inside a week.
Get in touch →Talk to the integration team
For SAP architects evaluating the technical fit: we'll walk through the released APIs, the auth flow for your edition, and the writeback pattern your team prefers.
Talk to the team →