NAME

SAP MDM CONSULTANT

Mobile: +91-xxxxxxxxxx
Email ID: *******@gmail.com

Professional Summary

 8+years of Total IT Experience, majorly in SAP Master Data Management (MDM).

 Excellent knowledge of SAP MDM components like MDM server, Console, Data Manager, Import
Manager, and Syndicator.
 Worked on integration between ECC – XI and MDM focusing on Customer Master, Material Master, and
Vendor Master. The key features of the scenarios were Data Consolidation, Deduplication/Cleansing of
Master Data and use of ABAP APIs for search.
 Worked on integration between Legacy systems and MDM focusing on custom objects for shipping
industry.
 Knowledge of interfacing SAP MDM with SAP BI, SRM etc.
 Well versed with working on Master – Slave repositories in single and cross systems, exposure to real time
issues.
 Well versed with handling errors.
 Experienced in SAP MDM implementation in end-to-end development scenarios. Well equipped to handle
various phases in MDM projects like design, configuration, data loads and maintenance.
 Given KT to new technical & functional associates
 SAP ABAP Certified (83%):-Having exposure in ABAP Development workbench, Data Dictionary, Internal
Table, ABAP List Viewer (ALV), Function Modules, Dialog (Transaction) Programming.

Core Competencies
Programming: SAP MDM, ABAP API
Technical Trainings & Certification: SAP ABAP
Six Sigma Green Belt Trained.
 Professional Experience
In invert chronological order of employment

1. PROJECT Name: AMS support for various masters—Location Master, Vessel master, Activity Charge type
master.
Client Neptune Orient Lines(NOL)
Role Project Lead
Organization [company name]
Duration Oct 2013-July 2014
Team Size 10 Module: Master Data Management
Environment SAP MDM 7.1 SP7,PI,JAVA API, Legacy systems

Project Description
This project aims at Central master data management of custom objects like Location, vessel master involved in
shipping industry.
Scope
The scope of the project maintenance of existing master data objects like location master, vessel master, Activity
charge type master and Unit of Measure master.
Contribution
As a Project lead/member, was responsible for
 Requirement gathering for various enhancements
 Resolve tickets
 Import data
 MDM solution development as required for enhancements

2. PROJECT Name: Business Blueprint for eCatalog

Client GE Lighting USA
Role Project Lead
Organization [company name]
Duration June 2013-August 2013
Team Size 2 Module: Master Data Management
Environment SAP MDM 7.1

Project Description
This project aims at defining business blueprint for eCatalog project for GE Lighting.
Scope
The scope of the project includes requirement gathering and business blueprint for eCatalog.
Contribution
As a Project Lead, was responsible for
 Requirement gathering
 Prepare Business blueprint and functional specification document.
 Design eCatalog Architecture
 Analyze different tools as option for eCatalog.
 Analyze different tools for rich content like images, Videos, PDFs etc.
3. PROJECT Name: CMDM for various custom objects involved in shipping industry—Location Master, Vessel
master, Activity Charge type master.
Client Neptune Orient Lines(NOL)
Role Team Lead
Organization [company name]
Duration Oct 2011-May 2013
Team Size 10 Module: Master Data Management
Environment SAP MDM 7.1 SP7,PI,JAVA API, Legacy systems

Project Description
This project aims at Central master data management of custom objects like Location, vessel master involved in
shipping industry.
Scope
The scope of the project encapsulates importing data from legacy systems of NOL for all masters.After data
consolidation MDM is used as system of record. Other consuming systems receive data from MDM.
Contribution
As a team lead/member, was responsible for
 Data model Design
 Define Import maps and Data import for all masters.
 Define Syndication maps and Data export to NOL Remodel systems.
 Design Workflow.
 Define MDM validations and assignments.
 Define Roles and Authorizations for all masters.
 Define test script for Integration test.
 Define master slave architecture
 Define MDM LDAP integration

4A. PROJECT Name: Customer and Vendor Master Consolidation and CMDM
Client Suncor Energy Inc
Role Team Member
Organization [company name]
Duration Nov 2010-Jan 2011
Team Size 10 Module: Master Data Management
Environment SAP MDM 7.1 SP3,PI,ECC,Peoplesof

