Skip to content
Chee Hong Book a call

SAP ME/MII End of Life: A Readiness Checklist

By Chee Hong ·

If you run SAP Manufacturing Execution (SAP ME) or SAP Manufacturing Integration and Intelligence (SAP MII), you have probably heard some version of "MII is going away." The real story is less dramatic, but it still needs a plan. This checklist is how I would get a plant or a group of plants ready to make a decision, before anyone budgets a migration.

What SAP has actually said

Here is what SAP's own published sources say, and nothing more:

  • SAP ME 15.5 and SAP MII 15.5 are the latest releases, and SAP has said there are no plans for further releases. SAP's Enterprise Architecture articles on the SAP Community state this and point to SAP Digital Manufacturing as the platform for future innovation. [1][2]
  • SAP ME 15.5 and MII 15.5 reach the end of mainstream maintenance in 2027, with extended maintenance to 2030. This is the wording in those same SAP Community articles, which refer readers to SAP's Maintenance 2040 strategy and the Product Availability Matrix (PAM) for details. [1][2]
  • The platform underneath follows the same timeline. SAP aligned SAP NetWeaver 7.5 with SAP Business Suite 7: mainstream maintenance until the end of 2027, with optional extended maintenance until the end of 2030. [3][4]
  • Extended maintenance is not free. For SAP Business Suite 7 core applications, SAP's support portal describes extended maintenance from the beginning of 2028 to the end of 2030 at a premium of two percentage points on the maintenance basis. SAP said NetWeaver 7.5 extended maintenance would be offered at the same price and conditions. [4][3]
  • After maintenance ends, the release does not simply switch off. Under SAP's general maintenance strategy (SAP Note 52505), a release whose mainstream or extended maintenance has ended moves into customer-specific maintenance. In that phase SAP no longer adapts it to new requirements such as legal changes or new technologies. [5]
  • Java is a specific risk after 2030. In October 2026, SAP wrote that its support arrangements for Java used with SAP NetWeaver AS Java 7.5 are scheduled to end at the end of 2030, and that AS Java 7.5 and its add-ons fall into customer-specific maintenance from 2031 with no follow-on release. [6] SAP ME and SAP MII 15.5 run on SAP NetWeaver 7.5 Java, so read that article with your Basis team. [8]

Two cautions. First, check your exact dates in the PAM for your own release and contract; it needs an SAP login. SAP Note 2894103 covers the SAP MII maintenance terms and also needs a login. Second, "end of life" is shorthand. The accurate phrase is "end of mainstream maintenance," followed by optional extended maintenance and then customer-specific maintenance.

The readiness checklist

Use this as a working document. Each item should end with an owner and an answer, not just a tick.

1. Confirm your releases and dates

  • Record the exact SAP ME, SAP MII, SAP Plant Connectivity (PCo) and SAP NetWeaver releases and support package levels on every system: development, quality and production, per site.
  • Look up each one in the PAM and write down the dates that apply to you.
  • Ask your SAP account team or contract owner whether you have, or plan to buy, extended maintenance, and what it covers.
  • Note your database and operating system versions; SAP's 2030 guidance on third-party databases and Java may affect you. [6]

2. Inventory what you actually run

Most of the effort in any MES move is in the custom layer, not the standard screens.

  • SAP ME customizations: Activity Hooks, custom activities, POD (Production Operator Dashboard) configurations and plugins, custom data collection, and any modified standard behavior.
  • SAP MII content: BLS (Business Logic Services) transactions, queries, scheduled jobs, message services, and any MII-hosted web pages or dashboards.
  • Shop-floor connectivity: PCo agents, OPC servers, PLC and machine interfaces, label printers, scales and scanners.
  • ERP integration: how orders, materials, routings and confirmations flow between SAP ERP or SAP S/4HANA and SAP ME/MII (for example the SAP ME integration layer, IDocs, or web services).
  • Reports and downstream consumers: who reads MII data, and where it goes (historians, BI tools, quality systems, spreadsheets).
  • For each item: is it still used, who owns it, and what breaks if it stops?

3. Map processes, not screens

  • List the real production processes per site: order release, assembly, serialization, nonconformance, rework, genealogy, labeling, shipping.
  • Mark which steps are standard SAP ME behavior and which depend on custom code or MII logic.
  • Flag regulatory or customer-mandated requirements (traceability, electronic records, retention) that any replacement must meet.

4. Do a first fit/gap against the target options

