DM&LT QUESTIONNAIRE COMPANY CODE SPLIT

Powered by
DM&LT
Global Hub

DM&LT Questionnaire
Company Code Split

Please fill out the questionnaire and send it to the following e-mail address:
SAP_DMLT_GCE@sap.com

DM&LT QUESTIONNAIRE COMPANY CODE SPLIT

TABLE OF CONTENTS
I.

INTRODUCTION.............................................................................................................................. 3

II.

SCENARIOS INVOLVING A COMPANY CODE SPLIT....................................................................4

III.

CONTACT INFORMATION............................................................................................................... 5

IV.

PROJECT-SPECIFIC QUESTIONS................................................................................................. 6

V.

SYSTEM-SPECIFIC QUESTIONS................................................................................................... 7

VI.

SAP LANDSCAPE TRANSFORMATION.......................................................................................10

VII.

SERVICE SPECIFIC QUESTIONS FOR A COMPANY CODE SPLIT............................................11

VIII.

ANNEX........................................................................................................................................... 15

DM&LT QUESTIONNAIRE COMPANY CODE SPLIT

I.

INTRODUCTION

Dear customer,
Thank you very much for your inquiry and interest in Data Management & Landscape
Transformation (DM&LT).
DM&LT are SAPs answer to the demand for changes in live systems of the SAP Business Suite.
They provide support to customers implementing business-related or technical modifications in
their systems. Typical examples of these are the centralization of existing system landscapes;
company mergers, sales, or acquisitions; and harmonization of business objects. When carrying
out such activities, DM&LT help customers migrate, separate, and harmonize data from SAP
organizational units and business objects (for example, by renaming or merging the data). Even
entire systems can be centralized by means of merging or decentralized by separation.
The complexity and feasibility of DM&LT projects depends on your individual situation. Your system
landscape, organizational structures, and applications play a role. To process your inquiry, we
require some information: We would ask that you fill out this questionnaire and send it back to us.
As soon as we receive it, we will undertake a preliminary analysis before coming to initial
conclusions regarding possible solutions and additional analyses that may become necessary
(particularly when merging systems or organizational units).
The fields highlighted in grey in the tables contain example answers to aid your orientation.
If you need more space than the tables provide for the system-specific questions, please use
section VIIIError: Reference source not found Annex.

DM&LT QUESTIONNAIRE COMPANY CODE SPLIT

II. SCENARIOS INVOLVING A COMPANY CODE SPLIT

Company code splits are applied in order to separate one company code into multiple company codes.
DM&LT utilizes a unique tool based approach in order to convert logistical processes with minimal business
interruption while on the financial side the open items are transferred.
Company Code Splits or partial company carve-outs are typically applied in the course of an M&A
transaction (Divestiture) where corporations sell parts of their business in a so called asset deal. In an asset
deal parts of a legal entity (in SAP typically represented by one or more company codes) will be transferred
(split) to another company code.
Company code splits do also occur when corporations restructure their business into new or different legal
entities. This can be for several reasons such as the separation of a line of business in separate legal
entities, the optimization of supply chain, legal requirements or for tax reasons.

System-wise a company code split can be done under different landscape scenarios depending on the
concrete case and the chosen segregation strategy. One distinction for the different split scenarios is whether
it is done within the same SAP client or into a different client or system. The chosen landscape scenario has
implications on project cost and duration.
Especially as SAP DM&LT offers the widest variety in DM&LT proprietary and traditional split approaches the
evaluation which split approach and landscape scenario does best fit to the concrete scenario is part of our
divestment and restructuring methodology. For this purpose SAP DM&LT project offerings usually start with
an initial analyses and scoping workshop covering these topics. Note: this questionnaire already asks for a
preferred landscape scenario. If the the landscape scenario is not finally decided this question is rather
meant to gather initial information about the current state of considerations/preferences or preliminary
decisions

You can find additional information in our service description for controlling area merges, included along with
this questionnaire and available on the SAP Support Portal: http://support.sap.com/DM&LT

DM&LT QUESTIONNAIRE COMPANY CODE SPLIT

III. CONTACT INFORMATION

To process your inquiry quickly, we require, among other things, information on how to reach specific contact
persons and a complete address to which to send the quotation. When applicable, please also supply the
contact information of your software reseller or outsourcer.
Customer information
Company:
Industry:
SAP Customer ID:
Address:
Contact person:
Department:
Telephone:
E-mail:

