SAP HR Interface Testing

[#1]

Dear all -

I am a newbie to SAP HR module. I am going to work on a project where the areas concentrated in HR are - Organizational Management/Personnel Administration; ESS/MSS and Interface Testing.

Could anyone please advise me as to what would Interface Testing involve? What would be the third party tools used?

Also, please let me know what could be the scenarios that would be tested in Organization Management/Personnel Adm and ESS/MSS?

Thanks very much -

Shilpa Reddy

[Former Member · Accepted solution]

An Interface is a program that takes data from one system and transfers it to an other.

Typically, the first program will produce a "report" in text or xml format, and the program will then read that file to input the information into the other system (with or without data manipulation).

For example, if a third party program takes care of attendance, the interface will take that information to "populate" the Attendance Infotype in SAP, and your task will be to make sure that the data is transfered completely and without error.

[Former Member]

Solved

[former_member47879]

Interface Testing- Check whether the files or employee record updated in the respective infotypes or fields

You can have multiple scenarios with different types of employees

Regarding testing of ESS/MSS

It would involve testing of the process such as transfers, contract changes, and other PCRs personnel change requests

You can test end to end processes also check whether manager able to approve all the requests

Coming to ESS , check whether employee able to submit details, checking of payslips, able to submit leaves, training requests etc

[Former Member]

Hi,

as 'third party tool', I would recommend to use SAP XI. This is standard SAP - middleware and will definitely speed-up the proces of creating the interface.

The testing of the interface would be based on business processes: What should the interface do in real - life and just test if all those scenario's are processed correctly by the interface in your test - landscape.

A good testing - strategy for your interfaces would be to initially perform unit tests:

• Is the outbound interface correct, in other words is the outbound interface file meeting specifications in terms of lay-out etc.

• Is the inbound interface correct, in other words does the inbound interface read the file correct and are the right actions perfomed in the target - systemn

Once all unit - tests have been performed, proceed with integration tests, in other words follow the process from front - to - back.

Normally interfaces testing can be integrated with testing of other processes that need to be tested as interfaces are mostly a technical solution to get data from A to B.

Wilfred.

[Former Member]

Hi Shilpa,

You have asked a question which is totally customer specific. Until unless some one knows the details of your customer it is very difficult to answer the question. Anyway here is the common guidelines.

For Interface...

1) First you have to identify the third party tolls which your customer will use.

2) If the third part tolls are identified, then you check the sap standard and custom interface which are using in your sysytem.

3) Check whether the interfaces are inbound or outbound and what type of data are send/received by the interfaces.

4) Execute the interface and check whether you are getting the correct data or not.

For org management..

1) Check the org structure are correct or not.

2) Test the scenarios related to org structure.

3) Check whether PA OM synchronization is on or not.

4) Test your customer specific scenarios.

For ESS/MSS..

1) Check the bank/address/own data change scenario from portal.

2) Check the portal Forms.

3) Check the ECM related thing to ESS/MSS.

I think you should have test scripts for that.

Thanks & Regards,

Sandip Biswas.