Connect SAP S/4HANA Cloud Public Edition using Cartograph’s Public Cloud wizard. Your SAP administrator must prepare supported inbound access and the services your workspace will use before the connection can be validated.
Choose the hosting model carefully. Public Cloud and Private Cloud/On-Premise use different setup paths. Validate the connection and data sync before enabling operational automation.
Before you start
You need Cartograph integration administration access and an SAP administrator authorized to configure inbound access. Have the tenant’s API URL and OAuth credentials ready in the secure setup flow.
Choose the correct SAP hosting model before beginning setup.
Connect the Public Cloud system
Confirm with your SAP administrator that this is Public Cloud, and identify the tenant, SAP release and required business objects.
Have the administrator prepare the communication setup and supported OAuth 2.0 Client Credentials access for the intended services. Use SAP’s documentation for the exact release and communication scenario.
In Cartograph, open Settings → Integrations → Add integration → SAP S/4HANA. Select Public Cloud and choose Next.
Read the introduction and choose Confirm and begin setup when ready to create the connection setup.
Enter the tenant URL requested by the wizard, then the OAuth Client ID and Client secret from the prepared SAP setup. Use the exact tenant URL supplied by your administrator.
Complete the connection checks and review the available services and access. Configure the required data sync, run it through the product controls and compare representative records with SAP.
Check the result
The connection is healthy, the required services are accessible and an actual data sync produces correct records. Successful authentication alone does not prove that every business object is available or correctly mapped.
SAP preparation checklist
Confirm the communication arrangement and authentication method supported for each required service. A communication scenario can constrain which methods and operations are supported.
Verify the OAuth client’s scope, service activation and business authorization. A client that can obtain a token may still be unable to read a particular endpoint. Do not assume a communication-user password is universally interchangeable with an OAuth client secret.
Use the API tenant address
The wizard’s example is https://myXXXXXX-api.s4hana.ondemand.com. It is an example, not a universal hostname. Use the API endpoint for your actual tenant and landscape.
Keep credentials in the secure connection fields. Do not place secrets in knowledge articles, task descriptions or screenshots.
Validate the business data
Check source identifiers, supplier and material links, order lines, quantities, units and date meaning. Requested, confirmed and expected dates describe different events.
Data sync pipelines choose which data is imported and how it maps. Review missing values and relationships before relying on Signals or Line of balance.
If something does not look right
What you see | What to check |
Authentication fails | Check the tenant URL, OAuth client, secret and the supported authentication setup for that SAP release. |
Authentication succeeds but a service fails | Check service activation, communication arrangement, scopes and business authorization with the SAP administrator. |
Records are incomplete or stale | Inspect the pipeline’s published version, mapping and latest run result. |
Does the connection import every SAP object?
Does the connection import every SAP object?
No. Available services, permissions and configured data sync determine the imported scope. Verify the objects your workflow actually requires.
Can I use these instructions for Private Cloud?
Can I use these instructions for Private Cloud?
Use the separate Private Cloud and On-Premise guide. That path also collects the SAP client and can require network or certificate setup.
Continue your work
Open the relevant area in Cartograph to continue with your workspace data.
SAP reference
Select the documentation for your release and required communication scenario with your SAP administrator.