Vistex migration → S/4HANA

01

What Vistex touches in your SAP

Vistex is not an isolated module: it consumes and produces data across seven SAP flows. Every link is bidirectional — and every one changes with S/4HANA.

Every arrow is a bidirectional exchange. What S/4HANA changes on each one is measured in the impact analysis.

The business partner changes shape

S/4HANA merges customers and vendors into a single partner object. Every Vistex agreement attached to a customer or a vendor must be re-linked — without losing one.

Pricing conditions change table

The storage structure of conditions evolves with S/4HANA. The Vistex programs that read or feed them are reviewed interface by interface.

The ledger changes grain

The S/4HANA universal journal changes how rebates and accruals are posted. BW extractions and FI/CO controls follow.

None of this is optional

An agreement not re-linked, a condition not taken over, an accrual out of step: each one shows directly on revenue. Hence the exhaustive inventory before anything else.

02

The method, in five steps

A plan-do-check-act loop applied to the migration: every step returns evidence, every piece of evidence gates the next. No milestone is passed on an assumption.

01

Inventory

Exhaustive extraction of Vistex objects: programs, agreements, conditions, rebates, chargebacks, and everything that references them.

OutputObject register

02

Impact

For each of the seven SAP flows: what the conversion changes, what breaks, what is reconfigured, what is rewritten.

OutputImpact analysis

03

Gap-fill

For every gap: a reasoned closing proposal, validated by your business teams — never applied without them.

OutputRemediation plan

04

Non-regression

Real business scenarios replayed on the target. Every test returns a traced verdict: compliant, in exception, or not testable.

OutputTest book

05

Cutover

Switch in waves, explicit go / no-go criteria, restart point at every wave. The rollback is written before the switch.

OutputCutover plan

↻ A gap found in non-regression goes back to gap-fill; a gap found at cutover goes back to inventory. The loop is never inverted: we do not switch in order to discover.

03

Three paths, one method

The path depends on your platform and your appetite for history. Checklists, planning and risks adapt if the method changes mid-project.

Greenfield

New implementation

The S/4HANA platform is built from scratch. WEVIA starts from your existing Vistex programs, extracts the target condition matrix and specifies every interface with no technical legacy.

Object register and rewritten condition matrix
Interface specifications per SAP flow
Data takeover limited to the strict minimum

When: model redesign, heavy technical debt, little history to keep.

Brownfield

In-place conversion

Your ECC becomes S/4HANA. WEVIA measures the gap between your current Vistex and the target, isolates the blocking points and produces a remediation plan per domain.

Impact analysis interface by interface
Anomalies detected and prioritised before cutover
Assisted gap-fill and full non-regression tests

When: stable processes, history to keep, tight deadline.

Preferred path

Bluefield

Selective transition

A fresh S/4HANA shell, a chosen takeover of Vistex data. It is the path WEVIA has developed the furthest: the takeover scope is arbitrated object by object, and everything is recomputed if the method changes.

Takeover scope arbitrated and frozen
Blocking points specific to selective transition and RISE
Cutover in waves, rollback at every wave

When: a model to clean up without losing everything, migration by scope, RISE with SAP.

04

Nine deliverables, all actionable

Nothing that does not help decide or do. Every deliverable is attached to the step that produces it and to the steering tab where it lives.

Know

▤

Object register

Exhaustive inventory of Vistex objects and their SAP dependencies.

Inventory

⇄

SAP interfaces

The seven flows, both directions, with what S/4HANA changes on each.

Inventory

▦

Condition matrix

Conditions, discounts and rebates: source, target, traceability of the rewrite.

Inventory · Gap-fill

Decide

◈

Impact analysis

Per interface: what breaks, what is reconfigured, what is rewritten — and the cost of each option.

Impact

◬

Anomalies

Blockers detected, qualified and prioritised before they reach the cutover.

Impact · Non-regression

⬡

Takeover scope

Which objects, which history, how deep: arbitrated with you, then frozen.

Impact · Bluefield

Do

✦

Gap-fill

One closing proposal per gap, validated by the business before application.

