Category Archives: SAP HCM

HR Innovations 2019 – My Conference Recap

HR Innovations 2019, hosted by SAPInsider in Las Vegas on March 19-21, 2019

I was fortunate enough to attend and speak at HR Innovations 2019 last week in Las Vegas. I have attended and been a speaker at the SAPInsider shows since 2006 (gulp!). During the 2006 conference, I spoke on “Guidelines and Best Practices for Leveraging Standard SAP Functionality for Career and Succession Planning” and “Structural Authorizations 101: What You Need to Know”. Boy, that definitely seems like a lifetime ago.

One of my first sessions at SAPInsider, back in 2006

At this year’s event, I was able to participate in a panel (“The great debate – on premise vs cloud”), as well as five (5) sessions spread across only two (2) days. I spoke on building a cloud business case, managing change in a cloud environment (versus on premise), as well as Fiori and SAP SuccessFactors Performance Management. Yes, I definitely felt immersed in the event! A few reflections on the event in general:

SAP Insider looked and felt different than previous shows

SAPInsider made some nice updates to the event. I liked the shorter sessions (30-minute delivery with 10-minute Q&A) with more time for participants to go between sessions and network. The sessions were more consumable for the audience and the event just felt less rushed in general. There were also sessions in the exhibitor hall, and – although it was loud and distracting at times – overall, I think it added another nice twist to the sometimes-mundane breakout room. (Of course, this was an added bonus for the sponsors and exhibitors at the event as well due to extra traffic).

Selfie shot with a few of our industry’s finest: (L to R): Danielle Larocca, Rinky Karthik, Steve Bogner, Imran Sajid, and me

Customers are still worried about life in the cloud

HR Customers get it – the industry is pulling them (whether they like it or not) to the cloud. Most customers weren’t (at least) overtly pushing back but remain surprised at some of the harsh realities when entering a cloud environment (whether it be hybrid or full). In particular, the topic of upgrades came up at a few of my sessions. Customers who have SAP Payroll on premise, for example, were horrified to hear they would need to continue with their annual HRSP (HR Support Pack) upgrades, as well as the added quarterly releases from SuccessFactors. SuccessFactors recently (as of Q4 2018) added test scripts to their releases which put some at ease. Still others fretted it meant more work to spread across little to no available resources.

Yet, Customers understand the benefits of moving to the cloud

Customers understand the benefits of cloud software. The enhanced user experience and continuous innovation seem to be the two most obvious ones. Many of the 15,000+ on premise customers are stymied now since innovating on their current SAP HCM ERP offering may not be justified if a move to the cloud is imminent. The effect on the marketplace is a slow pace of change, and the industry has felt this the past few years. Regardless, customers still understand they need to get there- they’re just struggled how to do so.

On premise is on life support until at least 2030 now (until SAP changes it again).

Ralf Wagner (VP, Product Management) from SAP did a nice job explaining the new offering in 2023 for SAP customers not able to migrate to SAP SuccessFactors in the next few years. The offering is called “SAP Human Capital Management for SAP S/4 HANA on premise addition” (take a breath!). This offering basically means the customer has to “carve out” their existing SAP HR module and deploy on SAP HANA database. It will be based on an EhP8 and supplemented by some HANA-based capabilities. The will then be integrated with the S/4 HANA suite. SAP will develop migration tools to do this. Still TBD on what effort this would really look like.

One of my industry colleagues, Danielle Larocca, Senior Vice-President of HCM Solutions at EPI-USE Labs, created a post on this with additional details.

SAP’s latest approach on migration options for on premise customers

New podcast

Check out the podcast from Steve Bogner’s Insight Consulting Partners. I was a special guest and I had a fun time recording it with Steve and friends. Steve hasn’t posted yet, but I’ll update this post when he does.

Taking in some beauty at the Bellagio

Until next time…. I expect SAPInsider to continue having an HR show in 2020, and go back to simply calling it HR 2020. Here’s to hoping it will grow on the productive changes done this year.

Jeremy

Top Tips Integrating SAP HCM Core and SuccessFactors Compensation and Variable Pay

