Discuss business intelligence, integration, compliance and a host of other SAP-related topics – implementation, best practices and resources to negotiate the world of SAP better!

« SAP Extended Warehouse Management | Main | Opportunity Maintenance- A point of view: Part 1 »

ESS MSS An Implementation Approach (Part 3)

Implementation Testing Issues and Solutions in Self Services Applications .

The blog highlights the critical and typical issues faced  during the testing phase and recommends the best practices to a good testing approach.Leveraging Testing Cycles to Train HR Service center and HR support team: Testing a system and being able to experience the resolution of issues has proven to be a powerful mechanism for getting the HR support/HRSC  team trained and prepared to support the production system post Go-Live.HR Service center team can also participate in the testing cycles (UAT phase)so that the training time for them  is reduced by 50%. By participating in testing cycles the support team will experience day to day real time scenarios that will soon become  easy and familiar to handle the functionalities  for the different self service applications and forms  when they go live in production

Issue : Self Service applications require an extensive set of data with many employees set to particular state. As we test each test case new employees are needed. For example if we are terminating employees as a manager role that are not terminated to continue to test.

Testing Approach: Create a "Build up" or "Tear down" as required  approach to testing based on what components  are implemented. We can create scenarios while do a hire of an  employee as  a part of test script and then use that employee to complete an entire lifecycle that test every self service component being implemented as a scope in the project. Also try to move the production master data to the test system by doing a client copy and consider which company codes or set of employees we can use for test data. Always separate the test data from the testing scripts so that they can be reused to accommodate different employees within different business scenarios. Sometimes we can also try the client refresh to "reset" employee data for the test cycle. This will return the testing environment data for the test cycles. This will return the testing environment data to a previous snapshot, while it will be helpful before each cycle of testing.

 Issue - Self Service applications require an extensive set of data with many employees set to particular state. As we test each test case new employees are needed. For example if we are terminating employees as a manager role that are not terminated to continue to test.
Test Approach : Create a "Build up" or "Tear down" as required  approach to testing based on what components  are implemented. We can create scenarios while do a hire of an  employee as  a part of test script and then use that employee to complete an entire lifecycle that test every self service component being implemented as a scope in the project. Also try to move the production master data to the test system by doing a client copy and consider which company codes or set of employees we can use for test data. Always separate the test data from the testing scripts so that they can be reused to accommodate different employees within different business scenarios. Sometimes we can also try the client refresh to "reset" employee data for the test cycle. This will return the testing environment data for the test cycles. This will return the testing environment data to a previous snapshot, while it will be helpful before each cycle of testing.
 Issue - Not enough Portal Users to complete test scenarios for functional and regression and Performance testing. Also a complicated set of users with varying passwords.
Test Approach: While we select the organization and employees, request the security team to create userID's based on what is assigned to info type 0105. Request every user should have a common password to limit confusion of testing .Make sure the HR master data is scrambled since it has sensitive information contained in the employee's Infotype records.
 Issue - Workflow notifications and system emails are being sent to active employees.
Test Approach  : Testing system notifications, such as emails, can be an issue and could expose the wrong people to HR data  that they should not have access to .Request a script be created by BASIS that will set all user emails addresses to a group emailbox that the testing team can access. Using this approach will make it easier to test system notifications and will reduce the possibility that data in emails is sent to the wrong email address and unintended users.
Issue - Many Self Service transactions can affect payroll processing. Lack of proper payroll testing could result in project delays or issues with end to end lifecycle testing.
Test Approach - If SAP Payroll is performed inhouse, allocate a payroll resource for your testing cycles that can run payroll for a specified payrollperiod. Payroll should be run at the end of a testing cycle and verified against the business scenarios that are been tested. Make sure all ESS related transactions get tested and approved by the Payroll Department. Services such as Online pay stubs, bank Information , W-4 Info should be tested and validated  by a subject matter expert in Payroll /Payroll Business user to make sure that the results are in adherence with the Business requirements and results.

Leveraging Testing Cycles to Train HR Service center and HR support team: Testing a system and being able to experience the resolution of issues has proven to be a powerful mechanism for getting the HR support/HRSC  team trained and prepared to support the production system post Go-Live.HR Service center team can also participate in the testing cycles (UAT phase)so that the training time for them  is reduced by 50%. By participating in testing cycles the support team will experience day to day real time scenarios that will soon become  easy and familiar to handle the functionalities  for the different self service applications and forms  when they go live in production.

Post a comment

(If you haven't left a comment here before, you may need to be approved by the site owner before your comment will appear. Until then, it won't appear on the entry. Thanks for waiting.)

Please key in the two words you see in the box to validate your identity as an authentic user and reduce spam.

Subscribe to this blog's feed

Follow us on

Blogger Profiles

Infosys on Twitter