How is everyone doing keeping “code current”?
Code currency is an arduous task, but it really does not need to be. We need to transfer the power from the dark arts of CNC to the blissfully easy world of BI reporting – surely! Is that not the panacea for all problems. No, I agree - it's not going to be that easy.
I’ve been working on a suite that can tell you everything you need to know about being code current, including items like:
- How modified an object is – to help you gauge retrofit
- How much you use the object (in terms of users, engagement time and also page loads)
- Is the code the same as current ESU level from oracle?
The above points alone would allow you to look at all of your code, and then determine how far from pristine you are. It would allow you to then look at usage and modification information and then choose how much effort you need to put into getting yourself code current.
As soon as you make changes and promote to prod, all of the reports can be updated to reflect this…
For example, the report of gold is a “honey pot” for determining code currency
This shows you all JDE applications being used and how much they are being used.
This report is comparing the code at this site with the latest oracle patches (yes true, this is what is being done) and can tell you if the code is a binary equivalent or not to the latest ESU's from oracle.
It’s only listing the programs that are not the same as the latest pristine
Clients can see what objects are being used and they can also see how much screen time and how many users are using the objects (for the specified date range)
All these data points allow clients to make better decisions on what modifications to keep. You can quickly see those that are not use by many people and have many OMW actions – mods that are not used… Get rid of them
You can quickly slice and dice by system code and know what needs to be tested when you get code current.
One of the nice things is that we keep a copy of pristine updates with all ESU's and then we generate hashes (like a unique signature of the code) in a cloud based database. We have code that will enable you to create a signature of your code and viola - we can tell if you are the same as PS920 with ALL the ESUs.
You can see from the above that we can have a very similar view for reports.
We can see how often the reports are run and only see those that have changed in the latest code from oracle.
This allows us to see the reports that we need to retro
I think that with a dashboard like the above (note that you can actually compare all object types
