Freescale presentation from ASUG Annual Conference 2015 (SAPPHIRE NOW) delivered by Cheryl Sutton and Gaylene Covarrubias. Topic is how they generated cost savings and improved user satisfaction by deploying SAP Screen Personas for several HR and purchasing scenarios.

1. Creating a Powerful New Procurement
Tool with SAP® Screen Personas
Cheryl Sutton & Gaylene Covarrubias
Freescale Semiconductor
SESSION CODE: SC1984

2. Agenda.
Intro & Overview
Projects & Demos
Lessons Learned & Best Practices

3. Who is Freescale?
Global Leader in Embedded Processing Solutions
- Automotive, networking, industrial, and consumer markets
17,000 employees in more than 20 countries

4. IT Landscape
• SAP™: ECC 6.0 EHP 4
• Kernel: 7.21_ext_rel SP 415
• Personas: 2.0 SP 2
• ECC, SRM, BW, SCM, eWM
‒ General Ledger ‒ Inventory Management
‒ Fixed Assets ‒ Product Costing
‒ Accounts Payable ‒ Project Systems
‒ Logistics Execution ‒ Human Resource Management
‒ Repetitive Manufacturing ‒ Travel & Exp. Reimbursement
‒ Procurement / SRM UI ‒ Adv. Planning & Optimization (APO)

5. Business Challenge
Transformation
Simplification
Speed
User
Experience

6. Overview - What Can be Customized?
Individual Transactions

7. Overview - What Can be Customized?
Launchpad Concept
External Links to other websites
Transaction
launch buttons
easily run
transactions
without users
having to know
the T-Code.
Radio buttons to add
selection functionality
Script buttons can
capture user input
and use it to run
reports or execute
transactions in the
background.
The Mock-up shown here actually incorporates 4 separate transactions: F-65, FBV2, FBV3, and FB03.

8. Original Pilot – HR Master Data
 Standard SAP GUI
 19 Different Screens

9. Original Pilot – HR Master Data
 Personas Interface – One Central Location

10. Procurement
‒ Start at the beginning – requisitioners
‒ Unique groups of end users with
slightly different processes
‒ Personas allows us to create multiple
versions of the same transaction
• Procurement identified as an area that could use simplification.

11. Procurement – Basic Process Screens
 MK03
 ZPROP / EBAN
 Y_RCD_07000368

12. Procurement – Requisitioner Launchpad
 Personas Interface – One Central Location

13. Business Results
4 Transactions
8 External Links
in One Location
Decreased
Transaction Time
Multiple
Customizations
Faster Lookups 400 Global Users

14. Capital Projects
CJ20N
Gaylene Covarrubias

15. Create Project – CJ20N

16. Create Project – CJ20N
Basic SAP Personas

17. Create Project – CJ20N
Basic SAP Personas

18. Simplification Results
Increased
Accuracy
Reduced
Transaction
Time
Reduced
Training
Time
Eliminated
75% of steps
Eliminated
Redundancy

19. Lessons Learned
• Make sure all structures and templates are in place in all environments to
avoid duplicate work
− Import / export feature
• Adding branding & changing color scheme
− Some global settings
− Consider time commitment
− V3 theming tool
• Personas V2 scripting engine is unique – macro recorder
− Powerful but some limitations - No native looping or nested IF
− Clever workarounds – tips & tricks on SCN
− V3 moving to JavaScript
− Error handling is key

20. Learning Curve - Functionality
• Lots of ways to learn
− SAP how-to videos demonstrate fundamentals
− Hands on training sessions
− Early discovery done mostly through trial & error
− SCN content - Blogs and user forums are growing exponentially
− Practitioner’s Forum
− Open SAP Course
• Understanding the limitations
− Adjusting our approach & reining in the scope of use
− Functionality wish list
− SAP is continuing to develop Personas based on user feedback as well as their
own roadmap

21. Best Practices – Creating Screens
• Our backgrounds:
− Analysts – Don’t need to be super technical
− Information systems & some development
− Helps to have programming exp. – logical flow – pseudocode
− Eye for design
− Creative options: dedicated designer, design consultant, or homegrown
− Freescale opted for a combination to keep Personas team small & agile
− Creative Services provided branding guidelines, image access
− Not client-facing, so not overly strict
− SAP Design & Co-Innovation Center

22. Best Practices – Design & Development
• Develop in stages
− Screens are only Phase I
− Collect user feedback
• Decide what transactions are appropriate for a launchpad
− Short lookup type transactions work on the home screen (smen)
− Longer, multi-screen transactions are harder to complete from the launch page
• Don’t have to be on latest and greatest EHP and kernel
− Keep up with notes
− V3 is close to GA

23. Best Practices – Requirements Gathering
• Conducting process interviews
− Have a business user champion
− Greatest resource is the users – talk to a small, diverse focus group
− Get a feel for user frame of mind
− what they like/dislike and what would add value
• Scrutinizing every detail
− Ensure that Personas can handle all aspects of a business process
− Understand any pre- and post- transaction activities
− Observe entire process multiple times with multiple users
− Ask about variations, alternatives, and shortcuts within a process
− Regional vs. global users – screens can vary

24. Making the World a Smarter Place.
Questions & Comments

25. STAY INFORMED
Follow the ASUGNews team:
Tom Wailgum: @twailgum
Chris Kanaracus: @chriskanaracus
Craig Powers: @Powers_ASUG

26. THANK YOU FOR PARTICIPATING
Please provide feedback on this session by completing
a short survey via the event mobile application.
SESSION CODE: SC1984
For ongoing education on this area of focus,
visit www.ASUG.com