Database Reference
In-Depth Information
CHAPTER 13
SAP Complex System
Landscapes
The implementation of SAP software by large organizations can take from six months to sev-
eral years, depending upon the scope of the software deployment, the size of the organization,
and the complexity of the business process that have to be set up in the new system. In this
chapter we will discuss the different implementation scenarios, release management
strategies for SAP software in a complex five-System-Landscape using N and N+1 architec-
ture, and the best practices for managing SAP logistics and change management in complex
SAP System Landscapes.
SAP Implementation Approach
SAP can be implemented in two main approaches: the big bang implementation approach and
the phased implementation approach. Each of these has its pros and cons. One of the ap-
proaches is decided up-front during the release management planning.
Big Bang Implementation Approach
In the big bang implementation approach, SAP software is implemented all at once. End
users will stop using the old legacy software and start using the new SAP software after the
go-live. After a month of stabilization in the newly implemented SAP system, the old sys-
tems are retired. This approach is riskier, as change is introduced at once and the resource re-
quirements are very high. If an implementation has any issues, this approach can cause busi-
ness disruptions and cause lasting damage to an organization. This is the one of the main
reasons why a phased implementation is recommended for deploying a SAP application in a
systematic manner, thereby reducing business risk. A three-System-Landscape is sufficient
for implementing SAP in a big bang approach.
Phased Implementation Approach
In a phased implementation, SAP software is implemented in several phases, which are re-
ferred to as releases. The standard SAP three-System-Landscape is not sufficient to address
the needs of a phased multirelease implementation effort. In a phased implementation ap-
proach, after the first release goes live in the production system, there is a need for new de-
velopment work and support packages application for the next release. If this is done in the
existing development system, very soon this will be out of sync with the production system
and cannot be used to create any production bug fixes. Because of this reason, SAP recom-
mends a five-System-Landscape strategy to support a phased implementation approach with
multiple releases over time.
