Why EHP7?
DTS Change Control
01/08/15
Background
• SAP requires periodic Support Packs be applied to ensure
software/system compliance and are required in order to maintain
continued supportability of KHRIS.
• Historically, we have completed these Support Pack updates on an
annual basis with supplemental updates (SAP Notes and TUBS) on
an as needed basis. Additionally, CLC’s (Compliance-related
updates) are applied as part of the Year-end W-2 Processing.
• An alternative option to the Support Packs is available with EHP7
(Enhancement Pack 7). This would include all necessary
compliance updates and SAP fixes, along with making available
new enhanced functionality that could be leveraged if determined
desirable by the business, planned, and prioritized as part of the
DTS Roadmap.
• Decision Point – Do we proceed with implementation of SPS
updates or move forward with EHP7?
Why EHP7?
• Objectives:
- Ensures software compliance for long-term maintenance and
support
- Aligns with long-term strategic direction of software provider and
COT business objectives
- Positions DTS to explore and potentially implement landscape
changes the could assist in reducing TCO (Total Cost of Ownership)
- Allows DTS to leverage existing SME’s and contract resources
before further budgetary reductions
- Enables CoKY to implement available enhancements, new business
functionality and support processes, as well as efficiencies for
system and operational performance
 Portal optimization
Why EHP7?
• What do we get with EHP7?
- Mobility enablers and FIORI framework and components
 Required for mobile solutions
 Supports ESS Self-Time Entry on mobile devices
 Provides opportunity to create mobile Apps (ex. Time and Pay
Statements)
 Improves user experience of ESS Benefits Open Enrollment on tablets
- Positions CoKY to leverage HR Renewal 2.0 functionality
 More friendly, harmonized and intuitive user experience
 New business functionality available (ex. Onboarding )
- Analytics for Managers (new)
 Perform operational reporting on the data of an application system
without having to replicate the data in a BW system first. A set of new
queries is available for managers to help them in their daily work – this
will require more in depth research to determine usability
- Mass Processing for Personnel and Organization (new)
 Enable HR professionals to process the data of multiple candidates
using the Mass Hiring/Reorgs Web application. With the Excel-like Web
UI, an HR professional can complete the whole maintenance process
for candidates
Why EHP7?
• What else do we get with EHP7?
- Enhancements to WebDynPro ABAP
 WebDynPro ABAP is SAP’s strategic direction, and has sunset
WebDynPro Java
 SAP continues to enhance WebDynPro ABAP – We’ve got to get there
- One step closer to HR Renewal
 Builds on ESS/MSS Web Dynpro ABAP
 Introduces us to SAP UI5(HTML5) and some Fiori features for mobility
- Improves portal look and feel and usability with newer/modern
screens (ESS, OE)
- In-line with SAP future goals (SAPUI5, Fiori, Hana, Screen
personas)
- Online W2 functionality (this could be enabled with EHP6)
 Will explore further after implementation of new ACA reporting
requirements
Why EHP7?
• What else do we get with EHP7? (continued)
- Analytics: The Analytics lane provides a single point-of-access for
starting HR-relevant reports and analyses from the landing page.
The lane includes sample reports from different technologies. Users
can change the selection of reports to suit their requirements. Users
can flag important reports as favorites and call recently used reports
- Salary Card
- Substitution Functionality – would allow us to use standard vs.
custom solution
Other Factors for Consideration
• Effort
- The effort required above our annual SPS upgrade is not
significant
• Timing (Why now is better than later?)
• Current vs. future resource availability
• Pre- and Post-Transition freeze
• New executive administration with their priorities
• Potential for COT/KHRIS landscape changes
• Best practice is to upgrade prior to migration or following migration, not
during migration
• Decision for landscape changes could further delay a move to EHP7 if not
completed ahead of any infrastructure changes
• Timeline – EHP7 -> Prod targeted for mid to late June
Strategic Drivers
• Enables CoKY for HANA, should CoKY choose to move in this
direction, which could be part of any re-platforming or cloud-hosting
initiative
- Cloud-hosting is one of COT’s strategic directions
- HANA is SAP’s cloud-based ERP solution, and is their
strategic direction regarding ERP software
- Provides for further optimization and potential cost reductions
Appendix
Appendix - Enhancements
• BASIS
- As with any upgrade, BASIS will get the upgraded versions of Upgrade
manager, DBA cockpit, Support Pack Maintenance tool,
system/performance monitoring tools and other operational tools. We
will be going to BASIS component level from 731 to 740 along with
Kernel 740, which are building blocks for all the functional components
and potential future enhancements
• Security
- No enhancements available for ACB based on CoKY business
requirements in this area
• FICO
- No enhancements available for FICO
Appendix - Enhancements
• OM
- Employee Master Data
 Enhanced visual appeal, including org.-chart-based navigation option
 Efficient and intuitive Web-based user interface for maintaining master data for
