Not so Seamless S/4HANA Data Integration: How to Configure Replication Flows with Datasphere Using Cloud Connector
Or: When Family has trouble talking to each other
We’ve all been to those family gatherings where certain relatives just won’t talk to each other without a mediator (or misunderstanding each other constantly). Setting up replication flows from SAP S/4HANA to Datasphere via Cloud Connector feels remarkably similar – it’s about getting two powerful systems to share information when they seem hesitant to do so.
Meet the Family
Let’s get to know our key players:
1. SAP S/4HANA (on-premise): The seasoned elder of the family, carrying decades of data expertise. Reliable and deeply knowledgeable, but not the most flexible. Prefers to keep information closely guarded.
2. SAP Cloud Connector: The well-meaning cousin who acts as the go-between for the family. Often helpful in bridging gaps, but occasionally adds complexity of their own. Always positioned in the middle of things.
3. SAP Datasphere: The modern, cloud-based relative full of fresh ideas and potential. Often needs help translating the traditions of the older generation and still relies on support to stay connected to its on-premise roots.
Skeletons in the Closet / aka Family History You Should Know (Prerequisites)
Before bringing everyone together, make sure you have:
- Administrative access to your S/4HANA system (the keys to the family home) or at least someone available that has the keys.
- The necessary SAP Notes installed (family guidelines everyone should follow) or a rather up-to-date SP Level. Don’t forget to run transaction code CNV_NA_DI to verify all required SAP Notes are installed. Think of it as checking that everyone’s on the same page before the big reunion.
- Admin rights to Cloud Connector (permission to mediate)
- Admin access to SAP Datasphere (an invitation to the new place)
As it is rare that anyone in a family setting (enterprise) has all of these admin accesses lined up, this will most likely be a group effort. Go Team!
Setting Up Cloud Connector as the Family Mediator
https://help.sap.com/docs/SUPPORT_CONTENT/datasphere/4535969591.html
Gathering Your Family Details
1. Log into your SAP BTP account to find your subaccount information
2. Navigate to the Account Information section (the family directory)
3. Note down the Subaccount ID, Region Host, and User (essential contact information)
Preparing the Mediator
1. Install Cloud Connector if you haven’t already – it’s like setting up the neutral meeting ground
2. Launch the administration interface and connect to your subaccount
3. Create a new connection using RFC protocol – think of it as establishing the rules of engagement (https://help.sap.com/docs/connectivity/sap-btp-connectivity-cf/initial-configuration-rfc)
4. Add the required functions – the topics that are safe for discussion
Introducing Datasphere to Its On-Premise Relatives
1. Log in to Datasphere and select your Space (the modern family member’s living room). It is generally recommended to have a separate space for acquiring data.
2. Create a new connection by clicking the (+) sign
3. Choose SAP S/4HANA On-Premise as the connection type – formally introducing the younger relatives to the „old folks“
4. Set „Use Cloud Connector“ to True – acknowledging they need a mediator to communicate effectively (generational slang translation)
Never forget to get feedback from your patients! (validate):
The result should show “Replication flows are enabled”.
When filling in the details, remember that precision matters. It’s like making sure you have the exact family address right – one wrong digit and your holiday cards never arrive at aunt Emma’s place.
Teaching S/4HANA to Share (CDS View Modification)
Unless you are using the official CDS views for data extraction (recommended if available for your use case), you need to teach your S4 (CDS View) to share. This is essentially telling S/4HANA, „Yes, it’s okay to share your valuable information with Datasphere. They’re family after all!“
(As it happens we have a blog series on that: https://www.zpartner.eu/cdc-data-extraction-lessons-learned-tips-tricks-part-1/)
Starting the Conversation (Replication Flow)
Setting up a replication flow is like arranging regular family calls:
1. Go to Data Builder and click „New Replication Flow“
2. Select your source and target – who’s calling whom
3. Configure how often they should talk (delta load frequency)
4. Deploy and run the flow – make the first call and establish a routine
Common Family Misunderstandings and How to Resolve Them
1. The „I Don’t Recognize This Number“ Problem
Symptom: „Expose the system in your Cloud Connector“ error
What’s Happening: Your systems are using slightly different addresses to refer to each other.
Resolution: Double-check that the virtual host and port match exactly in both systems – like making sure everyone has the current phone number.
2. The „Wrong Branch of the Family“ Issue
If your connection validation fails, it might be because the subaccount in Datasphere doesn’t match the one registered in Cloud Connector. It’s like showing up at the wrong family reunion – technically they’re relatives, but not the ones expecting you.
3. The „Not on the Guest List“ Situation (IP Allowlist)
Sometimes your systems can’t connect because they’re not on each other’s approved visitor list. Make sure Cloud Connector’s IP is in Datasphere’s trusted list, and the relevant domains are whitelisted in your firewall.
4. The Vague „Something’s Not Right“ Comments
Symptom: „One or more partitions have encountered an error“
What’s Happening: Like when a relative says „I’m fine“ but clearly isn’t, these generic errors hide specific issues.
Solution: Apply the latest SAP Notes from the Note Analyzer – think of it as following the latest family therapy advice.
5. The Trust Issues (Configuration and Authorizations)
Getting your systems to establish secure connections can be tricky. It’s like convincing family members with a history of misunderstandings that they can now safely share secrets. It’s like getting aunt Emma to talk to uncle Bob after all those issues. You know what I mean! – Details follow below.
Family Harmony Tips (Best Practices)
1. Regular Updates: Keep your systems current – like making sure everyone has the latest family news
(https://help.sap.com/docs/SUPPORT_CONTENT/datasphere/4457678727.html)
2. Check-ins: Monitor your replication flows regularly – don’t wait until the holiday dinner to discover there’s a problem (Transaction DHCDCMON in S4: https://help.sap.com/docs/SUPPORT_CONTENT/datasphere/4549335823.html)
3. Clear Boundaries: Set up proper authorization roles – not everyone needs to know everything about everyone. A rather good start is the standard role: SAP_DI_ABAP_REMOTE, but that will not be enough (https://help.sap.com/docs/SUPPORT_CONTENT/datasphere/4518522125.html)
4. Check under the hood: SLG1 / SU53 / DHCDCMON / ODQMON / SDDLAR / STAUTHTRACE are your friends. SAP provides a very good list of tools here: https://help.sap.com/docs/SUPPORT_CONTENT/datasphere/4428871866.html
5. Efficient Sharing: Use delta replication for large tables – share what’s new, not the entire family history every time
6. Practice Runs: Test in non-production first – like rehearsing a difficult conversation before the actual family gathering (e.g., missing notes might lead to nasty effects you do not want to test on production).
Conclusion
With patience and the right approach, you can successfully get your SAP systems to talk to each other like the family they were meant to be. The connection between S/4HANA and Datasphere might require some mediation from cousin Cloud Connector, but once established, they’ll share data smoothly and consistently.
Remember, even the most complicated family relationships can be improved with good communication tools, a bit of configuration finesse, and some group effort. Happy replicating!
General Therapy Options
The best collection of sources and information that does not directly pop up when you search for it (main source for this blog entry):
Especially the Tools for Troubleshooting section is a lifesaver!
Therapy Options That Helped Us (MVP)
- 3483470 – Guideline for Troubleshooting Data and Replication Flows with ABAP Source Systems – SAP Datasphere
- 2890171 – SAP Data Intelligence / SAP Datasphere – ABAP Integration
- 3100673 – SAP Data Intelligence / SAP Datasphere – ABAP Integration – Security Settings
- 3223810 – Known limitations and important considerations for Replication Flows
- 3297105 – Important considerations for SAP Datasphere Replication Flows
- 3100673 – SAP Data Intelligence / SAP Datasphere – ABAP Integration – Security Settings
- 3360905 – SAP Data Intelligence / SAP Datasphere – ABAP Integration – Performance when using RMS / Replication Flows
- 3260185 – SAP Data Intelligence / SAP Datasphere – ABAP Integration – Runtime Parameters (DHBAS_RUNTIME / LTBAS_RUNTIME)
- 3044005 – SAP Data Intelligence / SAP Datasphere – ABAP Integration – General Parameters (DHBAS_CONFIG / LTBAS_CONFIG)
- 3223735 – ABAP Integration – Job Settings (Transaction DHCDCSTG / Table DHCDC_JOBSTG)
- 3088317 – SAP Data Intelligence / SAP Datasphere – ABAP Integration – Settings for Retention Period
- 3035658 – SAP Data Intelligence / SAP Datasphere – ABAP Integration – Data Conversion and Serialization (Wire Format)
Author: Holger Kurz
Holger has been working as a Solution Architect at ZPARTNER since 2015 and specializes in building advanced BI solutions based on Datasphere, SAP Analytics Cloud, SAP Data Intelligence, BW/4HANA, GCP, BigQuery, AWS, and Azure. He has extensive technical knowledge in cloud and data engineering, as well as custom development using ABAP OO, Web Dynpro, OData, UI5, HANA SQL, Python, and JavaScript.