Recruitment- Vacancy Infotype 4002

Hi All,
If we are uploading the OM data for Position, will this be reflected in Vancancy infotype too.
Is there any feature that we need to maintain for this.
Regards,
Chetan S. Wahane

You will need to load the data into IT1007 and ensure that Intergration for vacancies is activated.
PPVAC PPVAC should be set to 1. in table T77S0

Similar Messages

  • E-Recruiting Vacancy Infotype 1007

    Hello all,
    I am trying to figure out if the OM infotype 1007 (vacancy) can be used in E-Recruiting. We have a split instance model that will be interfaced either through PI or ALE.
    We would want to restrict managers to only be able to recruit for positions marked as Vacant in their org structure.
    Just to clarify, I am not an e-recruiting expert. I work on the HCM side and I am trying to understand how we could control vacancies.
    In passing, I took a look at a config note in E-recruiting Technical Settings: OM integration, the Export Class for infotype 1007 empty in the standard system. I don't know if this will be relevant during realization.
    Any help would be greatly appreciated.
    Thank you very much!
    Edited by: LaddyBuck on Oct 22, 2010 8:35 AM, clarification.

    Thanks for the the reply.
    My real concern is the fact that there doesn't seem to be any way to control vacancies.
    This would mean that a manager could recruit for ANY position in his Org. Unit.
    Would there be a way to limit managers to only be able to create Requisitions for positions that are marked as vacant?
    Again, thank you to everyone who has read my question.

  • Append records to infotype 4002

    I need to append records to infotype 4002,  I am using the HR_MAINTAIN_MASTERDATA fm and it is not updating.  I know you can't update records via PB40 but I'm doing this using abap.
    Any help/ suggestion on whic function module will be able to do this
    Thanx

    Let me rephrase my question:  I want to delimit a record to infotype 4002 'Vacancy Assignment'.  I am using the following code.
      CALL FUNCTION 'HR_MAINTAIN_MASTERDATA'
        EXPORTING
          pernr              = a_num
          actio              = 'INS'
          tclas              = 'B'
          begda              = it_4002-begda
          endda              = it_4002-endda
          dialog_mode        = '0'
        IMPORTING
          return1            = return1
          hr_return          = hr_return
        TABLES
          proposed_values    = it_pprop[].
    I can't use 'HR_INFOTYPE_OPERATION' FM as it works well for PA infotypes,  even if I set tclas to 'B' it gives a short dump.

  • Recruitment - vacancy

    Hi experts,
    I'm new with Recruitment. Can you tell me about the vacancy in Recruitment. Is it the same with vacant position in OM. Why I have many vacant positions in OM but in RC I cannot see them.
    Your input will be highly appriciate with marks
    Huynh Thanh

    A vacancy is a position that must be staffed, either completely or partially. Vacancies are maintained by a line manager or personnel officer.The personnel officer responsible manages data for the vacancy according to the authorization assigned to him by the personnel department. The line manager is responsible for deciding on the applicant's suitability for the vacancy.
    The procedure used depends on whether Recruitment is being used as a stand-alone system or in conjunction with Organizational Management.
    If you are using Recruitment as a stand-alone system (without Organizational Management), you must manually enter all data on a vacancy.If you are using Recruitment in conjunction with Organizational Management, the latter component contains a list of all the positions in a company. In this case, all you have to do is set a vacant flag in Organizational Management for any positions that need to be filled. All positions marked vacant in Organizational Management are then available in the Recruitment system for further processing and evaluation. Probably this is the reason why you can not see all your OM positions in recruitment.
    Any vacancies that you created in Organizational Management are marked with a P in the Maintained in OM field of the Vacancy view (V_T750X). You can edit these vacancies in Recruitment.
    Vacancy (Infotype 1007)
    You only create a Vacancy infotype for positions. You might create a vacancy record for an occupied position if, for example, you know an employee is taking maternity leave.
    You can create a Vacancy infotype record for a position that is occupied or unoccupied. If your company does not distinguish between occupied and unoccupied positions - that is, you consider all unoccupied positions to be vacant - you can set an indicator rather than maintain the Vacancy infotype.
    Hope this information helps and in case you need more information you can refer to http://help.sap.com.
    Regards

  • Vacancy Infotype in OM

    Hi Sap Gurus,
    Pls guide me that,while i am filling intial entry data of applicant,am unable to fill vacancy infotype..Then while tranfering applicant data it is transfering to Personnel Admin like (pba7)...
    Awaiting for your reply....
                                                      Regrads:
                                                       KUMAR

    Hi Hemanth,
    Let me know the warning or error message you are getting while updating Vacancy Assignment Infotype in PB30.
    Regards,
    Aman

  • Updating Vacancy infotype VIA RFC

    Hi All,
    I am trying to move employees from one position to another via RFC that I have written. The problem is that if the position has a VACANCY "open" then I get a pop up screen.
    If I manually make the position filled in infotype vacancy using the SAP GUI and then transfer the employee then it works fine.
    Is there a way to make the position filled in vacancy infotype via an RFC?
    Regards,
    ~Mark

    Why not use a similar logic and use Modify or Update instead of a select. Assuming you are talkin about ZTables here. Do not update standard tables directly.

  • E-Recruitment - Requisition - Infotype Field Level Change Log

    Hi Experts,
    We are implementing SAP E-Recruitment, and would like to know how to capture the changes made in Requisition at infotype field level.
    For example: If a support team member is added/delete in the Requisition (Tab - Support Team), then these changes (NEW/DELETE) at the infotype field level are required.
    I have tried to maintain the infotype and the required fields in V_T582A, V_T585A, V_T585B and V_T585C. But didnt get any result when I executed the report RPUAUD00. Is there any additional configuration required for this?
    Please adivse.
    Thanks and Regards,
    Dinakaran R

    Hi,
    You can just to that with the infotype table log. Support team is stored in table HRP5131.
    Regards,
    Nicole

  • E-Recruitment Vacancy Requisitions

    Hi,
    Is it possible to freeze all the Vacancy Requisitions raised in E-Recruitment with no activity, status to be that nothing should be done for the vacancy requisitions for certain period, later to release to do the activities
    Regards
    Ratan

    What you just said is true.
    Even if you hold the requisition the job posting and the publication are still released.
    You can also change teh status of the job posting to onhold and withdraw the publications also.
    When you want it to be released again then you can simply change the status of the requisition of job posting and requisition back to released but the publication will have to be created again as a withdrawn publication cannot be released again.
    For the specific requirement you are mentioning I dont see any other clear cut solution or option in standard E-rec.
    Regards
    Divya

  • T588M like table for customize e-recruitment application infotypes

    Hi
    I am looking for the customizing table or a proper way to hide unwanted infotype fields like nameconnection , 2.title etc. on the candidate application screen .  we are on ea-hr 606 same instance with sap hcm , integrated central person. For there is no application configuration FPM like ESS. How should we proceed? Best Regards. 

    Hey.
    The data is not stored in infotypes but that doesn't matter. You should use personalization to hide the fields. You can pass the parameter in the URL's you use on your company's jobsite, but you should also look at following badis:
    HRRCF00_DET_APPL_CONFIG_STARTP
    HRRCF00_DETERMINE_APPL_CONFIG

  • Error in Recruitment module

    Hi SAP Gurus:
    My query here is that in the recruitment module, while doing prepare to hiring action, we face an error calle MESSAGE_TYPE_X
    when we exit and do the action again, we do not get it.
    did debug it and found out the following reason:
    I had a look at your system and was able to simulate the problem you
    mentioned. The reason what I could find out is the following.
    In your configuration of the view V_T751E, for the action type
    '04'(Offer applicant contract) an infogroup 'W4' is attached. Through
    this infogroup 'W4', an insert(INS) is done to the infotype 4002
    (V_T588D). This configuration means that when we execute the action type'04', the infogroup 'W4' will also get executed which would bring up
    the screen 'Change Vacancy Assignment Status' using which we can change
    the status to '5'.
    Now, SAP provides a dynamic action in standard which would update the
    vacancy assignment status. Please see the calling of the form routine
    SUBMIT_RPAPUT00_WITH_APPLICANT in the view V_T588Z. Here in this form
    routine, we update the vacancy assignment status to 5, when we execute
    the action '04'. So the updation of the status is already done. After
    this only the infogroup 'W4' is processed which will try to update the
    status again to '5'. This leads to some buffering issue in the system
    and as a result of this it is trying to insert the same record again.
    Hence the update of the database fails and the system dumps. So
    basically the dynamic action in T588Z as well as the infogroup 'W4' are
    doing the same thing. Both are updating the vacancy assignment status.
    So I would suggest you to kindly use either one of these since
    ultimately both of them are doing the same action. So either you can
    remove the infogroup assignment to the action '04' in V_T751E or you cancomment out the calling of the form routine -
    SUBMIT_RPAPUT00_WITH_APPLICANT in the dynamic action which SAP provides
    in the standard.
    Even after correcting this, i am facing with the same problem.
    please advise,
    Ayyaps

    MASSN Determining the Fast Entry Dialog Module
      Object
        Feature
      Use
        Transaction
      Procedure
        You select an action for fast entry in the entry screen of transaction
        PA42.
        The return value of the feature is a dialog module taken from table DCT.

  • Recruitment Infogroups

    Dear Gurus,
    I am implementing recruitment modules and actions which I am going to configure is following
    Initial entry of basic data, Call for Interview/Test, Reject applicant, Put applicant on hold, Offer applicant contract, Applicant rejects contract And Prepare to Hire
    Infotypes which suggested using for recruitment are the following
    Applicant Action (4000),Applications(4001),Vacancy Assignment (4002), Applicant Activities (4003),Status of Applicant Activity (4004),Applicant Personnel Number (4005),Organization Assignment (0001),Personal Data (0002),Address (0006) and Education (0022).
    Anybody can suggest that any more infotypes I need to add as per standard and how I have group these infotypes as u201Cinfogroups u201Ccorresponding to each Applicant actions  like
    Initial entry of basic data     INS            0001     Organizational Assignment
         MOD            4001     Applications
         INS     0006            Addresses
    Thanks and Regards
    Carlos

    Following are the standard infotypes which are available in standard system support. For grouping, please have a look of table, VV_T588B_IAP____AL0,
    Infotype Infotype name
    0001 Organizational Assignment
    0002 Personal Data
    0006 Addresses
    0007 Planned Working Time
    0008 Basic Pay
    0009 Bank Details
    0014 Recur. Payments/Deds.
    0015 Additional Payments
    0016 Contract Elements
    0022 Education
    0023 Other/Previous Employers
    0024 Skills
    0028 Internal Medical Service
    0041 Date Specifications
    0042 Fiscal Data A
    0077 Additional Personal Data
    0105 Communication
    0107 Working Time
    0108 Personal Data B
    0109 Contract Elements
    0185 Personal IDs
    0190 Construction Pay: Previous ER
    0280 GB View for Contractual Elements
    0336 Suppl. it0002 (PT)
    0342 Personal Data HK
    0343 Contract Elements HK
    0395 External Org. assignment
    0396 Expatriate attributes
    0398 Contractual Elements BR
    0432 View: Type of Employment
    0433 GB View for Bank Details
    0465 Documents
    0480 Enhancement: Contracts Processing
    0488 Leave Scheme
    0493 Education (PS-SG)
    0502 Letter of appointment
    0539 Personal Data
    0623 Career History (Public Sector BE)
    0625  
    0633  
    0695  
    4000 Applicant Actions
    4001 Applications
    4002 Vacancy Assignment
    4003 Applicant Activities
    4004 Applicant Activity Status
    4005 Applicant's Personnel Number

  • Vacancy and Positions Query

    Hi All,
    I have a query related to the Vacancy to a position. Lets says, I have 100 employees attached to positions. If 10 employees resigned, then I will create a vacancy for all the 10 positions. After a month or so, if i hire 10 employees as a replacement, from where I can take all these vacant positions ?
    From end user's point of view, how to find the vacant positions out of many positions ?
    Regards
    Vijay

    There are two aspects involved here when it comes to the definition of a vacant position.
    1. A position for which the vacancy infotype (1007) is active
    2. A position which does not have a holder relationship currently
    As per standard SAP terminology, (1) above is the correct method to identify a vacant position. Standard reports found in the Easy Access menu (under HCM > OM > Info systems) would cater to this.
    However, you could also build an infoset on the PCH LDB and set out a query to fish out those positions which do not have a valid 008 relationship as of the date of the report (catering to aspect (2) above).
    Lastly, when reporting, please be mindful of the reporting period. It is always safest to choose TODAY or a KEY DATE, since if a range of dates is chosen and if a position is occupied for even one of the range of dates, there is a chance that the position will not show up as vacant in the report.

  • Any standard BI extractors for E-Recruiting job descriptions?

    The job description is a long text (at least 5k characters) on E-Recruiting system. We can use a function module to fetch the data. Now we want to extract the job descriptions to SAP BI. Is there any standard extractors to leverage?
    Thanks!

    Hi,
    Pls Check these URL for standard BC
    http://help.sap.com/saphelp_nw2004s/helpdata/en/2a/77eb3cad744026e10000000a11405a/frameset.htm
    http://help.sap.com/saphelp_nw2004s/helpdata/en/1f/1f9ac6d7b2274ea847992e1ede270f/frameset.htm
    > SAP E-Recruiting
    Various Infotypes in HR
    http://help.sap.com/saphelp_nw04/helpdata/en/26/313024636611d2b43b006094b9c9b4/frameset.htm
    Regards
    CSM Reddy

  • E-Recruitment- standalone scenario

    Hello Experts
    Can anyone tell me what are the pros and cons of using E-Recruitment as a standalone scenario without integrating with HR system at all?
    What are the difficulties we may face while configuring such a scenario ?
    Which E-Recruitment versions can be used for this?
    Please help..
    Regards
    Asha

    Hi Asha,
    If your scenario is not integrated (the ERP system and SAP E-Recruiting
    run on different systems):
    1    Employees from the connected HR system are imported into the
    E-Recruiting system using ALE distribution (Application Link Enabling).
    2    The administrator creates an internal user.
    If your scenario is integrated (the ERP system and SAP E-Recruiting run
    on the same system):
    The system uses the implementation CONV_HR_DATA_TO_EREC (Conversion of employees  HR data in SAP E-Recruiting) of the BAdI HRSYBC_P (Synchronize Employee by Business Partner) to create a candidate for each employee. In doing so, only the data from the following infotypes is transferred:
    1    0000 (Actions)
    2    0001 (Organizational Assignment)
    3    0002 (Personal Data)
    4    0006 (Addresses)
    5    0105 (Communication)
    6    1001 (Relationships) The relationship to the qualifications
    The system saves the person's personal data, capabilities, and wishes in infotypes that are assigned to the candidate.
    The recommended procedure for a standalone E-recruiting system is :
    - activate 2 BAdIs :
         HR_INB_PROCESS_IDOC
         The BAdI must be implemented for SAP E-Recruiting so that the data
         of the Person object (object type P) may be used exclusively
         in the E-Recruiting application.
         HRRCF00_DELETE_SPREL
         With the help of the method PROCESS_IDOC, all S-P relationships
         between positions and persons are deleted from the inbound IDocs.
         The Central Person (object type CP) is assigned to the position
         instead of the Person (object type P).
    - The PA-Infotype data will be stored in E-Recruiting specific infotypes
      and not in PA-infotypes, but Object P needs to have at least some
      PA Infotypes (0000, 0001, 0002, 0006). But with the activated BAdi
      implemenation these data are not getting stored in PA infotype with
      the ALE message type HRMD_ABA.
      These data will be stored in central person in table HRP51XX
    - Please make sure that you have set up E-Recruiting w/o all of the
      ERP-components, i.e. install a basis system and on top of it
      E-Recruiting only.
    If the relationship CP-S is missing in your system I will need to have
    a remote connection on both system (HR and E-recruiting) with
    corresponsing logon details into the secure logon area. I will also
    need some variant for report RHALEINI and idoc number in ER system.
    Hope this help
    Sarah

  • Mass - Vacancy Creation

    Hi Experts,
    any one support me to finish the task.
    //sri

    Sri,
    You can use report RHCOPY00 (Copy Objects). Creating objects by copying existing object can save your data entry time.
    When you copy objects, you can also copy all appended infotypes. Pls check if you are able to perform Mass creation of 1005 - Vacancy Infotype through this report.
    Reference: http://help.sap.com/saphelp_47x200/helpdata/en/bb/bdb482575911d189240000e8323d3a/frameset.htm
    Regards,
    Gana

Maybe you are looking for