Database Reference
In-Depth Information
−
Modifications of the configurations
−
Refresher training
−
Training on additional modules or functionality
Lastly, the task addresses the obtaining of approval for the production environment. This is the
official approval of the live system.
13.2.5.2 Project End
The purpose of this task is to officially close the project. Any open issues that are still pending
resolution are reviewed and closed.
13.2.5.2.1 Project Review
This task commences the exercise of measuring the business benefits for the SAP
implementation:
1.
Review and close all open issues
: All issues in the issue database are identified, reviewed,
resolved, and closed.
2.
Review Business Benefits:
: The results of the SAP implementation are compared with the goals
and objectives that were set for the implementation project. This also leads to the establish-
ing of an evaluation procedure that can monitor benefits on an ongoing basis.
3.
Evaluate the knowledge transfer process
: The key lessons or conclusions of the project are
reviewed and documented. This is done with the help of the information gathered during the
course of the project in the Questions & Answers Database (Q&Adb) because that reflects
the distillation of the true insight into the functioning of the organization.
4.
Complete Organizational Change Management Process
: The key gains of the organizational
change management process are evaluated. Any remaining organizational change manage-
ment issues are resolved and closed.
13.2.5.3 Project Sign-Off
The purpose of this task is to obtain the formal approval for the close of the project.
When a company adopts ASAP methodology for implementing SAP, their success
depends on how quickly the company can implement changes in its business
processes that are in line with the best-of-business processes in SAP. While using
ASAP, it is advisable that the company should avoid undertaking a Business Process
Re-Engineering (BPR) effort in conjunction with the SAP implementation. It is recom-
mended that the company should implement a vanilla SAP functionality initially. Once the
implementation stabilizes, then custom functionalities could be introduced later judiciously.
The vanilla approach cuts down on maintenance, as well as speeds up the time to production
and benefits of the new system.
