on ‎2012 Nov 16 7:18 PM
Hello All,
We are using front and backend concept for e-recruitment. We have front end on a sepearate system than backend. When a candidate registers (which is done on front end system), will the candidate be created in front end system and backend system or he is created only in backend system?
As per our current system functionality candidates are being created in the backend, even when registering from the front end, so when the candidate is trying to login to start page his user id and password is displayed as invalid. Did we miss a integration step?
Thank you in advance for your help.
Request clarification before answering.
Hello,
The user is created in both but just the data is stored in the backend. It is necessary to have all SICF settings correctly for the services (IMG -> Technical Settings -> User Interfaces -> Candidates -> Front-End Candidate -> Specify E-Recruiting services (Web-Dynpro)) and also the RECFA UI2BL/BL2UI system table parameters.
Regards
Nicole
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Nicole,
We activated exactly all services we have in our backend system, in the backend BL2UI has the front end system RFC connection name and UI2BL is blank, in the front end system UI2BL has the backend RFC name and BL2UI is blank. Is that accurate?
we dont see any SLG1 errors either...main issue is candidates are not being created in front end, they are being created only in the backend. Is there any error logs i can check?
Your time is much appreciated.
Hi,
Are these external or internal users? For external users, shouldn't they be using the alias of their user ID?
@Nicole, are there english versions of note 1779471 & 1777933?
Regards,
Richard
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Richard,
The notes are quite new and the translation process can take some time. It's about a change we have performed regarding dismissal and re-hiring actions which are performed for the future. Before you had to active periodic service PROCESS_CAND_STATUS_CHANGE which did it and now it is performed by report HRALXSYNC.
Furthermore, the WD system constellation 3 with RECFA SYEMP "X" only set at the WD backend system, is considered correctly now.
Regards
Nicole
| User | Count |
|---|---|
| 7 | |
| 3 | |
| 2 | |
| 2 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.