This is what happens when you fly on a brand new Delta jet. So new that they haven’t even registered Wi-Fi. At least this blog has come out of it – hope you find it useful! I have jotted down a few of my top tips (so far) when integrating and implementing SuccessFactors Compensation and/or  SuccessFactors Variable Pay.

  • Data, data, data! OK, do we need to go through this again? Regardless of the systems being integrated, we are always attacking the same gremlins, aren’t we? As Compensation professions (or those IT Professionals supporting Compensation), there’s nothing like going through a compensation process to see how painfully obvious it is that the integrity of your core HR data is vital in your talent management processes – especially compensation.  Take, for example, an employee’s FTE % (sometimes referred to as employee percentage). If incorrect, this one data element can wreak havoc on your merit, merit budget, and incentive calculations.
  • If SAP HCM core is your system of record, be sure you are using the existing SAP provided integrations. With Integration Add-Ons 1.0 and 3.0 for SAP ERP HCM and SuccessFactors HCM Suite, both the SuccessFactors compensation and variable pay modules have pre-delivered content. You will need to time this integration with your current Foundation UDF “User Data File” file that you are using.
  • Be kind to your PI (Process Integration) middleware resources. Take them out to lunch and buy them a pizza since you will need their help. The integrations provided by SAP are SAP PI based and will need to be activated in your middleware environment. This is often a project plan task forgotten in the plan and will end up biting you if you don’t plan for it.
  • If you are migrating from ECM (Enterprise Compensation Management), don’t try to do too much with this. The new integration uses staging tables and is entirely decoupled from ECM. You may end of leveraging IT0759 or IT0761 so LTI handling, if you still intend to interface to your stock plan provider.  Also, you may need to do some incentive number-crunching for segments (e.g. “legs”, “assignments”, “rows”, etc.) in a custom infotype. You should consider keeping your existing bonus engine if your incentive plans have not been able to simplify / conform to the SuccessFactors variable pay model.
  • Don’t forgot that all of your compensation and variable pay templates need to have the <comp-group id=”xxxx”/> tag in the XML if you are sending your data from SAP HCM, where xxxx is a string with no capitalization. As the time of this writing, this can only added via the XML configuration. This tag is important since it tells the SuccessFactors system which forms (that use that template) to update during a refresh from SAP HCM. Like any tags of an XML template for compensation in SuccessFactors, the placement of this tag is very particular near the end of the XML. Read the SuccessFactors documentation carefully and be careful when you are downloading/uploading or editing the template in Provisioning.
  • Remember the power of the pay matrix (e.g. salary ranges) which drives everything from the compa-ratio and range penetration, as well as guidelines (if included as a dimension). Don’t try to interface this over ( not worth it) –  this would just be an upload every year.  If a range range/midpoint changes, the onus would be on your SuccessFactors compensation administrator to manually update that. This shouldn’t happen once the process has started unless there was an error or your compensation manager is trying to make your life more interesting…
  • Think carefully how you will leverage the Executive Review. Unlike the name implies, this functionality isn’t necessarily just for executives, but rather for calibration purposes in general. Based on Role-Based permissioning, you can define a group with display access and a group with edit access. I will be talking about this topic during the ASUG Compensation SIG (login required) later this month. If you are a SuccessFactors customer, please plan on joining me for this learning event!

That’s it for now.  Please send along any questions and comments in the area below.

Oh, and Worklogix is a Silver Sponsor at the upcoming SAP SuccessFactors conference, SuccessConnect.  If you are in Vegas, please visit us in booth #35.

Sending you my best,

Jeremy  @jeremymasters

ECM Nugget: “Lock Objects” in transaction PECM_PROCESS_SUPPORT

I wanted to share a useful piece of information about the use of the “Lock Objects” functionality in the program RHECM_PROCESS_SUPPORT_FOR_PLNG (transaction code PECM_PROCESS_SUPPORT) since it seems to come up in every ECM deployment that Worklogix is involved in.

Transaction PECM_PROCESS_SUPPORT for process support during ECM cycles
Transaction PECM_PROCESS_SUPPORT for process support during ECM cycles

First, there is a common misunderstanding that it’s about locking employee records. However, the “Lock Object” flag is only about locking Budgets (i.e., budget units)

Imagine you have an organizational structure having the depth of 4 hierarchical levels and the top node is A, subordinate from A is B, subordinate from B is C, and subordinate from C is D. Since Enhancement Pack 5 (EhP5), SAP ECM supports the employee-level budgeting approach (bottom-up).  This means we have 1) the budget structure as a mirrored org structure (BU-BU and BU-O) and 2) the employee budgets (BU-P).

