Page 157 - DCAP302_ENTERPRISE_RESOURCE_PLANNING

Unit 8: ERP Implementation Lifecycle

3. Function-wise implementation notes
4. Customization

5. Uploading of data
6. Test runs
7. Parallel run
8. Crossover

Mapping of Business Processes on to the Package

This is a crucial step where the re-engineered business processes are mapped on to the software.
In mapping, the implementation team tries to fulfill the user requirements by making use of the
standard functionality available in the software. However, if the requirements cannot be covered
fully by the standard system, then the next step of implementation, i.e. gap analysis comes into
the picture.

Gap Analysis

As mentioned above, the user requirements that cannot be directly mapped on to the standard
system form the basis of gap analysis. Here, all such uncovered requirements are compiled into
a gap analysis report. The ‘gaps’ are then classified into the following three heads:
1. Gaps which can be taken care of with a little programming effort

2. Gaps which involve an extensive programming effort and hence require extra resources
3. Gaps which cannot be taken care of in the system.
For the first category, the project team directly takes action and resolves the issue. For the second
and third category of gaps, however, the steering committee comes into the picture and decides
on the extra resource allocation / process change.

Customization

Once the process mapping and gap analysis have been done, the actual customizing starts. In
this step, first the customizing needs are chalked out and then the actual job is handed over to the
respective functional teams.

Development of User – Specific Reports and Transactions

As mentioned under gap analysis, any user requirements not covered by the standard system need
to be provided by extra programming effort. In this step, the required reports and transactions
are created.

Uploading of Data from Existing Systems

With customizing in place, the system is now ready to receive the master and transaction data
from the existing system. In this step, programmed transfer of data takes place from the existing
system to the new system. To avoid wrong tabulation of master data, the transfer process needs
to be thoroughly checked in the trial runs. At times it too involves a lot of programming effort.

LoveLy professionaL university 151