Predictika · SAP · RISE with SAP S/4HANA Cloud private edition

An AI sales agent's quote, checked before it goes out

An AI sales agent prepares a RISE with SAP S/4HANA Cloud private edition subscription quote (in euros) for a fictional customer. Before it goes out, the agent sends it to Predictika’s validator, which checks it against the sizing, landscape, add-on and commercial rules, compares the net total the agent states with the one it computes, and returns a verdict with every reason.

Scope: RISE with SAP S/4HANA Cloud private edition subscription quotes. See everything this validator covers

This validator covers RISE with SAP S/4HANA Cloud private edition subscriptions: sizing, landscape, availability, add-ons, term and discounts. It handles any quote made of these editions, HANA tiers and add-ons, not just the scenarios shown below.

  • Sizing — Full user equivalents (FUE) built from advanced, core and self-service users, a 50 FUE minimum, per-tier FUE ceilings, and HANA memory against database size with a headroom review.
  • Landscape and compliance — Two-, three- and four-tier landscapes, with GxP-regulated pharma customers needing at least three tiers.
  • Availability and add-ons — Availability targets against edition and high availability, EWM only from Premium upward, Transportation Management with EWM, and Integration Suite credits.
  • Commercial terms — A 3 to 5 year term, the five-year-only FUE ramp, hosting limits by HANA tier, discount limits and approval by contract value, and a check that the net total the agent states matches the validator total.

It does not cover SAP's public cloud edition, on-premise S/4HANA licensing, other SAP product lines such as Ariba, SuccessFactors or Concur, real SAP list prices, or tax and multi-currency quoting.

The AI sales agentBuilds the quote from the conversation and says it is ready.
Predictika validatorChecks the quote against the product and contract rules and returns every finding it has.

7 scenarios in 3 groups · each group runs from the agent’s first attempt to the outcome · click one to switch

What the agent proposes

The AI sales agent says

Illustrative agent statement. The validator receives the structured request below.

Proposing agent: AI sales agent (scripted)

Before sending, the agent must call Recorded run

Predictika validator


      
Waiting for the call.

Where rules-based CPQ gets it wrong

Click to expand

Our assessment of what a typical rules-based CPQ (product rules, price rules and validation rules, as in Salesforce CPQ or Revenue Cloud) does with the same cases. It is a judgment about effort and reliability, not a claim that nothing can be built.

What the validator catchesTypical rules-based CPQPredictika
HANA tier against FUE and database sizeOnly with workarounds
Capacity per tier and a memory ratio spread across one rule per tier.
Both limits come from the tier catalog and are checked together.
Edition and add-on prerequisitesOnly with care
EWM by edition and Transportation Management only with EWM are separate dependency rules.
Each prerequisite is evaluated against the quote on every call.
Term, ramp and hostingOnly with care
The ramp is only valid on five years and some tiers are not on some hosts, so term and hosting rules interact.
Term, ramp and hosting are all evaluated together.
Discount authority by contract valueOnly with workarounds
Approval bands depend on a total that other rules compute.
The contract value, the limit and the approval band are all evaluated.
The total the agent statesOnly with workarounds
Comparing a stated total with a computed one means a separate rule per quote layout, and price rules rarely run on stated figures.
The stated net total is a field in the request and is checked against the computed total.
Every problem returned in one answerOnly with workarounds
Rules tend to fire as the quote is saved, so a rep often fixes one error and meets the next.
All findings come back together, whatever order the choices arrived in.

What this validator catches

Click to expand

Every rule is checked on every call, in whatever order the choices arrive, and one problem never hides another. Blocking findings stop the quote; approval findings need a person to sign off; everything else is computed.

RuleEffectWhat it checks
Minimum usersblockAt least 50 FUE for RISE with SAP private edition
HANA tier capacityblockFUE must fit the capacity of the chosen HANA tier
Database size vs memoryblockHANA memory must be at least 1.5 times the database size
Regulated-industry landscapeblockGxP-regulated pharma needs at least a three-tier landscape
Availability targetblockRequired availability must not exceed what the edition and high availability choice deliver
Edition and add-onblockAdvanced EWM needs RISE Premium or higher
Add-on prerequisiteblockTransportation Management is quoted together with EWM
Integration Suite creditsblockAt least EUR 20,000 of BTP credits per year
Ramp termblockA year-one FUE ramp is only offered on five-year terms
Contract termblock3 to 5 years
Hosting availabilityblockThe HANA 12 TB tier is not available on Google Cloud
Discount limitblockAbove the maximum for the contract value (10, 25 or 35 percent)
Stated net totalblockAgent-stated net total differs from the computed total by more than EUR 1
Sizing reviewneeds approvalDatabase above about 53 percent of HANA memory: sizing team must confirm growth
Discount approvalneeds approvalAbove 10 percent and within the limit: an approver must sign off

