S4hana RISE on Private Cloud Vistex component

[Saurav_sap_IVFL]

Hello All,

Please can someone help me with the following.

We are converting from S4HANA 1909 to SAP S4HANA RISE on PRIVATE CLOUD. We have Vistex in 1909 which are referencing /IRM/ Tables in SAP which are Vistex Tables while calculating prices against agreements created in Vistex.

We have decided to discontinue Vistex and create all agreements in SAP RISE . During conversion if Vistex component is removed can we view these orders(Vistex Related) in SAP RISE once the Vistex component is removed.

IF not , please can you suggest an alternative how to view the Vistex related orders in RISE once the component has been removed.

An early response will be highly appreciated.

Thanks and Regards.

[Ndubuisi_PALMER · Accepted solution]

Dear Saurav

Once the Vistex component is removed during your S/4HANA 1909 to RISE Private Cloud conversion, you will not be able to access Vistex-specific tables (/IRM/*) or functionalities in the standard SAP environment. These tables and logic are part of the Vistex add-on, and without the component being installed, runtime references to /IRM/ tables will fail, and any dependency (e.g., in pricing conditions, agreements, historical orders) will be broken or inaccessible.

Standard SAP cannot interpret or render documents that rely on Vistex-specific structures if the corresponding add-on is not present. Therefore, orders that relied on Vistex logic for price determination or agreement reference might appear incomplete or not interpretable post-conversion unless precautions are taken.

To address this, here are your options:

1. Archive the Vistex orders in 1909 before conversion: Use SAP ILM or ArchiveLink to archive documents with full Vistex metadata and pricing context. You can then access them in a read-only mode post-conversion via archive viewers. This avoids the need for the Vistex engine in the new system.

2. Export Vistex-related order data: Before decommissioning Vistex, export all relevant order data (including pricing, agreements, and references from /IRM/* tables) into custom Z-tables or a sidecar HANA DB schema. Then create a custom Fiori or ABAP report in RISE to query this legacy data for historical analysis.

3. Retain a legacy read-only system: Keep a copy of your S/4HANA 1909 system with Vistex installed, in read-only mode, for audit, reporting, or access to legacy documents. This is common in large enterprises during system transitions.

4. Build a conversion utility for orders: Prior to uninstalling Vistex, enrich and copy all sales orders referencing Vistex agreements into new SAP-native pricing procedures. This allows continuity but requires significant development and validation effort.

5. Consider temporary retention of Vistex post-migration: Migrate Vistex to RISE only for the purpose of rendering historical orders. You do not create new agreements in Vistex, but keep the component technically installed to support old documents. Decommission later when legacy data is no longer required operationally.

Conclusion: You cannot directly view Vistex-dependent

Best regards

[Saurav_sap_IVFL · Accepted solution]

Hello Palmer, Thanks for your detailed answer. Regarding option 5 is a Vistex license required since the client has not renewed it's Vistex license this Financial year.