SAP to RELEX Integration
Solution by TeamIdea
Solution overview
Contact us
The SAP to RELEX predefined Integration Solution (S2R) is designed to significantly reduce the time, effort, and risk involved in integrating the SAP for Retail ERP system with the RELEX SaaS platform.
The S2R Integration Solution is built on S2X Integration Kit, using the following Extensions specifically designed for integration with RELEX:
- S2R Core Mapping Engine – provides the mapping logic between SAP dataset and RELEX data interface requirements
- S2R Configuration Tool – for interface customization without additional development using SAP standard business objects as a parameter for interface data flow configuration
- S2R Data Validation Report Kit – predefined list of Reports built on Power BI platform for Interfaces Data Validation and Checks
The S2X Integration Kit (SAP to eXternal Integration Kit) is a customizable integration Set that leverages standard SAP extractors and the capabilities of Microsoft Azure platform providing the scalable foundation for easy building enterprise level solutions for Integration, Reporting and AI based Add-Ons considering the amount of data available for processing.
The S2R Integration Solution processes SAP data (including SAP Delta data) and convert it into structured CSV files within the Microsoft Azure environment in accordance with RELEX data flow requirements.
By using the S2R integration Solution it is possible to accelerate the implementation of RELEX, reducing the typical integration timeline from 3–5 months to just 4 weeks for core RELEX functionality and standard SAP business processes.
A Proof of Concept (PoC) or Minimum Viable Product (MVP) implementation can be launched in as little as 3 weeks assuming core RELEX functionality and standard SAP business processes are in scope.
Core Architecture Principles
S2R Solution High-Level Architecture
Additional S2R Architectural Components
- DataMart – serves as an intermediate structured data layer enabling efficient Power BI connectivity and reporting within the prepared aggregated data in CSV files
- MS Power BI – for Data validation Reporting
- Multi-Tier Landscape Support – follows a DEV → PROD transport model, using Teamidea’s Release Registry for controlled deployment of customizable components.
Data Flow Overview
S2R Extensions designed for integration with RELEX
The Business Level Configuration Tool
A flexible and scalable configuration environment developed in SAP, that enables Business users and implementation teams to control and adapt integration behavior without requiring technical development.
Key Functionality
- Locations and Location Groups Definition and Maintenance (e.g. Regions, Warehouses, Store clusters, etc.)
- Wide Parameterization for Each Interface (e.g. Order type, Special stock type, Movement type, Sales Area, Price condition, Invoice type, etc.)
- Time Dependency Control for Integration profile and Locations
Rollout Capabilities
- Interface Scope definition for MVP and Rollout Phases (e.g. Stock, Sales, Orders, etc.)
- Product Groups Selection for Rollout Purposes (e.g., Foodstuff, Non-food, Seasonal, etc.)
- Location Groups Selection for Rollout Purposes
Configuration Tool – Rollout Application Diagram
The Mapping Engine
The Mapping Engine (ME) is a Python-based application that encapsulates our knowledge of SAP data structures, delta logic, and retail business semantics. The ME:
-
Supports SAP Business-level configuration Tool for interface data flow customization
-
Processes raw SAP data and applies business-level mapping logic
-
Outputs structured CSV files in RELEX-compatible format (current version)
-
Preprocesses RELEX Order Proposals and transfers them to SAP using REST API and standard IDOC mechanisms
-
Improved customer service
Data Validation Report Kit
The Data Report Validation Kit is a specifically designed set of DataMarts and Reports based on Power BI to support the critical Data validation process within integration projects that:
Allows Business users to check and validate each Data flow in a very familiar way as it provides information with reference to initial SAP documents or Master Data object.
Includes the Data Validation Methodology with detailed description of a suggested Data validation approach for each Data flow and provides step by step guide how to verify the data using standard SAP transactions and corresponding Reports.
Recommended Solution Implementation Approach
S2R solution can be implemented by Customer’s internal team or Consultant partner team, but solution installation steps required specific Vendor’s activity for the selected interface package and include direct support from Vendor regarding interface configuration and Data validation support.
Project Phases and Reference Diagram
The suggested sequence of main steps within project phases illustrated below on the Project Reference Diagram including possible Customer specific customization requests (if applicable). For clarity all activities are divided into two flows:
- Project implementation Activities (Customer’s and/ or Consultant Partner’s activities)
- Solution installation Activities (Vendor)
To facilitate the preliminary evaluation of potential Change Requests (CRs), a dedicated step called “Interface Scope Definition” is included in the Project Preparation Phase. This step enables a thorough analysis of solution assumptions and helps determine the applicability of the S2R Solution to the customer’s specific business scenario.
To support this evaluation, the vendor has developed the “S2R Business Assumptions” document. It provides a detailed description for each interface, outlining which standard SAP business processes are considered and how the interfaces can be configured using the S2R Configuration Tool to define the exact SAP data that should be transferred to RELEX.
In general, due to the flexibility of the solution, any standard SAP data supported by SAP standard extractors can be included in the current interface content by the vendor at no additional cost (subject to final approval based on the customer’s request).
S2R Installation and Activation
The installation and activation of the S2R solution follow a clearly defined sequence of steps, fully supported by the vendor’s experienced consulting team. This structured approach ensures transparency and enables accurate project timeline planning. At the same time, it places no restrictions on the customer, allowing either the customer or their consulting partner to plan and execute the implementation project based on their own schedule, available resources, and internal priorities.
Solution installation and Activation flow Diagram
The S2R installation process is based on an open and transparent model, with straightforward interactions between the customer and the vendor. It consists of two main parts:
Below is the detailed flow diagram outlining the solution installation and activation process, which is fully managed and delivered by the vendor.
Historical data upload is not included in the vendor’s standard solution installation scope. However, it can be supported by the vendor’s consulting team within the consulting hours included in the selected package. The reason for this exclusion is that each customer has a unique volume of historical data and specific SAP system constraints related to the high system load typically required for historical data extraction and upload.
To facilitate this process, the vendor provides typical “How-To” documentation, enabling the customer’s technical team to perform the historical data upload independently, at a time that best fits their project schedule.
Azure infrastructure cost Considerations
It is important to note that the recommended approach for solution deployment involves using a dedicated standalone Azure subscription.
Once the interfaces are activated, data will begin flowing into the Azure environment, which may result in Microsoft billing for data storage and processing. These charges will vary depending on the customer’s data volume.
Therefore, it is strongly recommended to define the initial scope of interface activation carefully. This helps avoid unnecessary costs associated with activating interfaces that are not yet implemented or used in the project.
Solution Output and Processing Flow
The successful implementation of the S2R solution results in the generation of CSV output files within RELEX ABS, which then become available for processing via RELEX Connect and subsequent consumption by RELEX Plan. Typically, the outbound data flow is scheduled to run daily at a defined time, depending on the calculation window. This window should be determined during the implementation project.
For the inbound flow (from RELEX to SAP), the outcome is the creation of IDOCs and corresponding purchase and/or transfer orders in SAP, based on order proposals calculated by RELEX. These order files are placed in a specific folder within RELEX ABS. The solution begins processing these files based on a trigger mechanism, which can be configured in one of the following ways:
- As a scheduled job
- Via a file watcher
- Or triggered by the receipt of a technical email sent to a predefined mailbox indicating the successful creation of order files in RELEX ABS.
Please note that the configuration of RELEX Connect lies outside the scope of the standard S2R installation and activation services provided by the vendor.
Solution Delivery and Support Model
Before submitting a request for solution installation, the available delivery window should be confirmed with the vendor. The typical lead time is approximately one business week.
The actual technical installation of the solution takes around 4 to 8 working hours per system. However, it is recommended to allocate approximately 3 business days in the project schedule to account for any unexpected technical issues and delays.
The S2R documentation package includes a comprehensive Solution Installation Guide, which outlines the technical prerequisites and credentials that must be provided by the customer to ensure a smooth and seamless installation process
Continuous Development and Release Schedule
The vendor continues to actively develop and enhance the solution, aiming to align with ongoing RELEX interface changes and updates, as well as to extend support to RELEX for Manufacturing in addition to Retail.
The development roadmap for the Retail version includes:
- Adding support for non-mandatory interface fields
- Enhancements to the Mapping Engine
- Updates to the Power BI report set to enable validation of the extended data content
New solution releases are currently planned on a quarterly basis, ensuring the platform remains up to date with RELEX requirements.
The overall solution lifecycle is illustrated in the diagram below.
Support Model
The availability of a new solution release as part of the vendor’s release plan does not automatically require immediate implementation. The decision to apply a new release should be made by the responsible party overseeing the integration with RELEX and managing RELEX system updates. If a decision is made to install the new release, a corresponding request should be submitted to the vendor.
The S2R Support Model offers two levels of support:
- Standard Support – included in the solution subscription at no additional cost.
- Premium Support – available for an additional fee, offering extended benefits for customers who require higher vendor involvement and oversight across the full solution infrastructure.
Standard Support
- Is designed for customers who maintain their own technical teams with sufficient expertise in SAP extractor functionality and Azure infrastructure components included in the solution architecture.
- Under Standard Support the vendor provides assistance only for Mapping Engine updates and related issues. Other components (e.g., Azure pipelines, SAP extractors, configuration files) must be installed and managed by the customer’s internal team, following the instructions in the provided Release Notes.
- If technical issues arise in areas outside the Mapping Engine – such as SAP extractors or Azure Data Factory pipelines – vendor assistance can be requested, but support will be billed on a time-and-materials (T&M) basis, according to the current consulting rates.
Premium Support
- Is ideal for customers who prefer full assistance in maintaining and updating the solution within their specific infrastructure.
- Installation and configuration of all solution updates by the vendor upon request.
- End-to-end analysis and resolution of technical issues across the entire data flow, with no extra cost if the problem lies within the vendor-managed solution components.
- Proactive issue handling, reducing the internal workload for the customer’s technical team.
Note: In certain cases, changes made by the customer’s internal team to SAP extractors (e.g., adjustments for internal data warehouse needs) may fall outside the vendor’s direct responsibility.
Support Response Time (SLA)
| Support Tier | Standard Support | Premium Support |
|---|---|---|
| General Response Time | Within 48 hours | Within 24 hours |
| High Priority Tickets | Response within 12 hours, but only if the issue is within the vendor's scope. Otherwise, misuse of high priority flags may result in a charge for the analysis | Response within 12 hours, with no charge for supported solution issues. |
Pricing Model (Retail version)
The pricing model is designed to offer maximum flexibility and transparency for customers. It allows to start with a basic interface package (for example, to support RELEX core Forecasting functionality) and then upgrade to a higher-level interface activation package as needed.
The price list template effective as of October 20, 2025, is presented below. All prices are listed in USD, excluding VAT and any other applicable taxes (actual price list available upon request).
| Item | Number of Flows | One-Time Fee | Annual Fee | Consultant T&M Rate (USD/hour) | Included Consultant's Hours |
|---|---|---|---|---|---|
| S2R Core License Fee | ###### | ||||
| S2R Core (Solution installation) | ###### | ||||
| Interface Activation Package 10 | 10 | ###### | 40,0 | ||
| Interface Activation Package 20 | 20 | ###### | 80,0 | ||
| Interface Activation Package 30 | 30 | ###### | 120,0 | ||
| Additional Interface (+ validation report) | 1 | ###### | 4,0 | ||
| Premium Support (optional) | ###### | ||||
| CR (Interface customization or Custom interface creation) | 90,0 |
S2R Subscription Cancellation and Renewal Policy
The solution is provided under a subscription-based license, which does not automatically renew.
Two months before the end of the subscription period (typically one year from the subscription start date, as defined in the contract), the vendor will send a subscription renewal notice to the customer. This will be followed by three reminder notifications, each spaced approximately one month apart. If no response is received, the final message will be a subscription termination notice, sent one month after the subscription end date.
At the end of the subscription period, the customer may:
- Project implementation Activities (Customer’s and/ or Consultant Partner’s activities)
- Solution installation Activities (Vendor)
Renewing the subscription involves the delivery of a new license key for the Mapping Engine. A valid license is required for the Mapping Engine to function. By default, the technical expiration date of the license is set to one month after the official subscription end date, allowing a brief grace period.
Subscription cancellation only affects the functionality of the Mapping Engine, including the processing of outbound and inbound interface files.
All solution infrastructure components (e.g., Azure setup, RELEX folders, data pipelines) will remain accessible to the customer. This ensures continued availability of any custom Add-On components built on top of the solution, for example, a customized Power BI Business Report Set developed by the vendor or another consulting partner after Go-Live.
Key Advantages of the S2R Integration Solution
-
1.
Business-driven integration methodology
-
2.
Supports flexible rollout scenarios and enables implementation without the need for external consultants or developers
-
3.
Supports unlimited independent SAP installations (e.g., for companies with multiple entities running separate SAP systems)
-
4.
40+ ready-to-implement pre-built data flows, covering the most common SAP-to-RELEX interfaces and significantly reducing the integration project timeline
-
5.
Full support for SAP transactional flows
-
6.
Flexible integration with non-SAP data sources
-
7.
Provides datasets for creating any type of business reports and dashboards.
-
8.
Can be used to develop AI-powered business add-on solutions, such as:
- Master Data Health Monitoring Dashboard
- Vendor Performance Scorecard
- Demand & Supply Anomaly Detection Service
- AI Chatbot for Logistics and Replenishment Teams
- Planning Collaboration Portal for Retail & DC Managers
Supported SAP Systems versions
| SAP System | Supported version (Azure SAP CDC) | ODP Support | DB Platform | Adaptation required |
|---|---|---|---|---|
| SAP ECC | ECC 6.0 (NetWeaver ≥ 7.0 SP17 and < 7.4 SP02) | Need to implement SAP Note 2232584 (enable ODP) | AnyDB | Yes (CDS-extractors) |
| SAP ECC | ECC 6.0 (NetWeaver ≥ 7.4 SP02) | Natively | AnyDB | Yes (CDS-extractors) |
| SAP ECC | ECC 6.0 (NetWeaver ≥ 7.4 SP02) | Natively | HANA | No |
| SAP ECC | ECC 6.0 (NetWeaver ≥ 7.4 SP02) | Need to implement SAP Note 2232584 (enable ODP) | HANA | No |
| SAP S/4HANA | All versions | Natively | HANA | No |
| SAP BW | < 7.3 SP08 | Not supported by ODP | AnyDB | Yes (all extractors) |
| SAP BW | < 7.3 SP08 | Not supported by ODP | HANA | Yes (all extractors) |
| SAP BW | ≥ 7.3 SP08 | Not Required (OpenHub/TABLE connection) | AnyDB | Yes (all extractors) |
| SAP BW | ≥ 7.3 SP08 | Not Required (OpenHub/HANA/TABLE connection) | HANA | Yes (all extractors) |
| SAP BW/4HANA | SAP BW/4HANA | Not Required (SAP HANA connection) | HANA | Yes (all extractors) |
| SAP POSDM | NetWeaver ≥ 7.0 | Limited (via ODP-enabled Data Sources) | AnyDB | Yes (all extractors) |
| SAP POSDM (no ODP) | NetWeaver < 7.0 or POSDM without ODP-enabled Data Sources | Not supported by ODP | AnyDB | Yes (all extractors) |
| SAP CAR | ≥ 2.0 (built on HANA, supports ODP natively) | Natively (ODP extractors) | HANA | No |
Final Notes
S2R is a ready-to-use solution that can be implemented in an out-of-the-box manner within a very short timeline. It can be adapted to various SAP system versions (not limited to those listed above) as well as to customer-specific business processes, including those involving Z tables and custom logic.
If you are interested, please download the Solution Overview presentation, which includes additional product information.
The “Solution Business Assumptions” document, along with the Solution Technical presentation, Demo videos, and Solution documentation examples, is available upon request.
For further inquiries or project-related requests, please feel free to contact us at S2R@teamideagroup.com