There Is No Undo Key in ERP: SAP's Seven Migration Agents, and a Language That Cannot Be Rolled Back

Today is Wednesday, November 18, 2026. On November 11, SAP made two statements on two occasions. Viewed separately, both are good news; viewed together, they make clear the difficulty of bringing agents into core systems.

The first sentence comes from the media open day of SAP China Research Institute. According to a November 17 report by IT Times, a simulated business scenario was demonstrated on site: the group controlling manager of a performance company opened his computer in the morning and received an alert—a competitor had canceled a performance because of the weather, and the market had suddenly opened up a slot. Before he had even worked it out, AI had already put forward three options: speed up hiring, find temporary employees, and redeploy internal staff from other cities, with cost, efficiency, and potential risks listed item by item. Cai Yanbin, SAP Global Vice President and President of SAP China Research Institute, put it this way: "AI has already moved from an auxiliary tool to truly entering the core operations of enterprises."

The second sentence comes from an interview with Sonja Liénard published by SAP News Center on the same day. As head of the SAP ABAP platform, she spoke about another side: once changes to ABAP are submitted, they take effect immediately in the running system; when something goes wrong, the usual approach is to “change it again” rather than “undo it.” Therefore, agents need isolated test environments and strict quality checks. She also mentioned that SAP is looking at agents that can manage and operate systems, but such agents should only assist people and should not operate in systems on their own.

On one hand, AI gives three business plans in seconds; on the other, "changes will not be undone." This is not a contradiction but a dividing line: A plan can be a draft, but writing cannot be a draft.

1. Two sentences from the same day, drawing a line

Putting these two scenarios side by side, you will find that they fall into two completely different types of actions.

DimensionInstructions
Decision-making actionsRead data, work out plans, rank priorities, draft recommendations. If wrong, recalculate once; the cost is a few minutes of compute, and a rejected proposal.
Write-type actionsChange code, change configuration, post entries, ship goods, issue invoices. If something goes wrong, traces must be left; the cost is a reversing voucher, an audit note, and a round of reconciliation.

The scenario Cai Yanbin described essentially compresses "decision-type actions" into a few seconds. It has value, but it does not change a single document. The seven agent families described by Liénard are essentially performing "write-type actions"—what they need to touch is the part of the program that customers wrote themselves. According to SAP, these seven families cover analyzing systems, testing, and migrating customer-written programs during upgrades, and can also be used independently to check the quality of these programs.

So when judging whether an agent can be given free rein, one shouldn't first ask "is the model accurate?" but should first ask: in this system, when it gets something wrong, can it be cleanly rolled back.

II. What the seven families are moving is twenty years of “writing it themselves”

The five-character phrase 'customer-written programs' sounds light, but in reality it is the heaviest part of the entire migration. It includes custom programs beginning with Z, user exits (user exit), BAdI enhancements, custom reports, custom interfaces, and the decision logic written back then to rush go-live and bypass standard processes. They are not among SAP's standard deliverables, and no one knows better than the customers themselves why they exist.

SAP's own proposition is clean core: keep the core as close to standard as possible, place extensions outside the core, and read and write through supported interfaces. On paper, this proposition is very clear; when applied to twenty-year-old legacy systems, it turns into a series of multiple-choice questions: should this piece of logic be discarded, changed back to standard, or moved to the side.

And the schedule is fixed.

时间点What happenedPractical implications for businesses
2026-05-31Compatibility Packs expire for most customersThe two-step window of "first transfer technology, then change processes" has closed, and technology conversion and process reengineering are compressed into the same project.
2027-12-31ECC 6.0 mainstream maintenance ended (SAP February 2020 policy)No longer provide new regulatory changes; requirements such as tax, statutory reports, and electronic invoicing must be implemented on your own
From 2028-01-01Optional extended maintenance until the end of 2030Purchasing time at a premium of 2 percentage points on top of the maintenance fee does not solve the migration itself.
Year 2040SAP promises that at least one version of S/4HANA is under maintenanceThe target platform's long-term cycle is clear; only the choice of path is a variable.

