Implementing the New Payroll Control Center – a consultant’s view



At last there has been modernisation of the way we run payroll in SAP with the release of HR Renewal FP3&4.  This is exciting news for those of us who work in this space.  Here is a brief summary of the steps to implement it and of my view having built a solution with it.

I have not covered “Test Payrolls” here.  I’m just concentrating on the Payroll Cockpit and Control Center in this post.

Basic Principles


The Payroll Cockpit


Provides a framework to create checks (not the American spelling of cheques, but rather validation of employee’s pay) and exception reporting for use during the payroll run. Note – these checks are not reports you download (there is not export to excel button), but rather each is a means to establish whether there is some exception that needs to be looked into.  Examples of such checks are; Net pay over a certain amount, missing master data, incorrect data, large retros etc.

These exception checks enable the business user to be guided directly to the employee(s) who need to be investigated to establish whether they are incorrect, or whether the exception is valid.  If they are incorrect then they can be corrected and re-run, if the exception is valid the user can mark it as such and it drops off the error list.

The Payroll Cockpit is accessed via URL:

http://<sap ecc server details>:<port>/sap/bc/ui5_ui5/sap/hrpy_cockpit/index.html?sap-client=010&sap-uilanguage=EN&sap-ui-appcache=false

The Payroll Control Center (Feature Pack 3 onwards)


The Payroll Control Center had some limitations in FP1/2, and the version in FP3&4 is re-vamped and far more viable for a customer to use.  If you are considering implementing a payroll control center, I recommend you jump straight to FP3 as a minimum.

There are 2 business roles catered for in the Payroll Control Center (FP3&4); The Payroll Manager (FP3), and The Payroll Administrator(s) (FP4)

The Payroll Manager accesses the PCC via URL:

https://<sap ecc server details>:<port>/sap/bc/ui5_ui5/sap/hrpy_pcc_proc_2/index.html?sap-client=010&sap-uilanguage=EN&sap-ui-appcache=false

The Payroll Administrator(s) accesses the PCC via URL:

https://<sap ecc server details>:<port>/sap/bc/ui5_ui5/sap/hrpy_pcc_errm/index.html?sap-client=010&sap-ui-language=EN&sap-ui-appcache=false#/Worklists


Note – there wasn’t any SAP documentation (that I could find) telling us the payroll administrator URL when we were building the control center (unlike the cockpit and payroll manager’s control center view), so we had to work it out ourselves.

However, once worked out and a process built, the solution really came together.

The Payroll Manager view



From here the payroll manager can physically run payroll, for example the process can be setup as:

  1. Release control record for payroll
  2. Run payroll driver (in parallel if required)
  3. Run Posting Simulation
  4. Run ‘Policies’ – i.e. run the checks described in the Payroll Cockpit section above
  5. Run ‘Monitoring’ – i.e. assign out the checks to the various payroll administrators for processing / actioning.  This step also allows the Payroll Manager to track what items have or have not been actioned
  6. Exit Payroll control record
  7. Run Production Posting

/wp-content/uploads/2015/08/1_770565.jpg

Each step can be re-run as necessary, i.e. once your payroll administrators have actioned their checks, you can, for example, simply select the “Run Payroll” item again and re-run pay.The most exciting part of the toolset (to me at least) isn’t actually that you can physically run RPCALCX0 from a UI5 browser, it’s the check and validation process (i.e. Policies and Monitoring in the above screen).  You can setup the Payroll Control Center to just perform the checking process (i.e. Policies and Monitoring steps) if you wish, and keep the payroll processing in the back end.As a payroll manager, in the monitoring step you see a summary of the issues identified:

/wp-content/uploads/2015/08/2_770566.jpg

and get to assign out the various items to be actioned by the payroll administrators of that area:

/wp-content/uploads/2015/08/3_770573.jpg



Then the (once the payroll manager clicks on “Start” in the monitoring screen) above the payroll administrator (Joe Bloggs in this example) can see those checks on their error management screen of the payroll control center (below):


/wp-content/uploads/2015/08/5_770574.jpg


One of the big, additional aspects available as part of FP4 is the extra detail you get within these checks / validations.  If you click on one of the items above (Net Pay > $4000 in my example) you get some additional information:


/wp-content/uploads/2015/08/4_770575.jpg


The “Solutions” link “Check employee pay details” here is actually a hyper link and will take you into SAP (GUI via your browser) to look at the employee.But even better than that is, if you click on the row you can go to the detail screen where you can set up the check to give you additional information for the employee like a wagetype reporter style output for them, their Payslip, and other important information.  This can all be customised to what you want for your customer:


