Dear masters,
We are having an issue with an e-Recruitment environment deployment regarding the External job Search and the applicant registration.
Our system landscape is defined by note 1017866 - Consulting note: Candidate scenarios using Web Dynpro ABAP as System constellation 2.
Our current issue is fully described on note 2154222 - External job search: error 'The publication period is over. You can no longer apply.'
My service settings are the following in e-Rec front-end:
hrrcf_a_reg_applwzd_unreg > Standard with no logon data
hrrcf_a_reg_applwizard_ext > Standard with no logon data
hrrcf_a_unreg_job_search > Required with logon data (pwd set for RFC_UNREG)
HRRCF_A_APPLWIZARD > Standard with logon data (pwd set for RFC_UNREG)
hrrcf_a_candidate_registration > Required with logon data (pwd set for RFC_UNREG)
At the same time, a trusted RFC exists between front-end and back-end (and also another trusted one from back-end to front-end). It is set on the front-end on RECFA UI2BL and HRRFC on T77S0.
This RFC is using another user RFC_SERVICE_1.
RFC_UNREG and RFC_SERVICE_1 are having the proper roles on the back-end and front-end environments.
From testing the service unreg_job_search and following the steps described on 215422:
TWO QUESTIONS:
1. When I click on button apply hrrcf_a_applwizard service is called and on this screen there is no place for defining the user linked to "your first visit to our page" (It is appearing if I click on Application Wizard and then on Register Here button) why are USER and PWD fields not appearing? (PROVIDE_UNAME_FIELD = R and RECFA VERIF is not set)

2. After filling information (considering question 1) and clicking on Register and Apply

Checking note 2154222, when function module HRRCF_MDL_JOBS_IS_PINST_VALID is reached, the user at this stage is the RFC_SERVICE_1 instead of the user provided by the applicant.
And it is obviously causing this error.
Does anybody know how to solve it?
Thank you very much in advance!
Kindest regards,