SAP BTP and Integration Suite

Integration flows, monitoring and clean-core extensions on SAP Business Technology Platform, from engineers who have connected SAP to everything else since the IDoc.

Book A Consultation
GlueData
Sanlam
Wastepro
FINN
Southco
OSIsoft
Sports Basement
SALT Analytics
AME Africa
Lock & Stern
ClearOn
WEG
Savantis
Sanquin
Hua Hai Pharma
Rumpke
GlueData
Sanlam
Wastepro
FINN
Southco
OSIsoft
Sports Basement
SALT Analytics
AME Africa
Lock & Stern
ClearOn
WEG
Savantis
Sanquin
Hua Hai Pharma
Rumpke

What we do

  1. We connect SAP to the rest of your landscape.

    Integration flows in SAP Integration Suite (CPI) between S/4HANA and your banks, customer platforms, procurement networks, payroll and the systems nobody wants to admit are still there.

  2. We run integration through one point.

    Every interface through Integration Suite rather than a tangle of point-to-point connections, so there is one place to look when something stops and one place to change when something moves.

  3. We watch the flows so you do not have to.

    Alerts and message monitoring reviewed every day, failed messages reprocessed by us, and the recurring error traced to its cause instead of restarted every morning.

  4. We extend SAP on BTP instead of modifying it.

    Side-by-side extensions, apps and services on SAP Business Technology Platform, so the core stays clean and the next S/4HANA release is an upgrade, not a rewrite.

  5. We design before we build.

    Design decisions on what runs in SAP, what runs on BTP and what runs elsewhere, made with you and written down, so the landscape still makes sense in three years.

  6. We keep what moves between systems under control.

    Transports tracked for what is in them and why, custom code versioned in Git the moment a transport is released, so nothing overwrites production unnoticed.

What that looks like in practice

The interfaces nobody could see

A landscape had its integrations spread across file drops, direct connections and a few flows in Integration Suite, and failures were found by finance when a payment did not go out. We brought the interfaces onto one integration layer with monitoring and alerting. Failures are now caught by us in the morning, before the business starts its day.

The launchpad that stopped after the upgrade

After an S/4HANA upgrade the Fiori launchpad simply stopped working and users were locked out of their apps. The obvious causes checked out fine, so we went through every transport applied during the upgrade. One had quietly reapplied an old launchpad template through the upgrade adjustment, which broke how the new support pack applies the theme. Restoring the standard template fixed it; upgrade adjustments are now reviewed before go-live, not trusted.

The flow that failed every night

An integration flow errored on the same step most nights and was restarted by hand each morning. We read the error log properly instead of restarting: a partner system was returning a changed format after their release. The mapping was corrected, retries added for the transient cases, and the morning restart disappeared from the routine.

Where SAP integration goes wrong

The same four things, in almost every landscape we inherit.

  • Point-to-point interfaces nobody owns end to end: the file side blames SAP, SAP blames the file.
  • Alerts that go to a mailbox nobody reads, so failures are found by the business.
  • Extensions built as modifications to standard code, paid for again at every upgrade.
  • Integration flows with no error handling, restarted by hand every morning.

What we work in

Every service, protocol and practice our integration engineers use, by layer.

SAP Integration Suite

  • Cloud Integration (CPI) flows
  • API Management
  • Event Mesh
  • Open Connectors
  • SAP Cloud Connector
  • Integration Advisor
  • Message monitoring and alerting

SAP BTP

  • SAP BTP (Cloud Foundry)
  • Side-by-side extensions
  • SAP Build Work Zone
  • Fiori launchpad and catalogs
  • Destinations and connectivity
  • BTP cockpit administration

Protocols and formats

  • IDoc and EDI
  • OData and SAP Gateway
  • SOAP and REST
  • SFTP and file interfaces
  • AS2 and partner connectivity
  • JSON, XML and flat-file mapping

Partners and endpoints

  • Banks: ACH, statements and positive pay
  • AP automation and invoice capture
  • SAP Ariba CIG
  • Salesforce and CRM
  • Payroll and HR platforms
  • Route, dispatch and warehouse systems

Practice

  • Interface design and documentation
  • Error handling and retries
  • Transport tracking with Git versioning
  • Upgrade adjustment review
  • Cutover and hypercare

Signs you need us

  • An interface fails and two vendors blame each other.
  • Someone restarts the same integration flow every morning.
  • Nobody can draw the landscape’s interfaces on one page.
  • Every upgrade pays for the modifications again.
Talk to an integration engineer

You can find us here

We have a strong global presence, marking our commitment to delivering tech excellence in key markets worldwide.

Colorado
14133 Downing Street Brighton,
Colorado 80602
Contact us
Cape Town
Regus Business Center, 1st Floor,
Willowbridge, Cape Town
Contact us
Haarlem
Frame Offices B.V.,
Haarlem, Netherlands
Contact us

AI that reads the integration log

The ETZ AI Platform reads your integration errors, logs and mappings, explains what failed and why in plain language and proposes the fix, with SAP-grade authorisation and an audit trail on every action.

See the ETZ AI Platform Book a consultation
  • Runs in your own SAP BTP subaccount. SAP data never transits ETZ.
  • Your SAP authorisations decide what it may see and do, not the AI.
  • Every action lands on an append-only audit record.
Available on the SAP Store (opens in a new tab)