How great the pressure is can be illustrated indirectly by third-party data: Gartner's judgment is that by the end of 2027, about 17,000 customers—nearly half of the ECC installed base—will still continue to run ECC (as relayed by consulting agencies); SAPinsider's 2026 benchmark survey shows that 35% of organizations plan to complete the switch by the end of 2026; and Horvath's survey is even more direct: among enterprises that have completed S/4HANA transformation, nearly 60% exceeded their original planned timeline. The commonly used migration duration ranges in the industry are: brownfield conversion 9 to 24 months, greenfield rebuild 18 to 36 months.

This is precisely where agents are expected to deliver. At its Sapphire conference in May 2026, SAP said that agent-led transformation tools could reduce ERP migration workload by more than 35%. But two things should be noted: this figure is the vendor's own claim, and no calculation methodology or sample was disclosed; and for the seven families mentioned in this interview, SAP did not provide release dates, pricing, or customer numbers, saying only that it would deliver more migration tools by the end of the year.

A press conference cannot be used as a schedule.

A tool family that has no release date, price, or customer count yet cannot get onto the critical path of a project plan. The only things a CIO can put into a plan are two: tools that can already be installed, and methods that can already be validated. Treating "the vendor says it can save 35%" as "my project can save 35%" is one of the most common types of budget illusions in migration projects.

III. Why "Undo" Does Not Work in ERP

Liénard's statement is worth reading word for word: ABAP changes take effect immediately in the running system, and errors are usually fixed with another change rather than by reverting.

Many people's first reaction is: Doesn't code have version control? Can't we just roll it back? In development systems, that's indeed possible. But the difference between ERP and ordinary software is that, code can be rolled back, but business documents cannot be deleted.

For an invoice that has already been posted, the way to handle it is not to “delete and reissue” it, but to issue a red-ink voucher to reverse it; for goods that have already been shipped, the way to handle them is not to “withdraw” them, but to process a return or adjustment. The reason is not that the system cannot do it, but a basic requirement of accounting and auditing: original vouchers must leave a trail, so that it is possible to trace back who changed what and when. This rule will not change just because the operator is an agent.

The most expensive mistake is often not the line of code that was changed incorrectly.

Rather, it was three adjustments made to get the accounts to reconcile: a reversing voucher, an audit note, and a round of discrepancy investigation. Rolling back the code takes only a few minutes, but these three things take several days, and they will come up again in next month's reconciliation.

So the answer to the question "Can an agent modify the core system?" does not lie in the model's accuracy, but in how much buffer this system has prepared for "irreversibility": whether there is an isolated environment isomorphic to production data that lets it make mistakes first; whether there is object-level authorization that lets it touch only the low-risk layer; whether there is a specific person who signs off before every write.

+2 percentage points

SAP's pricing approach for extended maintenance in 2028–2030 (a surcharge on top of the maintenance fee, February 2020 policy). An extension buys time, not answers

Conversely, this also explains why Liénard specifically adds a sentence: an agent capable of managing and operating the system should only assist humans, and should not operate within the system on its own. Operations actions may look “lighter” than business actions, but what they change is the environment on which all business actions depend to run. In such positions, “assistance” is not conservatism; it is the only reasonable design.

IV. CIO's Migration Agent Admission Checklist

Condense the above content into five gates. These five gates do not require waiting for new tools from vendors; they can be added to the project charter right now.

GateThe question to answerManifestations of Nonconformity
Isolated environmentIn which environment can the agent freely experiment and make mistakes? Is the data in that environment isomorphic to production but does not contain real sensitive data?“Debug it directly on the development machine” — the data isn’t isomorphic, so conclusions drawn from trial runs aren’t transferable
Object classificationWhich objects can be changed automatically (such as comments, formatting, unused reports), and which must be changed manually (posting logic, tax codes, approval workflows)?A one-size-fits-all “everything must be changed by agents,” or a one-size-fits-all “no use allowed at all”
SignatoryBefore every write, who signs off? Can the signer understand what this code change modified?The signer is written as 'IT department', or the signer only looks at the test report and not the change list
Shadow PeriodHow long will the old and new logic run in parallel? What are the comparison criteria for parallel running (number of documents, amount differences, exception list)?Only running the monthly close once before cutover; the differences cannot be explained.
Reversal ScriptIf after go-live we find that something was changed incorrectly, who does what in the first hour? How should reversal vouchers be issued, and how should the audit explanation be written?“We’ll see when the time comes” — this is the most common and most expensive answer

