Home
Categories
EXPLORE
True Crime
Comedy
Society & Culture
Business
Sports
History
TV & Film
About Us
Contact Us
Copyright
© 2024 PodJoint
00:00 / 00:00
Sign in

or

Don't have an account?
Sign up
Forgot password
https://is1-ssl.mzstatic.com/image/thumb/Podcasts/v4/53/e6/f0/53e6f082-8332-f7aa-1544-29fcf4e2c59a/mza_3753440219135836156.jpg/600x600bb.jpg
Art & Science of Being an IT Architect
Philip Hartman
6 episodes
2 weeks ago
A mix of crisp insight and totally random thoughts on software development, estimating, corporate politics, consulting skills, and more.
Show more...
Technology
RSS
All content for Art & Science of Being an IT Architect is the property of Philip Hartman and is served directly from their servers with no modification, redirects, or rehosting. The podcast is not affiliated with or endorsed by Podjoint in any way.
A mix of crisp insight and totally random thoughts on software development, estimating, corporate politics, consulting skills, and more.
Show more...
Technology
https://is1-ssl.mzstatic.com/image/thumb/Podcasts/v4/53/e6/f0/53e6f082-8332-f7aa-1544-29fcf4e2c59a/mza_3753440219135836156.jpg/600x600bb.jpg
Perils of Over-Customizing SAP-Broken Reports
Art & Science of Being an IT Architect
1 minute
17 years ago
Perils of Over-Customizing SAP-Broken Reports
I've been around clients for some great discussion on the perils of over-customizing SAP lately. I hope to collect some of the lessons learned here for your reading enjoyment and career enrichment. Here's a comment made by a country sales manager at a meeting I attended in May 2007. "They told us that the new SAP system would have over 160 reports out-of-the-box that we could use to run our business and we didn't plan on having to create a lot of custom reports. Now they tell us that's not true. Almost all the out-of-the-box reports are broken. Almost every report we need must be a custom development." It seems this company made some customizations to their base SAP system (ECC) when they were only operating in a only single country and were focused only on a transactional, commodity type business model. They then moved into multiple countries and began to look closely at big, relational customers and value-added services. To support this, they planned to create a new CRM system running on top of their existing ECC. They were not happy to find out that their legacy of prior ECC customizations "broke" a lot of the standard SAP reports. I'd love to hear from other people who might have an SAP over-customization lesson to share. Copyright © 2007 by Philip Hartman - All Rights Reserved
Art & Science of Being an IT Architect
A mix of crisp insight and totally random thoughts on software development, estimating, corporate politics, consulting skills, and more.