Job title:
Fax:

Send address for the quotation1

Company:
Industry:
SAP Customer ID:
Address:
Contact person:
Department:
Telephone:
E-mail:

Job title:
Fax:

Contact information for partners, outsourcing, consulting, and so on

Company:
Industry:
SAP Customer ID:
Address:
Contact person:
Department:
Telephone:
E-mail:

Job title:
Fax:

1
Please enter a send address if the quotation should not be sent to the customer address specified in 1.

DM&LT QUESTIONNAIRE COMPANY CODE SPLIT

IV. PROJECT-SPECIFIC QUESTIONS

What business scenario is this project based on?

Project status:

Example
Desired start date

November 11, 2011

Desired end date

June 1, 2012

Would an alternative end date

be possible? When?

Yes

Legal requirements

Deadline given by contract

Internal / external auditors

informed?

Yes
Project
preparation

Current project phase

Are there additional factors
relevant for project timing?
Which?

Fiscal year-end closing

End of fiscal year?

31.12.2013

DM&LT require a separate testing environment. Does your company have a testing environment
available exclusively for the project?
Yes
No
Requirements concerning system outage during go live / cut-over:
How long can the production system be exclusively locked for the cut-over activities?

> 48 h

12 24 h

24 48 h

< 12 h

Remarks:

DM&LT QUESTIONNAIRE COMPANY CODE SPLIT

V. SYSTEM-SPECIFIC QUESTIONS
The following systems will be affected. If you have more than four affected systems (or clients), you can use
the space provided in annex 1.

Example
System ID
Installation number

P12
123456789

System type

Live R/3

To what extent will the system

be affected?2

Directly
(target
system)

Number of production clients

Number of production clients

affected / to be changed

Release upgrade planned

within the next 12 months?
Is the implementation of New
GL planned in the next 12
months? When?
Hardware located in
different time zones?

Yes, to
ERP ECC 6.0
=> on
30.06.2013
Yes, End of
June
No

Number of users

100

Current SAP release

4.7

Operating system
Database (incl. version)
Database volume
Do you use data compression
features of your database?
Code page

HP-UX
Oracle 10.x
1.2 TB
No
Unicode

2
Possibilities / examples pertinent to the projects scope:- Direct / production system; target production system; source production
system
- Possible / direct development system
- Possible / direct / indirect associated with BW / CRM / APO / HR / Logistics / Accounting / SEM / KM / NetWeaver Portal

DM&LT QUESTIONNAIRE COMPANY CODE SPLIT

Our company uses the following components:

Example
System ID & Client

PR1/400

Number of named users in the client

ca. 280

FI

FI-AA

New General Ledger

(New G/L)

incl. document split?

X
X

CO

CO-PC-ACT (Material Ledger)

EC-PCA (Profit Center Accounting)

CO-PA (Profitability Accounting)

TR (incl. FSCM)

IM

SD
MM

PP
PS
PM

QM
HCM
i.e.

Only HR Mini-Master Data

Further HR-Components:

Others please list

SAP add-ons
Third-party add-ons
Industry Extensions / Solutions

CS, GRC,
PLM
Revenue
Recognition
IS-H-MED
Mill Products
/ IS-H

Example

DM&LT QUESTIONNAIRE COMPANY CODE SPLIT

System ID & Client

Does your company have many
in-house developments?
Approximate number of
customer-specific tables
Does your company
use SAP data archiving?
Does your company use optical
archives?

P12 (100)
Yes0
100
YES
YES

DM&LT QUESTIONNAIRE COMPANY CODE SPLIT

VI. SAP LANDSCAPE TRANSFORMATION

Most SAP Data Management & Landscape Transformation are delivered based on the SAP Landscape
Transformation solution. If you already have an SAP LT license for the installations available, please specify:
SAP LT (Landscape Transformation) software license exists for:

System ID

Installation Number

Example

P12

123456789

SAP LT Basis3

Leverage Sell, Buy and

Restructure

Unify and Transform Data

Consolidate and Reduce IT
Cost

In case you have already installed Data Management & Landscape Transformation Add-Ons
(DMIS) in one or more of the participating systems, please specify which release is installed? 4
Installed Data Management &
Landscape Transformation
(DM&LT) Add-Ons:

