E-Recruitment test cases for EHP4 upgradation

[Former Member]

Hi All,

We had implemented E-Rec with EHP2 and client is using last 1 year or more. Now we had already upgraded to EHP4. Now problem is that we do not have idea what to test or what to check?

Can anybody guide or share any test cases for E-Rec testing for EHP4?

What are all new functionality we need to test for E-Rec and other?

It would be great help if anybody can give lights on this.

Regards,

Purnima

[former_member31620 · Accepted solution]

Hi

Hope SAP Note 1241014 will be useful to you.

Best Regards

Reddy

[romanweise · Accepted solution]

As you see above and also in my post mentioned by a previous reply, activating the business functions in EhP4 is not only a small patch which has to be tested. The full ui for the HR guys changes, the handling is completely different. Some functions as changing correspondences undergo a huge change resulting in the need for adaption to all customer correspondences. This cannot only be tested, this need an full upgrade project, concept -> implementation -> test -> training. You furthermore need MSS including the requisition request using HCMPF which should require an own rollout project. The size here differes depending on you experience with portal, MSS and HCMPF for other HR parts.

So as long as you have not activated any business function the tests for the business functions in SWF5 do not apply. Here you just do a standard regression test with the key users and check if everything is as before (you might find some minor changes like the link area for data overviews depending on your original SP as this was included in an SP and not the EhP). If you activated the business functions you have a project. So you will need a test phase including test definition, testing and correction. You could use the description in SWF5 as a basis but as you come from a prior release you better start with your original rollout testplans and adapt according to your decisions made on how to work with the new release / ui.

Kind Regards

Roman

[Former Member · Accepted solution]

Hi Roman,

Thanks for all your help and guidance to give successful demo to our client.

I have few more doubts.... Could you please help me?

1. As mentioned by you, what is HCMPF?

2. In our original system (EHP2), line manager was initiating requisituion with two levels of approval from higher manager and so...Then it was going to recruiter for job posting and all. But after applying EHP4, we are not able to create requistion from manager. Even if we are creating requistion with all levels of approval, it is not going to recruiter for furtherance. Is there any specific business function need to actvate for MSS (Requisition can be created from manager)? Is there any specific role for MSS in EHP4? As mentioned by you, is it mandatory to activate business function HCM_MSS_ERC_CI_1?

Please note that we have activated below business functions:-

HCM_ERC_CI_1

HCM_ERC_CI_2

HCM_ERC_CI_3

HCM_ERC_SES_1

3. Recruiter is able to create external applicant from recruiter log on. But while searching, external candidates are not reflecting under search item? Are we missing something?

Thanks for all your help Roman. Waiting for your response.

Regards,

Purnima

[Former Member]

HI Roman / Purnima / Reddy,

Can any one please help me. I posted two thereds already bu tno reply pleae try to help my queston.

We are EHP3 - HCM_ERC_CI_1 now and we are planning to go for EHP4 and my understanding is after eHP4 it will update new buiness funciton HCM_ERC_CI_2 if I am worng please correct me.

I have seen on sap note which roman refered 1241014, it saying

1)When you activate the business function, the start pages for the recruiter and the administrator that are based on BSP are no longer supported and are superseded by the Enterprise Portal.

2)the current new IMG does not contain any settings for SAP E-Recruiting applications that are based on BSP technology. This IMG contains settings only for applications that are based on Web Dynpro ABAP.

3) When you activate the business function, the technology to display the user interfaces changes from Business Server Pages (BSP) to Web Dynpro ABAP. The previous BSP interfaces are no longer supported. This does not include the BSP interfaces for the candidate roles, which continue to be supported. All further UI developments are currently performed based on Web Dynpro ABAP only

Most of our development on BSP applications and few standard BSP application also enchanced alot standard applications.

My question is here If we go EHP4 still can we use HCM_ERC_CI_1? or HCM_ERC_CI_2 if it what will be the impact on BSP application as I mention we have everything on BSP apart from external candidate(webdynpro) and EHP3

Please help me to answer to my client.

Regards,

Kumar

[former_member31620]

Hi

Access the following to identify the functionality differences between EHP2 and EHP4

http://solutionbrowser.erp.sap.fmpmedia.com/

And, for test cases access T code SFW5 --> Business Functions, you have standard test cases created by SAP.

Hope this helps

Best Regards

Reddy

[Former Member]

Hi Reddy,

Thanks for your quick reply.

Can you please guide how to see test case details through Tcode SFW5? What business function set I need to select?

It would be graet if you can give step details to see test cases.

Regards,

Purnima

[former_member31620]

Hi

Unfortunately, I dont have SAP system access now.

In SFW5 T code --> eRecruitment specific Business Function (you can find them with the description) which is activated, against this business function on the Right corner you would have icons (document) put your cursor on those icons (Icon name would be Test Catalog).

If you are not able to find anything, I shall provide you exact steps later.

Best Regards

Reddy

[Former Member]

Hi Reddy,

Thanks again for all your help.

But sorry to say that I am not able to get exact place for test cases and I am not sure whether I am referring correct place or not.

I got 4 business function related to E-Recruitment. Find below all.

HCM, SAP E-Recruiting 1

HCM, SAP E-Recruiting 2

HCM, SAP E-Recruiting 3

HCM, MSS for SAP E-Recruiting

Since we had applied EHP4, business function name should be HCM, SAP E-Recruiting 4. Am I right or wrong?

Then which one I need to refer?

Regards,

Purnima

[former_member31620]

Hi

It is not necessary that EHP4 would have HCM, SAP E-Recruiting 4 as Business Function.

Dont you have document icon against these Busienss Functions? can you just try clicking on the buttons available against Business Functions? one of the buttons would take you to "Test Catalog" documents.

I have used these test documents against LSO Business Functions for LSO module after we upgraded to EHP4.

Best Regards

Reddy

[Former Member]

Thank you very much Reddy. I got EHp-4 under HCM, SAP E-Recruiting 2 & HCM, SAP E-Recruiting 3. Also got test catalog.

I will refer that.....

Have a nice day

[former_member31620]

Hi

You could also refer to following SDN thread, Roman has clearly explained the SAP support in EhP4.

Hope this is useful

Best Regards

Reddy

[romanweise]

Hello Purnima,

if you say E-recruiting EhP2 as the original system I suppose you were in an integrated system having the EhP2 for HR / ECC installed. E-Recruiting skipped the first 2 EhPs and joined the EhP cycle with EhP3. So your original E-recruiting release was 600 w/o EhP.

If you have installed EhP4 (and brought it to SP4, which is recommended) you should find the 4 business functions you mentioned. The HCM_ERC_CI_1 and HCM_ERC_SES_1 functions were delivered in EhP3 and brought some frontend addions (HCM_ERC_CI_1) like job agent and tell a friend and they brought the support for the SES TREX search interface (HCM_ERC_SES_1) which finally makes the old proprietary python extension obsolete. Business function HCM_ERC_CI_2 was the original delivery of EhP4. It contains the whole migration from BSP to WebDynpro for the whole recruiter and admin frontend. As a sideeffect it requires the business finction HCM_MSS_ERC_CI_1 which was optional in EhP3 but is now a must have as there is no standalone manager frontend anymore. HCM_ERC_CI_3 was originally part of EhP5 and downgraded to EhP4 due to strong demand of customers. It brings the most functions to the web dynpro ui which existed in BSP and were forgotten in the initial migration.