Project Description
This project aims at Central master data management of Vendor(EMPL and PAYR account groups) .
Scope
The scope of the project encapsulates importing data from Suncor ERP system into MDM, Cleansing it and
sending it back to Suncor ERP . Here MDM is used as system of record..
Contribution
As a team member, was responsible for
 Repository Modification
 Design Import maps fro various systems and Data import.
 Design Syndication maps and Data export to Suncor ECC.
 Design Workflow for syndication of data based on certain requirements.
 Configure MDMGX.Extract Reference data from Suncor ECC using MDMGX.
  Define Roles and Authorizations
 Define test script for Integration test.

4B. PROJECT Name: Customer/Vendor Consolidation

Client Suncor Energy Inc
Role Team Member
Organization [company name]
Duration Sep 2009-Oct 2011
Team Size 10 Module: Master Data Management
Environment SAP MDM 7.1 SP3,PI,ECC,Peoplesof,Suncor and Petro Canada Legacy systems

Project Description
This project aims at Central master data management of Customer/Vendor for different account groups in different
phases.
Scope
1)Joint Venture Scope-The scope of the project encapsulates importing data for Joint Venture Customers/Vendors
from Suncor ERP system and PeopleSoft system into MDM, Consolidating it and sending it back to Suncor ERP
and QBLM system to achieve single version of Customer/Vendor master. Going ahead MDM is used as system of
record.
Here the Business process was whenever a Joint venture Customer is created in SAP , it automatically creates a
Joint Venture Vendor in SAP. This process was replicated from MDM as in Whenever a Customer record is created
in MDM and sent to SAP , SAP creates the corresponding Vendor and sends back the vendor to MDM.
Once the Vendor is received in MDM a workflow is triggered to populate the Vendor number in Customer Table
which in turn triggers syndication to PeopleSoft Legacy System(QBLM).
2)Vendors and Manufacturer scope-This phase encapsulates Consolidation of two major account groups from
Suncor and Petro Canada systems. Data from Suncor ERP , PeopleSoft and Petro-Canada ECC was imported in
MDM temporary repository in QUT environment. The data consolidation and deduplication was done here in this
temporary repository. The merged data was then imported in Customer Vendor PRD repository. Here the challenge
was to do a fresh data load as this would affect the merged data here imports maps were designed as such so that
they do not affect the merged data but new data in all 3 systems was imported smoothly. Later MDM was the system
of record.
3)ZGAS scope-This phase aimed at consolidation of data from Suncor ERP and PeopleSoft system. Data from both
systems was consolidated and sent to Suncor and Petro-Canada Legacy(CXL) system.This again had the process
flow similar to Joint Vendor except for internal number range for Customer in SAP.MDM is now the system of
record.
4)IC,PLNT/ZPLT,ZREP, ZCRE scope- This phase aimed at consolidation of various Customer and Vendor
account groups from Suncor ECC system into MDM .Here Sales data and Partner function data along with Oil
Specific data was bought into picture, with MDM being system of record.

Contribution
As a team member, was responsible for
 Requirement gathering
 Repository Design and Modification as per each phase
 Design complex Import maps for various systems and Data import.
 Design Syndication maps and Data export to Suncor ECC, QBLM and CXL system.
 Design Validations,Assigments as per each account group
 Design Matching Strategies
 Design Workflow for syndication of data based on requirements.
 Configure MDMGX.Extract Reference data from Suncor ECC using MDMGX.
  Define Roles and Authorizations
 Define test script for Integration test.

Achievements:-Customer appreciation

4C. PROJECT Name: Customer/Vendor Sustainment project

Client Suncor Energy Inc
Role Team Lead
Organization [company name]
Duration May 2010-Oct 2011
Team Size 4 Module: Master Data Management
Environment SAP MDM 7.1 SP3

Scope
The scope of the project includes support for existing MDM environment that is Gone Live for 3 phases mentioned
above.
Contribution
As a team member, was responsible for
 Design for Enhancement for every pas eater go-live
 Resolve issues with Import of data (Value Exceptions especially).
 Work on syndication issues if there exists a problem in Target system.
 Daily Verify and Back up activity.
 Monitor ports for weekly reference data import and daily batch jobs.

