SAP SuccessFactors and OpenText: Basic Auth ends 21 May 2027, plan the OAuth move
SAP deletes Basic Auth for SuccessFactors calls to OpenText on 21 May 2027. The OAuth switch is short; the release check and the certificate owner matter more.
Helping future-focused leaders navigate what’s next:
VIM 26.2 lets AP ask about invoices and the process in plain language. Before anyone asks how long invoices wait, agree what wait, exception and touchless mean.
Purview retention now reaches Planner tasks, and plans made from Teams meetings expire after 180 idle days. Decide which plans are records before either runs.
Spain’s e-invoicing clock started on 6 Oct 2026. Large companies receive structured invoices from 6 Oct 2027, and AP must report rejections and payment dates.
Retention policies can soon archive SharePoint files. They stay under retention and in eDiscovery, but drop out of Copilot. Choose the archive clock with care.
Need a consultancy for SAP and OpenText process automation? Seven questions to ask any partner, starting with the OpenText for SAP dates that end on 1 Nov 2026.
Sweden’s inquiry reports by 30 Nov 2027, a month before VIM 7.6 and 20.4 leave maintenance. ViDA cross-border starts 1 Jul 2030. One table for both calendars.
Power Platform admins can now limit which SharePoint sites Copilot Studio agents read, and post the rules where makers build. The site list is a records call.
At year-end the invoices that hurt are the ones still in OpenText VIM, not yet posted. Five decisions and owners to settle before the vendor period closes.
SAP deletes Basic Auth for SuccessFactors calls to OpenText on 21 May 2027. The OAuth switch is short; the release check and the certificate owner matter more.
Default sensitivity labels on SharePoint libraries used to skip older files. A Purview policy now labels them, ten sites at a time. Pick the order with care.
OpenText VIM 26.2 adds payment terms based on intelligent text matching. Before it goes live, decide whose terms win: the invoice, the PO or the vendor master.
Purview priority cleanup deletes content a retention policy or eDiscovery hold would keep. Name the approvers and get records sign-off before the first run.
A plain guide to what OpenText AppEnhancer is, where it sits in the portfolio, and the products it gets confused with, so the next AX upgrade starts right.
Each OpenText product in your SAP landscape runs on its own clock. Here are five questions, one per product, to settle before the S/4HANA migration plan locks.
Core Capture for SAP 26.2 adds GenAI extraction you can switch on without upgrading VIM 7.6 or 20.4. Measure a baseline first; keep it apart from the upgrade.
SharePoint keeps 500 versions per file by default. Changing that, or trimming old versions, is a records decision, and trimmed versions skip the recycle bin.
OpenText VIM handles order confirmations, delivery notes and remittance advices, not only invoices. They share Foundation with AP but belong to other owners.
Extended ECM meets an existing SAP system through four decisions: objects, declarations, the doors users open, and prebuilt scenarios. Take them in that order.
Teams retention policies that also covered Copilot prompts are becoming Teams-only. Decide if Copilot interactions are records, then build a policy for them.
InfoArchive, Core Archive, ADA: they all keep data for the long haul but answer different questions. A plain-language guide for SAP teams choosing an archive.