Scribd
Upload
77 views

Data Migration Strategy: © 2009 Infosys Technologies Limited

Uploaded by

Vinay Muddana
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
77 views

Data Migration Strategy: © 2009 Infosys Technologies Limited

Uploaded by

Vinay Muddana
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
You are on page 1/ 9

Data Migration Strategy

© 2009 Infosys Technologies Limited


Purpose
• Define migration approach
• Finalize the migration tools
• Recommend the best solution to carry out the migration
process

© 2009 Infosys Technologies Limited 2


Source Systems in scope
• SAP FI systems for Company information
• BCE SAP HR
• Lawson
• Data Sul
• Vanguard Wisesoft
• Others

© 2009 Infosys Technologies Limited 3


Approach to migration
• Standard ETL (Extraction, transformation and Loading) will
be used for migration.

• Steps involved in ETL

Activities Responsibility
Data Identification Rexam
Transformation Rexam with inputs from
Infosys
Data Cleansing and Preparation Rexam
Data Upload Infosys
(Development/Quality)
Data Reconciliation Infosys
Data Validation Rexam
Data Upload (Production) Rexam
© 2009 Infosys Technologies Limited 4
Options Evaluated
Approach Description Pros Cons
LSMW – Standard SAP mechanism – Best suited for data upload – Not suited for scenarios with
which internally uses one of without any customization variable screen sequence and
Direct input, BDC, BAPI or an – Suited with less complex country-specific screens
IDOC. data (single country) – Separate recording for country
specific requirements; therefore
increased number of objects
BDC – Custom code generated from – Useful when multiple – Relatively more development
pre-recorded SAP countries are involved and testing time
transaction, – Simpler even when screens – Effort required for issue
are customized resolution is relatively more
iDoc/BAPI – Uses standard structures – Standard SAP method for – Requires configuring the source
defined by SAP for pulling the communication and target system ports and
data from source system to RFC settings
SAP. – Complex
Custom – Custom programs are – More flexibility to define – Analysing the error log and
Programs developed using the requirements reprocessing mechanism are
necessary function modules complex and time consuming.
or BAPI and are generally
interfaced with proxies to
allow data exchange between
Legacy and SAP.

© 2009 Infosys Technologies Limited 5


Recommended Approach
• Recommended tool: BDC
– Useful for country specific information
– Common program for all countries
Sequence
• Organisation data
– Organization objects (jobs, positions and organization units)
– Organization hierarchy
– Standard templates and reports to be used
• Employee Data
– Actions (Infotype 0000), Employee Organisation Information
(Infotype 0001), Personal Information (Infotype 0002) and
Company Information (Infotype) 0032 through BDC programs
– Generate mapping between Legacy employee number and new
SAP employee number
– Upload data into remaining infotypes through BDC programs

© 2009 Infosys Technologies Limited 6


Key decisions – Data migration Strategy

• Convert employees on Hire date using “Hire Action” with


position 99999999;
• Use conversion action on go-live date

• Store last promotion date in Date Specifications

• Historical pay data for BCE&A to be stored in custom


infotype

© 2009 Infosys Technologies Limited 7


Key Decisions
• Common template to be used across all countries
• Upload Organization data followed by employee data
• Use BDC to upload PA data, which involves multiple
country specific data
• Use Global Employee numbering
• Migration for staff and hourly employees together

© 2009 Infosys Technologies Limited 8


Thank you

© 2009 Infosys Technologies Limited

You might also like