Introduction
In this blog post you’ll find the following information
- Guidance to our customers of SAP Cloud Integration for data services (CI-DS) on the product positioning
- SAP Cloud Integration for data services product direction with the recent announcement of Sunsetting BTP NEO (Dec 2028)
SAP Cloud Integration for data services is a cloud-based data integration tool for batch/scheduled data integration between on-premises applications and cloud applications. The primary use case for SAP Cloud Integration for data services is data integration with SAP Integrated Business Planning for supply chain (SAP IBP). SAP Cloud Integration for data services is also used to connect to other cloud applications using standard protocols like SOAP, REST, or OData.
Product Positioning
SAP Cloud Integration for data services is positioned for time series and master data integration for SAP IBP and current roadmap investments are towards IBP use case only.
For Non-IBP use cases, refer to the SAP Integration Architecture Guide for Cloud and Hybrid Landscapes to choose the right integration tool for your scenario.
Product Direction
SAP Cloud Integration for data services is bundled with SAP IBP application license. There is no plan to sunset SAP Cloud Integration for data services, it will continue to be supported for IBP use cases.
SAP recently announced that legacy NEO environment will be sunset on December 31,2028. For more information, please refer to blog - Farewell, Neo! SAP BTP, multi-cloud environment – the deployment environment of choice
How does Neo Sunset impact SAP Cloud Integration for data services?
SAP Cloud Integration for data services is running on NEO and we plan to migrate to BTP Multi cloud to run on popular Hyperscalers.
The Architecture of SAP Cloud Integration for data services consists of two major components.
- The Data Services Agent, which requires a user site on-premise installation that interfaces with source side business data.
- The server component in the cloud that interacts with (IT) user to create design time ETL artifacts for data movement including transformation and schedule the data loads to and from on-premises/cloud systems.
Server component is configured on BTP NEO, and is the identified candidate for migrating with minimal configuration changes on the user site on-premise agent component.
What are the next steps for the existing customers?
SAP intends to work with customers to help minimize the impact and will assist in their migration of SAP Cloud Integration for data services off the Neo environment.
SAP Cloud Integration for data services product team will announce the timelines and migration plan in Q3 2024. Our plan is to provide flexibility for customers to schedule the migration and make it as less disruptive as possible.
How do I get updates about the migration?
We will keep you updated on this migration through the official blogs, and we will publish Part-2 of this blog with the migration plan and timelines in Q3-2024.
Migration updates will also be provided in webcasts, register for the upcoming SAP Cloud Integration for data services webcasts available at IBP Engagement Hub
Does the Neo Sunset impact consumption-based contracts (CPEA – Cloud Platform Enterprise Agreement)/PAYG for customers using SAP Cloud Integration for data services for Non-IBP usecases ?
- The CPEA/PAYG contracts will be renewed, but the "SAP Cloud Integration for data services" service will no longer be part of their Eligible Services List.
- If customers renew within the 6 month grandparenting phase, they will still be able to use the service after renewal.
If you have any additional questions, please reach out to our CI-DS Migration Experts
