OpenText VIM versioning follows release numbers such as 7.6, 20.4, 23.4, 24.4, and 25.4. These versions are not only product labels. They indicate which SAP platform versions, add-ons, Fiori components, capture integrations, and support package levels are expected to work together.
A simple way to understand VIM versioning is:
| VIM generation | Typical SAP platform relationship | General meaning |
| VIM 7.6 | SAP ERP / ECC-oriented landscapes | Older generation, still relevant in legacy ERP environments |
| VIM 20.4 | Earlier SAP S/4HANA releases | Often used in S/4HANA 2020–2022 landscapes |
| VIM 23.4 | S/4HANA 2023 generation | Transitional release with more modern Fiori and Foundation capabilities |
| VIM 25.4 | S/4HANA 2025 generation | Target release for latest S/4HANA 2025 compatibility and newer functions |
This is the most important message for beginners: VIM versioning must be read together with the SAP S/4HANA version. You cannot safely decide the VIM target version without first confirming the SAP target version.
The first step in any VIM upgrade preparation is to confirm the target SAP S/4HANA release.
This is important because VIM is installed as an SAP system add-on, and each VIM version supports specific SAP S/4HANA releases. Therefore, the VIM target version should be decided based on the SAP target release, not independently.
For example, if the SAP system is being upgraded to SAP S/4HANA 2025, the corresponding VIM version must be 25.4, according to SAP Note 3654390: https://me.sap.com/notes/3654390.
If the SAP system remains on an older S/4HANA release, the latest VIM version may not be compatible.
The OCR and capture area can be confusing because OpenText product names have changed across generations.
Before upgrading, do not rely only on the name used by the customer.
| Topic | Component / Name | What it means | Upgrade attention point |
| BCC | BCC | Older Business Center Capture generation used in legacy ECC / VIM landscapes. | VIM 25.4 does not supported any BCC/ICC components anymore |
| IES (Information Extraction Services) | IC4S / C4S | On-premise Capture for SAP Solutions based on IES. IC4S and C4S refer to the same product line across naming changes. | Check Windows Server, IIS, .NET, learning data, capture profiles, and Validation Client compatibility. |
| Core Capture / CC4S | Cloud-based IES capture option | Check cloud readiness | |
| Supporting Plug-In | Capture Imaging Plug-In | Supporting imaging component for capture/rendering. |
Always check the installed product, version, deployment model, and compatibility with the target VIM Foundation version.
The Validation Client is used to review and correct OCR extraction results before documents continue in the VIM process.
For upgrade preparation, the key rule is simple: keep the Validation Client on the same release level as VIM Foundation and the OCR/Capture component.
As an alternative, customers can also use the Fiori Capture Validation Workplace for browser-based validation. This reduces dependency on local Windows client installation and aligns validation with the modern Fiori user experience.
In short: align the Validation Client version with VIM and Capture, or consider Fiori validation as the modern alternative.
OpenText Archive Center, or OTAC, is used to store invoice images and attachments.
VIM does not store the physical document itself; VIM manages the invoice process, while the archive repository stores the document content. The connection is usually handled through SAP ArchiveLink:
| Component | Role |
| VIM | Manages invoice metadata, workflow, business rules, approval, and posting. |
| OTAC / Archive Repository | Stores and retrieves invoice images and attachments. |
| SAP ArchiveLink | Links the SAP/VIM document record to the stored document image. |
For upgrade preparation, there is generally no direct version compatibility dependency between VIM and OTAC.
For VIM upgrade preparation, the key point is to identify which SAP add-ons are installed today and which add-ons are required for the target VIM version.
| Component | Example add-on name in VIM 25.4 | Role |
| VIM Foundation | OTVIMBAS | Base framework for inbound processing, capture integration, workflow, and Fiori foundation. |
| VIM Invoice Solution | OTVIMINV | Invoice-specific processing, including PO/non-PO invoices, business rules, approvals, exceptions, and posting. |
| VIM Fiori UI | OTVIMFUI | Provides Fiori apps and UI framework for VIM users. |
| Optional scenario add-ons | For example, Ariba or TM-related VIM add-ons | Supports additional integration scenarios such as Ariba CIG or Transportation Management. |
SAINT (SAP Transaction): VIM add-ons are usually installed or upgraded by the SAP Basis team using SAINT, the SAP Add-On Installation Tool.
Use below checklist as a VIM upgrade preparation framework:
Use this order as the upgrade readiness checklist:
- SAP S/4HANA target release
Which SAP S/4HANA version will be used? - VIM target version
Which VIM Foundation and VIM Invoice Solution version is required? - Capture / OCR model
Will capture stay on-premise, or move to cloud capture? What OCR solution version will be adopted? - Validation approach
Will users validate invoices in Windows Validation Client, Fiori Validation Workplace, or both? - Fiori deployment model
Will VIM Fiori apps be deployed on-premise or via SAP BTP? - Archive repository
Which archive repository and ArchiveLink setup will be used? - Language and country scope
Which languages and countries are in scope for AP users, approvers, and validators? - Integration scope
Which integrations must remain active, such as email, scan, IDoc, Ariba, TM, DRC, or custom APIs?
Good luck to have a smooth and successful OpenText VIM upgrade.
Read more of my article on VIM introduction: VIM Foundation & Invoice Solution Configuration Ov… – SAP Community
