Avoiding SAP Audit Risk when Replicating

Originally published · Updated

The short version is on What SAP's change means for your data. This post is the longer story.

SAP pushes. Nothing pulls.

Simplement ODP Audit SAP Note 3255746

SAP Note 3255746

For years SAP has been saying DON’T USE ODP/ODQ for external CDC! This goes back to at least 2017. Note 3255746 has been revised multiple times, with each update reflecting SAP’s escalating efforts to restrict this activity and the associated risk of penalties.

SAP Audit

There is great risk of an SAP audit (which is their absolute and legal right) and/or risk that SAP will render the interface technically inoperable for external RFC.

This has put so many SAP customers at risk (Remember the Diageo licensing case anyone?) because vendors selling ODP CDC aren’t SAP experts. They view SAP as just another piece of software – without understanding the special, central place SAP occupies in an organization.

And that is where we are today – companies were sold a “CDC Solution” that was too good to be true.

The SAP Piper is getting his flute out of the case, and the tune isn’t one that most want to hear.

A Different Path

At Simplement, we chose a different path. We have been working with SAP since 1998 and have always respected their covenants and guidance. When we built Roundhouse, we researched and followed the rules.

Roundhouse has:

  • Zero reliance on ODP/ODQ
  • No direct database connection (no ODBC/JDBC)
  • Application layer integration

Start with the data. Add the answers when you want them.

When we built Roundhouse, we researched and followed the rules.

Book a live demo