Lleverage is an AI agent for production planning in SAP S/4HANA and ECC. It reads demand from the sales orders and planned orders SAP holds, replans your work centres when a supplier, a machine or a rush order moves the week, and writes the new dates back. Trade-offs between two customers go to your planner.
SAP MRP turns demand into planned orders, and a planner turns those into a week the plant can run. The agent does the part of that week that keeps changing, in 4 steps, and SAP stays the record throughout.
Sales orders, planned independent requirements from demand management and the stock and requirements list per material (MD04). Orders that our order agent creates in SAP count from the minute they exist.
The supplier mail that moves a steel delivery to Wednesday, the rush order a sales rep drops in Teams, the note that line 2 is down until noon. Most changes to a plan arrive there first, long before anyone keys them in.
Each job is placed on a work centre that can take it, with the routing’s operations, the changeover it causes and your minimum runs. Components on the bill of material are checked against stock and open purchase orders before a job is moved.
Planned orders and production orders get their new dates, so MRP and the shop floor work from the same week. A change that would move a date a customer already has waits for your planner, with both options written out.
The plan rebuilds itself whenever an order, a machine or a delivery moves, and the new dates land on the planned and production orders in SAP. The floor works from a schedule that is still true, and your planners spend their time on the calls only they can make.
Learn moreA rush order lands on a week that was already full. Nothing on the floor stops. This is what the agent does with the schedule.
Every constraint in the plan has a setting. A new date on a planned or production order that keeps every promise is written to SAP on its own, and any trade-off between two customers waits for your planner, written out.
SAP S/4HANA plans production with MRP Live, which creates planned orders, and with embedded PP/DS and the Capacity Scheduling Table app for finite scheduling. We read SAP Help Portal on 6 October 2026, and every statement in the middle column comes from those pages.
| SAP MRP Live and PP/DS | Lleverage | |
|---|---|---|
| What it produces | The planning run determines shortages and creates procurement proposals. Planned orders for in-house production are converted to production orders, one at a time, collectively or partially. | A week the plant can run: the planned and production orders SAP already has, on dates that hold, and moved again when a delivery, a machine or an order changes. |
| Capacity | PP/DS and the Capacity Scheduling Table app schedule finitely or infinitely. The app shows work centre load in red, yellow and green, and lets a planner switch production versions. | Capacities, changeovers and minimum runs are never broken to make room. A week that does not fit comes back with the conflict named. |
| Sequence and setup | PP/DS determines sequence-dependent setup times on single resources itself, reserves blocks for products with certain characteristics and propagates a change to the orders that follow. | Changeover rules come from your planners, set up with our engineers. For setup optimisation inside SAP, we think PP/DS is the stronger tool. |
| News from outside SAP | Not described on the vendor’s pages. | Reads the supplier’s mail, the message in Teams and the call note, and replans from them. |
| When something goes wrong | The planning run generates messages for critical parts and unusual situations so a planner can rework the results. PP/DS raises alerts in the Alert Monitor once an alert profile is set. | Changes that keep every promise are made on their own. A trade-off between two customers waits for your planner, with the options written out. |
| Who decides | Heuristics and optimisation in the planning run, or the planner on the detailed scheduling planning board and by drag and drop in the app. | You set how far it may move a job: within a shift, within a day, or never without asking. A promised date is only moved by a person. |
| What it needs first | Embedded PP/DS is part of S/4HANA from release 1709, with certain restrictions. Materials need the Advanced Planning flag in the material master and a production data structure. | The work centres, routings and bills of material in SAP, plus the rules in your planner’s head, turned into constraints with our engineers. |
| Version and price | The pages we read describe SAP S/4HANA. Licence terms are not described on them. | SAP S/4HANA and SAP ECC, on your own servers included. One monthly price per agent, with integration included. |
| Fits best when | Master data is complete, the plan changes inside SAP, and you want finite scheduling and setup optimisation in the ERP itself. | The plan breaks on news that arrives by mail and phone, and your planners spend the day keeping SAP in step with it. |
We think MRP Live and PP/DS are where a plan in SAP should be calculated, and if your changes start inside SAP they may be all you need. We think Lleverage fits when the week is broken by things SAP does not see yet: the late delivery, the rush order, the machine that stops. More on when MRP and ERP need to talk.
Forward deployed engineers build the first plan beside your planners and connect it to SAP, S/4HANA or ECC, so the replanning comes off the desk in the first weeks rather than at the end of a project. From there it automates gradually: every correction teaches it your work centres and your constraints, and fewer plans need a person to look.
They work inside your operation. They turn the rules in your planner’s head into constraints with your team, set the confidence line together, and stay on as lines and products change. Not a licence and a manual. A team that knows your floor.
The ERP and MES connections, the capacities, the changeover rules and the log are yours to configure. Our documentation and support sit behind your team, and an engineer is a call away whenever you want one.
Talk to us about either ↗In SAP S/4HANA, MRP turns sales orders and planned independent requirements into planned orders, which are converted to production orders on work centres. Embedded PP/DS adds finite scheduling and setup optimisation. The agent works on top of both: it keeps those orders on dates the plant can meet when the week changes.
No. MRP and PP/DS keep calculating requirements and schedules in SAP. We think the gain is in the hours around them: reading the late delivery, finding room for the rush order, and keying the new dates into planned and production orders. The agent does that work, and SAP stays the record.
Yes. Lleverage connects to SAP S/4HANA and to SAP ECC, in the cloud or on your own servers. Systems behind your firewall are reached without opening them to the internet, and the agent works with the access a planner has. Our engineers set up the connection with your SAP team. More on integrations.
Planned orders and production orders, and only within the limits you set: how far a job may move and which orders it may touch. Capacities, changeovers and minimum runs are never broken to make room. A date a customer already has is only moved by your planner, who sees both options written out.
The first process typically runs supervised within a few weeks. Forward deployed engineers build the first plan beside your planners, on your real lines and orders, and connect it to SAP. It moves to the background as the numbers earn it, for one monthly price per agent with integration included.
↗
Quote to orderQuote & SellQuotes drafted, orders entered and confirmed the moment they land.
↗
Purchase to paySource & ProcureInvoices, POs and confirmations, posted where they belong.
↗
Order to deliveryDeliver & SupportCustomers answered with full context, in their own channel.
↗
AP & ARPay & CollectInvoices matched, real variances flagged, the rest untouched.
↗
Master dataGovern & EnableMaster data kept clean and in sync across every system.
