When a VIM problem spans SAP and OpenText: write the ticket both sides can use

On 2 November 2026 OpenText announced that it has achieved SAP Certified Gold for Integration with Enterprise Support. In OpenText's words, the certification validates that its support processes, case management and escalation procedures align with SAP Enterprise Support standards. SAP's report, as OpenText summarizes it, found that OpenText involved SAP when needed to speed up case processing and acted promptly on the escalations reviewed.

For an AP team running OpenText VIM inside SAP, that's good news about the second half of an incident. The first half is still yours: what the ticket says, and where it lands.

VIM problems rarely stay in one layer. An invoice that won't post can be a VIM workflow step, an SAP posting error, an authorization, a Fiori app, a capture result, or an ArchiveLink entry that was never written. The symptom AP reports is the same every time: the invoice is stuck. OpenText's fix note for several VIM Fiori defects (KB0874931, sign-in required; it lists VIM 7.6, 20.4 and 23.4 as affected releases) is a good example. Problems such as the Enter Cost Assignment app not refreshing, or an AP Workplace error on Submit and Open, look like SAP Fiori trouble to a user. The fix sits in VIM.

A certified escalation path helps when a case needs both vendors. It can't rescue a ticket that started in the wrong queue with no evidence.

Know your door. VIM reaches customers under two names: OpenText Vendor Invoice Management for SAP Solutions, and SAP Invoice Management by OpenText through SAP. We've written about what that naming means. Your contract decides where first-level support starts. Put it in the runbook with the support portal, the customer number and who holds the login. Finding that out during a period-end incident is the slow way.

What a usable VIM ticket carries. Most of it is on screen when the problem happens. Capture it before anyone retries:

  1. Release. VIM version and support package, the SAP release (ECC or which S/4HANA release), and the capture product and version if capture is involved.
  2. The document. VIM document ID (the DP number), the SAP document number if one exists, company code, and the user and time of the failing step.
  3. The step. Which app or transaction, which action, and the exact message text.
  4. Recent change. Transports, support packages or configuration changes since it last worked.
  5. Reach. One invoice, one vendor, one company code, or everything.
  6. Reproduction. Whether it happens in QA, and the steps.
  7. Your read. Which layer you think it is, and why. Say so if you're unsure. A wrong guess stated clearly beats no guess.

Two cases isn't a failure. Sometimes an issue genuinely needs a case with SAP and a case with OpenText. Then put each case number in the other, and name one person on your side who owns the incident until both close. The certification describes OpenText and SAP working together on escalations. Your cross-reference gives them a place to start.

Who does what on your side. AP describes business impact: how many invoices, which vendors, what's coming due. The VIM process owner or Basis gathers the technical evidence. One named incident owner talks to both vendors. That's three roles, and in a small team they may be two people. They shouldn't be zero.

Better support processes at the vendor make a good ticket move faster. They don't write it for you.

Where does your landscape stand?

Take the free Assessment. It's about 10 questions, and you get a one-pager with your estimated level of effort and suggested next steps.

McCloy Data

Thought leadership on OpenText, SAP, and practical content and finance automation - from the McCloy Data team.

https://www.mccloydata.com
Next
Next

Dataverse long-term retention is a one-way move: choose what goes in