SAP SLO System Client Merge
-
Upload
ravi-rashmi -
Category
Documents
-
view
28 -
download
0
Transcript of SAP SLO System Client Merge
![Page 1: SAP SLO System Client Merge](https://reader030.fdocuments.net/reader030/viewer/2022020803/5571fd48497959916998c13e/html5/thumbnails/1.jpg)
5/10/2018 SAP SLO System Client Merge - slidepdf.com
http://slidepdf.com/reader/full/sap-slo-system-client-merge-55a0c6bd82f81 1/44
SLO Service Client Merge
Speaker NameSAP Deutschland
![Page 2: SAP SLO System Client Merge](https://reader030.fdocuments.net/reader030/viewer/2022020803/5571fd48497959916998c13e/html5/thumbnails/2.jpg)
5/10/2018 SAP SLO System Client Merge - slidepdf.com
http://slidepdf.com/reader/full/sap-slo-system-client-merge-55a0c6bd82f81 2/44
SAP AG 2002, Title of Presentation, Speaker Name / 2
Content
System Landscape Optimization (SLO)
Client Merge
Conversion approach (Conversion Workbench
Migration approach (Migration Workbench)
Data transfer
Further Information
![Page 3: SAP SLO System Client Merge](https://reader030.fdocuments.net/reader030/viewer/2022020803/5571fd48497959916998c13e/html5/thumbnails/3.jpg)
5/10/2018 SAP SLO System Client Merge - slidepdf.com
http://slidepdf.com/reader/full/sap-slo-system-client-merge-55a0c6bd82f81 3/44
SAP AG 2002, Title of Presentation, Speaker Name / 3
Content
System Landscape Optimization (SLO)
Client Merge
Conversion approach (Conversion Workbench
Migration approach (Migration Workbench)
Data transfer
Further Information
![Page 4: SAP SLO System Client Merge](https://reader030.fdocuments.net/reader030/viewer/2022020803/5571fd48497959916998c13e/html5/thumbnails/4.jpg)
5/10/2018 SAP SLO System Client Merge - slidepdf.com
http://slidepdf.com/reader/full/sap-slo-system-client-merge-55a0c6bd82f81 4/44
SAP AG 2002, Title of Presentation, Speaker Name / 4
SAP SLO
The SAP SLO team consists of experts for SLO issues from
all areas of SAP development and consulting
SLO has its own development group
and a specialized SLO consulting team
SLO
Consulting
SLO
Development
Experience from numerous projects
+ Successful team of consultants and developers
Standardized services: The SLO service offering
SAP System Landscape Optimization
![Page 5: SAP SLO System Client Merge](https://reader030.fdocuments.net/reader030/viewer/2022020803/5571fd48497959916998c13e/html5/thumbnails/5.jpg)
5/10/2018 SAP SLO System Client Merge - slidepdf.com
http://slidepdf.com/reader/full/sap-slo-system-client-merge-55a0c6bd82f81 5/44
SAP AG 2002, Title of Presentation, Speaker Name / 5
SLO – Service portfolio
Pre-defined services for typical
business scenarios
Service description Standardized approach
Project plans, document templates
Full service(from planning to implementation)
Long-standing project experience
Extensive knowledge base
Configurable, extendable services fornew requirements
SLO-specific tools
Analysis tools
Conversion Workbench (CWB)
Migration Workbench (MWB)
Use of SAP standard methods and
tools
LSMW*, Batch Input, BAPI
* LSMW – Legacy System Migration Workbench
Curren-cies
ArchivingServices
TechnicalServices
SAP Conversion Services /
Data Harmonization Cons.
Organizational StructureChange Consulting
System LandscapeChange Consulting
![Page 6: SAP SLO System Client Merge](https://reader030.fdocuments.net/reader030/viewer/2022020803/5571fd48497959916998c13e/html5/thumbnails/6.jpg)
5/10/2018 SAP SLO System Client Merge - slidepdf.com
http://slidepdf.com/reader/full/sap-slo-system-client-merge-55a0c6bd82f81 6/44
SAP AG 2002, Title of Presentation, Speaker Name / 6
Consulting
DevelopmentService &Support
SLO is an SAP expert group Direct know-how transfer from
and to other SAP teams / departments
First-hand SAP knowledge
SLO Back Office ensures quality and efficiency
SLO project at customer
Customer and partner
Project-specificrequirements andresults
SLO Back Office
SLO support (services, tools)SLO expert knowledgeExperience
SLO experts
![Page 7: SAP SLO System Client Merge](https://reader030.fdocuments.net/reader030/viewer/2022020803/5571fd48497959916998c13e/html5/thumbnails/7.jpg)
5/10/2018 SAP SLO System Client Merge - slidepdf.com
http://slidepdf.com/reader/full/sap-slo-system-client-merge-55a0c6bd82f81 7/44 SAP AG 2002, Title of Presentation, Speaker Name / 7
SLO‘s pre-defined, structured approach
Service Delivery System/ client merge by SLO specialists
Standardized phased approach
Transparent definition of objectives and results
Project support by SLO Back-office
Provision of programs for making the required changes,
Support during the complete project runtime (normal working hours)and
7*24 h support during conversion of the production system
SLO f ilit t i l t ti d ti f
![Page 8: SAP SLO System Client Merge](https://reader030.fdocuments.net/reader030/viewer/2022020803/5571fd48497959916998c13e/html5/thumbnails/8.jpg)
5/10/2018 SAP SLO System Client Merge - slidepdf.com
http://slidepdf.com/reader/full/sap-slo-system-client-merge-55a0c6bd82f81 8/44 SAP AG 2002, Title of Presentation, Speaker Name / 8
SLO facilitates implementation and operation of mySAP Business Suite
Harmonization of structures andprocesses
More transparency, fewer redundancies Unified master data, e. g. customers,
vendors, materials
Unified controlling structures
Unified chart of accounts
Improved communication andintegration
More efficient information exchange
through unified structures Facilitate cross-system processes
Master Data Management (MDM)
Cross-system planning
Central purchasing
Central / cross-system reporting
Company reorganization
Merger or divestiture of companies orparts of companies
System creation Initial load, e. g. for MDM server
mySAP SCM
mySAP PLM
mySAP
SRM
mySAP
CRM
mySAP ERPFinancials
Human ResourcesCorporate Services
Operations
Maintenance and QM
Inventory managem./manufacturing S a l e s
o r
d e r p r o c e s s i n g
a n d
d i s t r i b u t i o n
P ur ch a si n gm
an a g em.
SAP NetWeaver
![Page 9: SAP SLO System Client Merge](https://reader030.fdocuments.net/reader030/viewer/2022020803/5571fd48497959916998c13e/html5/thumbnails/9.jpg)
5/10/2018 SAP SLO System Client Merge - slidepdf.com
http://slidepdf.com/reader/full/sap-slo-system-client-merge-55a0c6bd82f81 9/44 SAP AG 2002, Title of Presentation, Speaker Name / 9
Efficient tool-basedanalysis of as-issituation
Identification andquantification ofoptimization potential
SLO project procedure
Recommendation Implementation
Project management Project management Project management
SLO knowledge andexperience Check severalpossible solutions
Recommend the bestsolution for the givenproject
Reliable estimate ofrequired work
Implementation bySLO experts
Application of SLO
Services
Proven methods
• Conversion
• Migration
Generic environmentfor development
• CWB, MWB
PerformanceConsulting
7x24Operations
ArchivingDB-Migration
TechnicalConsulting
Co-operationwith otherSAP teams
if required
...Business
Consulting
Analysis
SLO
![Page 10: SAP SLO System Client Merge](https://reader030.fdocuments.net/reader030/viewer/2022020803/5571fd48497959916998c13e/html5/thumbnails/10.jpg)
5/10/2018 SAP SLO System Client Merge - slidepdf.com
http://slidepdf.com/reader/full/sap-slo-system-client-merge-55a0c6bd82f81 10/44 SAP AG 2002, Title of Presentation, Speaker Name / 10
Overview of SLO’s technical methods
Conversion (using Conversion Workbench)
Change existing structures within one client / system Availability of data and document flow for all completed and open
transactions in target structure
Migration (using Migration Workbench)
Transfer business objects across systems / clients
Add to / change existing structures in target system Availability of data and document flow for all completed and open
transactions in target structure in target system
Data transfer (using Legacy System Migration Workbench (LSMW))
SAP standard tool for legacy data transfer
Can be used for reorganization purposes Implement required structures
Copy master data
Transfer selected data (e. g. balances, open items)
Detailed comparison of the methods
![Page 11: SAP SLO System Client Merge](https://reader030.fdocuments.net/reader030/viewer/2022020803/5571fd48497959916998c13e/html5/thumbnails/11.jpg)
5/10/2018 SAP SLO System Client Merge - slidepdf.com
http://slidepdf.com/reader/full/sap-slo-system-client-merge-55a0c6bd82f81 11/44 SAP AG 2002, Title of Presentation, Speaker Name / 11
System consolidation – general overview
Client copy Migration(MWB)
Client transfer
Conversionsolution
Migration(MWB)
Data transfer(LSMW)
Client merge
Systemconsolidation
![Page 12: SAP SLO System Client Merge](https://reader030.fdocuments.net/reader030/viewer/2022020803/5571fd48497959916998c13e/html5/thumbnails/12.jpg)
5/10/2018 SAP SLO System Client Merge - slidepdf.com
http://slidepdf.com/reader/full/sap-slo-system-client-merge-55a0c6bd82f81 12/44 SAP AG 2002, Title of Presentation, Speaker Name / 12
Content
System Landscape Optimization (SLO)
Client Merge
Conversion approach (Conversion Workbench
Migration approach (Migration Workbench)
Data transfer
Further Information
![Page 13: SAP SLO System Client Merge](https://reader030.fdocuments.net/reader030/viewer/2022020803/5571fd48497959916998c13e/html5/thumbnails/13.jpg)
5/10/2018 SAP SLO System Client Merge - slidepdf.com
http://slidepdf.com/reader/full/sap-slo-system-client-merge-55a0c6bd82f81 13/44 SAP AG 2002, Title of Presentation, Speaker Name / 13
Typical reasons for a client merge
Reduce size of system landscape and simplify it
Make maintenance and administration easier
Reduce costs
Re-centralize
Prepare for e-commerce
Merge companies that currently have their own separate R/3
systems
Harmonize structures and business processes
What is the reason for the given project?
![Page 14: SAP SLO System Client Merge](https://reader030.fdocuments.net/reader030/viewer/2022020803/5571fd48497959916998c13e/html5/thumbnails/14.jpg)
5/10/2018 SAP SLO System Client Merge - slidepdf.com
http://slidepdf.com/reader/full/sap-slo-system-client-merge-55a0c6bd82f81 14/44 SAP AG 2002, Title of Presentation, Speaker Name / 14
Content
System Landscape Optimization (SLO)
Client Merge
Conversion approach (Conversion Workbench
Migration approach (Migration Workbench)
Data transfer
Further Information
Basic facts on the conversion method (for client
![Page 15: SAP SLO System Client Merge](https://reader030.fdocuments.net/reader030/viewer/2022020803/5571fd48497959916998c13e/html5/thumbnails/15.jpg)
5/10/2018 SAP SLO System Client Merge - slidepdf.com
http://slidepdf.com/reader/full/sap-slo-system-client-merge-55a0c6bd82f81 15/44 SAP AG 2002, Title of Presentation, Speaker Name / 15
Basic facts on the conversion method (for clientmerge)
A client merge by means of the conversion method...
After the conversion, the target client willlook as if it had always been like that
... Affects the complete dataset of a client
... Cannot be restricted to certain parts of the dataE. g. individual fiscal years or applications
... Is not related to a key date
... Is not related to any SAP transactionsNo logical validation (SAP standard checks)
No change documents are created
![Page 16: SAP SLO System Client Merge](https://reader030.fdocuments.net/reader030/viewer/2022020803/5571fd48497959916998c13e/html5/thumbnails/16.jpg)
5/10/2018 SAP SLO System Client Merge - slidepdf.com
http://slidepdf.com/reader/full/sap-slo-system-client-merge-55a0c6bd82f81 16/44 SAP AG 2002, Title of Presentation, Speaker Name / 18
Client Merge - Principle
“Source client” remains in the system, but is no longer usedproductively
“Target client” contains all relevant data from the source client afterthe conversion and looks as if it had always been like that
Client 010
Client 020
System B
Client 010
Client 020
System B
![Page 17: SAP SLO System Client Merge](https://reader030.fdocuments.net/reader030/viewer/2022020803/5571fd48497959916998c13e/html5/thumbnails/17.jpg)
5/10/2018 SAP SLO System Client Merge - slidepdf.com
http://slidepdf.com/reader/full/sap-slo-system-client-merge-55a0c6bd82f81 17/44 SAP AG 2002, Title of Presentation, Speaker Name / 19
Client merge by means of conversion approach
ALL master and transaction data from the source client istransferred to the target client
Depending on conditions at the outset of the project, this mayinvolve a huge renumbering effort!
Customizing settings of target client have priority
Settings from target client are not changed
Different settings from source client are discarded Additional settings from the source client are transferred to the
target
If you need to keep any settings from the source client, or changesettings in the target client, this requires additional work in the
preparation phase Conflicts are found during the pre-analysis
![Page 18: SAP SLO System Client Merge](https://reader030.fdocuments.net/reader030/viewer/2022020803/5571fd48497959916998c13e/html5/thumbnails/18.jpg)
5/10/2018 SAP SLO System Client Merge - slidepdf.com
http://slidepdf.com/reader/full/sap-slo-system-client-merge-55a0c6bd82f81 18/44 SAP AG 2002, Title of Presentation, Speaker Name / 20
Client merge by means of conversion approach
Organizational units from the source client are transferred tothe target client without being changed in any way
Organization al units need to be disjoint, that is, each ID may occur only once in all affected clients organizational units can be renamed by means ofconversion if necessary
Example: In both the source client and the target client, there is a controlling area0001 one of these (normally the one from the target client) needs to be renamed
If required, lower-level structures (e. g. controlling areas) can be merged lateron
KOKRS
K001
KOKRS
K002
MANDTM001
KOKRS
K003
MANDTM002
KOKRS
K004
KOKRS
K005
MANDTM003
System
S001
KOKRS
K001
KOKRS
K002
KOKRS
K003
MANDTM001
KOKRS
K004
KOKRS
K005
MANDTM003
SystemS001
![Page 19: SAP SLO System Client Merge](https://reader030.fdocuments.net/reader030/viewer/2022020803/5571fd48497959916998c13e/html5/thumbnails/19.jpg)
5/10/2018 SAP SLO System Client Merge - slidepdf.com
http://slidepdf.com/reader/full/sap-slo-system-client-merge-55a0c6bd82f81 19/44 SAP AG 2002, Title of Presentation, Speaker Name / 21
“Basis package“ for client merge already contains solutions for
several typical tasks, such as
Renaming of clients, logical systems, FI document types, ledgernumbers
Automatic renumbering of transaction data
Automatic renumbering of documents, change documents,conditions
Renumbering of CO objects
Solutions for additional project-specific tasks (renaming,changing number ranges) are developed using the ConversionWorkbench
Standardized definition of conversion logic for a given task Implementation of necessary changes by means of generated
conversion programs
Client merge by means of conversion approach
![Page 20: SAP SLO System Client Merge](https://reader030.fdocuments.net/reader030/viewer/2022020803/5571fd48497959916998c13e/html5/thumbnails/20.jpg)
5/10/2018 SAP SLO System Client Merge - slidepdf.com
http://slidepdf.com/reader/full/sap-slo-system-client-merge-55a0c6bd82f81 20/44 SAP AG 2002, Title of Presentation, Speaker Name / 22
Client Merge: Structure of the technical concept
Size of individual components depends on
requirements in the project!
“Basis
package“ for client merge
Pre-definedsolutions thatcan be includedin the project ifrequired
Project specificadditional
development
![Page 21: SAP SLO System Client Merge](https://reader030.fdocuments.net/reader030/viewer/2022020803/5571fd48497959916998c13e/html5/thumbnails/21.jpg)
5/10/2018 SAP SLO System Client Merge - slidepdf.com
http://slidepdf.com/reader/full/sap-slo-system-client-merge-55a0c6bd82f81 21/44 SAP AG 2002, Title of Presentation, Speaker Name / 23
Client Merge: Restrictions
The following data will NOT be considered in the standard versionof a client merge:
R/3 User master data, authorizations, profiles and activity groups New authorization concept is needed!
R/3 System tables
Spool, Batch Input, jobs
ABAP queries
![Page 22: SAP SLO System Client Merge](https://reader030.fdocuments.net/reader030/viewer/2022020803/5571fd48497959916998c13e/html5/thumbnails/22.jpg)
5/10/2018 SAP SLO System Client Merge - slidepdf.com
http://slidepdf.com/reader/full/sap-slo-system-client-merge-55a0c6bd82f81 22/44 SAP AG 2002, Title of Presentation, Speaker Name / 24
Specifics
Archives can be converted by means of SLO Archiving Services.Without an archiving conversion Only the technical view of SAP Archive Information System (SAP AS) will be
fully available Unrestricted access to archives from the applications and via reporting is no
longer guaranteed after the conversion
Authorizations and Authorization objects are not converted
Manual adaptation required after the merge
Data from HR (Human Resources) is not covered by the standardservice, but can be included if necessary
Often it is possible to change the relevant HR data using standard functions
Data from Industry Solutions and other mySAP Business Suiteproducts is not covered by the standard service, but can be included ifnecessary Details need to be analyzed and discussed on project basis
SLO Technical Services are available e. g. for
Analysis of report variants
Doing a Coding Scan
![Page 23: SAP SLO System Client Merge](https://reader030.fdocuments.net/reader030/viewer/2022020803/5571fd48497959916998c13e/html5/thumbnails/23.jpg)
5/10/2018 SAP SLO System Client Merge - slidepdf.com
http://slidepdf.com/reader/full/sap-slo-system-client-merge-55a0c6bd82f81 23/44 SAP AG 2002, Title of Presentation, Speaker Name / 25
Prerequisites
The conversion blueprint must cover all applications and systemsthat are linked via interfaces
E. g. all clients that belong to an ALE integrated system
E. g. related systems (non-R/3 systems) for reporting, consolidationetc.
Make sure that data exchange between the systems will workcorrectly after the merge
Preparation of tests is an important part of the conversionblueprint!
Define general test procedures
Define test procedures for business processes
Provide test data and reports for reconciliation/comparison such as Balance sheet, account balances, ...
![Page 24: SAP SLO System Client Merge](https://reader030.fdocuments.net/reader030/viewer/2022020803/5571fd48497959916998c13e/html5/thumbnails/24.jpg)
5/10/2018 SAP SLO System Client Merge - slidepdf.com
http://slidepdf.com/reader/full/sap-slo-system-client-merge-55a0c6bd82f81 24/44
SAP AG 2002, Title of Presentation, Speaker Name / 26
Technical prerequisites
Access to server SAPSERV<X>
Transports provided by SLO must be imported
OSS connection
Test conversion and conversion of production system are usuallydone via remote connection
Users with the necessary authorizations must be provided(SAP_ALL, if possible)
Data backup prior to conversion
It must be possible to reload the data backup in case problemsoccur during the conversion!
System settings for the conversion
Change system parameters for the conversion Note 534036 System settings for conversions
and Note 376787 Technical documentation for 4.0 Conversions
Other settings at database and operating system level
T h i l b k d
![Page 25: SAP SLO System Client Merge](https://reader030.fdocuments.net/reader030/viewer/2022020803/5571fd48497959916998c13e/html5/thumbnails/25.jpg)
5/10/2018 SAP SLO System Client Merge - slidepdf.com
http://slidepdf.com/reader/full/sap-slo-system-client-merge-55a0c6bd82f81 25/44
SAP AG 2002, Title of Presentation, Speaker Name / 27
Conversion using clusters
Can be restarted
Does not depend on size of individual tables
Technical background
Cli t M P d
![Page 26: SAP SLO System Client Merge](https://reader030.fdocuments.net/reader030/viewer/2022020803/5571fd48497959916998c13e/html5/thumbnails/26.jpg)
5/10/2018 SAP SLO System Client Merge - slidepdf.com
http://slidepdf.com/reader/full/sap-slo-system-client-merge-55a0c6bd82f81 26/44
SAP AG 2002, Title of Presentation, Speaker Name / 28
Client Merge: Procedure
Project phases (high-level)
Technical analysis of the system shows feasibility of the conversionand project scope
A task list for unification of Customizing and master data is created
Draw up a blueprint for the conversion and have it accepted
Maintenance of control tables, e. g. for converting document numbers andnumber ranges; project-specific development (if required)
Several test conversions and thorough tests of conversion results
“Customizing freeze“ before last test conversion
Do not introduce e. g. new applications, tables or business transactions
Only “approved“ transports
Otherwise: Problems may occur during production conversion
Conversion of production system
Timeline Depends on numerous factors (e. g. database size, hardware,
requirements) For details, see next slide
Client Merge: Procedure and duration of individual
![Page 27: SAP SLO System Client Merge](https://reader030.fdocuments.net/reader030/viewer/2022020803/5571fd48497959916998c13e/html5/thumbnails/27.jpg)
5/10/2018 SAP SLO System Client Merge - slidepdf.com
http://slidepdf.com/reader/full/sap-slo-system-client-merge-55a0c6bd82f81 27/44
SAP AG 2002, Title of Presentation, Speaker Name / 29
Client Merge: Procedure and duration of individualsteps (according to experience)
1. Analysis: One to four weeks (and even longer for very complex projects)
2. Decision in favor of one solution, specification of project procedure: Depends
on workflows within customer company; usually about four weeks
(If necessary, consider also time required for client transfer!)
3. Project-specific development: Depends on requirements found duringanalysis
4. Client Merge: Technical cycle without subsequent acceptance tests: Five
weeks
5. Client Merge: First test run with subsequent acceptance tests : Five weeks
6. Client Merge: Second test run with subsequent acceptance tests : Four weeks
(If necessary, four weeks for each additional test run)
7. Client Merge: Last test run with subsequent acceptance tests : Four weeks
8. Client Merge: Preparations for production conversion: One week
9. Client Merge: Production conversion and post-processing: One week(production conversion itself is done at week-end)
T t i
![Page 28: SAP SLO System Client Merge](https://reader030.fdocuments.net/reader030/viewer/2022020803/5571fd48497959916998c13e/html5/thumbnails/28.jpg)
5/10/2018 SAP SLO System Client Merge - slidepdf.com
http://slidepdf.com/reader/full/sap-slo-system-client-merge-55a0c6bd82f81 28/44
SAP AG 2002, Title of Presentation, Speaker Name / 30
Test conversion
Prerequisites
Tasks as defined after the analysis must be completed
Preparation for test conversion
Provide test system (customer)
Test system = Copy of production system (the more recent, the better)
Hardware and application data are comparable to those of theproduction system
Test system should be available exclusively for conversion purposesduring the complete project duration
Import necessary transports
Reliability of the runtime estimation for the production conversion
is determined by similarity between test system and productionsystem
As a rule, a reliable runtime estimation is not possible until after the firsttest conversion
C i f d ti t
![Page 29: SAP SLO System Client Merge](https://reader030.fdocuments.net/reader030/viewer/2022020803/5571fd48497959916998c13e/html5/thumbnails/29.jpg)
5/10/2018 SAP SLO System Client Merge - slidepdf.com
http://slidepdf.com/reader/full/sap-slo-system-client-merge-55a0c6bd82f81 29/44
SAP AG 2002, Title of Presentation, Speaker Name / 31
Conversion of production system
Preparation
Import the transports provided by SLO and the customer-specific
modifications (e. g. test results)
Execution Conversion is usually done during a weekend so as not to interfere with daily
business
Project team members must be available!
This refers in particular to the system administrator
Operating system maintenance, database, SAP Basis such as transport system...
System lock Production system is locked during data conversion
System lock covers all clients in the system!
No other work is possible at that time – even in clients that do not participate in theconversion
System lock is not lifted until test of results has been successfully completed
Data backup prior to conversion It must be possible to reload the data backup in case problems occur during
the conversion!
Cli t M T t
![Page 30: SAP SLO System Client Merge](https://reader030.fdocuments.net/reader030/viewer/2022020803/5571fd48497959916998c13e/html5/thumbnails/30.jpg)
5/10/2018 SAP SLO System Client Merge - slidepdf.com
http://slidepdf.com/reader/full/sap-slo-system-client-merge-55a0c6bd82f81 30/44
SAP AG 2002, Title of Presentation, Speaker Name / 32
Client Merge: Test
Test of conversion results is soleresponsibility of customer Define suitable test procedures
(customer) SAP cannot provide test plans and
procedures for all possibleconstellations
Project members test conversionresults using the defined testprocedures
Scope of tests is similar to those that
are normally done after a systemupgrade
How many and which tests are requireddepends to a large extent on thespecific conditions in the affected SAPsystem
Tip: Have a look at documentationrequirements and recommendations fortesting that apply for the Euro
conversion and adapt them accordingly Customer confirms in writing that test
conversion was successful
This confirmation is a mandatoryprerequisite for the productionconversion
Tip:
Compare lists (status before
and after conversion)
Account balances for G/L accounts,customers, vendors
Open items lists for G/L accounts,customers, vendors
Asset history sheet, list of stock
values for assets Inventory management list for stock
account
Special Ledger
...
Test business processes
e. g. depreciation posting runs,purchasing process frompurchasing requisition to goodsreceipt, sales process fromcustomer request to delivery /returns, ...
Client Merge: Main tasks of project team (customer)
![Page 31: SAP SLO System Client Merge](https://reader030.fdocuments.net/reader030/viewer/2022020803/5571fd48497959916998c13e/html5/thumbnails/31.jpg)
5/10/2018 SAP SLO System Client Merge - slidepdf.com
http://slidepdf.com/reader/full/sap-slo-system-client-merge-55a0c6bd82f81 31/44
SAP AG 2002, Title of Presentation, Speaker Name / 33
Client Merge: Main tasks of project team (customer)
Collaboration of customer (project team) is needed:
For evaluation of analysis results
As contact persons for questions (business-related as well asorganizational)
Customer is responsible for:
Change management (e. g. information for end users)
Adaptation of authorization concept
Check interfaces with third-party and downstream systems and adaptthem if necessary
Provide test system
Check results of the conversion
Provide system administration/ basis support (e. g. data backups)
Allocation of tasks in SLO projects
![Page 32: SAP SLO System Client Merge](https://reader030.fdocuments.net/reader030/viewer/2022020803/5571fd48497959916998c13e/html5/thumbnails/32.jpg)
5/10/2018 SAP SLO System Client Merge - slidepdf.com
http://slidepdf.com/reader/full/sap-slo-system-client-merge-55a0c6bd82f81 32/44
SAP AG 2002, Title of Presentation, Speaker Name / 34
Allocation of tasks in SLO projects
Project team (customer)
Specialists from application departments Business and organizational issues
Conversion blueprint
Mapping tables (if applicable)
Information on customer-specific tablesand programs
Test results of conversions
System administrators / IT staff
Technical issues
Information on customer-specific tablesand programs
Technical prerequisites
Provide test system
Import necessary transports Transports from test system to production
system
OSS connection and user
System settings (number of batchprocesses, tablespaces)
The members of the projectteam must be availableduring the complete projectduration
This applies in particular to theweekend of the productionconversion
and also for staff from thirdparties (if IT administration isoutsourced)
A lot of experience with conversion method
![Page 33: SAP SLO System Client Merge](https://reader030.fdocuments.net/reader030/viewer/2022020803/5571fd48497959916998c13e/html5/thumbnails/33.jpg)
5/10/2018 SAP SLO System Client Merge - slidepdf.com
http://slidepdf.com/reader/full/sap-slo-system-client-merge-55a0c6bd82f81 33/44
SAP AG 2002, Title of Presentation, Speaker Name / 35
A lot of experience with conversion method
After the creation the SLO team in 2000, the conversionmethod proved its worth in about 700 SLO projects
Chart of Accounts Conversions
Fiscal Year Conversions
Material Number Conversions
....
Plus more than 6000 Euro conversions in which the conversionmethod was used as well
About 25 SLO Client Merges using the conversionmethod have been carried out to date (starting in2000)
Content
![Page 34: SAP SLO System Client Merge](https://reader030.fdocuments.net/reader030/viewer/2022020803/5571fd48497959916998c13e/html5/thumbnails/34.jpg)
5/10/2018 SAP SLO System Client Merge - slidepdf.com
http://slidepdf.com/reader/full/sap-slo-system-client-merge-55a0c6bd82f81 34/44
SAP AG 2002, Title of Presentation, Speaker Name / 36
Content
System Landscape Optimization (SLO)
Client Merge
Conversion approach (Conversion Workbench
Migration approach (Migration Workbench)
Data transfer
Further Information
Client Merge by means of Migration Workbench -
![Page 35: SAP SLO System Client Merge](https://reader030.fdocuments.net/reader030/viewer/2022020803/5571fd48497959916998c13e/html5/thumbnails/35.jpg)
5/10/2018 SAP SLO System Client Merge - slidepdf.com
http://slidepdf.com/reader/full/sap-slo-system-client-merge-55a0c6bd82f81 35/44
SAP AG 2002, Title of Presentation, Speaker Name / 37
Client 020
System B
g y gPrinciple
Client 010
System A
MWB system
Migration Workbench (MWB)
![Page 36: SAP SLO System Client Merge](https://reader030.fdocuments.net/reader030/viewer/2022020803/5571fd48497959916998c13e/html5/thumbnails/36.jpg)
5/10/2018 SAP SLO System Client Merge - slidepdf.com
http://slidepdf.com/reader/full/sap-slo-system-client-merge-55a0c6bd82f81 36/44
SAP AG 2002, Title of Presentation, Speaker Name / 38
Migration Workbench (MWB)
MWB
Data reader (server) Data writer (server)
Controller
Accessplan
Run /
Restart
info
Data reader (client)
Data converter
Data writer (client)
4711Johnnie W
1881Jim Beam
0001Johnnie W
0002 Jim Beam
Sender Receiver
Content
![Page 37: SAP SLO System Client Merge](https://reader030.fdocuments.net/reader030/viewer/2022020803/5571fd48497959916998c13e/html5/thumbnails/37.jpg)
5/10/2018 SAP SLO System Client Merge - slidepdf.com
http://slidepdf.com/reader/full/sap-slo-system-client-merge-55a0c6bd82f81 37/44
SAP AG 2002, Title of Presentation, Speaker Name / 39
Content
System Landscape Optimization (SLO)
Client Merge
Conversion approach (Conversion Workbench
Migration approach (Migration Workbench)
Data transfer
Further Information
Data transfer
![Page 38: SAP SLO System Client Merge](https://reader030.fdocuments.net/reader030/viewer/2022020803/5571fd48497959916998c13e/html5/thumbnails/38.jpg)
5/10/2018 SAP SLO System Client Merge - slidepdf.com
http://slidepdf.com/reader/full/sap-slo-system-client-merge-55a0c6bd82f81 38/44
SAP AG 2002, Title of Presentation, Speaker Name / 40
Data transfer
General remarks
The joint client is newly created in Customizing together with the
related lower-level SAP organizational units Selected data is transferred
Copy master data
Transfer account balances, open items etc.
Data from completed and open processes is not transferred
„Old data“ can only be accessed via old structure Document flow is destroyed
Open business transactions are transferred explicitly
Can be a problem particularly for companies with complex logistics and/orlong-term processes or projects
The new joint client is used as of a key date
The source client is not used any more but are still visible in thesystem(s)
LSMW – Legacy System Migration Workbench
Data transfer
![Page 39: SAP SLO System Client Merge](https://reader030.fdocuments.net/reader030/viewer/2022020803/5571fd48497959916998c13e/html5/thumbnails/39.jpg)
5/10/2018 SAP SLO System Client Merge - slidepdf.com
http://slidepdf.com/reader/full/sap-slo-system-client-merge-55a0c6bd82f81 39/44
SAP AG 2002, Title of Presentation, Speaker Name / 41
Data transfer
Technical details
Objects / data that are relevant for the migration are identified
basically by means of analysis of the Business Objects andprocesses
LSMW is a standard tool for transferring data from legacy systems(third-party) to SAP R/3 systems
It must be possible to extract the data from the source system andprovide it in files
Data is imported into the SAP system by means of standardtransactions
E. g. Batch Input, Call Transaction, Direct Input, BAPIs or IDocs
SAP standard checks for consistency and correctness are made
LSMW – Legacy System Migration Workbench
Data transfer
![Page 40: SAP SLO System Client Merge](https://reader030.fdocuments.net/reader030/viewer/2022020803/5571fd48497959916998c13e/html5/thumbnails/40.jpg)
5/10/2018 SAP SLO System Client Merge - slidepdf.com
http://slidepdf.com/reader/full/sap-slo-system-client-merge-55a0c6bd82f81 40/44
SAP AG 2002, Title of Presentation, Speaker Name / 42
Data transfer
Project steps (high-level description)
Analysis of Business Objects and processes shows project scope
Export relevant data
Existing solutions can be re-used
Map the old structure to the new one (LSMW)
Specify source, target and conversion rules for all relevant data
The most frequently used conversion rules are pre-defined
Change business processes
(Several) test migrations and thorough test of results
Migration into production system
Duration
Normally about four to six months
LSMW in detail
LSMW – Legacy System Migration Workbench
Legacy Migration Workbench (LSMW)
![Page 41: SAP SLO System Client Merge](https://reader030.fdocuments.net/reader030/viewer/2022020803/5571fd48497959916998c13e/html5/thumbnails/41.jpg)
5/10/2018 SAP SLO System Client Merge - slidepdf.com
http://slidepdf.com/reader/full/sap-slo-system-client-merge-55a0c6bd82f81 41/44
SAP AG 2002, Title of Presentation, Speaker Name / 43
SAP Standard
One or several files
CONVERT_DATA
Batch Input processing
Legacy dataon PC
READ_DATA
Converteddata
Read dataLegacy data
on applicationserver
IDoc inboundprocessing
Direct Input processing
Structurerelations
Fieldmapping
Conversionrules
Legacy Migration Workbench (LSMW)
Content
![Page 42: SAP SLO System Client Merge](https://reader030.fdocuments.net/reader030/viewer/2022020803/5571fd48497959916998c13e/html5/thumbnails/42.jpg)
5/10/2018 SAP SLO System Client Merge - slidepdf.com
http://slidepdf.com/reader/full/sap-slo-system-client-merge-55a0c6bd82f81 42/44
SAP AG 2002, Title of Presentation, Speaker Name / 44
Content
System Landscape Optimization (SLO)
Client Merge
Conversion approach (Conversion Workbench
Migration approach (Migration Workbench)
Data transfer
Further Information
![Page 43: SAP SLO System Client Merge](https://reader030.fdocuments.net/reader030/viewer/2022020803/5571fd48497959916998c13e/html5/thumbnails/43.jpg)
5/10/2018 SAP SLO System Client Merge - slidepdf.com
http://slidepdf.com/reader/full/sap-slo-system-client-merge-55a0c6bd82f81 43/44
SAP AG 2002, Title of Presentation, Speaker Name / 45
Further information
SAP Service Marketplace
http://service.sap.com/slo
Conditions and prices
Contact the responsible local SAP Subsidiary
General enquiries
Send an e-mail to [email protected]
Questions? Remarks?
![Page 44: SAP SLO System Client Merge](https://reader030.fdocuments.net/reader030/viewer/2022020803/5571fd48497959916998c13e/html5/thumbnails/44.jpg)
5/10/2018 SAP SLO System Client Merge - slidepdf.com
http://slidepdf.com/reader/full/sap-slo-system-client-merge-55a0c6bd82f81 44/44
Questions? Remarks?