Whenever a manager is logged into Manager Self-Service doing compensation planning, certain objects get locked. The system locks the employee itself (i.e. P and IT0759), the budget unit (BU) connected to the employee is locked (BU-P) and finally the budget unit (BU) connected to the org. units where the manager is the chief of is also locked. This leads to the dilemma that two functions of the Process Preparation Report (transaction PECM_PROCESS_SUPPORT) mitigate:

1) Option Update Planning and Budgets: Whenever an employee is turning eligible / ineligible, the employee budget is getting created or deleted. Therefore also the roll-ups are getting refreshed. This refresh doesn’t work when any manager is logged-into the Compensation Planning / Approval iView within the portal locking a budget connected to the org unit.

2) Option Recalculate Budget: Functionality doesn’t recalculate budget whenever any manager is logged into the Compensation Planning / Approval iView within the portal locking a budget connected to the org unit.

Dependent on how the compensation cycle is setup (is it a global or country compensation review; global organization or just within a region/country) the likelihood is high that there is at least one manager logged into Manager Self-Service during an ongoing compensation cycle. To bypass this dilemma, SAP has recently implemented the “Lock Object” flag. Whenever the flag is unchecked, the system is not checking any longer if a budget unit connected to an org unit is locked by a user or not. It always pushes changes into the database. Again, the “Lock Object” flag has nothing to do with locking an employee. It’s only about locking the budget structure by managers.

Here are the pros and cons of this functionality.

Pros:
As usually at least one manager is logged into MSS all the time, this facilitates the update of budgets significantly. Simply uncheck the flag and budget structures can be updated all the time. Additional programs which may kick out (or prevent) managers to perform budget updates are not needed any longer.

Cons:
The manager experience can be a bit tricky with these budgets, and proper communication should be made available to managers involved in the process. Let’s take an example where a manager who is logged into MSS and initially sees a budget of 100,000 USD. While the manager is logged in, you execute PECM_PROCESS_SUPPORT to perform a recalculate budget which reduces the budget in a lower org unit for example by 10,000 USD. This update is not immediately visible to the manager, but rather only when he/she opens another iView and then returns to Compensation Planning / Approval iView to get a refresh. This means that a manager who plans to keep his org unit budget at 100,000, but  in reality he only has 90,000, because someone executed PECM_PROCESS_SUPPORT in the meantime.

I would recommend to always use PECM_DISPLAY_BUDGETS to monitor any potential inconsistencies in the budget structures which can always be repaired using the button “Update Spent Amounts” in the budget audit report in case they exist.

Audit Report for Budgets

Hope this helps you. 

S/4 HANA: Your Deployment Options with SAP HCM / SF

Hey friends,

I was fortunate to attend SAPInsider’s 2015 conference in Nice where the weather was beautiful, the cuisine delicious, and the conference content bountiful.  One of the more interesting topics that I learned about was SAP’s support for S/4 HANA and SAP HCM platforms.  Based on customer feedback since the original plans were unveiled at SAPPHIRENOW, changes to the support of SAP’s productized integration was necessary. Here’s the skinny:

There are 5 basic scenarios. (I am sure there are others based on customers’ own deployments, but let’s stick with these for now):

If using SAP ERP HCM:

1) Keep SAP ERP HCM in its own instance on premise, and deploy S/4 HANA on premise

2) Deploy S/4 HANA and SAP ERP HCM in the same instance on premise

3) Keep SAP ERP HCM on premise, and deploy S/4 HANA in the cloud

If using Employee Central:

4) Deploy S/4 HANA on premise, and integrate with SuccessFactors Employee Central

5) Deploy S/4 HANA in the cloud, and integrate with SuccessFactors Employee Central

In all scenarios above, SAP has or will have productized integrations to support these scenarios to the year 20xx, where xx is something we need to hear from SAP on. I was able to grab some time with David Ludlow, Group Vice President at SAP, who really understands the customer landscape out there.  He presented this slide which captures the options pretty well.

S/4 HANA and SAP HR / SF integrations

So what does this all mean? Well, the answer is still to be determined, but for SAP HCM customers who are looking to use Simple Finance and other aspects of S/4 HANA, it simply means more options.   This has always been a bit of a double sword for SAP, but in my opinion, it’s something that SAP had to do in order to accommodate its vast customer base.

