Introduction
Project name
Customer Master Integration
Project team name
Team Members:
Project website:
Mona Kaushal
Project Manager & Lead
Puja Mehta
QA, Trainer
http://code.google.com/p/customer-master-integration/
Prepared by Mona Kaushal
CS 532 (O)-Concepts in Software Engineering
MID TERM Project presentation
Agenda:
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.
16.
17.
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?
2
Project Brief
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.
2.
Dealer Information Database-(DID)
SAP
- Mainframe DB2 database
- 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.
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
Project Scope – “AS-IS” MODEL
Necessity to integrate two Customer Master Database systems and create a Unique Master
Data Maintenance system
LEGACY SYSTEM
SAP SYSTEM
DEALER INFORMATION DATABASE
DID
CUSTOMER MASTER DATA
General data
Name
H.No.
Street
City
State
Zip
Phone
Fax
Email address,
Bank Name,
Bank a/c no.
etc...
Mainframe DB2 database
SAP
CUSTOMER MASTER DATA
General data
Name
H.No.
Street
City
State
Zip
Phone
Fax
Email address,
Bank Name,
Bank a/c no.
etc...
Oracle database
Project Scope – “TO-BE” MODEL
LEGACY SYSTEM
SAP SYSTEM
DEALER INFORMATION DATABASE
SAP
DID
CUSTOMER MASTER DATA
General data
Name
H.No.
Street
City
State
Zip
Phone
Fax
Email address,
Bank Name,
Bank a/c no.
etc...
CUSTOMER MASTER DATA
General data
Name
H.No.
Street
City
State
Zip
Phone
Fax
Email address,
Bank Name,
Bank a/c no.
etc...
Mainframe DB2 database
Oracle database
LSMW to upload
data
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
Why SAP
Disadvantages of using SAP
•
Return on Investment
•
Locked into relationship by contract and
manageability with Vendor
Inflexibility- vendor packages
•
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
SAP R/3 INTEGRATION MODEL
Customer Master dependant modules
FI
Financial
Accounting
SD
Sales &
Distribution
MM
Materials
Mgmt.
CO
Controlling
PP
Production
Planning
SM
Service
Management
QM
Quality
Management
AM
Fixed Assets
Mgmt.
EC
Enterprise
Controlling
R/3
Integrated Solution
Client / Server
PM
Plant
Mainten- HR
ance Human
Resources
PS
Project
System
WF
Workflow
IS
Industry
Solutions
Physical Distribution of R/3’s Logical Layers
Presentation Layer
components
Application Layer
components
Database Layer
components
reside in:
reside in:
reside in:
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.
Architecture of SAP
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.
What is LSMW
LSMWLegacy
System
Migration
Workbench
Accelerating Data Migration: LSM Workbench
How LSM Workbench works
Legacy data
on PC
Read data
Read data
Structure
relations
Field mapping
Legacy data
on application
server
Convert data
Batch Input
processing
Conversion
rules
Converted
data
Direct Input
processing
IDoc inbound
processing
 SAP AG July 1999
21
R/3 Standard
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.
One or several
files
Project Methodology- Accelerated SAP

Project Preparation

Business Blueprint

Realization

Final Preparation (Preparation for Production Use)

Go-Live & Support
Project Methodology Brief

Phase 1- Project preparation:


Phase 2 - Business Blueprint:


Implement all business and process requirements based
upon the business blueprint.
Phase 4 - Final Preparation:


Conduct workshop with business stakeholders, Gather and
document requirements.
Phase 3 - Realization:


Initial planning and preparation.
Complete testing, user training, system management and
cut-over activities.
Phase 5 - Go-Live & Support:

Transition from implementation to production.
ASAP Methodology - Project Milestones and tasks
Project Milestones
Project Preparation
Business Blueprint
Activities
Week start date ----> 10
17
24
31
6
13
20
27
5
Weeks -----> W1
W2
W3
W4
W5
W6
W7
W8
W9
Project Start
Analysis
Design
Realization
Design Freeze /
Client Sign-off
Construction
Final Preparation
Go-live & Support
Testing
Implementation &
Training
Change mgmt &
support
May-10
Jun-10
Jul-10
12
19
Aug-10
26
2
9
16
W10 W11 W12 W13 W14 W15
Key ASAP Deliverables from each phase:

Project
Preparation
1
Project
Plan
Scope
Methoddo logy
Milestone
Business Blueprint
Realization
2
Req. Interfaces
identified
Bus. Processes
identified
Baseline
SRS
3
Final
Preparation
Go
Live
4
5
Business
Process
Master List
x
x
x
x
x
x
x
x
x
x
System
Performance
Evaluation
Fun Specs
Tech.
Specs
Test Cases
End User
Training
Materials
Interfaces
established
Conversion
made
Test Plan
Test mat.
Go-Live
Plan
Project deliverable items
List of Project deliverables
S.No
Description
Author
filename
Project Roadmap Methodology.ppt
1
2
Project Planning document
Project methodology document
Mona K
Mona K
3
Project milestones document
Mona K
4
System Requirement document
5
Work-shop documents
6
7
Functional specification document
Mapping document
8 Technical specification document
9 Test Cases/scripts
10 Training manual
11
Minutes of Meeting
Mona K
Mona K/Puja
Mehta
Mona K
Mona K
Mona K
Puja Mehta
Puja Mehta
Mona K/Puja
Mehta
Project_Milestones_and_tasks ver 2.0.xls
SystemRequirementsSpecificationCustomer Master Interface ver 1.0.doc
System Req. Spec. Brief
Questions?