Tag Archives: SAP HR

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

Compensation, SAP HCM, SuccessFactors, , , , , ,

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

HR Renewal and SAP Fiori: What Should I Do?

ESS, HR Renewal, HR Tech, HR2016, SAP Fiori, Self Services, , , , , ,

Several years ago, SAP found themselves in a situation which happens to many large software companies. Two separate parts of the organization developed new HR functionality to solve for a common gap: usability.  On one side, HR Renewal came to fruition – a new landing page built off SAPUI5 with a new navigation and user experience. The other – SAP Fiori – was a cross-function solution (inspired with a Google design team) with a separate entry point (SAP Fiori Launchpad) and its own user interface using SAPUI5.

Many customers are now perplexed on how to move forward given both are viable solutions to solve SAP’s long-plagued usability problems, especially in the areas of Employee and Manager Self-Service.

It’s apparent that the bulk of innovation will go into SAP Fiori apps, since SAP Fiori is being leveraged across all platforms (On premise, SuccessFactors, Fieldglass, Ariba, etc.) It is SAP’s answer to a common UX, despite the disparate systems behind it.  Vishal Sikka (ex-CTO of SAP, now CEO and MD at Infosys) layed out his vision at the 2013 SAPPHIRE show.

VisionfromVishal

His “Fiori UX Paradigm” – drawn by hand and reminiscent of the days when the best solutions in software began on the back of a napkin – showed his vision, which SAP is trying to execute on.

So, with all this talk on SAP Fiori, does this mean that HR Renewal is dead? No. The functionalities are still more plentiful in HR Renewal (by a long shot), and are highly relevant for HR Professionals. It is unlikely that SAP will endeavor to re-write these apps in SAP Fiori. Although SAP Fiori is the better choice from a mobile perspective (since it’s responsive and device-agnostic), HR Renewal is still a good choice for companies who want to roll out services to their HR teams (admins, reporting) who don’t want to deal with the SAP GUI. The hard-core services performed in HR Renewal (i.e., Personnel Administration and Organizational Management updates such as employee movement scenarios and organizational updates) would almost certainly be done on desktop and not on device (e.g. I can’t see an HR admin performing a complex promotion/inter-company transfer on their Smartphone).  This should relieve some of the frustration from customers when they realize a majority of the transactions that are new with HR Renewal are using the Web Dynpro ABAP technology which is not mobile-optimized (as opposed to SAPUI5).

I will tackle more sound-bytes in future blogs. In particular, the question may not be HR Renewal versus SAP Fiori, but perhaps how could they work together for your organization.

Until then, please leave some questions or comments below…

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

Cloud, HR2015, S/4 HANA, SAP HCM, SAPInsider, SuccessFactors, , , , ,

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.