Gap-fill

✓

Tests & non-regression

Business scenarios replayed on the target, traced verdict for each.

Non-regression

⚑

Cutover plan

Waves, go / no-go criteria, restart points, rollback written in advance.

Cutover

And to steer

RACI & actors

Who decides, who does, who validates — per deliverable, not per phase.

Forecast planning

Recomputed at every change of path or scope.

Risks & mitigation

Every risk carries its warning signal and its plan B.

Workshops

One workshop per domain, with its agenda and the decisions expected.

05

What WEVIA commits to

No fabricated data

An unmeasured state is shown as such. A test that was not run is never counted as passed.

Sovereign

Your Vistex data stays on your platform or on dedicated infrastructure. Nothing is sent to a third party.

Rollback before switch

The restart point of every wave is written and tested before the wave leaves.

The business validates

No gap closing is applied without explicit validation from the team concerned.

06

Four packs, from scoping to run

Each pack has an explicit duration, deliverables and prerequisites. You enter at the level that matches where you are — and leave with artefacts your integrator can pick up.

Scoping

2 hours

Workshop with IT, procurement and management control. You leave with an initial object register, the likely variant and an effort estimate.

Output: initial register · variant · order of magnitude

Prerequisites: read access to ECC, one business referent

Readiness diagnostic

3 weeks

Full /IRM/* + Z inventory, condition matrix, fit/gap against S/4 standard (condition contracts), simplification-item impact, proposed data-slice scope.

Output: inventory · matrix · standard-vs-Vistex fit/gap · test plan · estimate

Prerequisites: Readiness Check, DEV/QAS access, key users

Managed migration

per wave

Steering the Vistex conversion inside the S/4HANA programme: remediation, to-the-cent non-regression, cutover with a tested restore point, mission journal measured weekly.

Output: identical settlements before/after · runbook · test evidence

Prerequisites: named integrator, governance, test environment

Run & hypercare

4 to 8 weeks

After go-live: daily checks of settlements and accruals, anomaly handling, knowledge transfer to key users, measured closure.

Output: stabilisation report · improvement plan · handover

Prerequisites: go-live done, read access to PROD

Output figures are measured on your system, never declared. A test that was not run is shown as not run. Choose a pack →

07

Frequently asked questions

Do we have to drop Vistex when moving to S/4HANA?

No — but nothing should be carried over by reflex. Each agreement type is challenged against the S/4 standard (condition contracts): standard is enough, Vistex is required, or hybrid. That decision is a diagnostic deliverable, not an assumption.

Greenfield, brownfield or bluefield for Vistex?

Greenfield reimplements on the standard; brownfield converts in place; bluefield (selective data transition) carries over a useful slice of data — our preferred path for rebate programmes, e.g. 24 months of settlements migrated and tested.

What happens to settlement and accrual history?

It is treated as migration data in its own right: scope (data slice), load, then to-the-cent non-regression — settlements before and after conversion must match, with evidence.

How long does a Vistex migration take?

Scoping takes two hours, the readiness diagnostic three weeks. The migration itself depends on agreements, conditions and custom Z code — the diagnostic produces a per-wave estimate, with 3-4 test runs planned.

Does Vistex work with RISE with SAP?

The point to watch is selective data transition on RISE private edition: the SDT ↔ RISE ↔ Vistex triangle is checked contract-in-hand at scoping — an explicit prerequisite on our checklist.

Does our data leave our systems?

No. Inventory and tests run on your environments; the mission cockpit is sovereign and nothing is sent to any third party.

Download the placemat (PDF, 1 page) ↓

08

Scope your migration

Two hours are enough to locate your Vistex in your platform, choose the path and size the inventory.

Scoping workshop

Vistex scope, S/4HANA target, likely path, calendar constraints. You leave with a first register and an estimate.

Talk to an expert → See the whole SAP suite

Request a scoping session

Two hours, your system, our questions. Nothing is sent to any third party.

Name Work email Company ECC version / Vistex add-on Likely path Horizon

Context (optional)

Your data stays in Europe on our servers. No newsletter without consent.