Planning for implementation of SAP

Lifecycle development
Project management
The current CRM is written using VB for finance, while the sales application is an old legacy system residing in a DOS environment. We are now in the planning phase of replacing all this with SAP. What is the best approach to take in such a situation where you have one application running in a windows environment while the other is in the good old DOS environment? Just so you know I have a decade of experince in the software development industry, but this would be my first experinece with SAP. I am only asking for some direction rather than detail technical solution. Thanks for taking your time to read this.

Answer Wiki

Thanks. We'll let you know when a new response is added.

Avoid specific tools. There are so much SAP implementation in the world, someone has had the same problems you will encounter. So there is already a solution in SAP.

You will probably will ask for consultants (not probably, surely). Work with them for a standard solution for each issue, it is he key of future upgrades. You will upgrade.

Consultants know the product. You know your business. choose your best inside professionals, free them half their time, and promote them Key Users. make what is necessary for this to be a promotion.
And the first job of your key users is to choose the junior that will work their job the half tome they are key users.

By this way, after ending SAP implementation you will have a strong product carrying a strong team (normaly, the junior + the senior becomes an effectiveness duo, this is your personnal challenge)

this was for the human point of view.

for the technical side, converting your actual data to SAP database can be done with at least half a dozen of tools. Your job is to be able to export your data in flat files. Let consultants doing the insertion in SAP. The oldest technique is BCD, I continues to uses it dayli. It’s a way to simulate keying in sap screns in bath mode. The efficiency is based on the fact that loading is made with a batch input folder : you can track the errors and re-run data that are not already loaded. That is the key of loading SAP (or any other soft / database) : the warranty ofnever miossing any data.

Discuss This Question: 1  Reply

There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.
  • Solutions1
    One aspect to look at is your infrastructure requirements and, probably, upward migration - modern PCs, etc. It is helpful to square away your infrastructure in advance (client devices, network, conversion to TCP/IP, if not already in, etc.). Also, it may make sense to look at Citrix or other "thin client" capabilities to move the legacy applications off the client PCs onto Citrix servers ("thin client" also often makes sense for SAP itself).
    0 pointsBadges:

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

Thanks! We'll email you when relevant content is added and updated.


Share this item with your network: