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.

Similar Messages

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

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.

Infotyp 1007 - doesn't change the vacancy status!!!

Hi,
I need to change vacancy status, but the 1007 infotyp doesn't work with success. I have used IDOC hrmd_A07 and it were filled the relashionships 1001 (A008 and B008) and 1007 (S status = 2). At the PP01 transaction the relashionships are Ok, but the Vacancy segment are not changed...
what happens????
Sandra

Hi people,
I have a solution to this problema:
It's only fill the structure as follows:
E1PLOGI P 00800000 U
E1PITYP
E1P0000
E1PITYP
E1P0001
E1PLOGI S 6000000 U
E1PITYP
E1P1001 A 008 S 6000000
E1PITYP
E1P1007 S 600000 2
Regards,

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

Updating infotype 1007

Hello experts,
I need to update the IT 1007 marking a position as Vacant.
Is this can be done using a Function Module? like the one that updates infotype in the PA30 (HR_INFOTYPE_OPERATION) ?
Thanks in advance for your help,
ArepaKing

Dear King,
Not much sure but kindly have a look at function module :-
RH_UPDATE_INFTY
Short Text
Change infotype records
Functionality
With this function module you can change multiple infotype records for OM objects from Personnel Planning database tables (HRPnnnn). The infotype tables of the table parameter INNNN must all have the structure Pnnnn (logical structure for the infotype nnnn). The records you want to change must exist in the Personnel Planning database tables. If not, this triggers the exception ERROR_DURING_UPDATE.
Might be other members can have some more better ideas as well.
Hope this helps.
Kindly reward in case useful.
Regards & Thanks,
Darshan Mulmule

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

Mass update vacany infotype 1007

is there any standard program for position
which looks for A 008 rel in hrp1001 and update hrp1007.
Thanks

Hi,
easiest way out would be to create a LSMW for mass update of this infotype.
Wilfred.
PS: Use transaction PP02 while recording the LSMW

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.

Data Communication between ERecruiting 3.0 standalone and R/3 4.7

Dear All,
We have the ERecruiting setup comprising of ERec 3.0 standalone with the backend HR system 4.7. We are using ALE to communicate between the two systems.
In ERec 3.0 we have the message type HRMD_ABA with basic type HRMD_ABA04 while on the R/3 side we have HRMD_A06 available. Our data transfer requirements are satisfied by HRMD_A06 but it is not available on the ERec server. Due to this we are not able to transfer certain infotype data required like IT1007,0023,0024 etc.
We managed to transport the basic type HRMD_A06 to the ERec server and tried sending the data across for Vacancy infotype 1007. It worked but the idoc went into error. On further investigation we found the table for IT1007 does not exist on ERec neither do the required functions to push the data into HRP1007. Is this becoz the PA component does not exist on the ERec 3.0? Is the PA component mandatory to be installed under such a landscape. We have only installed following components SAP_ABA-640,SAP_BASIS-640,SAP_BW-350 and ERECRUIT-300.
We are able to transfer the OM data and see the same on Requisition tabs but not the Vacancy information due to missing table for 1007.
How do we resolve this? Do we need to get the PA component installed or is there any other solution to transfer the data for IT1007,0022,0023.
Any suggestions and help will be appreciated.
Regards,
Chetan Mane

Closed

Issue Regarding Vaccancy OM

What 9is vacancy in OM? How to create vacancy in OM?
Edited the TEXT

div_os ,
Vacancy infotype 1007 helps to identify position vacancies present and also for future ones.
vacancy can be created for positions that are occupied and not occupied
business might sometimes not consider all the position not coccupied as vacant and to be filled.
there is setting in T77SO that can help maintain all uncoccupied positions as vacant .PPVAC PPVAC need to be checked.Entry 0 means all unoccupied positions are considered vacant. Entry 1 means infotype 1007 must be maintained.
PO13,PP01 tcodes as shared by our mates can be used to create position object.
Hope this helps
No Worries
KG
Edited by: SAPenjoy:) on Aug 20, 2010 6:16 AM

Issue while updating vacancy details through 'RH_UPDATE_DATABASE'

Hi,
i am trying to update the vacancy details through a Zprogram.
This zprogram updates the infotype 1007 correctly which is done by:
CALL FUNCTION 'RH_INSERT_INFTY'
    EXPORTING
      fcode               = 'INSE'
      vtask               = 'B'
    TABLES
      innnn               = lt_1007   " lt_1007 has all the values for updation.
After this i am calling the fm :
CALL FUNCTION 'RH_UPDATE_DATABASE'
      EXPORTING
        vtask     = 'S'
      EXCEPTIONS
        corr_exit = 1
This updates the infotype 1007 in the database but the vacancy table T750X is not updated.
However if i run the zprogram in foreground, this FM 'RH_UPDATE_DATABASE' updates infotype 1007 and also the table T750X. But in background mode only infotype 1007 is being updated and not T750X.
Please let me know if any idea on how to solve this.
Thanks.

any inputs on this if any one had the same issue using 'RH_UPDATE_DATABASE'.

E-Recruiting Vacancy Infotype 1007

Similar Messages

Maybe you are looking for