Using BusinessObjects Data Services in support of Data Migration and Master Data Management For the Chicago Chapter BOUG Meeting – August 20, 2010 Dan Lopez, Manager at Capgemini

Agenda Why is Data Migration Needed? How has SAP Data Migration Historically Been Done? Emerging SAP Data Migration Best Practices How do I Manage Data Quality after Data Migration? Q&A

SAP Data Migration/Conversion Use Cases Mainframe Legacy Application Modernization / ERP Implementation SAP Application Portfolio Rationalization JDE i2 PeopleSoft Global SAP SAP Instance Consolidation SAP

Agenda Why is Data Migration Needed? How has SAP Data Migration Historically Been Done? Emerging SAP Data Migration Best Practices How do I Manage Data Quality after Data Migration? Q&A

How Has SAP Data Migration/Conversion Historically Been Done? “ Let’s cross the fingers’ and hope it loads… Historical Approaches ABAP/ LSMW LEGACY SYSTEM(S) SAP Custom Code Upload / ADM But Data migration is far from easy. The results were: Analysts Designing access to numerous source legacy systems and/or data silos Proper mapping of source to target files Assuring consistent metadata Resolving data quality problems Why? More than 80% of data migration projects run over time and/or over budget. Cost overruns average 30%. Time overruns average 41%. Bloor, 2007 80% of organizations… will underestimate the costs related to the data acquisition tasks by an average of 50 percent” Gartner What was needed was an approach that leveraged simplified tools, best practice methodology and content to address the full cycle of data migration processes. Used with permission from SAP

Agenda Why is Data Migration Needed? How has SAP Data Migration Historically Been Done? Emerging SAP Data Migration Best Practices How do I Manage Data Quality after Data Migration? Q&A

DELIVER Data Migration Methodology Example Data Migration Best Practices Taken From Capgemini's DELIVER Methodology DELIVER Data Migration Methodology DELIVER: A tested methodology developed globally, based on a structured approach for the migration and quality improvement of data. Focus Areas: Data Discovery helps to determine issues with data in an early stage and gives information needed to define conversion rules of higher quality. Frequent “Trial Conversions” or “Mock Migrations” are executed and tested against controls in order to provide quality and completion. Data mapping and cleansing leverages accelerators through a data migration factory model. Data controls are put in place up front in order to quantifiably measure the success of a data conversion, which is critical to the “Go/No Go” moment in the project.

SAP’s Best Practices Architecture for Data Migration Legacy Data Environment Data Staging and Test Environment Loading Target Environment Dashboards and Business Reporting Performance Analysis Staging Area Mainframe SAP Data Services Platform load routines for SAP Objects Cleanse Transform Validate & Load Extract & Profile Databases Name Parsing Business Validation Rules Transform Data into SAP structure IDocs Address Parsing & Correction SAP Config Validation Material/Product Parsing Applications Matching Reconciliation Flat Files/ Excel Used with permission from SAP

Project Acceleration through SAP’s Best Practice For Data Migration Key Features: Predefined Migration Content Data validation content for SAP Business Objects Data Integrator (including enrichment rules) for the SAP Best Practices Baseline Package and a broad set of industries the content includes also extraction jobs to extract check tables from the SAP target system for the value mapping. Documentation Quick guide on how to install and use Data Integrator and the SAP Best Practices for Data Migration content. Business Process Document for Data Migration is a process guide that provides a process flow and the sequence in which the objects need to be loaded Business Process Documents for Objects are independent object documents that provide you instructions on the complete object processing tasks within DI all the way to loading IDocs into SAP. Extension Guide provides the information you need to extend and modify the DI content that is an integral part of the SAP Best Practices Data Migration solution. Implementation Accelerator Mapping templates for the mapping workshop at the customer site including field and value mapping. Used with permission from SAP

Used with permission from SAP SAP Best Practice for Data Migration Leverages BusinessObjects Data Services Currently supported Data Migration Content Built on Business Objects Data Services for SAP Business All-in-One Cost Element Characteristic Class Activity Type Activity Price Customer Master Vendor Master Material Master Material Master Classification Material Inspection Type Material Customer Replenishment Purchase Info Record Inspection Method Master Insprection Characteristics Inspection Plan Object Dependency BOM Routing SD Pricing Inventory Balances A/P & A/R HCM Baseline Transactional data Sales Order Purchase Order Internal Order Source List WBS Functional Location SAP BusinessObjects™ Data Integrator is the most productive and scalable data integration platform for ETL Used with permission from SAP

Agenda Why is Data Migration Needed? How has SAP Data Migration Historically Been Done? Emerging SAP Data Migration Best Practices How do I Manage Data Quality after Data Migration? Q&A

Used with permission from SAP Apply the Same Technology for Data Migration After Go Live to Provide a Proactive Data Quality Firewall Used with permission from SAP

Used with permission from SAP Apply the Same Technology for Data Migration After Go Live to Provide Reactive Data Quality Scorecards • Completeness: Is all the requisite information available? Are data values missing, or in an unusable state? In some cases, missing data is irrelevant, but when the information that is missing is critical to a specific business process, completeness becomes an issue. • Conformity: Are there expectations that data values conform to specified formats? If so, do all the values conform to those formats? Maintaining conformance to specific formats is important in data representation, presentation, aggregate reporting, search, and establishing key relationships. • Consistency: Do distinct data instances provide conflicting information about the same underlying data object? Are values consistent across data sets? Do interdependent attributes always appropriately reflect their expected consistency? Inconsistency between data values plagues organizations attempting to reconcile between different systems and applications. • Accuracy: Do data objects accurately represent the “real-world” values they are expected to model? Incorrect spellings of product or person names, addresses, and even untimely or not current data can impact operational and analytical applications. • Duplication: Are there multiple, unnecessary representations of the same data objects within your data set? The inability to maintain a single representation for each entity across your systems poses numerous vulnerabilities and risks. • Integrity: What data is missing important relationship linkages? The inability to link related records together may actually introduce duplication across your systems. Not only that, as more value is derived from analyzing connectivity and relationships, the inability to link related data instance together impedes this valuable analysis. Used with permission from SAP

Agenda Why is Data Migration Needed? How has SAP Data Migration Historically Been Done? Emerging SAP Data Migration Best Practices How do I Manage Data Quality after Data Migration? Q&A

Together. Free your energies Dan Lopez Manager, Capgemini Business Information Management Orlando, Florida Phone: +1 (407) 655-9176 E-Mail: dan.lopez@capgemini.com Together. Free your energies www.capgemini.com The information contained in this presentation is proprietary. © 2010 Capgemini. All rights reserved