SAP Community - Cloud Connector

Business Application Studio Cannot See BTP Destinations (Platform Issue)

2025-08-28T17:38:52.460000+02:00

Hello SAP Community,

I am facing a persistent issue where my Business Application Studio dev space is unable to see a BTP destination I've configured. The destination itself is set up correctly and the connection to my on-premise system is working perfectly, but it does not appear in the Fiori generator.

Environment:

BTP Environment: Trial Account
Region: US East (VA) - AWS
BAS Dev Space Type: SAP Fiori

Summary of the situation:

I have successfully installed and configured the SAP Cloud Connector.
I have created a destination in my BTP subaccount that connects to my on-premise SAP system. This destination has the required properties: HTML5.DynamicDestination = true and WebIDEUsage = odata_gen.
Crucially, when I click the "Check Connection" button for this destination in the BTP Cockpit, the check is successful and returns a "200 OK - Backend is reachable" message. This confirms the entire end-to-end connection is working correctly.
However, when I go into a Business Application Studio dev space and use the SAP Fiori generator, this destination does not appear in the "System" dropdown list.
I have tried restarting the dev space, which did not solve the issue. I then deleted the dev space and created a brand new "SAP Fiori" dev space, and the destination is still not visible.

When I run the diagnostic command npx fiori-tools destination in the terminal of the new dev space, I receive a DNS error:

npm ERR! code ENOTFOUND
npm ERR! syscall getaddrinfo
npm ERR! errno ENOTFOUND
npm ERR! request to https://.../_.../destinations failed, reason: getaddrinfo ENOTFOUND ...

This ENOTFOUND error in a brand new dev space, combined with the successful connection check in the cockpit, strongly suggests a platform-level DNS or networking issue within the BAS environment for my trial account.

Could you please advise if this is a known issue or what the next steps should be? I believe I have exhausted all possible configuration and troubleshooting steps.

Thank you for your help.

Migration of an HTML application from neo to cloud foundry environment

2025-08-29T13:10:41.339000+02:00

Hi All,
I have a problem to solve. Recently, I migrated an HTML5 application from BTP neo to cloud foundry with the process guided on sap help portal. the application got migrated successfully and also, I migrated my destination from my BTP neo to cloud foundry environment in order to connect my application to backend. But when I preview my application, it shows the error in my ui5.yaml file.

Attached pictures are the screenshots of my ui5.yaml file.

Here's the detailed log of the error in my terminal when I'm using command "npm run start":

backend: [{"path":"/sap","url":"http://pvlhe4decc1.lthe.com:8101","client":"110","destination":"S4HANA_DEV"},{"path":"/api/UploadDocumentToSP","destination":"SharePoint","url":""},{"path":"/api/DownloadDocumentFromSP","destination":"SharePoint","url":""}]
info fiori-tools-proxy ui5: [{"path":"/resources","url":"https://ui5.sap.com","version":"1.108.45"},{"path":"/test-resources","url":"https://ui5.sap.com","version":"1.108.45"}]
info fiori-tools-proxy debug: 'false'
info backend-proxy-middleware Using destination: S4HANA_DEV
info backend-proxy-middleware Backend proxy created for https://S4HANA_DEV.dest /sap
error fiori-tools-proxy Failed to register backend for /api/UploadDocumentToSP. Check configuration in yaml file.
error fiori-tools-proxy Error
error fiori-tools-proxy Failed to register backend for /api/UploadDocumentToSP. Check configuration in yaml file.
error fiori-tools-proxy Error

⚠️ Process Failed With Error

Error Message:
Failed to register backend for /api/UploadDocumentToSP. Check configuration in yaml file.
Error

Can someone help me with this error?

Regards,

Abhishek

Erro “Destination not found” ao usar ABAP Cloud para consumir API via BTP

2025-08-29T20:05:47.209000+02:00

Olá pessoal,

Estou tentando consumir a API API_BUSINESS_PARTNER do SAP S/4HANA Cloud usando ABAP Cloud no SAP BTP. Meu código utiliza cl_http_destination_provider create_by_cloud_destination para criar o cliente HTTP, mas estou recebendo o erro: Destino não encontrado.

Verifiquei a minha subconta de teste e existe um destino chamado S4HANA_API.

Best Practices for Enforcing API Governance for Applications Co-located with S/4HANA in Same Cloud I

