View
268
Download
2
Category
Tags:
Preview:
Citation preview
How to Deal with Role-Based Navigation Models for Different Countries and Languages. ID: 2213
Markus van Kempen – SAP Solutions Architect E: mvk@ca.ibm.com T: @markusvankempen Innovating with People and Technology
Abstract
How to Deal with Role-Based Navigation Models for Different Countries and Languages
In this session, presenters will discuss the lessons learned from Global SAP Portal implementations. They will share their experience with implementing global multi-language portals. They will demonstrate how they deal with multi-role navigation models, language preferences, and third party integration based on country requirements. Presenters will show the method to build navigation models, integrate help functionality, and address some of the ESS and MSS process challenges such as position base Personnel Change Requests (PCR), Organizational Change Requests (OCR), or people-based PCR/OCR. MSS personnel change requests and organizational change requests are part of the demonstration as well as policy and help desk (shared service) integration
Session ID: 2213
2
Agenda
Agenda
Global Portal Implementation
Multi-role navigation models
Integrate help and KB functionality
Demonstration
MSS/ Personnel Change Requests (PCR)
and third party integration based
3
Global SAP Portal challenges
Global SAP Portal Implementations challenges
•HR vs SAP language
•Translations
•Navigation
•Integration
•HR Policies
•MSS /PCR
•Small Markets
•Reporting and Adoptions
•Service Center Integration
5
LEARNING POINTS
How to use User Context to drive Navigation
Create a friendlier User Experience
How to bridge SAP vs. HR language
6
Navigation Model aka Information Architecture
Most SAP implementation starts out with the standard Portal content look and feel which over time, with a lot of effort and low user acceptance will improve the usability of the Portal.
Using Tools and approaches will help the Clients to ensure a successful Portal implementation which has high user satisfaction and adoption right from the start.
9
9
User Context – from HR and other system drives Country & Language Specific Portal and KB Content base on
employee roles
Usability Manager Home Page
Language Selector
Site map is Dynamic Role and Language/Country depended
Country & Language User context
11
NetWeaver Portal
Dynamic Navigation under the hood
KM
XSLT/XSL
/HTML
User Context
Language + Country + User Roles/Pages Matched with xsl
Dynamic Navigation
<page id=“p
15
17
Ways to Adapt the Look & Feel Levels of Customization
• There are more or less 5 different levels of how look & feel can be adapted.
• The levels vary in the degree of “Standardness” and “Design Flexibility”.
• The higher the level the higher the TCO might be.
Customization only
Addon-iViews
Smaller modifications
Custom developed replacements
Completely rewritten framework
Search Integration Context Diagram
20
Policies /Help
SAP NW Portal
Portal
Users
• Users based on their HR and
User context find Transactions
• Content is retrieved based on
country/language and roles.
• Portal will parse the results and render in iviews/portlet
SAP ECC ESS/MSS UserCtx
20 axXZ
Application Integration – example SAML connection to Taleo
24
Local Payroll Provider
Local HR Application
Global HR Application
Local Intranet Apps
Technology
Screen Sizes
Small Market/Country
Goal is Single HR system
One source for reporting and Talent Mgr
Make HR more efficient
Empower Mangers
Small Markets Local Interfaces
Limited HR , Mgr and IT staff
Local HR system
THANK YOU FOR PARTICIPATING
Please provide feedback on this session by completing a short survey via the event mobile application.
SESSION CODE: 2213
For ongoing education on this area of focus, visit www.ASUG.com
Contact Information
Markus van Kempen – SAP Architect Innovating with People and Technology email: mvk@ca.ibm.com Twitter: @markusvankempen Hashtag: #MVK
Recommended