Example

DMIS 2006

DMIS 2010

DMIS 2011

3
Since for each component release, DMIS requires the necessary support packages. For an overview of the
required software component releases and support packages, refer to SAP Note 1468391 and 1577442
4
For example DMIS 2006_1_XXX or DMIS 2010_1_XXX is installed and one of the following solutions is
already in use: TDMS, General ledger migration cockpit, MWB, LT, PCL.
10

DM&LT QUESTIONNAIRE COMPANY CODE SPLIT

TDMS

Solution Manager 7.0 (SP15) in

place? (please mark with X)

YES

NO

Do you have SAP Solution Manager 7.0 with Service Pack 15 or higher installed in your SAP Landscape?

In case additional software or tools will be required to deliver the requested service, these will be provided in
the software download area of the SAP Service Marketplace. Only registered users will be able to access
and download the software. Please specify the S-user to be registered for that purpose.
S-User-ID
VII. SERVICE SPECIFIC QUESTIONS FOR A COMPANY CODE SPLIT
Where is the source system located?

In-house

Outsourcing company:

Company:
Industry:
SAP Customer ID:
Address:
Contact person:
Department:
Telephone:
E-mail:

Job title:
Fax:

What is the area of business / industry of your company?

________________________________________________________________________
________________________________________________________________________

What is the background of the project? What kind of reorganization are you planning? What part of the
company is going to be split off, and what is the reason?
Examples:

11

Business area XY will become an independent legal entity

A plant will be split off (to become an independent legal entity)

There used to be a common organizational unit for sales and manufacturing; now this is going to be
split up

DM&LT QUESTIONNAIRE COMPANY CODE SPLIT

________________________________________________________________________
________________________________________________________________________
________________________________________________________________________
________________________________________________________________________
________________________________________________________________________

How would you describe the general motivation for splitting up the company / company code?
Reorganization and restructuring for strategic reasons5
(For groups: Split-off part of the company remains part of the group!)
Reorganization for legal reasons, e. g. enforcement of anti-trust laws and decartelization
(For groups: Split-off part of the company remains part of the group!)
Part of a company has been or will be sold off6, e. g. for recapitalization purposes
(For groups: Split-off part of the company will NO LONGER be part of the group!)
Others: ____________________________________________________________

Preferred landscape scenario. The target company codes where the split-off parts of business need to be
transferred to (could be new entities or existing ones) shall operate
within same ERP system and same client
within same ERP system into different client (empty client with similar configuration)
into an empty target system with same repository and configuration
into an empty target system with different repository and configuration (process template)
into an existing target system which is already productively used (different repository and config,
contains existing master and transactional data e.g. direct buyer integration)
If landscape scenario decision is not yet finally done or tentative only please indicate. DM&LT can offer a
scenario evaluation workshop to support decision for the most appropriate IT split approach.

5
Example: Create smaller units that act as independent companies in the market; isolate liability risks;
separate operative and non-operative assets; create subsidiaries; organize business areas as separate
units; build up a holding structure
6
This normally also applies for separation of stock held by family members from stock held by investors as
well as when claims to an inheritance must be settled
12

DM&LT QUESTIONNAIRE COMPANY CODE SPLIT

How independent is the part of the company that will be split off at the moment?
separate organizational responsibilities (organizational structure)
separate, delimitable business processes (process structure)

Is the part of the company that will be split off currently represented in its own separate organizational units
in the SAP system7?
Yes

No

If yes: In what type(s) of SAP organizational units is the part that will be split off currently represented in the
SAP system:
Its own separate plants (used exclusively for this part of the company)
Its own separate sales organizations (used exclusively for this part of the company)
Its own separate division(s) (used exclusively for this part of the company)
Its own separate purchasing organization(s) (used exclusively for this part of the company)
Its own separate business areas (used exclusively for this part of the company)
Its own separate profit centers (used exclusively for this part of the company)
Others: _______________________________________

Which SAP company codes need to be split? Are there already findings/suggestions/ideas for split criteria
i.e. how to identify the business data split out?

Example
Company Codes
Ca. number of users in these
company codes
Potential split/separation
criteria (suggestions, ideas so
far)
Rough indication in % of split
business data out of the
source company codes (if
possible at all to guess)

