SAP HR testing (OM,PA, PY ,Benifits,Time ,ESS,MSS)

[Former Member]

Hi Experts,

We are in testing phase ,as have been assigned testing for below modules.

Can any one please give me couple of test case live examples ( business scenario) on OM, PA, Benifits, PY,Time ,ESS,MSS with sequence of test steps.

Thanks,

Renu

[former_member47879]

For PA

You can have Hiring to Separation as one scenario

Maintain employee data here you can maintain some infotypes (without portal it can be employee initiated or manager initiated)

Maintain employee data with portal employee initiated

maintain employee data with portal manager initiated

Transfers with compensation change/without compensation change

Contact changes and extensions

Manager initiated separation

employee initiated separation

change start date

Time

You create absences

to check quotas

to work schedules

to check overtime

to check release of working times to payroll

these can be with portal without portal

OM

create positions

Org units

with portal with out portal

Payroll

You have scenarios testing of wage types

negative scenarios giving wage types for the person who are not entitled for that wage types

checking various deduction wage types payment wage types

MSS

Managers submitting various for the change requests

it can compensation changes

transfers

requesting for creation of positions

org units

or hiring some one using portal

appraisal

extension of contract

etc

[Former Member]

Hi,

You will have to go back to requirement phase documentation and blue printing. This documents will help you to find out all the business processes that user/customer would perform with help of SAP HR. For all such processes, you will create a test script with multiple scenarios.

Eg: If you are creating a script for business process of hiring, then you have to consider all the possibilities that system should allow and also those possibilities that system should not allow. ie try hiring an applicant. Try hiring an internal employee. try hiring a previously existing employee who is not active as of now. Here as per organizations policy and legal requirements, system should allow/disallow the hiring and data gathering while hiring.

Thus in PA you should test all actions, for OM also +test all org assignments through PA actions, In time and Py, carry out time evaluation and payroll run for sample pernrs with all the data in the system and check if the resultant output is as required by the organization policy and legal requirements. Also check if all the annual functions like leave balance updation or taxation works as required.

For ESS, try to use the system for all the ESS activities that are allowed in the system for your case... May be like changing self address, may leave application etc.

For MSS, test if manager can see the OM structure wise people under him (Direct/indirectly reporting). See if the allowed managerial functions are working as per the expected results. Also try creating reports required by managers through MSS.

You can try multiple things...

For all of this, Get a user mannual. Use it while test scripting. A tabular format for scripting is better idea. Col 1 may contain user steps, col2 may contain expected results, col 3 will contain actual results, col 4 may contain status (successful / failure / successful with deviation in expected results / etc).

For scripting templates, search on google. You may get some good templates.

Hope this guidelines help...

If this answer helps, Please allot points and close the question.

Let me know if you need more information on this.

Thanks,

Dhiraj

[Former Member]

Hi,

Test cases:

Nothing but expectation results. However we are doing project in IDES server, expecting results, at similar way we are doing live project in Dev client.

However we are testing the scenarios in IDES server, in similar way test the data in dev and quality client, But in ides no next clients , in live project we have different clients. and will do testing in different clients.

PA:Ex: Action we configured in dev, we are performing the actions in dev client, if it is working fine, then we will move quality client, again we will search here also, we will hire the employee, will perform the different actions, if it is fine, then we will move to prod,

TIME ex: Will create holidays, workschedules, quotas, absences in dev client, after completion of testing(expectation results), we will move to quality client(here also we will test the data(whether proper data correctly move or not, scenarios are working or not)) here scenarios means workschedule calendars(with perfect dates, quotas generations, absences deductions from quotas).

Payroll Ex: will create wage types, payroll area, absence valuation, changing the rules will do in dev client, then we will test different scenarios, with hire the employee different dates and will run the payroll, how employee payroll is generating will test in dev, once if it is correct then will move to quality client, again here also we test the data with different scenarios .

ESS ex: Leaves or coming correctly or not work schedule calendars are generated or not will test the data.

Before testing we will create the test scripts, after completion of testing in dev and quality will give the testing results whether test will be passing or failure.

If it is failure we will write small description, again will do configuration and will test the data, and will give the results of the scripts.

Test scripts models will be vary to company to company.

Good luck

Devi