SAP Fiori, HR Renewal – Reference Material

I did a recent podcast for SAPInsider, the conference producer for HR2015. You can hear the podcast and view the transcript here. Many of the questions were a precursor to the kinds of the questions I am sure we will be hearing from customers this year at the HR 2015 conference as well as ASUG/SAPPHIRE. Questions specifically around the roadmap for HR Renewal versus SAP Fiori and where/when/how these roads will merge within the SAP HCM space. Lots of questions around integration, mashups, and what types of skill sets customers/consultants will need in the future around these technologies.

Here are some of the resources that are available to us out there, specifically around SAPUI5 and its related offerings:

SAP Fiori Apps Library: Probably your best starting point for Fiori apps

HR Renewal 2.0 SAP Help documentation

The new SAP PRESS book on HR Renewal and SAP Fiori, the new Employee, Manager and HR Professional self service, from myself, Brandon Toombs, Kris Bland, and Justin Morgalis.

All Things Fiori and, specifically for HR, SAP HCM Fiori apps on SCN

My session on “Latest Enhancements in SAP ERP HCM Self-Services: HR Renewal, SAP Fiori, and SAPUI5“. The rest of my sessions are here:

I also suggest you check out some sessions on these topics by two of the finest in the business: Martin Gillet and Brandon Toombs. Both will both give you an independent viewpoint on what’s good (and bad) about these technologies.

Brandon’s session on “Guidelines and requirements for adapting to the HR Professional role UI” will definitely be one to check out for those interested in understanding what’s new for the HR Professional. The rest of his sessions are here.  You might also want to check out his blog series on SCN on comparing Employee Central and HR Renewal/SAP Fiori here: Blog 1 |  Blog 2

Martin’s session on “An A-to-Z guide to streamlining HR processes across desktop and mobile devices with SAP Fiori” will be another great session to understand how SAP Fiori fits into your overall desktop and mobile self service strategy. The rest of his sessions are here.

Less than two weeks to the conference, and will be great to see many of industry friends again.

If you are going, please drop by booth #410 where Worklogix will be exhibiting and say hello.

 

Best,

Jeremy

 

HR2015 – What You Want to Know at This Year’s SAP HR Conference

Hello friends,

The HR event from SAPInsider is almost upon us.  Please visit the website to see more details on what’s scheduled. Please visit me at one of my sessions, or at booth #410 in the Exhibit Hall during the show.

HR2015
The Bellagio will host this year’s SAPInsider conference, HR2015

I just recorded a podcast with Ken Murphy, Features Editor for SAPinsider & insiderPROFILES, about the conference and some hot topics.  It was a great discussion with him, as we exchanged thoughts on HR Renewal, SAP Fiori, SAPUI5, user adoption, change management, security, and other big league topics. I will update this post once that podcast is released so you can have a listen.

For those customers preparing for the conference, this is what I could be curious to listen for during the conference:

  1. What are the latest innovations within the SAP HR space around SAP Fiori?  Will there be another wave of HR apps released? If so, when? How will SAPUI5 apps be expanded in the HR space, or will they?
  2. How will HR Renewal continue to innovate, in areas like SAPUI5 replacement (of Web Dynpro ABAP services), as well as a more intuitive navigation scheme? In my opinion, the current lane approach looks fresher than previous homepage layouts, but also can cause more challenges for user adoption. This is something that I will discuss at the conference.
  3. Will HR Renewal and SAP Fiori “merge forces”, or will we they continue to be deployed in separate releases, style sets, etc? It’s important that we hear from SAP on these roadmap items, especially after Vishal Sikka’s (relatively) recent exit.
  4. What’s the “portal of choice” now for customers? Or, is there even a frontrunner? Currently, we have SAP NetWeaver Portal, NetWeaver Business Client (NWBC), SAP Fiori Launchpad, SAP Fiori within SAP Portal,  and other 3rd party portals (SharePoint, WebSphere are top).  How do we navigate these options, and which one’s best for customers?
  5. What’s new in the HR Professional role? For this, I would attend my co-author Brandon Toombs‘ session “Guidelines and requirements for adapting to the HR Professional role UI”. Brandon is a force to be reckoned with on this topic.

Hope to see you at the show!

Jeremy

(you can follow me on Twitter @jeremymasters)

