Pitfalls of not planning for the SD-module from the start

Pitfalls of not planning for the SD-module from the start

We are just starting an SAP R/3 project for FI/CO/MM/PP with the addition of SD in the future. What pitfalls around setting up your company codes are there in not blueprinting your SD process? For exampe, are you required to set up customers by company code? If so, it looks like the maintenance would be difficult.

    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.

It is important to look at end-state and where you want to go vis-a-vis sales process and purchasing process. You have to ask how your enterprise will be eventually structured. Some of the immediate pitfalls I can think of are:
1. Constrains in doing some of the processes, like inter-company shipments.
2. You will have to re-do the enterprise structure.
3. You'll have to do more data maintenance.

This was first published in April 2003