5. PROJECT Name: People Data Store (Support Project)

Client Philips
Role Team Member
Organization [company name]
Duration May 2009-June 2009
Team Size 25 Module: Master Data Management
Environment SAP MDM 5.5 SP06, SAP ERP,SAP XI

Project Description
This project aims at harmonization of Employee Master Data to achieve single version of Employee master.
Scope
The scope of the project encapsulates importing data from various ERP systems and Portal system into MDM,
Consolidating it and sending it back to SAP ERP system to achieve single version of Employee master.
Contribution
As a team member, was responsible for
 Analysis of the specifications developed for Project
 Issue resolution while data import using MDIS (Import server).
 Modifying various strategies in Data Manager to identify duplicates.
 Issue resolution while data syndication using MDSS (Syndication server).

6. PROJECT Name: Asset Management (Data Migration)

Client In House development
Role Team Member
Organization [company name]
Duration Nov 2008-Jan 2009
Team Size 4 Module: Enterprise Data Management
Environment SAP MDM 5.5 SP06, MS – Excel 2003.

Project Description
This project includes effective resource utilization by consolidating Employee master data.
Scope
The scope of the project encapsulates migrating employee data from various systems; consolidating the data .The
later stage includes Central Master Data Management.
Contribution
As a team member, was responsible for
 Analysis of the specifications developed for Project
 Reviewing and updating the data model from time to time.
 Importing data coming from various source systems (Files) in MDM.
 Designing MDM Assignments.
 Consolidating the data in MDM.

7. Project Name: Innovative Implementation of ABAP APIs : DuPont Service Offering (SO)
Client DuPont RFP
Role EDM/MDM Technical Consultant /Team Leader
Organization [company name]
Duration June 2008 – August 2008
Team Size Project: 5 Module: Enterprise Data Management
Environment SAP MDM 5.5 SP06, SAP R/3 6.0C, SAP XI

Project Description: The Project focuses on Innovative way of Managing Business Operations in SAP R/3 viz Supply
Chain Process with the help of MDM APIs. Material Master Data is extracted and pulled into SAP MDM, cleansed
(Deduplication being done) and ABAP APIs pulls this refined Master Data from MDM and helps to search on MDM
repository containing refined data. Also it is through the API enabled Search; Purchase Order Creation is done with
refined Global Data.
Scope
The scope of the project includes only Global Data as obtained in MDM after merging .It excludes CMDM scenario.

Contribution:

As a Team Member was responsible for

 Business Requirement Understanding and Gap Analysis
 All MDM Technical Work for Material Master Data Consolidation
 All ABAP deliverables including ABAP API development.

8. PROJECT Name: SAP MDM SRM Catalog

Client Pratt & Whitney USA RFP
Role Team Member
Organization [company name]
Duration Jan2008-May 2008
Team Size 4 Module : Enterprise Data Management
Environment SAP MDM 5.5 SP05, SAP SRM 5.0, MS-Access 2003.

Project Description
This was a development project to fully understand and explore the functionality of the SAP MDM 5.5 product as a
product catalog.

Scope
The scope of project includes the Integration of MDM with SRM where MDM is used as Product Catalog. It
showcases the functionality of MDM as a Data Storage system, through which SRM forms its catalogue search. It
showcases realization of one of the complex Integration scenario.

Contribution
As a team member, was responsible for
 Analysis of the specifications developed for POC.
 Framing the system Landscape.
 Design and development of the Repository in MDM.
 Setting up the required configurations in MDM.
 Import of data, PDF’s and Images.
 Mapping Images and PDFs to the Records.
 Adding Governance to dataflow through Workflows.
 Establish Relationship between records.
 Established integration between SRM MDM using WAS.
 Developed the EBP configurations in SRM for catalog.
 Preparing Prototype Demo for Sales Presentation Kit.

Achievements
o Customer Appreciation

9. Project Name: Customer Data Integration (CDI) Through Multiple Repository Integration: Service Offering
(RFP)
Client AXA RFP-SAP APAC
Role EDM/MDM Technical Consultant /Team Leader
Organization [company name]
Duration November 2007 – January 2008
Team Size Project :6 Module : Enterprise Data Management
Environment SAP MDM 5.5 SP04, SAP R/3 6.0C, MS – Excel 2003