Top Ten Gotchas when Implementing SAP Enterprise Compensation Management (ECM)

Thought I would share a few lessons learned around Compensation management using SAP ECM (Enterprise Compensation Management), but these could be used for any compensation system.

  1. ECM supports the annual compensation (“focal review”) process, but not the off-cycle (ad hoc) increases associated to promotions, laterals, downgrades, etc. Don’t force the off-cycle process in the tool or it will turn ugly.
  2. Ensure budgeting requirements are well understood early in the project between the compensation and project teams.  For example, what is the budget/organizational freeze date (or, is there a freeze date?), can budget funds be re-allocated during planning, what  do you do with terminated employees during the cycle, etc.
  3. Don’t rely too much on “macro-eligibility” to drive your compensation eligibility rules. Infotype 0758 (Compensation Program) is where “macro-eligibility” is defined.  Putting too much intelligence in this infotype is a recipe for disaster because you are at the mercy of master data maintenance (PA30/PA40 transactions).  Bake your eligibility requirements into your “micro-eligibility” rules (including the eligibility BAdI) since you have absolute control over the logic.
  4. Listen carefully to the requirements around compensation planning and approvals. For discretionary plans, ensure that the system is configured to handle the appropriate workflow and business logic to handle compensation worksheet level approvals, routing and escalation rules.
  5. Ensure that all your process inputs (market data, performance ratings, potential ratings, etc.) are configured prior to the compensation worksheet being opened to management.
  6. Agree with the compensation team on which master data will be entered by them in Production versus input by IT in Development (and transported to the upper environments).  Time-sensitive information such as Business Unit Results, Black Sholes/Fair Market Value, Bonus modifiers/kickers, etc. should be controlled by the business in the Productive environment.  This data may also be very confidential as well, for “comp’s eyes only”.
  7. Give the compensation team the ability to proof the compensation worksheets before releasing to management.  Seems a given, but worth it’s own line.
  8. Conduct your system testing with a dedicated QA system with unmasked employee/compensation data. (This may not be realistic for all companies due to budgetary and/or environment  constraints, I understand, but shoot for the stars and maybe you will reach the moon.)
  9. Just because functionality is offered, doesn’t mean you should use it. Test the waters within a demo environment with the compensation team to ensure they really do want all the functionality offered. There is nothing wrong with hiding functionality until if (or when) it’s needed. For example, the Compensation Profile is neat but also can backfire on you if you expose too much data that’s difficult to explain (or – even worse – wrong!)
  10. Don’t over-engineer the stock granting process.  At maximum, collect and split the stock recommendations, but all other activities (vesting management, exercising, life events, etc.) should be handled by your stock plan administrator.

Until next time!

Jeremy

@jeremymasters

SAP and SuccessFactors Compensation Management Q&A

Yesterday, SAPInsider hosted a Q&A on SAP and SuccessFactors Compensation Management.  You can view the full transcript here. It is always challenging and fun to do these live Q&A blogs because when you are in the “hot seat”, you need to think (and type!) fast.  Because we only had less than two weeks of marketing for this online event, I was skeptical on the amount of attendees who would show up, but the turnout was a lot higher than I thought. I did see a ton of questions flood in but was only able to answer an hour’s worth.

Compensation

Some takeaways from my chat were the following:

  1. Customers are still confused about the longevity of SAP ECM (Enterprise Compensation Management). I had to (again) reinforce that SAP will not be stopping support of this module. In fact, there is a program called “Customer Connection” which SAP exclusively has for listening to the user community for minor enhancements to the product.
  2. SAP is currently building an integration between SAP HCM On premise and the SuccessFactor’s Variable Pay module. One of SAP’s Product Managers for Compensation/Variable Pay, Deeksha Mittal, was nice enough to join me in on the conversation to articulate some high level timelines for this. She mentioned: “we are working towards an integration between Variable Pay and SAP HCM as well and is definitely on the roadmap for 2014. By the end of 2014 (your next planning cycles) you should be able to take advantage of the integration between Variable Pay and SAP HCM.”
  3. Regardless of using on premise or cloud compensation, customers’ pain points are focused in similar areas, such as: data integrity, process efficiencies (workflow/approvals), and integration with payout process (payroll and/or data extract to equity 3rd party administrator). It doesn’t matter where you deliver your compensation – these themes follow us regardless of platform.
  4. As in other modules, customers who have implemented on premise solutions  are trying to understand how extensible SuccessFactors Compensation/Variable Pay is. I briefly mentioned the introduction of the MDF (Meta Data Framework) as well as SAP HANA Cloud Platform as ways that SAP/SuccessFactors are opening up the platform. Will cloud compensation ever be fully customizable? No, but these tools can be evaluated by the customer to see if their processes’ complex and/or unique logic can be incorporated into SuccessFactors’ technology.
  5. Some mention was made with respect to  future modeling capabilities coming in SuccessFactors. Deeksha Mittal mentioned: “At present, the SuccessFactors Compensation & Variable Pay modules provide flexible ways for defining budgets. We are definitely looking at more advanced modeling features that will help HR to develop more effective comp and bonus plans that are in-line with the company’s financial and HR goals.”