0001
Ca. 200
Plant code
4711
50 %

7
E. g. if a separate distribution company is to be created and the relevant business is already represented in
its own sales organization and supplying plants. This question is important here because it makes a
difference if the part of the company that will be split off already has its own organizational units for logistics
purposes or not.
13

DM&LT QUESTIONNAIRE COMPANY CODE SPLIT

Do you plan any additional reengineering activities in parallel with the company code split? That is, does the
split involve any significant changes to existing business processes?
Yes

No

If yes, please specify:

________________________________________________________________________
________________________________________________________________________
________________________________________________________________________
________________________________________________________________________

If possible, please provide a rough overview of the As-Is and To-Be organizational setup
________________________________________________________________________
________________________________________________________________________
________________________________________________________________________
________________________________________________________________________

14

DM&LT QUESTIONNAIRE COMPANY CODE SPLIT

VIII. ANNEX
. . . allowing to enter data for further systems:

Example
System ID
Installation number

P12
123456789

System type

Live R/3

To what extent will the system

be affected?8

Directly
(target
system)

Number of production clients

Number of production clients

affected / to be changed

Release upgrade planned

within the next 12 months?
Is the implementation of New
GL planned in the next 12
months? When?
Hardware located in
different time zones?

Yes, to
ERP ECC 6.0
=> on
30.06.2013
Yes, End of
June
No

Number of users

100

Current SAP release

4.7

Operating system
Database (incl. version)
Database volume
Do you use data compression
features of your database?
Code page

HP-UX
Oracle 10.x
1.2 TB
No
Unicode

8
Possibilities / examples pertinent to the projects scope:- Direct / production system; target production system; source production
system
- Possible / direct development system
- Possible / direct / indirect associated with BW / CRM / APO / HR / Logistics / Accounting / SEM / KM / NetWeaver Portal

15

DM&LT QUESTIONNAIRE COMPANY CODE SPLIT

Example
System ID & Client

PR1/400

Number of named users in the client

ca. 280

FI

FI-AA

New General Ledger

(New G/L)

incl. document split?

X
X

CO

CO-PC-ACT (Material Ledger)

EC-PCA (Profit Center Accounting)

CO-PA (Profitability Accounting)

TR (incl. FSCM)

IM

SD
MM

PP
PS
PM

QM
HCM
i.e.

Only HR Mini-Master Data

Further HR-Components

Others please list

SAP add-ons
Third-party add-ons
Industry Extensions / Solutions

CS, GRC,
PLM
Revenue
Recognition
IS-H-MED
Mill Products
/ IS-H

Example

16

DM&LT QUESTIONNAIRE COMPANY CODE SPLIT

System ID & Client

Does your company have many
in-house developments?
Approximate number of
customer-specific tables
Does your company
use SAP data archiving?
Does your company use optical
archives?

SAP LT (Landscape Transformation) software license exists for:

System ID
Installation Number

P12 (100)
Yes0
100
YES
YES

Example
P12
123456789

SAP LT Basis9

Leverage Sell, Buy and

Restructure

Unify and Transform Data

Consolidate and Reduce IT
Cost

In case you have already installed Data Management & Landscape Transformation Add-Ons
(DMIS) in one or more of the participating systems, please specify which release is installed? 10
Installed Data Management &
Landscape Transformation
(DM&LT) Add-Ons

Example

DMIS 2006
DMIS 2010

DMIS 2011
TDMS

Which SAP company codes need to be split? Are there already findings/suggestions/ideas for split criteria
i.e. how to identify the business data split out?
9
Since for each component release, DMIS requires the necessary support packages. For an overview of the
required software component releases and support packages, refer to SAP Note 1468391 and 1577442
10
For example DMIS 2006_1_XXX or DMIS 2010_1_XXX is installed and one of the following solutions is
already in use: TDMS, General ledger migration cockpit, MWB, LT, PCL.
17

DM&LT QUESTIONNAIRE COMPANY CODE SPLIT

Example
Company Codes
Ca. number of users in these
company codes
Potential split/separation
criteria (suggestions, ideas so
far)
Rough indication in % of split
business data out of the
source company codes (if
possible at all to guess)

18

0001
Ca. 200
Plant code
4711
50 %