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

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

Reading time: 17 mins

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 Premium Members.

Sign In Learn more about Premium Access

Meet the Experts

More Resources

See All Related Content