Hello payroll professionals,

As you read in earlier posts the new SAP Payroll control center add-on provides a fundamentally new approach to ensure payroll accuracy in which potential issues are pointed out near real-time by the application rather than payroll administrators digging through information and trying to find issues and resolutions themselves. With this functionality payroll administrators only need to focus on issue solving and this saves payroll departments a lot of valuable time.

SAP Payroll Processing control center rapid-deployment solution V1.607

SAP now released a rapid-deployment solution with pre-configured validation rules which focus on Master Data monitoring, for the pre-payroll process, and Reconciliation Rules for post-payroll processing. With this rapid-deployment solution SAP provides best practice examples and documentation which serve as a foundation for the implementation of the SAP Payroll control center add-on. This helps organizations to increase the efficiency of the process, reduces errors, and improves the accuracy of the payroll.

Master data validation rules


Validating master data before the payroll runs helps customers to optimize their data quality and it provides certainty around error free payroll runs. Personally I have talked to customers that have implemented the SAP Payroll control center add-on which are really helped by the capabilities the solutions delivers to validate their master data.

The examples provided in the rapid-deployment solution are used as examples and are easily copy pasted to create new validations. Customers told me they can implement new validations within 30 minutes based on the examples provided.

The following predefined master data validation rules are part of the rapid-deployment solution:

  1. Employees without main bank account details?
  2. For which employee does the employment percentage not match their utilization (Comparison of infotype 7 with infotype 8)?
  3. Duplicate earnings (Comparison of infotype 14 with infotype 15)
  4. Lived-in a certain state / Worked-in another state
  5. Zero base payment and payment in infotype 14 or 15
  6. Personnel number locked for payroll
  7. Validate if salary increases more than work hours compared to previous pay period
  8. Validate if salary decreases compared to previous pay period
  9. Validate if salary changes >=10% compared to previous pay period

One of the benefits for the master data validation capability in the SAP Payroll control center add-on is decentralization. The ability to provide stakeholders in the business almost continuous access to potential issues they need to solve before the payroll can run is vital for a quick processing time. The authorization framework only points out the relevant potential issues to the end-user. They now instantly see which corrections are necessary to run a successful payroll.

In addition to this, the payroll manager has a helicopter view dashboard which points out the errors that still need to be processed and or fixed before they can run the payroll.

Post-payroll validation rules

The rapid-deployment solution also contains predefined validation rules which run after the payroll run is executed. This provides insight into the payroll results and ensures that payment to employees will be correct.

The following predefined reconciliation validation rules are part of the rapid-deployment solution.

  1. Overview of cash payments
  2. Validate active employees without any pay in current period
  3. Total number of employees paid
  4. Gross pay over a certain amount
  5. Net payment over a certain amount
  6. Retro pay over a certain amount
  7. Issue statistics
  8. Net payment less than a certain amount
  9. Negative deductions
  10. Negative gross payment
  11. Variance in net pay over a certain amount
  12. Variance in net pay over a certain percentage
  13. Overtime payment over a certain amount
  14. Employees with overtime exceeding percentage of total pay
  15. Terminated employee with payment

These validation rules are executed on the payroll system after running the payroll. The rules run on data in the new declustered tables. More information on declustered tables can be found here: http://scn.sap.com/community/erp/hcm/blog/2013/12/19/how-do-sap-hcm-customers-benefit-from-declustering-payroll-and-time-management-on-sap-hana

An additional benefit of declustering is the ability to perform ad-hoc reporting on this data. This post provides an overview on how to accomplish that. http://scn.sap.com/community/erp/hcm/blog/2014/07/04/new-analytic-capability-of-payroll-results-via-declustering Speed improvements (even on traditional data bases) have been really massive. This helps to get rid of background processes for payroll result report assemblance and to provide instant insight into your payroll data.

More information


More information around the rapid-deployment solution can be found here https://service.sap.com/public/rds-pcc.You can download the package and a step-by-step guide on how to implement the functionality.

Please also double check the following notes:

What are the benefits?

SAP delivers rapid-deployment solutions including content like the step-by-step guide which explain step by step what needs to happen during an implementation. This content is available for every customer. 