2025-09-11T11:29:31.316000+02:00

I have an architectural question regarding API governance and security:

Current Scenario:

S/4HANA On-Premise system deployed in AWS cloud infrastructure
External applications accessing S/4HANA On-Premise OData/APIs are properly governed through:
- SAP Cloud Connector (for BTP applications)
- API Management (for external platform applications)

Challenge: Applications deployed in the same AWS infrastructure as S/4HANA On-Premise can potentially access the OData services/APIs directly, bypassing any API governance layer. This creates a security and governance gap.

Questions:

What are the recommended approaches to ensure all API access to S/4HANA On-Premise is properly governed, even for co-located applications?
Are there any reference architectures or best practices for implementing API governance within the same cloud infrastructure
How can we enforce the use of API Management or similar governance layer for applications in the same network?
Any guidance, documentation links, or reference architectures would be greatly appreciated.
Thanks in advance !

[Attached simplified architecture diagram showing the scenario]

Provision of Sales Cloud V2 APIs via Integration Suite and Cloud Connector for on-prem clients

2025-09-19T10:32:21.059000+02:00

Dear colleagues,

As part of our ongoing platform transformation, we are migrating to Sales Cloud V2 and S/4HANA. Initial testing within our sandbox environment has confirmed successful access to the Sales Cloud V2 APIs.

For productive use, we aim to establish a secure and scalable integration architecture by leveraging SAP Integration Suite in conjunction with the Cloud Connector. This setup is intended to enable on-premise clients to proactively consume Sales Cloud V2 APIs.

The envisioned scenario involves external calls initiated from on-prem systems, with responses returned from the cloud — for example, accessing data related to the Business Partner object.

We would like to validate whether this architecture is technically feasible and aligns with best practices for hybrid connectivity and secure API exposure.

Principal propagation in sap CPI to ECC

2025-09-25T04:05:11.273000+02:00

HI Members,

Hope you are doing well.

i have scenario as external system is sending data to SAP CPI from there it should reach to ECC via Cloud connector and do the transaction with same user as external system sent. where external system is using basic authentication and message is reaching to sap CPI but when request is going to ECC it giving error as "no identity configured for the user" . same user existed in sap ecc but its failing even we used the principal propagation setup in ECC and cert mapping in ECC.

Can you please help me with details to do the principal propagation in SAP CPI to ECC .

Thanks & Regards

Madhu

Principal Propagation failing between BTP Mobile Services, Cloud Connector and S/4 HANA - Access Den

2025-10-15T21:00:09.897000+02:00

Hello SAP Community,

I'm experiencing an issue with Principal Propagation when connecting SAP Mobile Development Kit (MDK) application through BTP Mobile Services to an on-premise S/4 HANA system via Cloud Connector.

Current Setup:

Source: SAP Mobile Services (BTP)
Middleware: SAP Cloud Connector
Target: SAP S/4 HANA on-premise (Client 400)

Problem Description:

When I configure the connection in Mobile Services to use "Cloud Connector SSO" as the SSO mechanism and try to test it using the "Launch in Browser" button, I receive the following error:

Access denied to system molinos.rise:8000. In case this was a valid request, ensure to expose the system correctly in your cloud connector.

However, the same OData service works perfectly when:

Accessed directly from the S/4 HANA system browser
Using a BTP Destination with Basic Authentication (username/password)

But it fails when using Principal Propagation authentication method.

Current Configuration:

Cloud Connector:

Principal Type: X.509 Certificate
Resources: / exposed with "Path And All Sub-Paths"

Connection to S/4 HANA: ✅ Active

What I've Already Checked:

✅ Cloud Connector can reach S/4 HANA system (green status) ✅ OData service is active in SICF ✅ Resource "/" is exposed in Cloud Connector ✅ Virtual-to-internal host mapping is correct ✅ Basic Authentication works (confirms the OData service itself is working) ✅ Cloud Connector certificate appears to be in STRUST

Questions:

Is there any additional trust configuration needed between BTP, Cloud Connector, and S/4 HANA for X.509 certificate-based SSO?
Are there any specific authorizations my user needs in S/4 HANA to consume OData services via Principal Propagation? (Besides the standard OData consumption authorizations)

How can I verify that the Cloud Connector is correctly sending the certificate/user information to S/4 HANA?

Logs/Additional Info:

The error appears immediately when clicking "Launch in Browser" in Mobile Services. The Cloud Connector audit log shows the request is being blocked at the Cloud Connector level with the "Access denied" message.

Any guidance on the correct configuration steps or troubleshooting approach would be greatly appreciated!

Thank you in advance for your help.

Best regards

Connection Issue Between SAP BTP Trial and S/4HANA On-Premise via Cloud Connector

2025-10-20T14:07:04.600000+02:00

Hi All,

I’m currently configuring the connectivity between our SAP BTP free trial account and our S/4HANA on-premise system using the Cloud Connector. After completing the setup, I tried to validate the connection between the cloud and on-premise systems, but I encountered an error.

Upon checking the related SAP Note, it seems that the issue might be due to a possible spelling mistake in the host name or a connectivity issue with the internal host.

I have verified that the internal hostname and port are correct, and I also checked in SICF in on-premise system to ensure the correct internal host and port are maintained. However, the connection is still not working. I’m using an HTTPS connection.

Could you please help me resolve this issue?

BR/Kannan.

Integration Suite Cloud Connector Connectivity Test fails

2025-11-19T17:23:07.063000+01:00

I'm trying to set up Cloud Connector to my BTP and Integration Suite so I can access SMB shares on an internal Windows 11 server.

Everything I can see the status of, looks like everything is working except it seems Integration Suite isn't talking to BTP, maybe.

Here are screenshots of everything I have running.

Cloud Connector on Windows Machine

This windows machine has confirmed access to the SMB file share I want to get files from.

Tested in PowerShell and basic authentication user name and password are verified working.

Status of that cloud connector

Status of connection in BTP

I set up a "Destination" in BTP as a test as well just to see and that checks out.

But, now In integration suite if I try and use this in a SMB Adapter in an iFlow I get errors (some details obscured, my company is very sensitive)

All of the parameters are 100% correct (as long as this is what is supposed to go there).

Address is the virtual address I have set up.

Location ID is the Location ID is have set up in Cloud Connector on the Windows Machine

Share is the name of the Share Drive I'm trying to access via SMB on the Windows Machine

Credentials Name is set up and deployed and verified as correct username and password that can access the SMB share at the destination.

"org.apache.camel.CamelException: <Exception><Message>Error in Session connect: On-Premise connection failed for bXX-XXX:445. Ensure cloud connector is configured correctly for location id : us-XXX-XXX and host is exposed correctly in your cloud connector. SMB uses TCP as protocol. Error : SOCKS5 command failed with status: NETWORK_UNREACHABLE</Message></Exception>"

Also, in Integration Suite, if I go to "Monitor->Manage Security->Connectivity Tests->Cloud Connector"

and put in my location ID the only feedback I get is "Could not connect to Cloud Connector" error.

Not sure how to proceed to try and get this working.

Unable to authenticate backend system from SAP BAS via Cloud Connector – “Authentication incorrect”

2025-11-24T07:45:40.372000+01:00

Hello Experts!!

I am trying to consume an on-premise S/4HANA system from SAP Business Application Studio (BAS) using SAP Cloud Connector and a BTP Destination.

The Cloud Connector connection is reachable, and the Destination is visible inside BAS, but when I select the destination (“S4H”) in the SAP Fiori Generator wizard, BAS returns the error:

"Authentication incorrect. Please check the SAP BTP destination authentication configuration."

Even when I remove authentication from the BTP Destination and directly enter credentials in the BAS wizard, the same error appears.

I can successfully log in to the S/4HANA backend via SAP GUI with the same user and password, and the SAP Easy Access screen loads correctly.
However, BAS / Cloud Connector authentication fails.

Datasphere: Issues creating data federation connection between datasphere and S/4hana on-prem

2025-12-01T15:47:53.471000+01:00

Hi guys,

we´re currently in the process of connecting our datasphere to S/4HANA on-Prem using ABAP SQL services for data federation. We´re struggling to establish the connection with S/4HANA

During setup we followed the official documentation:

We get the following error message when trying to import remote tables in datasphere.

According to SAP Note 3076454 we have to install the ODBC driver on S4. However S4 team informed us no ODBC is required on S4 side but the pre-installed in datasphere is sufficient. Hence I´m a bit confused whether ODBC is needed on S4 for our scenario, any thoughts from your side?

