Who can help with an OpenText VIM 25.4 upgrade on SAP S/4HANA?
Four groups, and a VIM 25.4 upgrade on SAP S/4HANA needs all of them. OpenText owns the product, its compatibility statements and its support. Your SAP Basis team owns the S/4HANA release and installs the VIM add-ons. Your AP and capture owners decide what invoices actually do once the new release is in. And a partner who has done VIM work on S/4HANA holds the plan, the test set and the cutover together. McCloy Data is one of those partners: implementation, upgrade and support of OpenText VIM for SAP is what our VIM practice is built around. Here's how we'd split the job.
Start from the SAP release, not the VIM number. VIM 25.4 is the newest VIM for SAP Solutions release on OpenText's public lifecycle page, released in October 2025, with Current Maintenance running to 31 December 2030. An SAP product and topic expert, writing on SAP Community in May 2026, points to SAP Note 3654390 for the pairing: a system going to S/4HANA 2025 needs VIM 25.4, and an older S/4HANA release may not accept it. So the first question isn't for OpenText at all. It's for whoever owns the S/4HANA roadmap. We covered that pairing in August, and it still holds.
OpenText: product, compatibility, defects. Take OpenText the questions only the manufacturer can answer: the supported source releases and support package levels for your landscape, the 25.4 upgrade guide, and any open defect. Where you bought the product decides where you look. If it came through SAP as SAP Invoice Management by OpenText, SAP keeps a knowledge base article, 2648674, on where to download OpenText documentation, patches and support packages for the OpenText products it resells.
One distinction from OpenText's VIM partner deep dive in June is worth repeating, as an attending partner reported it. A support case is for system errors, software issues and missing or wrong documentation. How to set up users, design a process or configure a feature is a consulting request. Expect the second kind of question to land with your partner, not in a ticket queue.
SAP Basis: the add-on event. VIM is installed as SAP add-ons, and Basis usually installs or upgrades them with SAINT, SAP's add-on installation tool. That puts the VIM upgrade inside the S/4HANA release plan, with its own transports and its own downtime window. Basis also answers a question the same SAP Community checklist raises early: will the VIM Fiori apps run on premise or through SAP BTP?
Capture and AP: what the invoices do. Two capture facts decide a lot of scope. The SAP Community post says VIM 25.4 no longer supports any Business Center Capture or Invoice Capture Center components, and that the Validation Client should sit at the same release level as VIM Foundation and the capture component. If BCC or ICC still runs in production, your 25.4 upgrade contains a capture migration. The AP process owner then owns the regression set: the invoice types, countries, languages and integrations (email, scan, IDoc, Ariba, TM, DRC) that must still work on day one.
The partner: one plan instead of four. Each group can do its part well and the upgrade can still slip, because nobody owns the joins. The capture cutover has to fit the add-on window. AP's test cases have to follow Basis's transport sequence. An answer from OpenText has to reach the decision it changes. That joining work is what we take on. We confirm the supported path for your installed release against OpenText's upgrade guide rather than assume one, and we write it down before anyone books a weekend.
Have five answers ready before you call anyone:
Your current S/4HANA (or ECC) release and the target release, with a date.
The VIM release and support package in production, read from the system.
Your capture product and version, by its installed name.
Whether you hold VIM through SAP or directly from OpenText.
Who in AP signs off that invoices still post correctly after cutover.
With those on one page, the first meeting is about your upgrade instead of about finding out what you run.
