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.
It’s hard to believe, but the SAP COE has been around for more than 21 years. SAP COE’s started around the same time that Rev-Trac did and it’s safe to say that they began for many of the same reasons. That is – in general – to help SAP customers reduce the cost of operations, provide a required level of governance and continually improve SAP processes.
A frequent exercise for many SAP organizations is to refresh SAP QA Systems from Production. This ensures that suitable and up-to-date data is available for testing. With testing becoming increasingly important the need to refresh QA Systems is also on the rise.
When it comes to managing SAP changes, things are beginning to look different for SAP IT teams. Building a DevOps capability is becoming important.
Reflecting the need to provide steady state, stable SAP enterprise systems, things like control, governance, cost reduction and stability have been important for SAP IT teams for a long time.
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.
It’s a bit late for New Year’s resolutions already in the first half of February, but with 10 ½ months of 2018 left, here are three quick questions with corresponding resolutions to help simplify and improve your SAP change management processes
It can be difficult keeping SAP landscapes consistent. For example, as Quality Assurance environments are refreshed, over time systems can begin to get out of sync. The number of DEV system transports existing only in the development system, unlikely to ever be moved to Production, grows.
I’ve been spending the last week or so travelling and speaking with customers and potential customers. In two consecutive meetings, two SAP IT team leaders from two different companies told me the exact same reason for automating their SAP change control processes.
Over the last few posts I’ve been discussing some of the things SAP IT teams will need to address on their journey to accelerated SAP change delivery. In my previous post I explained the need for process maturity and process automation. This time, we will look at the value of multi path development and release management.
Recently, I came across a post outlining the steps for development teams to successfully start a DevOps transformation. In his post, John Jeremiah, points out that for a successful proactive transformation certain stars need to align. That is a business need for velocity and speed and management’s impatience with the current pace of change.
However, in speaking with SAP IT teams looking at a DevOps transformation it almost always is in reaction to pressure from the business rather than a proactive change in approach. So how can an SAP IT team better anticipate the need for change and become a little more proactive?