Use Cartograph’s private SAP connection path for SAP S/4HANA Private Cloud and On-Premise systems. Coordinate network reachability, SAP client and inbound authorization before completing the wizard.
Keep authentication credentials and CA material in the supported secure setup flow. Use screenshots with no secrets when asking for help.
Before you start
You need Cartograph integration administration access, an authorized SAP administrator and the team responsible for network and certificates. Obtain credentials through your organization’s secure process.
Private Cloud and On-Premise use the private SAP connection path.
Connect the private SAP system
Confirm the hosting model and identify the correct SAP system, release and three-digit SAP client with your administrator.
Have the SAP administrator register the required OAuth 2.0 client and enable the intended services and authorizations. Arrange approved network access from Cartograph to the system.
Open Settings → Integrations → Add integration → SAP S/4HANA. Choose Private Cloud or On-Premise, then Next.
Read the introduction and choose Confirm and begin setup when ready to create the connection setup.
Enter the system’s HTTPS host, SAP client, OAuth Client ID and Client secret in the secure fields. Supply the supported custom CA certificate when your environment requires it.
Complete the connection checks, review available access and configure the required data sync. Compare representative imported records with the intended SAP client.
Check the result
The connection reaches the intended SAP system and client, authenticates successfully and can read the services the workflow requires. A completed import has correct record values and relationships.
Network and certificates
Use a reachable HTTPS endpoint and the correct port when your landscape uses a custom port. A URL that works only inside your office network is not necessarily reachable from Cartograph.
Coordinate firewall, routing and certificate trust with the infrastructure team. Use the supported custom CA field when needed; do not disable certificate validation to make a failed connection pass.
SAP client and authorization
The SAP client selects the relevant logical environment in the system. Confirm it before importing so records do not come from the wrong business context.
OAuth configuration and OData service activation vary by release and landscape. Use SAP’s release-specific administration instructions rather than copying a Public Cloud communication scenario into a private system.
Check the imported scope
Inspect the published pipeline, filters, mapping and recent runs. Verify a representative supplier, material and order line against SAP, including units and requested versus confirmed dates.
Connection success, import success and write-back success are separate checks. Verify the actual source result before relying on an update going back to SAP.
If something does not look right
What you see | What to check |
The host cannot be reached | Check DNS, HTTPS port, routing and approved network access with your infrastructure team. |
A certificate check fails | Review the certificate chain and supported custom CA configuration. |
The wrong records appear | Check the SAP client, source filters and mapping before running more imports. |
Is Private Cloud the same path as On-Premise?
Is Private Cloud the same path as On-Premise?
Both use the private connection flow, with hosting selection, system host, SAP client and OAuth configuration. Their network arrangements can differ.
Does a working login prove every service works?
Does a working login prove every service works?
No. Check the specific service and business authorization, then validate the actual import.
Continue your work
Open the relevant area in Cartograph to continue with your workspace data.
SAP reference
Choose the release and administration guidance that matches your landscape.