With regards to the SAP Payroll control center add-on the biggest benefit is the flexibility the framework offers to create meaningful validations. Until now SAP could serve all customer requests for payroll validations so we have yet to experience the limits of the framework. However, the flexibility in the framework is a result of coded validation rules. Think of them as individual BAdIs per validation rule. Obviously this requires strong skills to implement the SAP Payroll control center add-on.

One of the lessons learned from implementing the functionality is that this rapid-deployment solutions really helps to drive a best practice for implementation. The predefined validations helped experienced consultants and developers to build a quick and detailed understanding of how to develop content. In addition, one of the benefits is that the predefined content accelerated the understanding of working with data in declustered tables. This avoids pitfalls for poorly performing validation rules. So if you want your validations to run in real-time you need to understand how to develop the validations.



What if you’re a SAP Partner?


Rapid-deployment solutions are also provided to qualified SAP Partners. That means that partners can also leverage the 24 predefined rules to accelerate implementations, get a best practice on how to code the rules and use it as starting point to build out own content. More information on the RDS qualification process can be found on the SAP Partner Edge portal: https://partneredge.sap.com/en/partnership/implemention/rds.html 

Therefore I really recommend everyone who implements the SAP Payroll control center add-on to leverage this best practice!!

Looking forward to your implementation experiences!

And if you need more information you can always reach out to me or to the package owner for this RDS: alexsandra.zanetti@sap.com

Best regards,

Frans Smolders

Frans.smolders@sap.com

To report this post you need to login first.

9 Comments

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

  1. Edgar Valverde

    Problematic Payroll Control Center (PCC) The configuration was completed under the standard steps but have certain functionality that are not working the form at that  should do in the system. Payroll Control Center operates on programs that the PCC portal sends to ERP to be executed in background. These programs work properly:

    • Open Payroll
    • Run Payroll
    • Sent to accounting
    • Close payroll

    The origin of the problem is the execution of the policies which they have by standard PCC, these are not being executed because PCC Portal  is sending these programs to the ERP, they are being aborted and stopped, for this reason they don’t end adequately and the distribution of the mistakes cannot be sent to the payroll administrators.

     

    The programs that are stopped are standard elements that the system uses to send the policies and to distribute the possible mistakes. Therefore we observe that the possible origin of the problem is in some standard functioning; which is not executed correctly and / or having some problem or fault.

    The origin of the problem is in the PYC_EXECUTE_POLICES program and throws the following mistake:

    “No execute instance found”

     

    This program throws the policies to evaluate the execution of the payroll and to find possible mistakes

     

    When analyzing this program this performs a search in the PYD_D_INST table (its content is created with the standard report PYC_STEP_GES which takes the settings made for PCC and generates the content of the table) of standard policies ZPYP_V2_INIT_POLICIES (copy of PYP_V2_INIT_POLICIES), the search is performed whit the TYPE field, (the detail search are standard polices, example PYD_CHECK_PY_REJECTED_EES, PYD_CHK_FP4_SAMPLE, PYD_EXAMPL_PERNR_CHECK_FP3) this policies are not found in the table then  we see that the error is triggered.

    Alternatively we try to change the TYPE field-value with a value where it finds the first policy manually, but if we do the above, the  instance PCC in the portal is not  executed and stopped. And there is no way to continue working on the portal.

    We understand that PYD_D_INST table is created with the PYC_STEP_GES report therefore believe it is something that should not be working properly, this situation causes that instance is not found and the policies process is aborted and stopped.

     

    We appreciate any ideas or help possible cause of the problem

     

    (0) 
  2. 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) 
  3. Daniel Piggott-Genge

    The notes mentioned

    Don’t seem to exist currently….. We’re really stuck as, at the start of the steps to implement the control center it says it needs to copy classes (all beginning /SMBERP/) into the customer namespace but we don’t have any of those classes at all… Have we missed something obvious ?

    (0) 
    1. Daniel Piggott-Genge

      Just to update.  In the end we realised we hadn’t implemented the Rapid Deployment for PCC and now we have we have the classes etc.  So if anyone is in a similar position, make sure you are using the Rapid deployment method to implement this.

      (0) 

Leave a Reply