E-Recruiting : Requisition status

Dear experts ,
Please throw some light on the following thoughts :
I can see that if the object NB has status draft,released,on hold or closed, i can assign candidates to the Requisition.
Is this the standard system behaviour? or have i missed something here.
Can someone explain the need/provision to assign candidates to a requisition when it is in status Draft, On Hold or Closed?
Thanks in advance,
Sowmya

Hello Sowmya,
I'll give you two answers please choose which you like.
The scientific process focused one
- it is necessary to assign applicants / candidates to requisition in status draft if you want to evaluate if a publication of the requisition is necessary or if you are confident to do the hiring based on your candidate pool only. In addition assignment must be able when you are redoing requisition and posting for better applicant address or changed requirements. This also requires status draft while the exisiting hiring process has to continue.
- it is necessary to add applicants to the requisition in status closed if you have already closed it as you thought you were finished but in the last moment the candidate does not show up. Espacially combined with mass hiring where a single requisition means many positions filled this can be a valid issue (often happens with apprentices). If you use the approval process it is often very handy to not set the status back to released as it would require new approval which makes no sense.
- adding candidates in status on hold is used to put spontaneous applicants to requisitions wich soon will be open (as far as the on hold is temporary) so you do not loose a suitable candidate int the depths of the candidate pool where it gets probably lost.
The unscientific but probably true one
- if you ever would have worked in hr you would have learned that no matter what is done for process design (which is often done by organization experts of hr the other hr guys do not like) recruiter will not give a s*** about the processes. They will do what they think it is right. Process designs do not care. But to be fair this is not only caused be the hr guys but by the field of work. You can define a process which requires 2 screenings and 4 tests for hiring and still the upper management shows up with a candidate and says "hire him!". So a real process flow control in a sense of the restriction of action posibilities will fail. So the reason for the status of requisition is not to say you can assign someone or not, it is more a guideline how far the process is and to filter them in the lists. You can assign a candidate whenever you want as not recruiter would accept a stronger restriction.
Best Regards and Happy E-Recruiting
Roman Weise

