Extended ECM for SAP: what OpenText's recent support alerts ask you to check
OpenText's recent Extended ECM alerts cover CVE-2025-8716, a purge data-loss risk and a delivery change. Each fix depends on version, so keep one register.
Helping future-focused leaders navigate what’s next:
OpenText VIM 25.4 pairs with SAP S/4HANA 2025 and drops BCC and ICC capture. Who does what in the upgrade, and the five answers to have ready before you call.
OpenText's recent Extended ECM alerts cover CVE-2025-8716, a purge data-loss risk and a delivery change. Each fix depends on version, so keep one register.
VIM 7.6 and 20.4 leave Current Maintenance on 31 Dec 2027, the same year SAP ECC mainstream ends. Choose 23.4 or 25.4 against your S/4HANA plan, not by habit.
Three OpenText for SAP 21.4 releases leave Current Maintenance on 1 Nov 2026. Start by confirming the release you run, then choose a target with a later date.
Germany phases in e-invoice sending from 2027. Core Capture for SAP 26.3 now checks X-Rechnung and ZUGFeRD files. Someone still decides what VIM does on a fail.
Before the first OpenText VIM invoice posts, name the ArchiveLink document types, the content repository, and who owns storage readiness on the cutover list.
OpenText VIM park reasons are the words finance reads when an invoice stalls. Decide who may add, retire or rewrite one, and when finance must sign the change.
Document type decides the screen, the SAP transaction and the process path in OpenText VIM. After go-live, someone still has to own how invoices get typed.
A duplicate-check hit in OpenText VIM is a control moment. Decide who clears it, what evidence they leave, and when a true duplicate may still post at all.
Practical AI in OpenText VIM needs a clear operating boundary: what the model may suggest versus what only a named human may change, post, or clear holds.
After OpenText xECM for SAP go-live, name who owns each business workspace: who may create, classify, and retain documents before process content drifts.
After go-live, OpenText VIM IDoc mapping is living work. Name who owns Level 1/2 mapping, the exits, and who clears Status 51 versus vendor-data issues.
Configure OpenText VIM Foundation in /OTX/PF00_IMG before Invoice Solution in /OPT/SPRO. Name who owns channels, profiles, and the PO/non-PO rules layer.
Before you activate OpenText VIM BC-Sets in SCPR20, compare them to your tables, back up what you have, and name who may activate process-affecting sets.
Supplier bank changes in OpenText VIM: name who may clear the hold, what evidence is required, dual control, and the vendor-master versus invoice path.
OpenText VIM reporting after go-live lies when email PDF, structured e-invoice, and EDI share one score. Separate channels before you trust the number.
OpenText VIM price and quantity tolerances are finance policy expressed in match—not a technical knob. Name finance before you tune any of those bands.
OpenText VIM business rules age after go-live. Name who may change a rule, who tests it, who signs it, and where the change log lives—before the next transport.
Go-live is not proof AP is fine. After OpenText VIM on S/4HANA, own the exception types you actually see by volume—then name an owner for each type you keep.
For SAP TM carrier invoices in OpenText VIM, name where VIM stops, where TM dispute starts, and who owns carrier exceptions when invoices land with AP.