So, the crux at what I'm getting at is the layout/structure of OOTB Procedures/Functions.
When the System Journal says something like 'Procedure X failed on Line Y' is not much help when "Line Y" is not really relevant as the SQL code within the Procedures/Functions as it is 'minimized' making finding the line close to impossible (especially with some of the large procedures).
If they could be formatted, then when the system responds that 'Line Y' failed, it actually matches the position on the code making it less of a time consuming exercise to diagnose. This is especially problematic when the procedures are chained through a spiders' web of mish-mash 
.