I think it would be beneficial to do another compensation session later in the year since there was so much interested. I will talk to SAPInsider about that.

And hope to see some of your this year HR 2014 in Orlando or Nice, France. I will be doing several sessions this year, including one on compensation: “A guided tour of compensation management functionality: On-premise vs. cloud

Please remember to follow me on Twitter @jeremymasters

 

Until next time!

Jeremy

SuccessFactors Talent Management Seminar 2013 Wrap Up

Over the past 5 weeks, several industry colleagues and I have traveled in the US (Las Vegas and Orlando) and Europe (Copenhagen) meeting with over 50 customers from over 20 countries for a seminar on SuccessFactors’ Talent Management.

SuccessFactors Seminar

The below list is in no particular order but reflects some important themes, questions, and comments:

Integration is still a main concern.  Integration has always been central to SAP’s value proposition. The recent focus on cloud cannot derail this.  I was fortunate to spend these sessions with fellow speakers from SAP. From the messaging and interactions with them, I can confirm that SAP / SuccessFactors is committed to continued investment in integration (they term them “iFlows”).  This is a very good thing for customers, to ease the transition for using cloud technologies where practical. Prashanth Padmanabhan, SAP’s Senior Director, has written a recent blog on the topics for talent hybrid and full cloud integrations. Revisiting my list of concerns from nearly two years ago,many of these items are being addressed. (That blog post alone has gathered over 3,000 unique page views since June 2012).

Platform-as-a-Service (PaaS) will be the differentiator.  Like other functional areas, the HANA Cloud Platform will be a critical piece for HCM to make the suite competitive in a very competitive cloud space (Workday, Oracle Fusion, Infor).  The HANA Cloud Development environment is key to SAP’s eco-system. Worklogix is actively developing applications and excited about the opportunities here with the future HANA marketplace (think Apple’s App Store but for SAP).

In my opnion, HANA (as a database) is a distraction to HCM customers. Yes, SuccessFactors would like to dump its Oracle databases (and soon will), but we need to focus on the platform HANA so that customers and partners can develop apps on. This has been articulated by Vishal and Hasso as well, but hasn’t reached most customers yet.  My hope is that this eco-system ramps up like salesforce.com has done.

Speaker Team for Las Vegas and Orlando
Speaker Team in Las Vegas and Orlando

Can we crack the User Experience nut?  Most hybrid customers have two (if not three or four) portals by the time they implement SuccessFactors. How will we truly make the user experience seamless? This is an area I have a lot passion in, as I have worked with employee, manager and HR self service since 1998 when I was a wee lad at Price Waterhouse.  We cannot be in the business of building and supporting “Frankenstein” portals (my term). However, the reality is that we need to support customers with their own internal realities. (For example, many customers will have to make sense of how their intranet, SharePoint, NetWeaver, and SuccessFactors sites/portals all come together).  This isn’t new but is becoming a pervasive issue as we venture into hybrid customers adding SuccessFactors into the mix. Putting simple (and single) sign on aside, we still need to team together to figure out how this all will be transparent to the end user.

Access control (security authorizations) is a major pain point for hybrid customers. Since authorizations won’t (and can’t) magically port over from SAP to SuccessFactors (or vice versa), we need to put this at the top of our list during design sessions. Especially with customers using complex structural authorizations (including context-sensitive structural authorizations). This will be – GULP – a big area for SIs and customers to work out together.

