Paul Hamerman

Paul Hamerman
achieve approach code developing generation integrate java legacy move multiple next open oracle pure retain sap task though whereas
SAP is going to retain a lot of its proprietary ABAP code in developing its next generation SOA applications whereas Oracle's approach is to try to get away from legacy and proprietary code and move to a pure Java J2EE environment. Even though the task Oracle has is more complicated in that they have to integrate applications from multiple acquisitions, they will achieve a more open kind of environment.
compare entire interface microsoft office provide sap useful
Compare that to what SAP and Microsoft are doing jointly to provide some useful functionality and you'll see that Microsoft is retooling entire interface around Office and that is much more extensive.
compliance deadline gain imposed meet minimum systems time underlying
The first time around with SOX, there was an imposed deadline and everyone scrambled to meet minimum compliance requirements. Now, it's time to look at the underlying systems and processes, and see how they can gain efficiencies from them.
base increased maintained
As they have made these acquisitions they have maintained the maintenance base and even increased it.