In general, below are the step in user side, while implementing the SAP (HR) implementation :
- Length of the Implementation
- State your Project Goals and Objectives.
- Choosing the right implementation partner
- Choosing the right project team members
- Choosing and understanding a methodology.
- Creating a “favorable” project environment facilitating communication and team working
- Extensive Training Required
- Cost of Consultants
- Careful preparation of a budget.
- Fixed contract versus time and material
- Cost of Software, Licenses and ESS
* Steering of the committe will be there like
client side mis pepole like IT GM will be involved regarding project preperation stage
*From our side top ceiling like head of sap hr will be involved
*The project scope is prepared here
2. Business blue print
A business blue print is a document that specifies all the business process requirements within the scope of the project.
1) AS – IS study.
2) Re – engineering techniques are applied (not mandatory, only if required).
3) TO – BE process requirements are identified and documented. These requirements are what you want your R/3 system to perform.
4) A last chance to make slight changes in the project scope.
5) Conducting and organizing work shops for gathering information and suggestions to frame the requirements.
TOOL – Q & A data base.
6) A Q & A data base tool is used, which is generated from EASD scope document. Depending on the scope the Q & A data base with change. Example: If you do not have PS module you do not have PS module related questions
a) A Q & A data base also contains ISSUE data base which can be logged and resolved from project management.
b) A Q & A data base also can be used to generate reports on all information that you log into data base
c) Reports can be generated based on the answers the users give and the solutions given by the consultants for the possible requirements.
d) You can generate answer reports which contain only answers that have been entered in data base.
e) You can generate business print when the consultants enter their analysis of the requirements.
7) AS – IS study is done and analyzed if any gap is found which is not supported in SAP. Gap analysis is done (not mandatory).
8) If the initial development of system was not set up that it has to set up in the phase with necessary user logins.
9) Technical architecture has to set up.
(Data base – Application – Presentation)
10) Transport request management has to set up.
11) Release strategy.
12) Remote connection to SAP has to set up.
[A tool where we can access in to user server (production)].
13) The desktops should be should be connected to LAN with SAP login.
14) One of the important deliverable of this phase is to develop the training strategy of the team.
This phase is sub divided into:
1) Base line configuration
2) Final configuration
3) Unit testing
4) Integration testing
1) Base line configuration, all critical and regular processes are configured in SAP R/3 system. Once this is configured it offers a foundation for the forthcoming final configuration phase. In base line configuration – 80% would be completed. Those business requirements that are not considered in baseline configuration must be defined final configuration. Any problems/errors that are found in base line configuration must be faced at final configuration.
2) Establishment of production system.
3) Unit and integration testing.
4) Stress test and tests on any interfaces.
5) Technical team need to work on system authorizations and end users for the production system.
6) Start preparing the end user documentation.
7) End user training and desktops duly configured.
4. Final preparation
1) Finalize entire system configuration and environment, including tests, user training, and productive system setup from the functional and technical point of view.
2) Need to develop a cut over plan – include both manual conversion and conversions through programs.
3) Provide end user training to end users with the training material that you developed in previous phase.
4) End users should have hands on experience on SAP R/3 system so that they can work from day one after Go – live.
5) Setup of 1 and 2 level help desk i.e., if not solved by level1 then g\it goes to level2.
5) Finally start converting data from your legacy system to the SAP R/3. You can use conversion programs (or) manual conversion.
5. Go – live & support
1) Go productive with production system (SAP R/3).
2) Dismantle the existing system.
3) Regular transactions in SAP R/3 system.
4) End users may require more support in the initial phase. Hence more support be given.
* Further media Go-live if required
* post Go-live Support is give for further like 2months 0r 6 months according to the client requirement
Continuous change to improve the capability of production system.