4/24/07

4:00 Pm – 5:00 Pm
Session Code 0511
Presented by Paul Cahill & Gregg Schelmetic
Hubbell Wiring Systems

Improving Master Data

Quality at Hubbell
Agenda

• Quick Hubbell Overview

• Hubbell SAP History
• Master Data Challenges
• TxShuttle Applications
• Line Add Example
• With M3 & TX Shuttle
Learning Points

1.How to reduce errors and

improve quality of your SAP
master data
2.How to reduce the resources
required for SAP data
management
3.How to empower business units
to manage their own master
data
What Hubbell is not…
What Hubbell is…

Hubbell
• Connecticut based
• International manufacturer of
quality electrical products
• Serving the residential,
commercial, industrial and
utility markets

1888 Patent
Hubbell Structure – 5 Platforms

Electrical
Products
Wiring Systems

Industrial
Power Systems
Technologies
Lighting
What Hubbell Wiring Systems is..

Wiring Devices
Raceway
Wire Management
Safety Devices
Marine Devices
Lighting Control
Marine Devices
Hospital Devices
Network Wiring
Telephone Wiring
Fiber Optic Products
Hubbell SAP Implementation

HWS
Wiring Systems
Nov 2004

HIT HEP
Industrial Tech
Electrical Products
Oct 2006
Oct 2005

HPS HLI
Power Systems Lighting
Apr 2006 Oct 2005 - Oct 2006
Master Data Challenges – Nov 04

• Data conversion quality

• Customer, vendor, material, etc
• New business processes TBD
• Line add/delete
• Customer/vendor application
• Price change/maintenance
• Data ownership unclear
• SAP master data knowledge
Why Hubbell Needed A Tool

• SAP tools
• Lacked required functionality
• Too technical for most users
• Controlled by centralized IT
• Data quality was not improving
• Large number of
resources/users dedicated to
data management
Why TxShuttle?

• Excel based
• Excel knowledge base already existed
• User controlled easy-to-use solution
• No need to contact centralized IT group
• Short user training period
• SAP role based access control
• Tool limits user access based on assigned
SAP roles
• Audit trail
• Records all updates and activity
TxShuttle At Hubbell

• September 2005
• 30 day trial
• October 2005
• 9 named users
• Started with one user in a plant
• March 2007
• 54 named users
• Every platform uses the tool
• Expanded use planned
• TxShuttle, TablePro, TxRunner
TxShuttle & Master Data

• Master data
• Customer updates
• Sales hierarchy, partner functions, etc
• Material creation and updates
• D-chain, safety stock, item category, etc
• Vendor updates
• Tax ID, payment terms, etc
• Pricing creation and updates
• Price increase, back price roll, etc
• Employee updates
• Banking info, % pay increase
TxShuttle & Transactional Data

• Transactional data
• Inventory
• Used for all inventory events to feed actual on hand
levels back to SAP
• Receivables
• Close old/non-collectable receivables
• Purchase orders/PIRs
• Update open pos/PIRs with new terms, purchase price,
etc
• Production orders
• Close orders with partially open quantities
• Quote updates
• Add new skus and adjust pricing
Impact / Benefit of TxShuttle

• Quality of Data
• Dramatic increase on the overall quality due to
elimination of manual key strokes
• Tool helped hubbell document business processes
• Speed / Responsiveness
• Requests no longer go to central IT group
• Cut most requests down from days to hours
• Improved service levels to the business
• Resource / Time Savings
• Hubbell estimates we save 4 to 5 FTEs over a
year
Hubbell’s Use Of TxShuttle

M3 / TxShuttle / SAP
By Gregg Schelmetic
Hubbell’s Use Of TxShuttle

Question:

How long does it take to load

one finished good?
Loading a New Product
Manual Entry

- Line by Line from Spreadsheet

- Prone to Typos
- Missed Fields
- It’s going to take a while
Loading a New Product

24
Different
Screens
of Data
are
required

How Many
Fields in
Total?
The Material Master

Basic Data 1
15 Fields

15 So Far
The Material Master

Basic Data 2
3 Fields

18 So Far
The Material Master

Additional Data
6 Fields

24 So Far
The Material Master

Classification
4 Fields

28 So Far
The Material Master

Sales Org 1
7 Fields

35 So Far
The Material Master

Sales Org 2
15 Fields

50 So Far
The Material Master

Sales General/Plant
5 Fields

55 So Far
The Material Master

Export
3 Fields

58 So Far
The Material Master

Purchasing
5 Fields

63 So Far
The Material Master

Import
3 Copied Fields
(not counted)

63 So Far
The Material Master

MRP 1
8 Fields

71 So Far
The Material Master

MRP 2
11 Fields

82 So Far
The Material Master

MRP 3
5 Fields

87 So Far
The Material Master

MRP 4
3 Fields

90 So Far
The Material Master

Work Scheduling
1 Field

