SAP APO vs. PeopleSoft's Advanced Planning engine

SAP APO vs. PeopleSoft's Advanced Planning engine

We're a supplier of parts & devices for wireless technology, and we're trying to move to a truly global "available to promise" environment. We have 60,000 customers worldwide that we sell to via multiple types of channels (direct, 3rd party partner sales, Web-based ordering, OEM deals). We recently received SAP's Advanced Planner and Optimizer (APO) solution. We are now grappling with the fact that, a few years ago, we installed Peoplesoft's Advanced Planning engine (formerly the Red Pepper product). Do you recommend completely overhauling the whole infrastructure and going to a pure SAP shop?


    Requires Free Membership to View

    When you register, you will start receiving targeted emails from my award-winning team of editorial writers. Our goal is to keep you informed on the hottest topics and biggest challenges faced by SAP professionals today.

    Hannah Smalltree, Editorial Director

    By submitting your registration information to SearchSAP.com you agree to receive email communications from TechTarget and TechTarget partners. We encourage you to read our Privacy Policy which contains important disclosures about how we collect and use your registration and other information. If you reside outside of the United States, by submitting this registration information you consent to having your personal data transferred to and processed in the United States. Your use of SearchSAP.com is governed by our Terms of Use. You may contact us at webmaster@TechTarget.com.

I have found that the philosophy "if it's not broken, don't fix it" suits most situations. While you could certainly rip out all of your existing infrastructure and move to a "pure" environment, you likely will not achieve your Global ATP "end state" any more efficiently. The idea is to achieve greater efficiencies with new SAP functionality that makes sense, but not at the expense of jeopardizing the cost and timing of the project by pulling out solutions that are still effective. Try taking a more fluid approach to how to use software, and what pieces you use (remember, just because you have APO doesn't mean you have to use the whole thing immediately) while remaining firm on what ultimately need to achieve.


This was first published in November 2002