Scenarios and results

Click to expand

The recorded result of the validator for each scenario on this page: the request the AI agent sent, the verdict, and every finding, in the order they appear above.

1. HANA sizing: 600 FUE on HANA 256 GB

The agent's request. RISE Premium for 600 FUE on the HANA 256 GB tier, three-tier landscape on Azure, 3-year term. Net total EUR 3,906,000. Ready to send.

Verdict: Blocked.

  • HANA tier capacity. 600 FUE exceeds the 250 FUE the HANA 256 GB tier is sized for.
  • Database size vs memory. A 200 GB database needs at least 1.5 x that in memory; the HANA 256 GB tier has 256 GB.

2. HANA sizing: 600 FUE on HANA 1 TB

The agent's request. RISE Premium for 600 FUE on the HANA 1 TB tier, three-tier landscape on Azure, 3-year term. Net total EUR 4,986,000. Ready to send.

Verdict: Allowed.

3. Add-ons: Base edition with EWM

The agent's request. RISE Base for 80 FUE on the HANA 256 GB tier, two-tier landscape on AWS, 3-year term, with the EWM add-on and Integration Suite. Net total EUR 891,000. Ready to send.

Verdict: Blocked.

  • Edition and add-on. Advanced EWM is included from RISE Premium upward; RISE Base covers basic warehouse management only.
  • Integration Suite credits. Integration Suite needs at least EUR 20000 of BTP credits per year; 0 quoted.

4. Add-ons: Premium with credits

The agent's request. RISE Premium for 80 FUE on the HANA 512 GB tier, two-tier landscape on AWS, 3-year term, with the EWM add-on and Integration Suite with EUR 30,000 of BTP credits a year. Net total EUR 1,350,000. Ready to send.

Verdict: Allowed.

5. The total the agent states: Stated total above computed

The agent's request. RISE Base for 80 FUE on the HANA 256 GB tier, two-tier landscape on AWS, 3-year term, with a 5 percent discount. Net total EUR 742,995. Ready to send.

Verdict: Blocked.

  • Stated net total. The quoted net total of EUR 742995.0 does not match the EUR 675450.0 the validator computed.

6. The total the agent states: Stated total corrected

The agent's request. RISE Base for 80 FUE on the HANA 256 GB tier, two-tier landscape on AWS, 3-year term, with a 5 percent discount. Net total EUR 675,450. Ready to send.

Verdict: Allowed.

7. Review by a person: 600 FUE at 20 percent

The agent's request. RISE Premium for 600 FUE on the HANA 1 TB tier, three-tier landscape on Azure with high availability, the EWM and Transportation Management add-ons and Integration Suite, 5-year term with a year-one ramp, and a 20 percent discount. Net total EUR 7,162,000. Ready to send.

Verdict: Needs approval.

  • Discount approval. 20 percent discount is above the 10 percent an account executive can give; approvable up to 25 percent for this contract size.

Narration transcript

Click to expand

The text of the narrated walkthrough, step by step.

  1. Welcome to a demo of Predictika's Validator. An AI sales agent prepares a RISE with SAP S/4HANA Cloud private edition subscription quote (in euros) for a fictional customer. Before it goes out, the agent sends it to Predictika’s validator, which checks it against the sizing, landscape, add-on and commercial rules, compares the net total the agent states with the one it computes, and returns a verdict with every reason.
  2. I will start with the first request by the agent.
  3. The agent says. RISE Premium for 600 FUE on the HANA 256 GB tier, three-tier landscape on Azure, 3-year term. Net total EUR 3,906,000. The rest of the request is on screen.
  4. Before it goes out, the agent calls the validator.
  5. Blocked, with two findings, all in one answer. 600 FUE exceeds the 250 FUE the HANA 256 GB tier is sized for. A 200 GB database needs at least 1.5 x that in memory; the HANA 256 GB tier has 256 GB.
  6. The validator returned two blocking findings in one answer. A check that reads one field at a time would pass most of this; it shows only when the choices in the quote are checked against each other.
  7. What this shows: for HANA tier against FUE and database size, a rules-based CPQ can do this only with workarounds.
  8. Now the agent resubmits.
  9. The corrected request. It changes the HANA Tier to HANA 1 TB and the stated net as to 4986000.
  10. It calls the validator again.
  11. This time the validator clears it.
  12. The validator also returns the line-item quote, on screen.
  13. Both earlier findings are cleared, and the validator's total, EUR 4,986,000, matches the quote.
  14. Two problems caught in one call, fixed in one pass, and a clean quote. That is the value of Predictika's validator: catching mistakes before they reach the customer. Now you can try the other scenarios yourself.