91 So Far
The Material Master

Plant Data Storage1

1 Field

92 So Far
The Material Master

Warehouse Mgmt 1
3 Fields

95 So Far
The Material Master

Accounting 1
2 Fields

97 So Far
The Material Master

Costing 1
4 Fields

101 So Far
The Material Master

Costing 2
6 Fields

107 So Far
The Material Master

MMSC
6 Fields

113 So Far
The Material Master

VK11 Base Price

9 Fields

Total:
127 Fields
Loading a New Product
Method: Manual Keying Data
1 Finished Good
Material SKU

Engineering S&D MDA Demand Planner Finance MDA

Creates MM01 Creates MM01 Creates MM01 Creates MM01

24 Fields Manually 46 Fields Manually 45 Fields Manually 12 Fields Manually
of Basic Data of Sales Org/Pricing Operations Data Finance Data

Totals: 127 Manual Entries per Plant

Jeopardy: - Decentralized
- Inconsistent data loads
- Missing fields
- Incorrect values
- Materials not available for sale
The Problem
Miss a key field?

If one goes out….

….They all go out

The Proposal

Let Automation do what Automation does

best….

AND

….Let People do what People do best

The Solutions

- Standardize the spreadsheets

- Normalize the data in the spreadsheets

- Eliminate as much hand keying as possible

- Explore methods of mass upload

- Establish Workflow
M3 Data Normalization

- M3 is a fully compatible PC based program

M3 Data Normalization

- Hubbell’s business rules are

contained within M3
M3 Data Normalization

M3
Interface

- Input 29 values 107 are created

automatically
- Only 20 values need manual entry
M3 Data Normalization

M3
Interface
Data Grid

- Data preview window

M3 Spreadsheet Standardization

- M3 has created formatted Excel spreadsheets

on a shared drive
- Pre-mapped for automatic upload into SAP via
TxShuttle
M3 Workflow

- M3 will E-Mail an automatic announcement

to a distribution group
M3 Workflow

- Attachment is the spreadsheet

- Subject is the project number
- Additional messages included
M3
Now we have standardized data
in standardized spreadsheets

- How does the data get into SAP?

M3 & TxShuttle

M 3 and TxShuttle
TxShuttle
What is TxShuttle?
An SAP transaction runner
Key Features:
- Any SAP transaction
- Simple, complex or custom
- Data transfer
- Upload or download
- Excel or Access and any SAP transaction
- No change to standard SAP
- Allows scheduled data transfers and transaction
runs in an unattended mode
TxShuttle

Creating
Upload
Maps

After watching one complete transaction, TxShuttle

learns what fields in SAP that data has been loaded to -
these are called Maps
TxShuttle - Learns Transaction

- One TxShuttle Map must be made for each

transaction required for a material load
TxShuttle - The “Map”

Fine Tuning
Map of
Transaction

M3
Spreadsheet
TxShuttle - Uploading Data
After Recording…

Run the Transaction:

- SAP Map
- M3 Spreadsheet #
- Sheet Name
- Start Row
- End Row

TxShuttle will load the spreadsheets created

by M3 into SAP rapidly and consistently
TxShuttle

Product
M3 TxShuttle SAP
Management
The Results
The New Way
Method: M3 & TxShuttle
1 Finished Good
Material SKU

S & D MDA
Creates MM01
107 Fields Automatically

Engineering S&D MDA Demand Planner Finance MDA

Modify MM02 Modify MM02 Modify MM02 Modify MM02

2 Fields Manually 0 Fields Manually 14 Fields Manually 4 Fields Manually
of Basic Data of Sales Org/Pricing Operations Data Finance Data

Totals: 20 Manual Entries per Plant

Jeopardy: None
The Results

Question:

How long does it take to load

one finished good?

Answer:

Manually- About 5 Minutes per SKU

Automated- About 4 Seconds per SKU
Impact / Benefit of TxShuttle

• Time/$ savings for 1 power user

• Est. 2 million fields up/downloaded in 1 year
• Estimated 100,000 + transactions performed
• Avg. Manual transaction 1.5 mins to complete
• TxShuttle transaction 2 seconds to complete
• 100,000 (trans) X 1.2 minutes (time savings) =
120,000 minutes
• 120,000 minutes/60= 2000 hours/40= 50 weeks
• 1 FTE/year
M3 & TxShuttle

Time Savings
+
Data Quality
+
Upload Consistency
Recipe for Success

1. Detail Business Rules - “If - Thens”

2. Determine User Interface- Excel or Custom Program?

3. Dedicate Resources- Who’s responsible for what?

4. Design Procedure - Should address various

material types.

5. Test and Verification

6. Training
Learning Points - Reviewed

1.How to reduce errors and

improve quality of your SAP
master data
2.How to reduce the resources
required for SAP data
management
3.How to empower business units
to manage their own master
data
Session Code:

0511