SAP R/3 implementation is generally a key project for any organization. It is necessary to do preparation before implementation. 

Many organizations speak of "transferring technology." But what does that mean? Transfer technology involves transfer of the system which includes the

It becomes obvious that the transfer of any part of the system, without the rest of it, does not transfer technology. In our context, the software SAP/3 is being changed. In most of the cases the hardware needs to be changed. The people need training to operate SAP system. But unfortunately, many organizations fail to understand that they need to change their processes. SAP is a package & it contains many best practices suitable to almost each industry. The designer (configuring the system) must design the system keeping the objective of the business objective in mind. The user should be prepared to change it’s processes and ensure that the objective of the processes is met. This should be done without or minimum distortion of the processes designed by SAP. This is a big challenge to the designer as well as user. It should noted that the user representative involved in the system design should be empowered for low level BPR decisions.

Also the information stored in the system will be in different form than the legacy system. The user must be prepared & trained for the changed.

The major challenge is behavioral change. Implementation of SAP R/3 system changes relationship of different persons, it gives/denies access to information which was not available/available to the person, it changes processes and control functions. This all gives behavioral issues. To get best out of SAP, these issues must be addressed before implementation.

SAP R/3 re-engineers many processes and the fear of downsizing and loosing job hinders free acceptance of SAP in many organizations. This fear hinders free communication between the end-users and SAP system designer. The communication is a vital element in successful implementation of SAP R/3. This issue of 'Fear Of Downsizing' must be addressed before starting implementation project.