- [Instructor] Implementing and customizing SAP
to suit a company is a huge undertaking.
Let's walk through this steps needed
for a successful implementation.
There are multiple successful strategies to implement SAP
but they all follow a similar flow.
Project preparation is first.
This is where the cost
and scope of the SAP implementation are defined.
This is also the time to ensure
there's a great team in place
that has all the skills necessary
for successful implementation.
This team studies the current systems being used
then they determine which system interfaces are required.
This step also includes business blueprinting.
This is where requirements for the new system are mapped.
The second step is called, realization.
System configuration takes place during realization.
Configuration is where SAP is matched
with the company's existing business processes.
All configuration is done
utilizing the existing SAP structure in functionalities.
In other words,
configuration ties together the way a company works
with the out of the box functionality of SAP.
Realization is also where customization occurs.
Basically customization is making a change
that is not supported by SAP's default functionalities.
Customizations are expensive
and can really extend the length of an implementation.
They can also complicate future upgrades.
The third step in typical implementations, is testing.
There are different types of testing.
Unit testing is typically first
and this is where we test individual parts of the program.
An example here would be to make sure
that each SAP transaction is working properly on its own.
Next, integration testing test how the systems
are working together
and how the program affects downstream processes.
These first two types of testing
are usually executed by project team members.
Next is user acceptance testing.
This testing is where end users
are able to get into the system
and ensure that SAP has been configured
to accomplish everything needed
for the business to run well.
And finally performance testing,
ensures the system can handle all the data and transactions.
This is the testing phase that makes sure
the system is fast enough for the end users.
The fourth step and an implementation is final preparation.
This is where all master data
like business partners in materials
is uploaded into the new system.
Final preparation is also where
end user security rules are set up
and training is conducted for all end users.
The fifth step, is Go-live.
This is when the actual switch
from old systems to SAP occurs.
These are frequently referred to as cutover activities.
At this point end users start using
the SAP production environment daily for their work.
Finally, the last step is, post go-live support.
This is where any problems in production
that were missed during the other phases are solved.
This is also a non-business critical
or your nice to have customizations are developed,
tested and implemented in a system.
The SAP implementation process end to end
can take as little as six months up to four or five years
for very complex implementations.
Companies often choose multi wave implementations.
This means they'll implement in one location
and ensure the system works well
before implementing at other sites.