External job search: error 'The publication period is over. You can no longer apply.'

[Former Member]

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,

[Former Member · Accepted solution]

Regarding the issue: 'The publication period is over. You can no longer apply.'

It seems we solved it.

The issue was on the RFC from e-Rec Front-end to e-Rec/SAP HCM back-end.

RFC was using a service user

I double checked the documentation on the SPRO and from the Front-end to the back-end is not mentioned specifically that a service user is needed for that RFC.

We removed the service user for this RFC and we set it to "Current user".

Regarding the issue on the User and Pwd fields

1. PROVIDE_UNAME_FIELD functionality is only activated if RECFA VERIF = 'X'
2. PROVIDE_UNAME_FIELD available values:
   • R (only registration screen): It refers to hrrcf_a_applwizard
   • A (only application start screen): it refers to hrrcf_a_candidate_registration
   • B (both screens): hrrcf_a_candidate_registration and hrrcf_a_applwizard
   • N (None of the screen)

So after setting the RECFA VERIF to 'X' and PROVIDE_UNAME_FIELD to B they are available on both screens.

From here I understand,

In case USER and PWD are available and provided then the user is "identified" by this alias.

How is identified the external user if the RECFA VERIF = blank? Is the alias the email?

Thank you very much for your support!

Kindest regards,

[NicoleGeischnek · Accepted solution]

Yes, you don't need a user for the RFC connection - just checking it as trusted relationship (which you did).

With RECFA just handles the email verification where an email is sent out to candidate to verify the email address. PROVIDE_UNAME_FIELD also shows you user and password input fields in the unregistered job search service. If you don't activate that, a random user and password is generated. (The idea of this service is that a candidate doesn't want to register but only apply to a job once).

[NicoleGeischnek]

Hi,

How do you start your test? You will only get the correct application wizard service if the system recognizes you as eg. external user.

That means no testing from SE80, SICF, cookie disabling and so on ....

Regards,

Nicole

[Former Member]

Hi Nicole,

Thank you very much for your quick reply.

Yes, the way testing is conducted considers your comment.

Actually we were able to debug it and we saw that the issue is with the change on the user as instead of picking the newly created user it is replacing the service user (RFC_UNREG) by the RFC user (RFC_SERVICE_1).

So when it gets into the HRRCF_MDL_JOBS_IS_PINST_VALID, it is the RFC_SERVICE_1 obviously dropping the error message.

Any other idea?

Are user/pwd fields expected to appear on application wizard?

Thank you very much in advance,

Kindest regards,

Xavier Rovira Rojas

[NicoleGeischnek]

Hi Xavier,

That shows that the SICF settings are wrong.

You see the settings in the IMG documentation of step:

SAP E-Recruiting -> Technical Settings -> User Interfaces -> Candidate -> Front-End Candidate -> Specify E-Recruiting Services (Web Dynpro ABAP)

For example:

hrrcf_a_applwizard has to be assigned with the service user and procedure "Standard" but others with nothing and others with "mandatory with logon data"

Regards,

Nicole

[Former Member]

Hi Nicole,

SICF services are set according to the documentation on the SPRO.

Also, according to SAP NOTE 2154222, services (hrrcf_a_reg_applwzd_unreg > Standard with no logon data; hrrcf_a_reg_applwizard_ext > Standard with no logon data) were set.

So, it seems by now we are on the right track but it is still not working.

Any other hint?

Thank you very much!!!

Your help is very much appreciatted!

Kindest regards,

[NicoleGeischnek]

Have you checked the service user having NO candidate object assigned?

[Former Member]

Hi Nicole!

Again, thank you very much for your replies.

On the same hand, how should I do so? (I am not a "User maintenance" expert )

I have checked relationships CP - US in order to see if any US is RFC_UNREG or RFC_SERVICE_1 and IT0105 in case they are linked to employees.

Searches provided NO results.

So, I understand Service User(s) is not having a NA object assigned.

Thank you very much!

Kindest regards,

[NicoleGeischnek]

Easiest way:

Go to transaction SE24 and execute class method CL_HRRCF_CANDIDATE => GET

Type in UNAME RCF_UNREG and if you get an error, no candidate object is there and everything is fine

[Former Member]

Hi again Nicole!

Unfortunately RCF_UNREG is not assigned to any candidate object, so everything should be fine with it.

Thank you very much!!!

Kindest regards,

[NicoleGeischnek]

You want to see user and password in the registration screen, correct?

For that make sure you have the parameter set:

EhP5 functionalities - ERP Human Capital Management - SCN Wiki  - Improvement of application process w/o previous registration

[Former Member]

Hi Nicole,

For this topic, again, I feel I am bringing bad news... everything is set as expected (and not working).

(I wanted to double check before replying)

Thank you very much for all your inputs!

Kindet regards,