Near-Perfect SAP Is Easier to Achieve than Good SAP Is: Part 2

In this Part 2 of his Lessons Learned series, SAP simplifier Kurt Goldsmith walks project managers through achieving Near-Perfect SAP projects. What does that mean? Whereas good = easier and great = hard in other contexts, Kurt’s decades of SAP experience have taught him that good = hard while great = easier when it comes to SAP. This how-to continuation focuses on the tactics that become possible with the five categories from Part 1 as a target, including a case study to help ground readers in the concepts. Read this article to understand:
• The two kinds of business requirements an SAP system can help with, and how
• The variations in ERP that those functionalities must individually allow vs. prevent and must collectively count and allocate

This content is available to SAPinsider Premium Members.
Please click below to log in or create an account

Login Now »

Create Acount»


Kurt Goldsmith SAP Solutions Director, Tata Consultancy Services
Read More

Kurt Goldsmith is an SAP Solutions Director for Tata Consultancy Services (TCS). 25 years, and 18 sites, Kurt specializes in clients with highly aggressive project needs in regards to functionality, timeline, or budget complexity. Relentlessly in pursuit of SAP simplification, he co-created in 2002 with Wellesley Information Services (WIS) a condensed format SAP Education concept that became the SAP Financials Expert monthly newsletter. An MBA graduate (University of Texas at Austin), Kurt in his spare time enjoys proving repetitively that it is impossible to win at wagering on thoroughbred horse races.  You can reach Kurt at