Similar Messages

  • Recruiting Requisition: Status Overview iview not refreshed

    Hi
    When new E-recruitment requisitions are created its not getting updated in the iview - Recruiting Requisition: Status Overview.
    Its getting updated after many hours only. Can anyone provide the solution for refreshing the iview with the latest requisition say within few minutes.
    Regards,
    Sasha.

    Hi
    Can anyone please provide an input on this.
    Regards
    Sasha.

  • Problem with Restricted Recruiter Requisition Status Change Approval Proces

    Hello,
    Our company is having a problem with Recruiters recieving any approval notifications for requisitions where the status change is performed by someone logged on as a Restricted Recruiter.  The approval notification never appears in the Recruiters approval page.  The Restricted Recruiter is able to submit the request without any problems.
    I was hoping that someone could help point me in the right direction so that I may begin troubleshooting this.
    Thanks for your assistance.
    Ryan

    I have been doing some digging on this matter on E-Recruiting workflow and have discovered transaction SWI2_FREQ (Work Items per Task), very useful.  Upon running this utility I found 8 pending approval request tasks.  I double clicked on the task to show the workflow status of each task.
    I double clicked on one of the request for status change tasks for a requisition which took me to the approval request for status change of Req ########.  Here I clicked on the activities tab selected the activities tab, selected the activity Approval request for status change of Requisition ######## then clicked on the execute icon.
    Doing this opened up a new web browser and prompted me to login.  Using the correct login credentials for this environment I click the login button and promptly recieve the error message...
    Error in Web service execution
    E:SWF_HTTP:050 TS51807979
    At this point I am unsure of where to go...
    Any help would be appreciated.
    Ryan

  • Requisition status - E-Recruitment

    Hi,
    When does the job requisition status changes to closed?Does it changes automatically once the person is hired or it should be closed manually?

    In standard this has to be maintained manually by the recruiter / recruiting team in charge of the requisition. It highly depends on the customer process if there is a chance of doing some customer development to add some automatical function there.

  • Requisition Status in e-Recruiting

    Dear Experts,
    In e-Rec (we are using BSP), a manager creates a requisition and then sends for approval to approve the status to a recruiter(support team). The approver releases the requisition. However, in one of our instances, manager goes back to the released requisition and changes the status to closed and again sends for approval.
    Now the approver cannot see the requisition in the 'Approval' link but is able to see it in the 'Maintenance' link. In the maintenance link, he cannot approve the latest status as it is disabled (locked).
    Now the question is how to unlock or delete such requisition which has the Requested status closed/on hold/withdrawn etc. Because neither the manager nor the recruiter/support team is able to edit or change the status.
    PS: A manager can set the status u2018to be deletedu2019 only if the requisition is in the u2018draftu2019 or u2018releasedu2019 status. But in this case, manager has put the released requisition status to u2018closedu2019 which is locked for any change.
    Request your inputs in this regard.
    Regards
    Sushma

    I understand that the Req Title is generated upon creation.  However, the user can still search for and select a Job or Position for the Requisition. 
    The order of the Org Data tab should be irrelevant.  I was hoping that someone had created a mechanism by which the Req Title could be updated as mentioned upon save of the Org Data tab in the container sequence.  In this scenario, the req title would change anytime the org data (job/position) was changed, which is logical given that req title corresponds to the job/position title (based on our naming convention).
    Thanks for the input.

  • Automatic refresh requisition status overview in MSS e-recruiting

    Hi guys,
    We are implementing e-recruiting 6.0 and de MSS functionality to request a requisition with approvals. The manager can see his/her requests in the requisition status overview to follow-up. If we create a new requisition, the list is only updated with this after you close the browser and log back in in the portal. Is there any way to activate the automatic refresh of this list?
    Thanks
    Karolien

    Nilesh,
    iam working on setting up E-rec in stand alone scenario.
    While we have been able to setup the workflow in MSS up to approval of Extended req. request, i could not see the recruiter getting the requisition to release and publish it.
    Can u pls, send some documentation you have to the below mail address
    raaj333 at rediffmail dot com
    Thanks
    G RAJ

  • FM for Purchase requisition status

    Hi,
      Is there any FM for Purchase requisition status.
    Do let me know.
    Regards,
    SP

    Hi,
    Check this FM, hope this will solve ur problem.
    'BAPI_ACC_PURCHASE_REQUI_CHEC'

  • Not updating status of Purchase requisition status

    Dear Friends,
    Our client has got third party software interface with SAP.We create Purchase requisitions in SAP,doc type-NB and PRs are also created in Third party software and it will create Purchase requisitions with starting with number ZR in SAP automatically.
    When PRs with NB type are created and RFQs are created with reference to PRs and POs with reference to RFQs,then status of RFQ and PO is displaying in Purchase requisition status tab at item details.
    But PRs created by Interface Purchase requisitions status under item details tab i.e.ZR is not updated with RFQ and PO status.
    For updating Purchase requisition status, is there any setting in customisation,the samething we need to do for PRs for Third party soft in SAP.
    Please suggest what needs to done
    Regards,
    Magana

    PR active signifies that all relase procedure is complete and the PR is being in use.
    Status field indicates whether the PR is in release, prartial release, complete release or whether PR is refused to release.
    Soon after complete release status gets chaged to active and if not subjected to release startegy, then soon after completing the creation of PR, status becomes active.

  • While TECO of PM order, purchase requisition status reverting to In release

    Dear Guru's,
    I want to know the relation between Maintenance order TECo(Technical completion) to Purchase requisition status. Bcoz while we do TECO, dependant PR's which was in Release completed status reverted baclk to In release. Plz help
    Guruprasad KS

    Hi
    In QS51-->selected set of UD >select the Code>Here remove the followup action -->QM_PM
    Save
    Regards
    Sujit

  • MSS Recruitment Requisition 'Internal error: null" message

    We are setting up the recruitment requisition functionality of MSS.  When the form loads (via the Form Tree) we just get the message "Internal error: null". 
    I have checked the back-end config and iView properties.  All of the required PAR files are loaded.  We have MSS 50.2 on EP5-SP6.
    I think the same message might come up with the PCR forms too.  I would really appreciate any tips as I'm pretty stuck here.  I couldn't find any relevant SAP notes. Thanks.
    Log:
    com.sapportals.portal.prt.component.PortalComponentException: Error in service call of Portal Component
    at com.sapportals.portal.prt.core.PortalRequestManager.handleRequestException(PortalRequestManager.java:688)
    at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:289)
    at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
    at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:231)
    at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:475)
    at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:285)
    at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
    at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:524)
    at com.sapportals.portal.prt.portalconnection.sapnative.DelegatedPlugIn.handleRequest(DelegatedPlugIn.java:715)
    at com.sapportals.portal.prt.portalconnection.sapnative.PortalPlugIn.handleRequest(PortalPlugIn.java:138)
    at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:648)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at com.inqmy.services.servlets_jsp.server.InvokerServlet.service(InvokerServlet.java:126)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at com.inqmy.services.servlets_jsp.server.RunServlet.runSerlvet(RunServlet.java:147)
    at com.inqmy.services.servlets_jsp.server.ServletsAndJspImpl.startServlet(ServletsAndJspImpl.java:789)
    at com.inqmy.services.httpserver.server.RequestAnalizer.checkFilename(RequestAnalizer.java:644)
    at com.inqmy.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:305)
    at com.inqmy.services.httpserver.server.Response.handle(Response.java:166)
    at com.inqmy.services.httpserver.server.HttpServerFrame.request(HttpServerFrame.java:1152)
    at com.inqmy.core.service.context.container.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:36)
    at com.inqmy.core.cluster.impl3.ParserRunner.run(ParserRunner.java:30)
    at com.inqmy.core.thread.impl0.ActionObject.run(ActionObject.java:46)
    at java.security.AccessController.doPrivileged(Native Method)
    at com.inqmy.core.thread.impl0.SingleThread.run(SingleThread.java:132)
    Caused by: java.lang.NullPointerException
    at com.sapportals.portal.pcdeditor.message.PCDEditorMessageHTML.isValidUrlParamString(PCDEditorMessageHTML.java:97)
    at com.sapportals.portal.pcdeditor.message.PCDEditorMessageHTML.createOnLoadJs(PCDEditorMessageHTML.java:54)
    at com.sapportals.portal.pcdeditor.message.PCDEditorMessageHTML.createEmptyMessage(PCDEditorMessageHTML.java:31)
    at com.sapportals.portal.pcdeditor.message.PCDEditorMessageMain.doContent(PCDEditorMessageMain.java:39)
    at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:127)
    at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:285)
    at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
    at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:231)
    at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:475)
    at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:285)
    at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
    at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:524)
    at com.sapportals.portal.prt.portalconnection.sapnative.DelegatedPlugIn.handleRequest(DelegatedPlugIn.java:715)
    at com.sapportals.portal.prt.portalconnection.sapnative.PortalPlugIn.handleRequest(PortalPlugIn.java:138)
    at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:648)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at com.inqmy.services.servlets_jsp.server.InvokerServlet.service(InvokerServlet.java:126)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at com.inqmy.services.servlets_jsp.server.RunServlet.runSerlvet(RunServlet.java:147)
    at com.inqmy.services.servlets_jsp.server.ServletsAndJspImpl.startServlet(ServletsAndJspImpl.java:789)
    at com.inqmy.services.httpserver.server.RequestAnalizer.checkFilename(RequestAnalizer.java:644)
    at com.inqmy.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:305)
    at com.inqmy.services.httpserver.server.Response.handle(Response.java:166)
    at com.inqmy.services.httpserver.server.HttpServerFrame.request(HttpServerFrame.java:1152)
    at com.inqmy.core.service.context.container.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:36)
    at com.inqmy.core.cluster.impl3.ParserRunner.run(ParserRunner.java:30)
    at com.inqmy.core.thread.impl0.ActionObject.run(ActionObject.java:46)
    at java.security.AccessController.doPrivileged(Native Method)
    at com.inqmy.core.thread.impl0.SingleThread.run(SingleThread.java:132)com.sapportals.portal.prt.core.PortalRequestManager@7a687b #

    Hello Mike,
    We already had this kind of situation.
    On the transaction QISRSCENARIO you need to select your scenario and generate the .PAR file again (they will be on C:     emp). Then unzip those files and search for the "default.properties" and there you will find a parameter "SystemIdentifier.value=" that need to be your System Álias on Portal. I don't know why, but when you generate the file this parameter it is filled with SAP_R3_Financials. After the change you need to upload the .par file.
    Good luck!
    Daniel Kiel

  • E-recruiting: Requisition management - Possible to change the field names??

    Hi to all e-recruiting experts,
    Need some assistance pertaining to the requisition management portion in e-recruiting.
    We have showed the standard SAP E-recruiting requisition bsp pages to our client and they have requested changes to the field names as they feel that the standard names are not intuitive enough.
    For instance,
    The field - "Hierarchy Level" - They have requested to change to "Job Grade"
    and the field "Functional Area"  to "Type of Work".
    Is there any way that i can change the name of the field through configurations?
    I understand that in a infotype, we can change the field name through translation. But can we change it in BSP? I was told to explore on how to configure via OTR.
    Can anyone share on the steps involved?
    Many thanks in advance.

    Well quite easy,
    create a context for an otr text (E-Recruiting are in package PAOC_RCF_UI). You will find that in SOTR_EDIT.
    Activate this context with implementing BADI BTFR_CONTEXT.
    After doing this, adjust context in SOTR_EDIT with Go To -> Context -> Adjust.
    Eventually refresh otr buffer with Transaction /$otr
    For one text there can be more than one OTR Text in backend, so you might change more than one.
    Regards

  • E Recruitment : Requisition - Position Validity issue

    Hi All,
    In Requisition creation, I am trying to assign a Position ID in Org Structure assignment Tab.
    When I search for position ID here, in the result of search list it also shows the positions whose status is NOT "vacancy open" as on today.
    If the position's status was "Vacancy Open" in the past, but not valid as on today's date, still that position shows in the search list. Which ideally it should not.
    Any clue will be appreciated.
    Thanks.
    Tejas

    Hello Tejas,
    it is standard behaviour of sap e-recruiting to allow the assignment any position, a vacancy is not required.
    When searching for positions there should be a checkbox to search for vacant positions only. This should reduce your result list.
    Best Regrads
    Roman

  • E-recruitment requisition workflow(WS 51800008)

    Hello All,
    We are facing issue in approval of requisition workflow(WS 51800008).The issue is as follows,
    When we forward the requisition to recruiter for approval,the workflow WS51900008,WS51900005 are triggered corresponding to events CREATED,Status Change,but no agent is assigned for both of them.So i suppose the approval  Workflow WS51800008 is not triggered
    Could someone pls explain me in detail as i m relatively new to e-recruitment.We have done all the necessary settings for the workflow and implemented the note
    Note 746709 but with no results.
    Thank you pls do advice.

    Hello Pavan,
    I m pasting the url which is generated which contains all the import parameters and after pressing the approve button there is a page that comes up saying "Request approved".but that url doesnt contain decision parameter.
    http://tcscq1.hrservicesonline.com:8001/sap(bD1lbiZjPTQ1MQ==)/bc/bsp/sap/hrrcf_approval/application.bsp?objid=50002412&otype=NB&plvar=01&requestdate=20090420&requestedRsnCode=12&requestedstatus=1&requester=Dave+Bankar&SAPWFCBURL=http%3a%2f%2ftcscq1%2ehrservicesonline%2ecom%3a8001%2fsap%2fbc%2fwebflow%2fwshandler%3f_sapwiid%3d000000006031%26_saptask%3dTS51807979%26_saplogsys%3dTD1CLNT451%26_sapuname%3dAARONMINYARD%26_saplangu%3dE%26_sapxid%3d976FEC491D6F880DE1000000AC11300B%26sap-client%3d451
    Url after clicking approve button.
    http://tcscq1.hrservicesonline.com:8001/sap(bD1lbiZjPTQ1MQ==)/bc/bsp/sap/hrrcf_approval/application.bsp?objid=50002412&otype=NB&plvar=01&requestdate=20090420&requestedRsnCode=12&requestedstatus=1&requester=Dave+Bankar&SAPWFCBURL=http%3a%2f%2ftcscq1%2ehrservicesonline%2ecom%3a8001%2fsap%2fbc%2fwebflow%2fwshandler%3f_sapwiid%3d000000006031%26_saptask%3dTS51807979%26_saplogsys%3dTD1CLNT451%26_sapuname%3dAARONMINYARD%26_saplangu%3dE%26_sapxid%3d976FEC491D6F880DE1000000AC11300B%26sap-client%3d451
    Both the url are almost same,atleast the return url should contain decision parameter but its not the case here.
    What can be the problem,have any one faced similar issue.
    And what are the events/workflow steps that occur after clicking approve button.i guess it should trigger
    status change workflow WS51900005 to change the status.
    In my case if i check in swel it jus says WEBSERVICE completed event been triggered.
    Pls do help stuck in this for very long now.
    Regards,
    Sharad

  • E-Recruitment - Requisition not visible in Recruiter Dashboard

    Hi,
    We have configured the E-Recruitment (HR_MSSRCF_REQUISITION) process and are using the standard workflow to route it to Manager.
    The steps we have followed is as follows;
    1. The requisition is created and sent it to Manager for approval.
    2. Manager is able to open and approve the requisition
    3. The Data is saved to the Database
    4. Support groups are defined (HRP5151) and releavant lead recruiter is assigned (HRP5131) but when check the dashboard of the lead recruiter, the requisition isn't available.
    Please let me know, if there are any additional steps to be performed.
    Thanks,
    Roopesh

    Hello,
    Which query have you used for checking as the requisition is usually in status 'draft'?
    Regards
    Nicole

  • E-Recruiting Requisition Process

    Hello Gurus,
    I am trying to configure the Requisition Process based on BSP.
    When I run the application on our Portal it creates a Obcect in HRP5125 and if I check the Trace log via SWEL I can see that the workflow WS51900008 and WS51900010 is running well. But WS90000004 is red. (?????)
    Does anyone know what WS90000004 is doing and for what this workflow is responsible?
    I expectet an email and an workitem for approvment in my business workplace. But I have nothing received.
    Does anyone know what I have to configure to receive the workitem from the requisition pocess?
    Many thanks!
    Marco

    Hello Marco,
    as the Id of the workflow WS90000004 indicates this is not a part of the standard delivery. It only exists in IDES systems. The red icon in t-code SWEL is no error. The workflow has a starting condition you can check e.g. in the header data of the workflow in t-code swdd. If an event is raised the workflow is linked to but the starting condition is not met the workflow is not started and the icon gets red. But this is for a reason. That way you can easily reduce instances of workflows started. E.g. e-recruiting knows the general workflow event "object status changed". If you have a workflow which only need to be processed if a requisition is set to status released you put it into the starting condition. That way the workflow won't be started every time an application or candidacy changes its status.
    Kind regards
    Roman

Maybe you are looking for