Mobility, mobility, mobility! Should I say it again: mobility! I don’t need to mention how important this area is for SAP HCM / SuccessFactors in order to keep up with customer demand as well as the competition’s offerings. How to offer one customer-facing (i.e., employee-facing) mobile app (or apps?) will be a challenge, and will be huge over the next 5 years.  If/when SuccessFactors will go device-agnostic (e.g., HTML5) is to be determined. (Secondary question: how does SAP Fiori come into play here – if it even does?). Mobility is another passion of mine, and one that I will speak on during next year’s HR2014 conference. Here are the session details.

Speaker Team in Copenhagen
Speaker Team in Copenhagen

Proxy functionality needs to be killer. In fact, I will call proxy (or delegation) management the third (or fourth?) killer app (this is self-proclaimed, but where can I copyright this???). SuccessFactors has done a nice job with proxy management. You can both manage proxy assignments, as well as use the proxy functionality easily within the tool. Compared to SAP HCM functionality, customers will be enthused.  On premise SAP HCM has always struggled with transactional and approval authorization (in part why Worklogix built the Proxy Manager product).

Social collaboration is great, but its benefits are not yet well understood. SAP Jam is a great tool (we use it internally, during our SuccessFactors trainings, as well as to share knowledge within the SAP/ SuccessFactors eco-system), but many customers don’t understand its context in the (corporate) world.  They ask: “Why do I need a LinkedIn / Facebook for the enterprise if I have access to LinkedIn and Facebook?” We need to evangelize on the importance and power of team collaboration, especially with video at our disposal. (Can you imagine what the internet would be without YouTube, Vimeo, SlideShare, MOOCs, Khan Academy?). SAP has a huge asset with Sameer Patel who I think is doing a great job in this area. You should follow him on Twitter you are not already: @SameerPatel

Being clear with messaging around on premise and cloud innovation will be important for SAP/SuccessFactors.  We need to be clear with customers that there is HCM innovation happening in both SAP’s on premise (e.g., SAP Fiori and HR Renewal) and cloud offerings (SuccessFactors, HCP, Jam). This is a good thing for customers, as they move to cloud at their own pace but are still looking for continuous improvement with their current HRIS investment.  We know where massive innovation is happening, but we do need to remember that some customers will either never have an option to go to the cloud, or won’t have the opportunity to get there sooner than they wish.

I want to thank SAPInsider for supporting my idea back in February 2013 for this SuccessFactors seminar. It was a huge success and, as always, the events in all three cities were interactive, engaging, and educational for all involved.

Please follow me on Twitter @jeremymasters

Until next time!

Jeremy

HR2013 Amsterdam – Blog and Twitter Guide

Hi there,

Conference time again. This time the SAPInsider team is bringin’ it to Amsterdam for HR2013.  I was here in 2011 for HR2011 at Amsterdam RAI, and it is a great venue, and of course, beautiful city.

I am Amsterdam
HR2013 – This Week in Amsterdam!

I wanted to write a quick post to include some blogs and Twitter information so you can maximize your time while in Amsterdam this week.

Several colleagues  have already wrote some nice posts on some sessions they will be attending. The line up is great. Here are some posts:

I also wrote a short post on the Insider Learning Network:  Getting Ready for HR2013 Amsterdam which highlights the sessions I am doing as well as some key topics I will be  on the lookout for.

During this week, be sure to follow the hashtag #HR2013 on Twitter. There should be lots of activity, including tweets from myself (@jeremymasters), Martin Gillet (@mgillet), Luke Marson (@lukemarson), Sven Ringling (@svenringling), Anita Lettink (@NGA_Anita), and Danielle Larocca (@DanielleLarocca)

Some SAP peeps to follow: Jean-Bernard Rolland (@watchthewave), Prashanth Padmanabhan (@sprabu), Paru Sankar (@SankarParu), Yannick Peterschmitt (@ypeterschmitt),  Paul Hopkins (@phpkns)  and David Ludlow (@dHRludlow)

Some SAPInsider peeps to follow: Allison Martin (@AllisonMartin14), Riz Ahmed (@rizalahmed),Benny DiCecca (@bdicecca) and tweeting from stateside: Amy Thistle (@AmyHThistle). Not sure who else from SAPInsider will be there, but you can catch the action on the #HR2013 hashtag.

I am sure I am missing a bunch more.

Looking forward to a great conference!

Jeremy (@jeremymasters)