Introduction

1. Project name Customer Master Integration Project team name Team Members: Mona Kaushal Project Manager & Lead Puja Mehta QA, Trainer Project website: http://code.google.com/p/customer-master-integration/ Introduction CMI CMI BETA Prepared by Mona Kaushal

2. Agenda: Project brief Existing Problems with Multiple Master Data Systems Project scope-AS-IS Model Project scope-TO-BE Model Advantages of Consolidating Master Data into SAP system Why SAP ? SAP R/3 INTEGRATION MODEL Physical Distribution of R/3’s Logical Layers Architecture of SAP What is LSMW Project Methodology- Accelerated SAP Project Methodology Brief ASAP Methodology - Project Milestones and tasks Key ASAP Deliverables from each phase Project deliverable items System Req. Spec. Brief Questions? CS 532 (O)-Concepts in Software Engineering MID TERM Project presentation CMI

3. This project is scoped on creating a Centralized Customer Maser Database. The stakeholders of this project are from the Auto Industry. Currently there are two systems being used for maintaining Customer Master Data as of now. Dealer Information Database-(DID) - Mainframe DB2 database SAP - Oracle database Given the volume of the DID data, Customer Master Data maintenance in both the systems has become a nightmare. Going forward there is a need to merge these 2 systems. This interface will bring in all the changes (create/change/delete) made to the customer master from DID into SAP, on a daily basis to keep both the systems in sync. Project Brief CMI

4. CMI Existing Problems with Multiple Master Data Systems Issues with existing master data: • Redundant data • Incomplete data • Misaligned master data • Duplicate data Challenges faced by Business : • Streamline in-efficient business processes • Identify, match, and purge duplicate master data • Eliminate administrative miscommunication and costly supply chain delays • Simplify IT landscape and reduce costs for IT maintenance and support

5. Project Scope – “AS-IS”MODEL CMI Necessity to integrate two Customer Master Database systems and create a Unique Master Data Maintenance system LEGACY SYSTEM DEALER INFORMATION DATABASE SAP SYSTEM CUSTOMER MASTER DATA General data Name H.No. Street City State Zip Phone Fax Email address, Bank Name, Bank a/c no. etc... SAP CUSTOMER MASTER DATA General data Name H.No. Street City State Zip Phone Fax Email address, Bank Name, Bank a/c no. etc... DID Mainframe DB2 database Oracle database

6. Project Scope – “TO-BE” MODEL CMI LEGACY SYSTEM DEALER INFORMATION DATABASE SAP SYSTEM CUSTOMER MASTER DATA General data Name H.No. Street City State Zip Phone Fax Email address, Bank Name, Bank a/c no. etc... SAP CUSTOMER MASTER DATA General data Name H.No. Street City State Zip Phone Fax Email address, Bank Name, Bank a/c no. etc... DID Mainframe DB2 database Oracle database LSMW to upload data

7. Advantages of Consolidating Master Data into SAP system CMI Key Features: • Consolidate, harmonize, and centralize master data • Synchronize data from multiple sources • Consolidate and manage vendor data Business Benefits: • Improve effectiveness and efficiency • Increase productivity and reduce IT maintenance costs • Make strategic, accurate, and timely decisions • Publish and distribute relevant data

8. Benefits of implementing SAP Solution: CMI Why SAP Disadvantages of using SAP

9. Customer Master dependant modules SAP R/3 INTEGRATION MODEL FI Financial Accounting SD Sales & Distribution MM Materials Mgmt. CO Controlling PP Production Planning AM Fixed Assets Mgmt. R/3 SM Service Manage- ment EC Enterprise Controlling Integrated Solution Client / Server QM Quality Management PS Project System PM Plant Mainten- ance WF Workflow HR Human Resources IS Industry Solutions CMI

10. Physical Distribution of R/3’s Logical Layers reside in: reside in: reside in: CMI Application Layer components Presentation Layer components Database Layer components Presentation servers: Systems capable of providing a graphical interface. Application servers: Specialized systems multiple CPUs and vast amounts of RAM. Database servers: Specialized systems with fast and large hard drives.

11. Architecture of SAP CMI Communication The Presentation Layer collects user input and creates process requests. The Application Layer uses the application logic of SAP programs to collect and process the process requests. The Database Layer stores and retrieves all data.

12. CMI What is LSMW LSMW- Legacy System Migration Workbench The LSM Workbench is an R/3-based tool that supports you when transferring data from non-SAP systems ("Legacy Systems") to SAP systems once or periodically. The tool supports conversion of data of the legacy system in a convenient way.

13. Project Preparation Business Blueprint Realization Final Preparation (Preparation for Production Use) Go-Live & Support Project Methodology- Accelerated SAP CMI

14. Phase 1- Project preparation: Initial planning and preparation. Phase 2 - Business Blueprint: Conduct workshop with business stakeholders, Gather and document requirements. Phase 3 - Realization: Implement all business and process requirements based upon the business blueprint. Phase 4 - Final Preparation: Complete testing, user training, system management and cut-over activities. Phase 5 - Go-Live & Support: Transition from implementation to production. Project Methodology Brief CMI

15. CMI ASAP Methodology - Project Milestones and tasks

16. x x x x x Fun Specs Tech. Specs x x x x x Method- do logy Project Plan Test Plan Test Cases Scope Mile- stone Test mat. End User Training Materials Go-Live Plan CMI Key ASAP Deliverables from each phase: Project Preparation Final Preparation Go Live Business Blueprint Realization 4 5 2 3 1 Business Process Master List Req. Interfaces identified System Perform- ance Evaluation Bus. Processes identified Interfaces established Baseline SRS Conversion made

17. List of Project deliverables Project deliverable items CMI

18. CMI System Req. Spec. Brief

19. Questions? CMI