E-Rec Front End and Back End

[Former Member]

Hi Friends,

We are implementing E-Rec in front end and back end model.

i.e., unregistered and external candidates would be using front end system to access and internal candidates and recruiter uses back end.

here, we were able to set up the system and proper communication happening (tested by RFC) and job search works in front end.

i.e., job publications created in back end does displayed when job search executed from front end.

But, candidates are not able to login when they are try to click on apply button. System throws error saying, unfortunately system not available at the moment. please try again later.

also, when candidate registers .. after the continue button... i see the same message. But the candidate gets registered and the user gets created in back end. Front end does not contain the user details.

When we exectute External Canddiate Start Page, and candidate when trying to login.. error message...

the client, user id or password is incorrect.

Please suggest.

Regards

Sadhu

[NicoleGeischnek · Accepted solution]

Hello Sadhu,

That looks like wrong SICF settings. Please check that in comparison to the given data in IMG step documentation: IMG -> Technical Settings -> User Interfaces -> Candidates -> Front-End Candidate -> Specify E-Recruiting services (Web-Dynpro)

Regards

Nicole

[Former Member · Accepted solution]

Hi Nicole,

So, external candidate data gets stored only in Back End and not in front end? When we try to login to front end, how does SAP checks the data from back end? Is it through WF-BATCH?

Can you please suggest any new config/roles required for WF-BATCH as of EhP6. I did maintain the role SAP_CAND_INT as reference user as that is what it was suggested in earlier versions.

Please suggest.

Regards

Sadhu

[NicoleGeischnek · Accepted solution]

Hello Sadhu,

Yes, the data is stored on the backend and is received by the frontend via RFC function module calls.

WF-BATCH was and is always adviced to have eg. the recruiter role assigned because it needs authorizations eg. for creating objects, changing status and so on.

Regards

Nicole

[Former Member · Accepted solution]

Ok, so what could be the reason the data is not read when trying to login from front end system.

everytime i give the candidate credentials, is says client/id or password does not exist.

but, using the same credentials, i am able to login to backend.

Please suggest.

Regards

Sadhu

[NicoleGeischnek · Accepted solution]

Hello Sadhu,

As first guess, I would say wrong SICF settings. Have you checked the services settings with the IMG step docu I mentioned above?

Regards

Nicole

[Former Member · Accepted solution]

Hi Nicole,

Yes, i did maintained as per the document. Also, i tried configuring CSL and without CSL but it does not work.

I would like to understand this concept .. when candidates login to front end system using data in back end system... how does security works? I assume that candidate data atleast the user details exist in front end system and once the candidate successfully logs in, the data overview like candidate profile and job applications should be picked up from back end system.

Regards

Sadhu

[Former Member · Accepted solution]

HI Nicole,

I just looked into this new note Note 1716811 - EREC: Front-end user
not updated when employee leaves. What i understand is, user details do exist in front end system too?1!

I am confused. Can you please throw some light on this. if yes, why is the users getting created only in back end and not on front end. which part of config will control this.

Regards

Sadhu

[NicoleGeischnek · Accepted solution]

Hello Sadhu,

The user objects itself are always created on both because otherwise the candidates could never log on to the frontend. Just the data stored for each candidate in the database tables is only done on the backend if you are using a distributed WD scenario.

Regards

Nicole

[Former Member · Accepted solution]

Hi Nicole,

There is an additional authorization object was required apart from standard sap role provided and this resolved the issue. User Data is getting updated in both the system and hence cnadidate able to login to Front End.