employees via SAP NetWeaver Business Client (NWBC)
 Activity-based-access to frequent tasks with efficient access to relevant data
 Option to integrate SAP collaboration framework
-
Organizational Master Data
 Intuitive Web-based application for looking up information on organizational structures
and reporting lines for organizational units, positions, and assigned employees
 Organization structure visualization with option to access related actions
 Users can directly edit the data for an organizational object or start a business activity
that provides all task-relevant data on one screen. Changes can be saved as a draft
and tracked until completion
 Enables customers to access simplified organizational master data information in a
Web-based application
 Supports HR professionals in their daily tasks without requiring in-depth technical
knowledge
 Increases transparency of information on reporting lines and allows information to be
gathered quickly
 Allows customer-specific UI configuration without code changes with Web-based tools
for system administrators
Appendix - Enhancements
• PA
- Analytics: The Analytics lane provides a single point-of-access for
starting HR-relevant reports and analyses from the landing page. The
lane includes sample reports from different technologies. Users can
change the selection of reports to suit their requirements. Users can flag
important reports as favorites and call recently used reports.
- Search feature: The search features provided with this business
function allow users to quickly identify and navigate to relevant data.
- While many of the above enhancements pertain to the HCMPF forms,
we feel we already have the offered enhanced functionality through our
customized version of the forms in place today.
• Payroll
- New employee salary statement that is card based. A card based salary
statement would improve the statement for viewing on a smart phone
but would provide a different look and feel.
Appendix - Enhancements
• BNA
- User comments can be added when a lock is set on a participant or
agency account. Comments are also displayed in the Evaluating Locks
transaction (FPLKA).
- Broker Functionality:
 An alternative broker can be assigned to specific documents, and if filled, it overrides the master data
broker of a participant. (EHP6, but not activated)
 If there are multiple broker contracts for a single broker, documents can be assigned to an alternative
broker contract. (Currently this would not be needed at the Commonwealth)
 There is also a Direct Collections checkbox, in which a document will be ignored by broker collections.
You could check this if the participant is going to pay the commonwealth directly.
 Broker Net View – Additional selections available in FPL9 and IBR02, so you can report on alternative
brokers at the document level. Additional reporting functionality in IBR06, IBR13, and FPO4.
 Simulation Run of IBR50 (Create Broker Report). This was also made available in EHP6, but not
turned on.
 You will be able to reopen closed broker reports.
 Faster clarification of Broker Reports – “Processing Info” field added to clarification cases – added
item and changed item. This information can be used in processing clarification cases in IBR51 and
IBR04.
 Broker Report items not assigned to a broker or BP can be added. I’m not sure how this will affect our
current SIBRODUMMY functionality.
- Biller Direct – Several FSCM enhancements, but it looks like the
enhancements apply to customers that use multiple contracts for
individuals. This is not something that would currently apply to the
Commonwealth.
- Processing Open Items:

Account maintenance enhancement of the screen and ability to select all items in FP06, FPE1, and FPE2M.