Project Description:
This RFP addresses the CDI problem. Customer Data along with Insurance Policy Data is being consolidated here
with the technique of Data Staging (2 repositories are used one for Staging (Only General Customer
Data), the other for final Consolidated Data (General Data + Policy Data).
Scope:
It was just an Integration with SAP MDM and Non SAP i.e. Legacy system.

Contribution:
As a Team Member was responsible for
 RFP development and Functional Spec Design
 All MDM Technical Deliverables

10. PROJECT Name: CRM Business Partner

Client FORD Australia RFP
Role Team Member
Organization [company name]
Duration Sep 2007- Nov 2007
Team Size 4 Module: Enterprise Data Management
Environment SAP MDM 5.5 SP04, MS – Access 2003.

Project Description
This is a complete business transformation of the project in which the Enterprise Data Management team is
responsible for managing the data at the enterprise level. MDM team is a part of EDM team, which manages the
Master data .It consolidates, harmonizes and centrally maintains the master data (Business Partner).
Scope
The scope of the project encapsulates importing data for different business objects from single source systems,
consolidating the data and then harmonizing the data back to the respective CRM systems.
It showcases the remarkable ease through which we can solve the most crucial problems faced by global giants in
synchronizing their distributed master data.
Contribution
As a team member, was responsible for
 Analysis of the specifications developed for Project
 Design and Implementation of the data plan model as repository model in MDM.
 Reviewing and updating the same from time to time.
 Designing MDM workflows.

11. Project Name: Product Hierarchy Consolidation: Service Offering (SO)

Client Volvo RFP
Role EDM/MDM Technical Consultant
Organization [company name]
Duration May, 2007 – August, 2007
Team Size Project: 5 Module: Enterprise Data Management
Environment SAP MDM 5.5 SP04, SAP BI

Project Description
This SO addresses the Product Hierarchy issue of Volvo CE .The Product Data is maintained in different level
Hierarchies across multiple systems. This SO showcases an innovative Solution Methodology to consolidate the
different level Hierarchy data, identify and eliminate the duplicates in MDM and also Standardize to a single
structure which drastically improves the Data quality, consequences of which is improved Reporting and Better
Business Process. The Consolidated and Standardized Hierarchy Data is syndicated to BI for reporting

Scope
The SO leverages some vital features of MDM viz Consolidation, Identification of Duplicates, Deduplication, Data
Governance and also integration with BI. It excludes Central Master Data Management scenario.

Contributions:
As a team member, was responsible for
 Analysis of the specifications developed for POC
 Design and development of the plan model
 Setting up the required configurations, assigning Roles and responsibilities
 Import of data (Initial load and subsequent deltas)
 Consolidating and Standardizing Data.
 Syndication (Export) of data to desired clients as required by the client.

12. Project Name SAP MDM COMPETENCY DEVELOPMENT

Client In – house
Role Team Member
Organization [company name]
Duration February 2007 – May 2007
Team Size 5 Module: Full life cycle implementation
Environment SAP MDM 5.5 SP04, SAP R/3 4.6C, XI, SAP BI ,SRM MS – Excel 2003 MS-Access
2003,XML .

Project Description
This is an In-house development project to fully understand and explore the functionality of the SAP MDM 5.5
product and realize the real world scenario and the problems that might be faced. It is a full life cycle
implementation with emphasis laid on understanding the integration of various components of MDM with other
Netweaver components.

Contribution
As a team member, was responsible for
 Analysis of the specifications developed for POC
 Design and development of the plan model
 Setting up the required configurations, assigning Roles and responsibilities
 Import of data (Initial load and subsequent deltas)
 Maintaining Rich GUI through the Data Manager
 Syndication (Export) of data to desired clients

Education
Qualification Institution Board/University Aggregate
Bachelors in Electronics
Engineering Dr D. Y Patil College Of Engineering
Shivaji University 71%
and Technology

Maharashtra State
XII Vivekanand College 82.5%
Board
Maharashtra State
X Holy Cross Convent School 82.13%
Board

Personal Information
Date of Birth: dd-mm-yyyy
Marital Status: Unmarried
Nationality: Indian
Language: English, Hindi,Sindhi