About This Architecture

SAP VIM with HEU and HILL architecture integrates vendor invoice processing across two S/4HANA instances using IES/IC4S OCR platform for document classification and OpenText Archive servers for content storage. Invoices flow from vendor email through SMTP, OCR processing, and document classification into separate content repositories—HEU for System 1 (S/4HANA 2021, VIM 20.4 SP5) and HILL for System 2 (S/4HANA 2023, VIM 23.4)—with ArchiveLink connectors routing documents to FI/AP posting. This dual-system design demonstrates how to scale invoice automation across heterogeneous SAP landscapes while maintaining separate archive repositories and VIM versions. Fork this diagram on Diagrams.so to customize OCR thresholds, add additional SAP systems, or integrate alternative archive backends. The architecture isolates each system's document lifecycle, reducing cross-system dependencies and enabling independent VIM upgrades.

People also ask

How do you set up SAP VIM across multiple S/4HANA systems with separate OCR processing and archive repositories?

This diagram shows a two-system SAP VIM deployment where vendor invoices enter via SMTP, undergo OCR classification through IES/IC4S platform, then route to separate HEU and HILL content repositories via ArchiveLink connectors. Each S/4HANA instance (2021 with VIM 20.4 SP5, 2023 with VIM 23.4) maintains independent FI/AP posting, enabling parallel invoice processing without direct cross-system dep