Вы находитесь на странице: 1из 9

DEUTSCH

(HT TP: // WWW.DATAVARD.COM/DE/HOME- ENGLISH (HT TP: // WWW.DATAVARD.COM/EN/BLOG-


7/ ) USING-SLO-TOOLS -IMPLEMENT-DIVESTITURES -
CARVEOUTS -SAP-LANDSCAPES/ )

/
"

! BACK BLOG (HTTP://WWW.DATAVARD.COM/EN/CATEGORY/BLOG/)

Posted on 19.09.2017 by Goetz Lessmann

USING SLO TOOLS TO IMPLEMENT DIVESTITURES AND


CARVE OUTS IN SAP LANDSCAPES

!3 "0

In my last blog post I presented an overview of System Landscape Optimization (SLO)


(http://www.datavard.com/en/blog-transforming-sap-landscape-calls-right-tools/) and how it
supports business transformation. I walked through some of opportunities and potential benefits of
using SAP LT (Landscape Transformation) including flexible golive dates, conserving the integrity
of SAP data, and minimizing the impact of a transformation on ongoing business.

For this post, I wanted to take a deeper dive into the topic of divestitures. In these scenarios, a
portion of the business is sold to another company. From the perspective of business
transformation in SAP, the goal is usually to provide the acquiring company with the data
belonging to part of the business they acquired. Sometimes, a clean-up in the SAP systems of the
selling company can be included in the carve out project, for example by deleting the data of the
sold-off part of the business.

DIFFERENT SCENARIOS CAN OCCUR WHEN DIVESTING A BUSINESS UNIT:

1. The part of the business that is sold off is implemented as one or several company codes in SAP,
which can be sold completely

2. The sold off portion of the business can be implemented as one or more plants that can be sold
completely

3. The carve out affects a product line, or a part of the business that is co-mingled with data and is not
sold off.
In looking at these scenarios, the complexity and the difficulty of a carve out of complete company
codes is lower than of plants, or of completely co-mingled data. Basically, there are two ways to
implement a carve out from a SAP system landscape for each of the three scenarios: c l o n e a n d
d e l e t ee, or a d a t a m i g r a t i o n based approach. It is important to carefully pick and choose the
correct approach and tools (e.g. include masking and scrambling tools for co-mingled data).

THE CLONE AND DELETE APPROACH

In the clone and delete approach, the complete SAP system is copied and undesired data is
deleted. For the carve out of complete company codes from an existing, productive SAP system
landscape the clone and delete approach is the fastest and easiest way. For ERP systems, this
approach is covered by tools such as SAP LT out of the box. For satellite systems such as BW, or
other solutions such as CRM or SCM, the clone and delete approach can be implemented by
experienced service providers such as Datavard.

For such deletions, SAP LT derives all data which belongs to selected company codes across the
complete ERP system, and then generates deletion programs for all relevant database tables. The
resulting system will appear as if the deleted company codes had never even existed. This is
because SAP LT purges data from all areas including customizing, master data, transactional
date, open and closed business processes.

The figures below show an example organization structure in SAP before the company code
deletion.

(http://www.datavard.com/wp-content/uploads/2017/09/datavard_170918.png)

In this example, only company code 2010 is supposed to remain in the system. The result of a
deletion based on SAP LT looks like this:

(http://www.datavard.com/wp-content/uploads/2017/09/datavard_170918_2.png)

THE DATA MIGRATION APPROACH

Now let’s look at the migration approach where a new SAP system is set up. This can be done by
either creating a new system and performing a client copy of type customizing (which involves a
fair degree of manual work), or a shell creation process such as Datavard’s Lean System Copy
(LSC). With LSC, an empty system copy of an existing SAP system can be created. Empty means
that only customizing, custom developed programs, and SAP users are included in the new
system. Data is then selectively migrated into this empty system copy to bring in the data for the
carved out business unit.
IN COMPARING THESE TWO APPROACHES, IT’S APPARENT THAT CLONE AND
DELETE HAS A NUMBER OF DOWNSIDES:

1. The complete system must be copied before SAP LT can be used to delete data. This can be a
lengthy and costly procedure, especially when the ERP system is running on SAP HANA, and only a
minor part of the system is to be handed over to the buying company

2. The clone and delete approach works “out of the box” only for complete company codes.

3. The data deletion step can be lengthy (20 to 40 hours), especially for large systems. To overcome
this, downtime minimization tools such as Datavard’s Company Code Obfuscation can be used to
shorten the SAP system lock (downtime) during the cutover significantly.

For the carve out of plants using clone and delete, a plant reallocation would be required as a first
step, which increases the complexity of the project to some degree. This plant reallocation is used
to move all deletion relevant plants into a separate company code, which is then removed using
the out of the box functionality provided by SAP LT.

Depending on the nature of cross-plant business processes and how they are implemented in
SAP, this may be a significant effort driver. Therefore, when a carve out is to be done on plant
level, the migration approach may win over the clone and delete approach. SAP LT supports such
migrations, however some of the required scenarios in SAP LT are “restricted,” meaning they are
not available to customers without expert consulting services from SAP’s own SLO team, or in
close cooperation with experienced service partners such as Datavard.

For completely co-mingled data, the clone and delete approach is extremely difficult to implement,
and the migration approach is more appealing. SAP LT includes data migration scenarios for
“object based” migrations — migrations of business objects, executed directly on the database
instead of performing postings. Such object based migrations include historical business data
such as data of closed fiscal years or periods where postings cannot be performed any more.
Masking and scrambling tools can help a lot to fine tune the data transformation and hide sensitive
data in divestiture scenarios. Datavard offers extensions to SAP LT which cover exactly this aspect
of transformation projects. These extensions are also very useful in the context of GDPR
(http://www.datavard.com/en/blog-sap-compliant-with-gdpr/).

SLO WEBINAR SERIES

In addition to these blog posts, we are also launching a 5-part webinar series covering everything
from why SLO is so important, to harmonization and M&A best practices and more. The series
started on Sept. 5 and continues through the end of October. Don’t miss this opportunity to learn
about SLO from the experts. Go to our landing page today to sign up
(http://www.datavard.com/en/system-landscape-optimization/).
SLO WEBINAR SERIES (https://cta-service-cms2.hubspot.com/ct
71b884568694&portal_id=385509&redirect_url=APefjpFWY_ejJYFHh3_-B7GQGxD-DeRa
oAjF2oVPeiCs-U5EaRjsYg&hsutk=8b78af476bbb37f4a196c48ec0e97daa&canon=http%3A

7426fc57bba5&utm_referrer=https%3A%2F%2Fwww.google.com%2F&__hstc=35702079.8b

TAGS: SLO (HTTP://WWW.DATAVARD.COM/EN/TAG/SLO/), SYSTEM LANDSCAPE

OPTIMIZATION (HTTP://WWW.DATAVARD.COM/EN/TAG/SYSTEM-LANDSCAPE-

OPTIMIZATION-EN/)

! PREVIOUS NEXT #

(HTTP://WWW.DATAVARD.COM/EN/BLOG-
FOUR-REASONS-
START-PACKING-
SUSECON-PRAGUE/)

3 COMMENTS ON “USING SLO TOOLS TO


IMPLEMENT DIVESTITURES AND CARVE OUTS IN
SAP LANDSCAPES”

Rishma on September 27th, 2017 - 12:43pm (http://www.datavard.com/en/blog-


using-slo-tools-implement-divestitures-carveouts-sap-landscapes/#comment-9952)

And what if the data will not be deleted in the SAP system but the divested company

code data will have to remain in the system and the new buyer still wants to access the

data in a readable format? The new company will have a new ERP ( no SAP) and will

not migrate all data to the new system.

I copying the company code data to a new environment and grant read only rights the

best solution?

Reply (http://www.datavard.com/en/blog-using-slo-tools-implement-divestitures-
carveouts-sap-landscapes/?replytocom=9952#respond)

Goetz Lessmann (http://datavard.com) on September 28th, 2017 - 6:38pm


(http://www.datavard.com/en/blog-using-slo-tools-implement-divestitures-
carveouts-sap-landscapes/#comment-9959)
Hi Rishma,

in such a case the buying company will still need the full history (minimum Finance,

but probaly more). There are legal requirements to keep data for auditing purposes

for +/- 10 years (depending on region and local legislation). What I would recommend

is to provide them with a SAP system, or access to a SAP system which you run for

them, which only contains their own data. This can be done using the “clone and

delete” approach.

I would not recommend giving them access to a full copy, where you implement ring-

fencing with authorizations only for several reasons (data volume, data protection,

security, etc.).

Hope this helps,

Goetz

Reply (http://www.datavard.com/en/blog-using-slo-tools-implement-divestitures-
carveouts-sap-landscapes/?replytocom=9959#respond)

Rishma on October 5th, 2017 - 10:35am


(http://www.datavard.com/en/blog-using-slo-tools-implement-divestitures-
carveouts-sap-landscapes/#comment-10037)

Thanks a lot for your reply!

Reply (http://www.datavard.com/en/blog-using-slo-tools-implement-
divestitures-carveouts-sap-landscapes/?replytocom=10037#respond)

LEAVE A REPLY

Your email address will not be published. Required fields are marked *
Comment
Name *

Email *

Website

POST COMMENT

SEARCH

Search...
(http://blog.feedspot.com/sap_blogs/)

RELATED ARTICLES

TRANSFORMING YOUR SAP LANDSCAPE CALLS FOR THE RIGHT TOOLS


(HT TP: // WWW.DATAVARD.COM/EN/BLOG-TRANSFORMING-SAP-LANDSCAPE-CALLS -RIGHT-TOOLS/ )

5 THINGS A GROWING COMPANY MUST KNOW ABOUT SYSTEM LANDSCAPE OPTIMIZATION


(HT TP: // WWW.DATAVARD.COM/EN/5-THINGS -A-GROWING-COMPANY-MUST-KNOW-ABOUT-
SYSTEM-LANDSCAPE-OPTIMIZATION/ )

MEET THE GDPR DEADLINE WITH DATA MASKING (HT TP: // WWW.DATAVARD.COM/EN/BLOG-MEET-
GDPR-DEADLINE-SAP-DATA-MASKING/ )

GET YOUR SAP COMPLIANT WITH THE NEW DATA PROTECTION LAWS (GDPR)
(HT TP: // WWW.DATAVARD.COM/EN/BLOG-SAP-COMPLIANT-WITH-GDPR/ )

WHY (ALMOST) EVERY SAP HANA NEEDS A DATA MANAGEMENT SOLUTION


(HT TP: // WWW.DATAVARD.COM/EN/BLOG-WHY-ALMOST-EVERY-SAP-HANA-NEEDS -A-DATA-
MANAGEMENT-SOLUTION/ )

AGILE TRANSITION TO SAP S/4HANA USING THE SLO APPROACH


(HT TP: // WWW.DATAVARD.COM/EN/BLOG-AGILE-TRANSITION-SAP-S 4 -HANA / )

$
(http://www.linkedin.com/company/1071681?
% & '
trk=vsrp_companies_res_name&trkInfo=VSRPsearc
(https://www.xing.com/companies/#datavardg
(https://twitter.com/datavard)
(https://www.facebook.com/DataV
PARTNERS

DATAVARD

Who we are (http://www.datavard.com/en/who-we-are/)


What we do (http://www.datavard.com/en/what-we-do-2/)
Careers (http://www.datavard.com/en/careers/)
Events (http://www.datavard.com/en/category/events/)
Blog (http://www.datavard.com/en/category/blog/)
Support (http://www.datavard.com/en/support/)
Privacy Policy (http://www.datavard.com/en/privacy-policy/)
Copyright (http://www.datavard.com/en/copyright/)

OUTCOMES

Shrink your database (http://www.datavard.com/en/shrink/)


Hana and Hadoop (http://www.datavard.com/en/hana-hadoop/)
IT Operations Analytics (http://www.datavard.com/en/itoa/)
Road 2 Hana (http://www.datavard.com/en/road-2-hana/)
Transition and Migration to S4/HANA (http://www.datavard.com/en/transition-s4-hana/)
System Fitness (http://www.datavard.com/en/system-fitness/)
System Landscape Optimization (http://www.datavard.com/en/system-landscape-optimization/)

PRODUCTS

BW FitnessTest (http://www.datavard.com/en/bw-fitnesstest/)
ERP FitnessTest (http://www.datavard.com/en/fitness/)
Datavard Insights (http://www.datavard.com/en/insights/)
Datavard Validate (http://www.datavard.com/en/datavard-validate/)
Outboard for Analytics (http://www.datavard.com/en/otb-for-analytics/)
Outboard for Housekeeping (http://www.datavard.com/en/housekeeping/)
Outboard for Transactional Systems (http://www.datavard.com/en/otb-for-transactional-systems-2/)
Datavard Glue (http://www.datavard.com/en/datavard-glue/)

CONTACTS

info@datavard.com (mailto:info@datavard.com)
Contact (http://www.datavard.com/en/contact-2/)

Made with passion by DATAVARD AG 2018


All rights reserved

LEGAL DISCLAIMER (/EN/DISCLAIMER) | IMPRESSUM (/DE/IMPRESSUM/)

Вам также может понравиться