real world optimizations for sap material master data ... · pdf filereal world optimizations...
TRANSCRIPT
Real World Optimizations for SAP Material Master Data Processes Using Winshuttle Query, Central and Transaction Lance Yoder | Rockwell Automation
Winshuttle User Group | San Diego 2013
Who is Rockwell Automation?
The world's largest company dedicated to industrial automation
Headquartered in Milwaukee, Wisconson
About 23,000 employees
$6.3B 2012 Rev
Worlds largest four sided clock tower until 2010
“Not so” Big Ben – 23’
Rockwell Automation- 40’
Abraj Al Bait Tower – 140’
Winshuttle User Group | San Diego 2013
Rockwell Automation’s SAP Landscape
ECC 6.0
Still deploying SAP globally (and may be forever!) 104 actively managed SAP plants
36 actively managed SAP sales org
We have 200,000+ products for sale 3,758,498 plant extensions
4,612,573 sales org extension
“That’s a lot of dater!” – Lance’s Dad, at a BBQ after a few drinks, 2013
Winshuttle User Group | San Diego 2013
Where Does Lance Fit In?
Project Engineer working for the non-IT shared service group that “owns” the Material Master and related processes (with a degree in Chemical Engineering, this makes sense, right?)
Extensions, mass updates, data quality reports, etc
Main focus is process improvement in the material master area.
The old SAP-based extension and workflow process not good enough to meet business needs so redesigned the process using Winshuttle
Winshuttle User Group | San Diego 2013
2013 Extension Volumes through September
203,000 Sales Extensions
156,000 Plant Extensions
0
5000
10000
15000
20000
25000
30000
35000
40000
January '13 February '13 March '13 April '13 May '13 June '13 July '13 August '13 September'13
0
5000
10000
15000
20000
25000
30000
35000
January '13 February '13 March '13 April '13 May '13 June '13 July '13 August '13 September'13
Winshuttle User Group | San Diego 2013
Overview: Working the Process
1. Collect requests Excel based request forms
2. Gather live SAP data on those materials Winshuttle Query
3. Validate the requests and apply business rules Access
4. Extend the “good” requests Winshuttle Transaction
5. Tell people the results Email through Access
Winshuttle User Group | San Diego 2013
Step 1: Import the requests
Request Staging Folder
Access Database
Query Input File with materials
Winshuttle User Group | San Diego 2013
Step 2: Extract Real-time SAP data
File with materials used as input to
Query
Linked Query Scripts extract real-time SAP data
Data from each Query stored in its own tab of a
single spreadsheet
Winshuttle User Group | San Diego 2013
Step 3: Validate Requests / Apply Bus. Rules
Validated and built data staged in a table within database ready for loading by Transaction
Extracted SAP Data in Excel
Access Database: Button imports SAP data, validates requests, and
applies business rules for additional data
Winshuttle User Group | San Diego 2013
Step 4: Load Data to SAP via Transaction
MM01 Transaction script loads data to SAP
Data staged for SAP. Updated with SAP message by Transaction
Winshuttle User Group | San Diego 2013
Step 5: Generate Notifications to Stakeholders
Excel file containing messages and stakeholder
for each message is attached to email
Extracted SAP Data in Excel
Access Database: Button reads SAP results and sends
email to stakeholders define by each situation
Winshuttle User Group | San Diego 2013
Keys to Success
End User Experience: Users fills out a form and receives an email with the results
in less than 6 hours
Processor Experience: Runner never reviews any data. Simply presses buttons in
Access and runs Query and Transaction
Rules, Rules, Rules: Validation and business rules stored inside Access VBA.
Makes the process very flexible, robust, and easy to manage
Increases “initial data quality” and reduces post-extension maintenance
Winshuttle User Group | San Diego 2013
Keys to Success
Winshuttle Central: A single source for scripts All runners have to use the same Winshuttle scripts stored
in Central. Makes change management easier.
One Transaction, One Script Every material type has it own requirements. A single
transaction script uses built in condition functions to accommodate the needs of each material type
Winshuttle User Group | San Diego 2013
Benefit$ to the Bu$ine$$
Time to Market: Extensions used to be a big holdup with regards to time to
completion. By taking the time from days to hours, we’ve taken this issue off the table.
Order Entry: Using business rules, data quality is much higher and customer
orders that fail – and are therefore delayed – due to data issues have dramatically decreased
Big or small, it can do it all: Product launches with large numbers of materials to extend used
to be very time consuming and error prone. Now, there is almost no limit to how many materials can be requested at once. This process can do 1,000 – 3,000 an hour, correctly the first time!
Do More with Less: Given the volume of requests, several headcounts have been
saved as a result of the automated process
Winshuttle User Group | San Diego 2013
Pretty Good, but not Perfect
No traceability of downstream activities i.e. Email to purchasing sent but no tracking of whether or
not they have completed their actions
Its still a batch process: Requestors used to be complain it took several days for their
material to get extended with so-so quality, now six hours with high quality is to long!
Trying to get the action of a request coming in to trigger the process. Cannot launch Winshuttle from run command prompt when running from Central.
Winshuttle User Group | San Diego 2013
Questions