Setting the correct change management procedure can be challenging. You need to capture the right things and not too much.
For one SAP PI/PO client, I just had to do development in Dev, and then move to production to test. I was really uncomfortable doing this.
Another client requires a lot more effort to do the transportations needed. Here is multiple checks and validations to do transports. Here it takes too long time to do something.
That is the reason I believe there is a Goldilocks zone for change management you need to do not too little and not too much.
In many places, people are just trying to implement the same changes that they have to do ERP changes. Which is probably not ideal for transporting SAP PI/PO objects. I have been spending a lot of time making documentation that was not ideal.
In my example where I had to change a field in the XML formats it would be nice if I could mark the changes and then use it. The more manual work you are going to do the more difficult it will be to make the documentation and ensure it is correct. And how do you find it when it is necessary. So at the client, I worked where we had a lot of documentation we could just capture a few lines text about what we had done on the interface. Finding it again would be difficult because how did you find the message mapping information.
For SAP PI/PO we are working to improve our Change Tracking tool that allows you to do better change management on your landscape. We have currently been looking at just directory objects, but in the next, release we will also have documentation of repository objects. This will allo you to assign a ticket and a description of why something was changed. You can then see for a message mapping when something was changed in it and why. You can also do an easy comparing between the versions to find the differences.
Read more at http://figaf.com/ctt