sap-wd-configId parameter

[MariaJo]

Dear experts, I need you help. .

Webdynpro app hrrcf_a_startpage_ext_cand has two app configurations in se80. In production system when a candidate register happens, the right one is chosen,but the wrong one in our test system. Do you know where this parameter is configurated? 

Thanks in advance and have a nice day!

[Ramprabhu_Sukum · Accepted solution]

Hello Maria,

Check whether you have implemented the BADI HRRCF00_DET_APPL_CONFIG_STARTP. This BADI is responsible for choosing the application configuration.

Regards,

Ram

E-Recruitment Development

SAP

[MariaJo · Accepted solution]

Many thanks!  I was lost...

I've checked it, and is ok:

method IF_EX_HRRCF_DET_APPL_CONFIG_SP~DETERMINE_APPL_CONFIG.

   IF IV_CANDIDATE_TYPE = 'E'.

     RV_CONFIG_ID = 'YHE_A_SP_EXT_REG'.

   endif.

endmethod.

but although I register as an external candidate the wrong configuration appears in url.

do you have any clue for me?

Thanks so much, I've really appreciate your answer.

Regards,

[NicoleGeischnek · Accepted solution]

Hi Maria,

Which configuration do you mean? The startpage after registrating?

This is parameter "candidateStartpage" in the HRRCF_C_REGISTER_UI component configuration.

Regards,

Nicole

[MariaJo · Accepted solution]

Hi Nicole,

I've checked in Development this parameter in HRRCF_C_REGISTER_UI but I can't in Production as service is not active.

The point is that in D when I test in se80 hrrcf_a_candidate_registration,it takes this value coming from parameter candidateStartpage (value YHE_A_SP_EXT).

In P a different one /value YHE_A_SP_EXT_REG).That value seems to come from badi HRRCF00_DET_APPL_CONFIG_STARTP

method IF_EX_HRRCF_DET_APPL_CONFIG_SP~DETERMINE_APPL_CONFIG.

   IF IV_CANDIDATE_TYPE = 'E'.

     RV_CONFIG_ID = 'YHE_A_SP_EXT_REG'.

   endif.

endmethod.

And they should be the same

We have done SP upgrade in development system and we will go to Production in a few days, so it's critical for us figuring out if it could be an issue due to upgrade.

Thanks so much for your help!

[NicoleGeischnek · Accepted solution]

Hi Maria,

What do you mean with "service is not active in Production"? Do you mean there is no custom component configuration for this component?

Regards,

Nicole

[MariaJo · Accepted solution]

sorry for the misunderstanding... service in SICF transaction was not active, but i've already activated.

THen I could check parameter candidateStartpage in component configuration in Production , and is the same as in D,  YHE_A_SP_EXT.

But when I register a new candidate, application configuration in  P is YHE_A_SP_EXT_REG in P.

So in P sap-wd-config-id is YHE_A_SP_EXT_REG:

/com/sap/bc/webdynpro/sap/hrrcf_a_startpage_ext_cand?sap-wd-configid=YHE_A_SP_EXT_REG

but in D sap-wd-config-id :

/com/sap/bc/webdynpro/sap/hrrcf_a_startpage_ext_cand?sap-wd-configid=YHE_A_SP_EXT

Regards,

Maria

[NicoleGeischnek · Accepted solution]

Do you use an application configuration of hrrcf_a_candidate_registration which refers to the HRRCF_C_REGISTER_UI component configuration where you set the candidateStartpage parameter?

[MariaJo · Accepted solution]

yes, exactly

[MariaJo]

Hi guys,

I think mistery is solved:  

Before SP upgrade 12 (Note 1865619 - Registration: 'candidateStartpage' is not considered)

sap-wd-configid value came  from badi HRRCF00_DET_APPL_CONFIG_STARTP , so this is the current behaviour now in our productive system. As we have implemented SP12 in development, now we get value from candidateStartpage parameter. You both were right!

Many thanks!