YUNIT SL
YUNIT SL
Senior Hands on Delivery
English Deutsch Català

Blogs

Technical insights from the field

Commerce Cloud Integration with S4/HANA

SAP Commerce Cloud • S/4 HANA Order Management

Integrating SAP Commerce Cloud (formerly Hybris) with S/4 HANA Order Management requires careful alignment of extension layers to avoid conflicts with legacy LORD/OMS extensions while enabling modern order simulation and fulfilment flows.

Order Management Extension Layers

saps4ombackoffice

Introduces the s4OrderSimulation tab within the SAP Configuration entity in Commerce Cloud Backoffice. This allows administrators to configure S/4 HANA order simulation parameters without touching core extension code.

saps4omservices

Establishes connections to S/4 HANA OData APIs for:

  • Order simulation — pre-submission availability and pricing checks via SapS4SalesOrderSimulationService
  • Order placement — via S4PlaceOrderStrategy, replacing the default Commerce Cloud order placement
  • Order history retrieval — pulling order and invoice documents from S/4 HANA into the Commerce storefront

saps4omfacades

Introduces additional order populators and billing/invoice document retrieval facades. These sit between the OCC API layer and the service layer, enriching cart and order data with S/4 HANA-specific fields (schedule lines, billing document references, delivery status).

saps4omocc

S/4 HANA-specific OCC v2 REST API extensions exposing schedule line data to the composable storefront. Enables the storefront to display confirmed delivery dates and partial fulfilment information directly from S/4 HANA without additional backend calls.

Compatibility with Legacy LORD/OMS Extensions

A common concern when introducing S/4 OM extensions is whether they conflict with existing legacy LORD (Local Order Routing & Delivery) or OMS (Order Management System) extensions. The S/4 OM stack is designed as a replacement strategy — not an overlay — so organisations should plan a phased migration: run S/4 OM in parallel on a separate order type or business unit, validate the flows end-to-end, then deprecate the legacy extensions.

Direct co-existence of both stacks on the same order type is not supported without custom mediation logic at the S4PlaceOrderStrategy level.