Project name Customer Master Integration Project team name Team Members: Mona KaushalProject Manager & Lead Puja MehtaQA, Trainer Project website:

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

Prepared by Mona Kaushal

2

Agenda:

1. Project brief

2. Existing Problems with Multiple Master Data Systems

3. Project scope-AS-IS Model

4. Project scope-TO-BE Model

5. Advantages of Consolidating Master Data into SAP system

6. Why SAP ?

7. SAP R/3 INTEGRATION MODEL

8. Physical Distribution of R/3’s Logical Layers

9. Architecture of SAP

10. What is LSMW

11. Project Methodology- Accelerated SAP

12. Project Methodology Brief

13. ASAP Methodology - Project Milestones and tasks

14. Key ASAP Deliverables from each phase

15. Project deliverable items

16. System Req. Spec. Brief

17. Questions?

CS 532 (O)-Concepts in Software Engineering MID TERM Project presentation

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.

1. Dealer Information Database-(DID) - Mainframe DB2 database

2. 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

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

Existing Problems with Multiple Master Data Systems

Project Scope – “AS-IS” MODEL

Necessity to integrate two Customer Master Database systems and create a Unique Master Data Maintenance system

CUSTOMER MASTER DATA

General dataNameH.No.StreetCityStateZipPhoneFaxEmail address, Bank Name,Bank a/c no.etc...

CUSTOMER MASTER DATA

General dataNameH.No.StreetCityStateZipPhoneFaxEmail address, Bank Name,Bank a/c no.etc...

DIDSAP

LEGACY SYSTEM

DEALER INFORMATION DATABASE

SAP SYSTEM

Mainframe DB2 databaseOracle database

Project Scope – “TO-BE” MODEL

LSMW to upload data

CUSTOMER MASTER DATA

General dataNameH.No.StreetCityStateZipPhoneFaxEmail address, Bank Name,Bank a/c no.etc...

CUSTOMER MASTER DATA

General dataNameH.No.StreetCityStateZipPhoneFaxEmail address, Bank Name,Bank a/c no.etc...

DIDSAP

LEGACY SYSTEM

DEALER INFORMATION DATABASE

SAP SYSTEM

Mainframe DB2 databaseOracle database

Advantages of Consolidating Master Data into SAP system

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

Benefits of implementing SAP Solution:

    • Increase revenue• Reduce costs• Adaptable

• Complete solution

• Personalized

• Improve customer relationships

• Maintain IT solution as you grow

• Clear, immediate insights

• Business Critical alerts

• Improve efficiency

• Support Multi-currency transactions

• Multi-lingual capabilities

Why SAP

Disadvantages of using SAP

• Return on Investment• Locked into relationship by contract and

manageability with Vendor• Inflexibility- vendor packages

Customer Master dependant modules

SAP R/3 INTEGRATION MODEL

R/3R/3

FIFIFinancialFinancial

AccountingAccounting

COCOControllingControlling

PSPSProjectProjectSystemSystem

WFWFWorkflowWorkflow

ISISIndustryIndustry

SolutionsSolutions

MMMMMaterialsMaterials

Mgmt.Mgmt.

HRHRHumanHuman

ResourcesResources

SDSDSales &Sales &

DistributionDistribution

PPPPProductionProductionPlanningPlanning

QMQMQualityQuality

ManagementManagementPMPM

Plant Plant Mainten-Mainten-

anceance

SMSMServiceServiceManage-Manage-

mentment Integrated SolutionIntegrated SolutionClient / ServerClient / Server

ECECEnterpriseEnterpriseControllingControlling

AMAMFixed AssetsFixed Assets

Mgmt.Mgmt.

Physical Distribution of R/3’s Logical Layers

reside in: reside in:reside in:

Database Layer components

Application Layer components

Application servers:Specialized systems multiple CPUs and vast amounts of RAM.

Application servers:Specialized systems multiple CPUs and vast amounts of RAM.

Presentation servers:Systems capable of providing a graphical interface.

Presentation servers:Systems capable of providing a graphical interface.

Presentation Layer components

Database servers:Specialized systems with fast and large hard drives.

Database servers:Specialized systems with fast and large hard drives.

Architecture of SAP

The Presentation Layercollects user input andcreates process requests.

The Presentation Layercollects user input andcreates process requests.

The Application Layeruses the application logic ofSAP programs to collect andprocess the process requests.

The Application Layeruses the application logic ofSAP programs to collect andprocess the process requests.

The Database Layerstores and retrieves all data.

The Database Layerstores and retrieves all data.

CommunicationCommunication

What is LSMW

SAP AG July 1999 21

Accelerating Data Migration: LSM Workbench

One or several files

R/3

Sta

nd

ard

Convert data

Batch Input processing

Legacy dataon PC

Read data

Converted data

Read dataLegacy data

on application server

IDoc inboundprocessing

Direct Input processing

How LSM Workbench works

Structure relations

Field mapping

Conversion rules

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.

Project Preparation

Business Blueprint

Realization

Final Preparation (Preparation for Production Use)

Go-Live & Support

Project Methodology- Accelerated SAP

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

ASAP Methodology - Project Milestones and tasks

  Activities May-10 Jun-10 Jul-10 Aug-10

Project MilestonesWeek start date

-----> 10 17 24 31 6 13 20 27 5 12 19 26 2 9 16

  Weeks -----> W1 W2 W3 W4 W5 W6 W7 W8 W9 W10 W11 W12 W13 W14 W15

Project PreparationProject Start                              

Business BlueprintAnalysis                              

Realization

Design                              

Design Freeze / Client Sign-off                              

Construction                              

Final PreparationTesting                              

Go-live & Support

Implementation & Training                              

Change mgmt & support                              

1 2 3 4 5ProjectProjectPlanPlan

ScopeScope

Req. Interfacesidentified

Bus. Processesidentified

Interfacesestablished

Conversionmade

Fun SpecsTech. Specs

Test Cases

End UserTrainingMaterials

Test Plan

Test mat.

Go-Live Plan

xxxxx

x

xxxx

SystemPerform-anceEvaluation

Baseline SRS

Business ProcessMaster List

Business Blueprint RealizationFinalPreparation

ProjectPreparation

GoLive

Key ASAP Deliverables from each phase:

Method-Method-do logydo logy

Mile-Mile-stonestone

List of Project deliverables

Project deliverable items

S.No Description Author filename       1 Project Planning document Mona K  

2 Project methodology document Mona K Project Roadmap Methodology.ppt

3 Project milestones document Mona K Project_Milestones_and_tasks ver 2.0.xls

4 System Requirement document Mona KSystemRequirementsSpecification-

Customer Master Interface ver 1.0.doc

5 Work-shop documentsMona K/Puja

Mehta  

6 Functional specification document Mona K  

7 Mapping document Mona K  

8 Technical specification document Mona K  

9 Test Cases/scripts Puja Mehta  

10 Training manual Puja Mehta  

11 Minutes of MeetingMona K/Puja

Mehta  

System Req. Spec. Brief

SystemRequirement Specification-Customer

Questions?