Tips, Expertise, Articles and Advice from the Pro's for Your Website or Blog to Succeed
"By my estimate, more than 89% of the S/4 transformation is still to be done."
As I was preparing for a recent webinar, I was looking for data on the current state of S/4HANA adoption from ECC customers, and what I found was quite interesting.
A question I get every week from customers across the globe is, "How can I integrate my SAP system with Apache Kafka?" This post explores various alternatives, including connectors, third party tools, custom glue code, and trade-offs between the different options.
After exploring what SAP is, I will discuss several integration options between Apache Kafka and SAP systems:
In part one of this blog, I provided a high-level introduction to SAP Systems, Clients, Landscapes, and Transports and how they might fit together in a ‘standard’ configuration. But like life, SAP tends to be a bit more complicated than that. The reality of marrying architectural constraints with complex business needs means that the kind of simple landscapes I described in my last piece often will not do the job. Something more complex is required.
In this article - part two of three - I will look at some of the more advanced concepts associated with SAP Landscape Design and how to manage the increased complexity that comes with them.
Regression testing of SAP changes is a bit like flossing: everyone knows they should do it, but in practice, it’s something that only gets done sometimes, and usually not very thoroughly.
To stretch the metaphor further — everyone knows substandard flossing can have nasty results, maybe even the loss of a tooth or two. It’s the same with regression testing: everyone knows poor coverage means defects can slip through into production, causing errors and downtime in business-critical systems.