In addition we have already checked Note 3586001 (https://userapps.support.sap.com/sap/support/knowledge/en/3586001), but haven´t been able to resolve this matter.

We´ve already double checked:

Cloud connector settings
Firewall (hanacloud.ondemand.com / k8s-hana.ondemand.com) and whitelisting all necessary IPs

Everything seems fine.

The S4 connection is validated reachable in cloud connector.

We looked into the cloud connector logs and see a failing handshake request and terminated connection due to SSL/TLS communication. Any advice how to approach this matter further? Looks to me we might have some certificate issues between cloud connector – BTP – Datapshere - S4, but that´s not really my area of expertise.

Any help appreciated!

Connect to Onprem LDAP Destination from CAP (Nodejs) App running in K8s cluster???

2025-12-03T10:22:57.877000+01:00

Hi All,

We have a requirement where we have to display users when a Cost Center value is entered.

We are looking to use LDAP protocol to fetch user details and have a working setup locally via ldap client

We have Kubernetes setup where we deploy our applications. We are looking for documentation/ gudance on how to connect to this on prem destination with SAP BTP connectivity service.

We use Transparent proxy, connectivity proxy intalled in the cluster and Destination and Connectivity services, cloud connector from BTP.

Though there is SAP help documentation, we dont have much clarity on how this can be done in CAP.

Looking forward for suggestions/support if someone has already implemented it.

We also interested in knowing if Default SAP IDP provides API's using which we can fetch the user data.

Thanks in Advance.

How to Export Analytical Model Output from SAP Datasphere to Azure Data Lake Storage?

2025-12-03T17:51:46.079000+01:00

Hello Experts,

I am working on a requirement where I need to export the output of an Analytical Model in SAP Datasphere into Azure Data Lake Storage (ADLS).

Connections to both Datasphere and Azure are already established.

Question:
Is there a way to export Analytical Model data into ADLS?

I attempted to create a Replication Flow with Datasphere as the source. However, when selecting the source object, I only see:

Local Tables
Fact Views
Dimension Views

The Analytical Models do not appear as selectable source objects.

Has anyone implemented this scenario or knows if Analytical Models are supported in Replication Flows or if there is an alternative approach?

Thanks in advance!

SAP Datasphere Cloud Integration Cloud Connector

Setup cloud connector to connect to non sap on premise application with 2 way ssl

2025-12-11T21:53:23.501000+01:00

Hello Experts,

I am new to the cloud connector topic and looking for a confirmation if cloud connector can setup 2 way SSL with on prem servers and authenticate using the client certificate authentication method for https connections.

I checked sap help pages but did not find the relevant information to further confirm this setup. If possible, share any blog or help links for step by step guide.

Thanks for your time.

Regards,

Rahul

Cloud Connector

2026-01-19T20:31:56.224000+01:00

Hi everyone, I'm trying to establish a BTP connection using Cloud Connector, but I'm getting this error when I enter the host and port information. Has anyone encountered this before?

Enabling WebSocket for Fiori Elements app

2026-01-28T09:11:36.862000+01:00

Hi,

I have a few Fiori elements apps that use event driven side effects as well as collaborative drafts. Both of these features are using websocket connection to receive changes from backend. All apps work fine when they are deployed to ABAP AS and accessed via Fiori launchpad hosted directly on ABAP AS.

The main problem is that the ws connection does not work when apps are deployed to HTML5 repository on BTP and exposed via SAP Wokrzone. I adjusted xs-app.json to contain websockets section as well as I enbabled Cloud Connector connection for WebSockets. The ws connection still does not work. The apps work but the connection is not established so there are no real time updates.

Secondary issue is that the ws connection does not work when developing locally in VSCode. I am runnig proxy in Fiori Tools with setting ws: true but the connection still does not get established.

What else needs to be set to enable ws connections from BTP down to backend system? What could be blocking the ws connections?

Thanks

Principal Propagation via SAP Build Work Zone for S/4HANA content not working.

2026-01-28T14:17:20.090000+01:00

Hi everyone,

we configured principal propagation and exposed our S/4 content as described on the following blogs:

It worked fine when we used basic auth in Runtime Destination. When switching to principal propagation it looks like this:

Console log:

Heres our Design time

Runtime

We also updated the channel manager in work zone after editing the destinations.

SCC Log doesnt show anything suspicious.
Greetings
Rouven

SAP Cloud Connector - websocket connection in SAP cloud connector and Hive MQTT

2026-02-03T09:51:25.061000+01:00

Hi Experts,

Business Scenario: Hive MQTT Broker is using 8883 for HTTPS and 8884 ports for WSS. we want to connect our SAP Cloud Connector with Hive MQTT using WebSocket port. we have some of the question as below:

Question -1 : can we setup connectivity between Hive MQTT broker and SAP CC on WSS?

Question -2: if there is a way to achieve it, can anyone please guide as how we can implement this in our system.

any help/guidance will be appreciated.

Feel free to pose any question if you have related to requirement.

Regards,
Ankit Gupta

cap application failed while deploying schema to sap hana cloud

2026-02-04T12:58:29.142000+01:00

I am trying to deploy my DB to SAP HANA CLOUD, But after binding the database connection and deploying getting the following error
The purpose of this task is to deploy schema in SAP HANA PROJECT ( Database explorer )
error:
Error running command _hanaExplorerView.deployFromTree: Deployment failed with code 1, see terminal for more details. This is likely caused by the extension that contributes _hanaExplorerView.deployFromTree.

log:
* Executing task in folder db: echo 'Prepared environment for deployment' && (npm ls --depth 0 --production || npm install) && (node ../db/node_modules/@sap/hdi-deploy/deploy.js "--exit")

Prepared environment for deployment
npm warn config production Use --omit=dev instead.
/home/user/projects/CAP_02/db
└── (empty)

npm error code EJSONPARSE
npm error JSON.parse Failed to parse root package.json
npm error JSON.parse Failed to parse JSON data.
npm error JSON.parse Note: package.json must be actual JSON, not just JavaScript.
npm error A complete log of this run can be found in: /home/user/.npm/_logs/2026-02-04T11_28_51_389Z-debug-0.log
npm error code EJSONPARSE
npm error path /home/user/projects/CAP_02/db/package.json
npm error JSON.parse Unexpected end of JSON input while parsing empty string
npm error JSON.parse Failed to parse JSON data.
npm error JSON.parse Note: package.json must be actual JSON, not just JavaScript.
npm error A complete log of this run can be found in: /home/user/.npm/_logs/2026-02-04T11_28_51_767Z-debug-0.log

* The terminal process "/bin/bash '-c', 'echo 'Prepared environment for deployment' && (npm ls --depth 0 --production || npm install) && (node ../db/node_modules/@sap/hdi-deploy/deploy.js "--exit")'" terminated with exit code: 1.
* Terminal will be reused by tasks, press any key to close it.

Package.json
{
"name": "CAP_02",
"version": "1.0.0",
"description": "A simple CAP project.",
"dependencies": {
"@cap-js/hana": "^2",
"@sap/cds": "^9",
"@sap/xssec": "^4",
"express": "^4"
},
"scripts": {
"start": "cds-serve"
},
"cds": {
"build": {
"tasks": [
{
"for": "hana",
"dest": "../db"
},
{
"for": "node-cf"
}
]
},
"requires": {
"db": {
"kind": "hana-cloud"
}
}
}
}

CAP-consuming on-premise OData API : read ECONNRESET error. 'Error during request to remote serv

2026-02-18T19:11:01.425000+01:00

Hello, I am not a developer — my background is more functional — but I am trying to build a small study case for my own learning. Please excuse any basic mistakes; I am open to feedback and to deepening my understanding.

My scenario is the following: using a BTP trial account, I am creating an application in SAP Business Application Studio (BAS) and connecting it to an SAP S/4HANA system. In this application I also plan to call the OpenAI API.

Currently I am getting the error:

[error] - 502 > {
code: '502',
message: 'Error during request to remote service: read ECONNRESET'
}

This happens when I call the API API_JOURNALENTRYITEMBASIC_SRV from an S/4HANA environment. The S/4 system is a cloud (RISE) environment from an account where I do not have admin access — only SAP GUI access — so I am using SAP Cloud Connector.

What I have already tried:

I changed the backend system — I have access to two different infrastructures — and I get the same error in both.
I cannot set HTTPS in the BTP destination; even with TrustAll = true the BTP destination configuration does not allow it.
I have already reviewed and recreated all my destinations.
I triend, using AI, change my js files, cds and everything but always fail in the same issue.

[error] - 502 > {
code: '502',
message: 'Error during request to remote service: read ECONNRESET'