1 / 13

Testing and Validating Payroll in SAP A Company’s Story

Testing and Validating Payroll in SAP A Company’s Story. Janet Batchelor Marthe Perron Jocelyne Latour. A Company’s Story. Payroll processes from three different companies Configuration and Development Testing – Marthe Perron, Hydro Quebec

butch
Download Presentation

Testing and Validating Payroll in SAP A Company’s Story

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Testing and Validating Payroll in SAP A Company’s Story Janet Batchelor Marthe Perron Jocelyne Latour

  2. A Company’s Story • Payroll processes from three different companies • Configuration and Development Testing – Marthe Perron, Hydro Quebec • Payroll Controls and Segregation of Duties – Jocelyne Latour, Pratt & Whitney Canada • Testing HRSPs, CLCs, Year-End – Janet Batchelor, SaskPower and Solvera Solutions • Day to day production issues - Janet Batchelor, SaskPower and Solvera Solutions • Each company will described at a high-level their process • Open-up to audience for discussion

  3. Configuration and Development Testing We have to support our tests • Over 70 scenarios for the module HR alone – including E-Recruit • Over 300 scripts of detailed transactions • Our focus is to make it easy for the person who's doing the test to be able to do it without knowledge of the HR solution • Our longest scenario is call "Vie condensée" (condensed life) it is made with over 50 steps and consist of somebody who begins it's life at Hydro-Québec, to the retired, dies ;O( and leave's his retirement pension to me ;o) as a beneficiary

  4. Configuration and Development Testing Testing When testing a new functionality, a new development or a configuration change, the person can choose from a range of scenarios and script to test the changes Each time something new is created, we amend our scenarios or scripts to reflect the addition If it is a modification or a correction, we can then change a scenario or script or we find one that is in line with what we are testing Also depending on the modification we can have more then one person testing 4

  5. Configuration and Development Testing Our environments We have one development system We also have three QA's, one for production support, one for our delivery to come and one for our delivery plus one We also installed HRSP's twice a year and Enhp once a year By doing this we do need a series of scenarios and scripts and they need to be up to date when we make some configuration or development changes into the system 5

  6. Payroll Controls and Segregation of Duties Segregation of Duties (SOD) • Adequate segregation of duties is an important consideration in determining if control activities are effective. Business units are encouraged to use this form to help identify potentially conflicting duties within each application and within related applications. • Sensitive SAP transactions (Master data, additional payments & basic pay) as well as access to HR & Payroll data drives are password/ID protected. A quarterly audit is performed.

  7. Payroll Controls and Segregation of Duties

  8. Payroll Controls and Segregation of Duties Audits before closing Payroll To ensure no duties or tasks are forgotten, we created a check lists.

  9. Testing HRSPs, CLCs, Year-End A Quality or Test system refreshed with most current copy of production environment Find it helpful to have two ID’s for testing purposes; one is identical to Production and ‘2’ id has more support and administrative type roles included Payroll Parallel with Before steps to provide snapshot for comparison and After steps to confirm process still works as expected, or differences/discrepancies are fixed or explainable Payroll Scenario test to use when a parallel is not an option PC00_M07_CCYR Year end reporting (Canada) Audit/Reconciliation reporting using T4xx and/or TAxx which equate to the form configuration – very useful in analyzing $ in boxes and pinpointing issues before generating test prints 9

  10. Payroll Controls and Segregation of Duties Quality system with good data akin to Production and/or a ‘Clone & Test’ tool Access that allows you to run simulations (PC00_M07_CALC_SIMU) Check Display Log (on) Open sections and drill down to rule(s) Programs RHUSERRELATIONS and RHAUTH01 T-code PC_PAYRESULT or S_AHR_61018788 Display payroll results (RK) Tcode S_AHR_61016380 Logged Changes in Infotype Data Config in personnel management > Personnel Administration > Tools > Revision > Set up change document define the infotypes, fields on the infotype and type of document(s) by field group (characteristics) (Pick & choose what you really need – database entries made for each) 10

  11. Payroll Controls and Segregation of Duties Tcode PA20 Display Master Data Tcode PC00_M02_LINF0 Infotype Overview for Employee Tcode PC00_M99_DLGA20 Wage Type Utilization Tcode PC00_M99_DKON Wage Type Assignment Display GL Accounts Tcode PA03 Payroll Control Record 11

  12. Key Learnings • Take the time to update your scenarios and tests • Take the time to get them right and include all your process • It will simplify the process of all your testing • Don't overlook/underestimate the ongoing process of keeping them up to date • Value Realization of having them always up to date

  13. ] • Thank you for participating.

More Related