These gates apply equally on the open-source stack. Odoo 20 merges the original model-level ACLs and record rules into a unified access model, so any custom module that defines security rules must be redone; worksheets built in Studio also need to be migrated from Studio fields to property fields. In other words, the more custom code you have, the more upgrades depend on the order of “who has permission to change, what was changed, and whether it can be rolled back”, rather than on how smart the agent is.

Three actions for the CIO:

  • First, make a list of “irreversible actions.” List these six types of actions separately: posting, invoicing, shipping, price publication, tax-code changes, and permission adjustments, and stipulate that none of them may fall within an agent’s automatic execution scope; they may only enter the “draft—review—sign” chain. The list itself is more useful than any model evaluation.
  • Write the “change list” into the acceptance criteria. Every time the agent changes an object, it must produce a readable change description: which object was changed, what it was before and after the change, and which requirement it was based on. Acceptance looks at whether this list can be understood by a third party, not at how fast it made the changes.
  • Set aside budget for write-offs, not just for migration.In the project budget, list a separate line item for the cost and staffing of "three months of post-launch adjustments," and make clear who is responsible for it. Admitting that mistakes will happen is closer to engineering reality than promising that none will.

Let's return to those two sentences from November 11. The fact that AI produced three business plans within seconds is worth getting excited about, because it truly pushes the starting point of managers' thinking forward; and the sentence 'changes will not be undone' is worthy of awe, because it reminds us: what is truly scarce in enterprise systems is not generation capability, but the ability to keep the cost of errors under control.

The most moving scene in a demo is the AI laying out the plan before you have even finished calculating. The most moving scene in production is when, three years later, someone asks “why is this account like this?” and the system can answer it item by item. The former depends on the model; the latter depends on order.

Whether the seven agent families will ultimately deliver depends on whether they can be placed into this order. And order is not something vendors can deliver; it can only be established by enterprises themselves first.

Source: SAP News Center interview with Sonja Liénard (head of SAP ABAP platform), 2026-11-11; reported by ERP Leaders on 2026-11-12 16:09 (including statements such as "ABAP changes take effect immediately; errors are usually fixed by making another change rather than rolling back", "an isolated test environment and strict quality checks are needed", "agents that manage and operate systems should only assist people", "more migration tools to be delivered before year-end", and "the seven families have not been given release dates, prices, or customer numbers"). The simulated business scenario at the SAP China Research Institute media open day and Cai Yanbin's statements are from the IT Times report on 2026-11-17. The SAP ECC maintenance schedule and extended maintenance premium (2 percentage points on top of the maintenance fee), and the commitment to maintain S/4HANA until 2040, come from SAP's February 2020 maintenance policy; the compatibility pack expiry on 2026-05-31, the migration cycle ranges, the SAPinsider 2026 benchmark (35% plan to complete by the end of 2026), the Horvath survey (nearly 60% overdue), and Gartner's estimate of about 17,000 customers are all cited via third-party institution articles and are not official SAP statements.

Basis note: The statement by SAP Sapphire 2026 (May 2026) that "agent-led transformation tools can reduce migration effort by more than 35%" is a vendor claim; no calculation methodology or sample has been published, and it cannot be used directly as an estimate of project labor-hour savings; the scope of "customer-written programs" described in this article (Z programs, user exits, BAdIs, custom reports and interfaces) is a summary based on implementation experience, not an official SAP classification; the comparison of the five gates with the Odoo 20 permission model and Studio field migration is an implementation perspective; for specific upgrade target versions and support status, please refer to official releases.

关于我们

​我们致力于帮助中小企业实现数字化转型,我们的团队由一群充满激情和创新思维的专业人士组成,他们具备丰富的行业经验和技术专长。

扫一扫获取顾问以及手册

Sign in to leave a comment
Thirty-four minutes to replace an ERP system—why does your project take three months?