Академический Документы
Профессиональный Документы
Культура Документы
a Technical Perspective
Applies to:
SAP ECC 6.0 onwards on a complex NW Landscape with multiple legacy and third party application
systems. As this white paper is about managing separation projects from technical perspective, the versions
generally do not matter. For more information, visit the ABAP homepage.
Summary
Similar to SAP integration projects as a result of acquisition/mergers, separation projects can be complex. In
this presentation, author is attempting to outline the technical approach and managing the expectations from
the client during an SAP separation initiative. This document is outlining, where/how to begin the complex reimplementation of an up and running SAP implementation after copying the entire system landscape into a
newer one.
Author:
Venkat Gururajan
Author Bio
Venkat Gururajan is an SAP Consultant with specialization in logistics modules, ABAP
development and system integration. He has 14+ years of consulting in SAP/Oracle with 8
years of core manufacturing planning and execution experience.
Table of Contents
Background and Introduction ......................................................................................................................... 3
Customer Requirement ................................................................................................................................. 3
Understanding the existing systems landscape ............................................................................................. 3
Comparing with the proposed landscape ....................................................................................................... 4
(ETL System proposed to be eliminated moving all the interfaces to ECC/HR to Portals) ............................... 5
Determining the key business processes ....................................................................................................... 5
Can the parent organizations IT Support help? ............................................................................................. 5
Inventory of the Custom programs and enhancements .................................................................................. 6
Data migration from conversions perspective and How SAP can help? .......................................................... 6
What are the common fixes? ......................................................................................................................... 7
Unit and Quality System Testing ................................................................................................................... 7
Integration Cycles and Defect Resolution ...................................................................................................... 7
Performance and Stress Testing ................................................................................................................... 7
Critical deliverables ....................................................................................................................................... 8
Are we done yet? .......................................................................................................................................... 8
Related Content ............................................................................................................................................ 9
Disclaimer and Liability Notice ..................................................................................................................... 10
Customer Requirement
The proposed customer requested an RFP to copy modify test - deploy all of the existing systems as a
new landscape and separate the Design and Manufacturing divisions into two separate entities. While the
Design organization becomes parent, needing no change to the current system, the implementation work
was primarily focused on the Manufacturing division and the operating application systems comprised of
multiple Non SAP systems and a comprehensive Netweaver landscape integrated with custom portals
running on a Java engine. The customer also requested replacement of few of the existing systems that do
not add value in terms of functionality as well expensive from the annual license maintenance costs. It is
important to note that the Manufacturing requires an order processing functionality to complete the supply
chain, which was owned by the Design and marketing division so far and this specific part requires a process
redefinition. This process requires partial blue printing of order management and a mini development project.
(ETL System proposed to be eliminated moving all the interfaces to ECC/HR to Portals)
By this, we will have the documentation of all the existing objects that help the client as well the production
support team to cross verify the specification for any functionality maintenance or fix.
Data migration from conversions perspective and How SAP can help?
It is quite normal that when a company operates as a single entity from design and manufacturing
perspective in the same country, only one company code is defined. When the design/marketing is located in
one country and manufacturing is located in a different country multiple company codes and controlling areas
are defined for accounting purposes from inter-company perspective. Defining and managing multiple
company codes help SAP AG slice the data. This would help eliminate a conversion process as the data preexists in the system built ground up. Making sure, data is managed based on separate company codes is a
key factor for engaging System Landscape Optimization process performed by SAP.
As it is a separation initiative, Data migration is one of the major process absent from conventional SAP
deployments. SAPs System Landscape Optimization can not only perform integrations between two
companies but also separations. Based on key master data such as company code and controlling area, the
data that is not relevant to the separating division can be deleted by SAPs intelligence programs. The key
parameters for deleting or retaining are verified / validated and confirmed to SAP, before they begin the SLO
process. SLO normally takes a day time or more, depending on the system landscape and the data volume.
After SLO is completed, Functional and Business owners verify the configuration, Master and transaction
data. It is important to verify and validate key information such as organization structure. The org structure
before SLO may not fit the separated organization and some changes may be required. As the HR Systems
normally run on Workflows, a correct definition of organization structure is imperative for business process.
Critical deliverables
As the SI team completes the various testing cycles, documentation needs to be generated specific to the
functional and technical areas. All the functional specifications, Technical specifications, Unit testing results,
an indexed document of list of technical objects with proper document naming conventions need to be
generated or modified that was received as a result of knowledge transition from the production support
team. Other than these final deliverables, there would also be SIT/Integration related documents generated
during testing cycles stored on the share point.
Related Content
For more information, visit the ABAP homepage.