Just when you thought you’d seen everything after 20+ years in the ever-changing SAP world, you come across something new. That is a customer who required a continuous delivery pipeline for SAP changes. As part of the scope of work, the organization wanted a seamless integration with legacy tools including Jira, ServiceNow, while dipping a toe in the water with Micro Focus and Jenkins.
Recently, Rev-Trac announced it won’t charge additional license fees for integration to 3rd party applications like ServiceNow, HP, ALM etc. Also, customers on the current 7.x version of Rev-Trac can leverage the value of our SALT application without the burden of additional license costs.
I’ve worked specifically in SAP change management for more years than I care to mention, and one thing I’ve heard repeatedly is the need for a reliable method of checking inter-object dependencies between transports.
As many know, Revelation Software Concepts’ (RSC) focus is on developing world class change control automation software for SAP. Our flagship product, Rev-Trac is an ever-evolving automation platform to facilitate the simplification and transformation of managing SAP change. Regardless of an SAP IT team’s development or delivery method, Rev-Trac has evolved to ensure success.
Before heading to Las Vegas this week for SAP TechEd, I have had to take my bride to the hospital. It was for one of those common check up type procedures that we have to get from time to time. As I sit here, patiently waiting, I started to think of the importance of health checks more broadly. Believe it or not, SAP change management processes came to mind.
After many years analyzing customers’ change control processes we’ve learned that no two processes are ever the same. However, I’ve noticed that when a company sets out to improve their change control processes, they tend to make them more complex than necessary. Particularly when attempting agile processes for the first time.
In the rush to get to SAP’s HANA database, some customers have not given proper consideration to the Z-code that has been developed over the years and its compatibility with the new DB. During the initial SAP implementation, nearly every company that I know of was “special” in some way and choose not to go with the SAP standard. Therefore, we all have substantial Z-code we used to fill that and other gaps in our processes. Now with the HANA DB on the scene, some are finding that post migration, some of their Z-code either won’t work or has some serious performance issues running on the HANA database.
Join the Rev-Trac newsletter and we'll keep you informed of the new articles, resources and updates.
I’d like to take credit for this, but can’t as I just heard it and I’m not even sure where I heard it, but it resonated with me…!
The gist of the article/conversation was that with more and more change automation being available to us, the desire for Agile change processes and the overall desire for speed of development, the comment was that going forward we should not be asking who is going to approve the change, but rather what is going to approve the change.