SAP's stated go-forward option is SAP Digital Manufacturing, a cloud-based MES on SAP Business Technology Platform. [1][2] It is not the only possible SAP MII replacement, so be clear about which route you are assessing.

  • For each process and integration, classify it: covered by standard SAP Digital Manufacturing, needs configuration or extension, or a real gap.
  • Check whether cloud deployment is allowed for your plants. SAP's own guidance notes that SAP Digital Manufacturing may not suit every regulated environment and that it runs as software-as-a-service. [7]
  • Decide what needs to run close to the line if connectivity drops, and check edge options early. [7]
  • If you keep a non-SAP MES, focus the plan on its integration with SAP S/4HANA instead. [7]

5. Size the risk of waiting

  • Which systems would fall into customer-specific maintenance first, and what would that mean for security notes, legal changes and new interfaces?
  • What depends on Java or the operating system or database version, and when do those supports end? [6]
  • Is your ERP move to SAP S/4HANA on the same timeline? Sequencing the two together usually changes the plan.
  • Who on your team knows SAP ME/MII today, and what happens if they leave?

6. Build the roadmap

  • Choose a pilot site or line with representative but manageable complexity.
  • Sequence the work: pilot, then rollout waves, with decommissioning of each SAP ME/MII instance explicitly planned.
  • Decide which custom logic to retire, rebuild, or replace with standard functions.
  • Budget for data migration and genealogy history: decide what moves and what is archived read-only.
  • Set decision points with dates, working back from your own maintenance end dates rather than from the headlines.

Common traps

  • Treating it as a lift and shift. BLS transactions and Activity Hooks rarely map one to one. Expect redesign.
  • Inventorying only production. The test and quality systems often hold the forgotten interfaces.
  • Starting with the tool demo. Start with your processes and integrations; the demo will look good regardless.
  • Ignoring the people. Operators live in the POD every shift. Involve them before the pilot, not after.

Where I can help

I'm Chee Hong, an independent SAP ME/MII consultant based in Atlanta. I offer a fixed-fee, vendor-neutral SAP ME/MII to SAP Digital Manufacturing Readiness Assessment that works through this checklist with your team and ends with an inventory, a fit/gap, a risk list and a phased roadmap you can take to budget. If you'd like a second pair of eyes, book a 30-minute call.

Sources

  1. SAP Community, Enterprise Architecture knowledge base, "Solution Options for Manufacturing Engineering": https://community.sap.com/t5/enterprise-architecture-knowledge-base/solution-options-for-manufacturing-engineering/ta-p/13642091
  2. SAP Community, "Solution Options for Manufacturing Performance Management": https://community.sap.com/t5/enterprise-architecture-knowledge-base/solution-options-for-manufacturing-performance-management/ta-p/13646041
  3. SAP Community, "Maintenance strategy for SAP NetWeaver 7.5 fully aligned with SAP Business Suite 7": https://community.sap.com/t5/technology-blog-posts-by-sap/maintenance-strategy-for-sap-netweaver-7-5-fully-aligned-with-sap-business/ba-p/13456253 (also https://pages.community.sap.com/topics/abap/netweaver-maintenance-strategy)
  4. SAP Support Portal, "Maintenance 2040": https://support.sap.com/en/release-upgrade-maintenance/maintenance-information/maintenance-strategy/s4hana-business-suite7.html.html
  5. SAP Note 52505, "Support after end of mainstream maintenance or extended maintenance" (public copy hosted by SAP): https://assets.dm.ux.sap.com/eur-costofstandingstill/pdfs/sapnote-52505.pdf
  6. SAP News Center, "Planning Beyond 2030: What SAP Business Suite 7 and SAP NetWeaver Customers Using Third-Party Databases or Java Need to Know" (October 2026): https://news.sap.com/2026/10/beyond-2030-sap-business-suite-7-sap-netweaver-customers-third-party-databases-java/
  7. SAP Community, "Solution Options for Manufacturing Operations Management": https://community.sap.com/t5/enterprise-architecture-knowledge-base/solution-options-for-manufacturing-operations-management/ta-p/308677
  8. SAP Community Q&A, "SAP MII ends support, no new release?" (answers quoting SAP Note 2894103 and noting the SAP NetWeaver 7.5 dependency): https://community.sap.com/t5/enterprise-resource-planning-q-a/sap-mii-ends-support-no-new-release/qaq-p/12574700

Independent consultant; not affiliated with SAP SE. SAP, SAP ME, SAP MII, SAP NetWeaver, SAP S/4HANA, SAP Digital Manufacturing and other SAP product names are trademarks or registered trademarks of SAP SE in Germany and other countries.

Next step: see the SAP ME/MII to Digital Manufacturing Readiness Assessment.

Related services

Ready to talk it through?

Book a 30-minute call to scope your assessment