/wp-content/uploads/2015/08/7_770576.jpg


As far as relevant information presented in one place for a payroll administrator to review and action, this is excellent!



What you need in order to implement


This solution is a significant change / addition to the normal ECC back end only functionality many consultants / customers may be familiar with.  Therefore, I recommend you take a 2 step process to getting it up and running.


Step 1 – Get the payroll cockpit working. This is significantly helped by the RDS solution SAP provide, and is less complex and better documented than the FP3&4 control center


Step 2 – Get the FP3/4 Payroll Control Center working



Additionally, the below skillsets are necessary to be able to implement (and change) the toolset effectively to be of value for businesses:

  1. ABAP (Object Oriented) programming skills (sorry functional only people, it doesn’t mean you need to be able to code yourself, though it is an advantage, but you need access to someone who can to implement what changes you want, and it’s all ABAP OO code)
  2. Gateway (limited knowledge required)
  3. SQL (if you’re using declustered payroll results, which you need to really be to be able to run payroll checks in a practical timeframe)
  4. Payroll result structures
  5. Master data structures
  6. Payroll Processes
  7. Perseverance – this stuff is not intuitive (to start with at least) and will require your problem solving skills to get it running

Step 1 – Get the payroll cockpit working


Firstly, get the technical base items installed:

  1. Get on to the required HRSP / FP level (and associated dependencies like SAP_UI)
  2. If you’re installing the control center (i.e. not just the cockpit) then make sure you get as up to date as you can.  There were a lot (approx. 20 or so) notes released in July / August 2015 to fix issues, before I had those notes in the Control Center wasn’t working well for me
  3. Install the RDS solution (http://scn.sap.com/community/erp/hcm/blog/2014/11/24/a-best-practice-to-implement-sap-payroll-control-center-add-on)

Then on to activating items:

  1. Get familiar with the (200 page L ) document on the payroll cockpit and control center available in OSS note 2053309Note – for the control center, this document provides information on the original control center (i.e. pre-FP3).  Though it’s good to read this for background knowledge, the FP3 one is reasonably different so don’t use this as the bible for FP3. The install info is from page 157 of this document
  2. Someone (normally basis) who can setup the gateway components in section 7.4 (you don’t need a standalone gateway box, the gateway items can be done on a normal ECC box)
  3. The test item in section 7.6 of this document will not do much, it’s just a test to see if you can see the object from the payroll cockpit link.  If you can’t see anything from your URL then it’s likely an auth issue. Basis can run an auth trace to see what objects your ID is failing on, it’s likely it’s those in section 6.6.1. Talk to your security team about getting your role updated to include these objects
  4. If you can see the test object then chances are (if you’ve installed the RDS) that you’ll also be able to see those tiles, click on them and you should be able to see the details of the RDS provided checks (provided you’ve run program PYD_EXECUTE_INSTANCES)

Once you’ve got to this point you’re up and running.  Now it’s a question of using the templates SAP provide in the RDS, and playing with them to understand how they work and how to alter them for your business.



Step 2 – Get the Payroll Control Center working

  1. Read the document provided in OSS note 1995698
  2. Create 2 users, one being the payroll administrator, one the payroll manager
  3. Ensure both are setup in table T526 as administrators for your payroll (the large 200 page document talks about this)
  4. Run program PYC_ADM_TRANSACTION to get the various background jobs required to support the payroll control center going
  5. Get a basic payroll process up and running (i.e. use process template PYP_V2_PRODUCTIVE_PAYROLL as a start).  Don’t worry about your checks (i.e. policies and monitoring step) for now.  Again, you may hit auth issues here, so use a trace to find out the objects you’re hitting and failing on
  6. Once you have the payroll process working, get a FP3 check up and running, use data source type PYD_CHK_FP4_SAMPLE, data source class PAYROLL_POLICY_EXAMPLE_3 as your base. Note – the class and methods for the FP4 checks are reasonably different from the ones the payroll cockpit uses, so don’t worry about using any payroll cockpit ones for now, just use the SAP provided FP4 one.  Note – this SAP provided FP4 check reads declustered payroll results, so if you don’t have declustered results you’ll need to copy this class to something else and change the check to return information from master data just for the purpose of ensuring you get a result from the check
  7. Once you have one working, you can now start to copy across the payroll cockpit checks you have from the RDS solution into the FP4 version of the data source classes to give yourself a suite of checks
  8. Then you can really get to grips with the additional items you get in FP4 with the various subscreens of the swim lanes in the payroll administrator’s UI5 view (i.e. the solution suggestions, Key Values, Generic overview etc) that enable the payroll administrator to be given more information about the employee that has come up in the check

Areas for improvement


     1. No RDS available for the FP3/4 Control Center yet

If you want to get the Control Center in FP3/4 going, it will require effort to do so, but effort that I believe is certainly worthwhile

     2. Automatic assignment of items to be investigated / resolved

Most clients I have (particularly large ones) distribute their payroll by personnel area, employee group (or something similar).  The payroll control center does not yet have functionality that will automatically assign all errors associated with personnel area 1234 to payroll administrator A, etc.  The payroll manager has to do this manually


     3. Position based access

Currently a user has to be assigned to the administrator group directly in table T526 in order to appear in the UI5 screen as a user to assign checks to in the control center (as well as have the relevant auth objects assigned). Given people move in and out of positions, it would be best (in my opinion) if this access to the control center was provided based on an attribute against a position.  Having T526 drive it makes things very manual

     4. Auditing who did what

The payroll administrators can flag employees who have come up in a check as being ‘correct’ and their exception ‘resolved’.  However, there isn’t a report (or screen) at this stage that a payroll manager can use to establish who has set an employee to being OK. This kind of functionality would be of additional benefit should there be an overpayment (or worse still underpayment) to an employee which an administrator had looked at and decided was OK to pass.

     5. Scheduled processing

Currently the payroll control center requires someone to trigger it, i.e. you can’t set it to run overnight.  This may impair some customers from taking it up as they like (for obvious reasons) to get the payroll processing and locking down of employees done out of business hours

Key mindset changes


The payroll control center (and to a lesser but similar extent the payroll cockpit) is about running the pay, establishing exceptions, and correcting those exceptions in order to complete the payroll efficiently and correctly.  It doesn’t cover ‘reporting’ or reconciling the pay in the way we are used to via WT reporter, etc (currently at least).


In Summary


FP3 brings SAP payroll processing into the modern age.  It gives the payroll manager and administrator the ability to interact directly in their processing, leveraging payroll and master data validation checks, parallel processing performance, and declustered payroll results to give a faster, more efficient and more effective process.

To report this post you need to login first.

26 Comments

You must be Logged on to comment or reply to a post.

  1. Imran Sajid

    Hi Steve,

     

    Great article and blog post! Thanks for sharing your perspective and providing all of the helpful information! I am sure this will be useful for many people.

     

    Regards,

     

    Imran

    (0) 
  2. Jarret Pazahanick

    Really great job with this Steve and especially like your “Areas for Improvement” as all real world scenarios and given the investment in the Payroll Control Center wouldnt be surprised if they are there in a future release.

     

    I would add another that I mentioned to product management last week at SuccessConnect of not having to set up processes by hard coding payroll area in configuration as wouldn’t be hard to design where payroll area sits at a higher level.

     

    The monitoring functionality (prior to running the actual payroll) is a real step forward and something customers have wanted for years so am glad that is included.

     

    I will be going live with a customer using the Payroll Control Center on FP4 including much of the RDS content in 40 days and it is been a fun experience as after working on the “old” SAP Payroll for 17 years nice to see the new UI/UX.

    (0) 
  3. Yi He

    hi Steve,

     

       Great blog post ! Thanks for your sharing, someone refers this blog to me….( actually in a new message, aha~don’t worry)

       URL https://<sap ecc server details>:<port>/sap/bc/ui5_ui5/sap/hrpy_pcc_errm/index.html?sap-client=010&sap-ui-language=EN&sap-ui-appcache=false#/Worklists  is a new feature in FP4.

       we still use payroll cockpit in FP3.

      Thanks again for your blog, this really help users to understand our PCC.

     

    Best regards,

    Yi

    (0) 
  4. Sven Ringling

    Hi Steve,

     

    thanks  a lot for this. With the documentation being quite patchy at the moment, any sharing of experience is very welcome 🙂

     

    One question:

    It seems the declustered simulation results are only used for checks and custom programs? Or did I miss any standard programs (wage type reporter would be great) to be working on these results?

     

    best wishes

    Sven

    (0) 
    1. Yi He

      hi Sven,

       

         the declustered results is optional for customers, not mandatory…so that there is no standard core report using declustered results till now…I’m not sure if country team did any report/program using declustered results, you may connect with them for more info…

       

      Best regards,

      Yi

      (0) 
      1. Sven Ringling

        Thanks, Hi Ye,

         

        I understand customers have tobuse declustering for FP4 and that’s where the test results are. Without declustering, non test run results.

        These test results are, what I’m talking about (the fact they don’t live in a cluster is secondary). The whole purpose of storing reportable test results would be to report on them, right?

        But other than checks (also mostly custom), there are no reports, unless you build your own. I would have expected wagetype reporter and posting simu to run on test results at least to help identifying errors early. Plus local ones like RTI simulatiin for UK.

         

        Anybody knows the SAP roadmap?

        (0) 
        1. Yi He

          hi Sven,

           

            yes, you r right, for PCC test run results/checks, the declustered results are mandatory.

          Maybe the wagetype report which based on test results could be replaced by results checks ?  I’m not sure…and if all the payroll results are correct then the posting should also be correct, right ? 

           

          Best regards,

          Yi

          (0) 
    2. Steve Cottrell Post author

      Hi Sven,

       

      Sorry for for not replying earlier, I’ve been on vacation.

       

      As Yi says, all uses for declustered results (both real and “test”) are only available by custom checks and reports at the moment.  That means our classical way of checking payrolls doesn’t simply and directly translate to “test” payrolls yet. “Test” payrolls can’t be checked by a posting simulation, payslip validation or a standard wagetype reporter yet. It can only be checked by custom programs / reports built in ECC or in the Payroll Control Center.

       

      Cheers

      (0) 
  5. Marc Frenay

    Hi experts,

     

    Thanks for this great blog.

    I try to add a worklist to an employee (whom exists in the t526) but the employee’s name is not shown up in the UI5 screen. Do you know wich authorization objects is needs to be able see the employee’s name in the list?

     

    Thanks a lot.

     

    3. Position based access

    Currently a user has to be assigned to the administrator group directly in table T526 in order to appear in the UI5 screen as a user to assign checks to in the control center (as well as have the relevant auth objects assigned). Given people move in and out of positions, it would be best (in my opinion) if this access to the control center was provided based on an attribute against a position.  Having T526 drive it makes things very manual

    (0) 
    1. Steve Cottrell Post author

      Hi Marc,

       

      Thanks for the feedback.

       

      It might be easier if you private message me.  Basically table T526, program PYC_GENERATE_STEP and the user’s user record (SU01 / SU3) need to have the relevant administrator group in it.

      Send me a message and we can work through it.

       

      Cheers

       

      Steve

      (0) 
        1. Steve Cottrell Post author

          If you follow me in SCN (button on top right of page generally on the blog) then you should be able to direct message me in the communications screen of your profile once I accept you.

           

          Cheers

          (0) 
  6. Arijit Barik

    Hi Steve

    Excellent article and a perfect overview for a consultant..i just have one point. You mentioned that there is no log available for Auditing…but there is a Action Log Viewer UI5 application available where the payroll manager can check which payroll admin took what action and which date…Also there is a backend report which displays for every process the steps executed with the outcome of that step…

     

    Thanks,

    Arijit.

    (0) 
    1. Steve Cottrell Post author

      Thanks Arijit,

       

      Sorry for not getting back to you earlier, I was away over Christmas.

       

      There is indeed the action log viewer (http://<sap ecc server details>:<port>/sap/bc/ui5_ui5/sap/hrpy_pcc_al/index.html / ECC Program PYC_ACTION_LOG_VIEWER) however, that will only show the actions taken to start or confirm a step in the control center, it doesn’t go to the level of detail my customers tend to want.  (Unless I’m missing something about how it works).

       

      What most of my customers want is the ability to see who set an employee to resolved (and for what reason) when that employee appears in the Policies exceptions.

       

      Basically, if an employee came up as an exception before they were paid, and an administrator then marks that employee as OK (when in fact that employee did have a problem with their pay that needed to be resolved).  Should that employee be paid incorrectly and call up the payroll department upset that they have been paid incorrectly, the payroll manager would have the ability to see whether this employee appeared in the Policies exception report and whether a payroll administrator incorrectly marked them as OK.  This can assist in ensuring payroll administrators are appropriately trained / retrained in order to catch these issues. 

       

      Also, if there are gaps in the policies where exceptions aren’t being caught then such a reporting capability could assist in establishing additional policies that would be of value to the payroll manager.

       

      Thanks

      (0) 
      1. Arijit Barik

        Hi Steve,

         

        i am currently implementing the Payroll Control Center FP4 for one of the customers and have completed the RDS setup. I am wondering what needs to be done inorder to bring up the poposed ‘Solutions’ and navigation to the PA30 screen. Is there some SAP documentation available.

         

        Thanks for your help.

         

        Regards,

        Arijit Barik.

        (0) 
        1. Steve Cottrell Post author

          Hi,

           

          A way of using the solutions to trigger a PA30 screen would be to put something like the below in the ERR_SOL_GET_LIST method of your validation rule:

           

                  ls_sol-row_id = ‘000’.  
                  ls_sol-type = ‘CHG’.    
                  ls_sol-semantical_id = ‘CHGKEY’.
                  ls_sol-title = ‘Change employee data’.
                  ls_sol-description = ‘Go to transaction PA30’.
                  ls_sol-link = lv_server_url && |/sap/bc/gui/sap/its/| && |webgui?~TRANSACTION=*PA30%20RP50G-CHOIC=0000;RP50G-PERNR=$$$$$$$$;DYNP_OKCODE=DIS|.
                           
                  replace ‘$$$$$$$$’ with ls_err_sol-id into ls_sol-link.
                  append ls_sol to ls_err_sol-sol_tab.
                endif.
                modify ct_err_sol from ls_err_sol.

           

          This will trigger SAP WebGUI so the user can go in and make the change.

           

          Cheers

           

          Steve

          (0) 
          1. Arijit Barik

            Thank you  Steve,

             

            i discovered yesterday the sample code from the Data Source Run time class CL_PYC_CHK_F4_SAMPLE. It would have been great to have this enabled through customizing and without the need to get into coding.

             

            Regards,

            Arijit.

            (0) 
            1. Steve Cottrell Post author

              Hi,

               

              I think the architects of the PCC decided to use coding for the solution aspects as 90% of any new validation rule will always require code, it’s only if the validation rule can be used as-is but with parameter variances that you can use customizing.

               

              Additionally, having code allows greater flexibility as to what you can do to apply a solution and resolve an issue, i.e. you can call SAP WebGUI, and HRF, you could go to an interface tool, go to Success Factors etc.  I don’t think doing this via customizing only would have been a practical method to have designed into the product.

               

              Thanks

              (0) 
  7. Utkarsh M parikh

    Hi Steve,

     

    Blog is superb but need some help on this.

    Need your help in implementing Payroll Control Center.

    Can you please share end to end step to implement this functionalities.

     

    Regards,

    Utkarsh

    (0) 
  8. Steve Cottrell Post author

    As I mentioned in my blog, the existing RDS was for the previous version of the PCC.  The RDS for the new PCC is now available!  See:

     

    Rapidly improve your payroll experience with the NEW SAP Payroll Processing control center rapid-deployment solution

     

    SAP Service Marketplace – Payroll Control Center

     

    Implementing validation rules in the new Payroll Control Center

     

    this should really help you accelerate your implementation

    (0) 
  9. Debjani Kar

    Hi Team,
    We are in the process of upgrading the Payroll Control Center (FP2) to PCC FP5. As per the documentation, I understand that the below Business Functions must be activated to ensure that the new layout is visible in the front end. Please confirm if anything else is needed to view the Process Templates (PYP_V2_TEST_PAYROLL, PYP_V2_PRODUCTIVE_PAYROLL in the front end. Also, after adding a custom process and adding a Policy to the Process, while generating the Process, the error ‘Incorrect input parameters for check type PYD_EXAMPL_PERNR_CHECK_FP3 in policy PAYROLL_POLICY_EXAMPLE_1’ which eventually is a standard check.
    HCM_LOC_CI_50
    HCM_LOC_CI_62
    HCM_LOC_CI_63
    HCM_LOC_CI_68
    HCM_LOC_CI_72
    HCM_LOC_CI_76
    HCM_LOC_CI_79
    HCM_LOC_CI_88
    HCM_LOC_CI_89
    HCM_LOC_CI_92
    Please advise, how to reflect the new layouts in the front end.
    Thanks,
    Debjani 

    (0) 
  10. Tsahi Deleon

    Regarding the RDS for the PCC, very important for EhP 8 installations –

    It turned out, that one of the RDS prerequisites, BP-ERP add-on package, cannot be installed on EhP 8!

    When asking about it at SAP (via a support message), that’s what I was told:

    “For SAP ERP 6.0 EhP 8 there is no BP-ERP package available.

    Currently there is not planned a BP* package for EhP 8 systems.

    The latest version of BP-ERP is only available for EhP 7-based systems.

    Sorry for the inconvenience caused!”

    and:

    “If it is involving the BP* packages, there is no workaround for EhP 8.

    I have discussed this issue some time ago with the responsible developers, but they stated that there will be probably no new BP-ERP release for EhP 8.”

    So take it into consideration when installing/upgrading to an EhP 8 system – you won’t be able to implement Payroll Control Center on it using the PCC RDS.

    Regards,
    Isaac

    (0) 

Leave a Reply