on 09-15-2008 6:57 AM
Hi all,
Can anyone clear my concept of vacancy infotype that it need to create infotype 1007 to create a vacancy. My point is that when we maintain org. structure and assign personal number to different position. If any position is not assign to any personal number it mean its vacant position. So why create infotype 1007 for vacancy?
Regarads,
Syed Tayab Shah
Hi Syed,
By declaring a position vacant through IT1007 we intimate recruitment module; if we are using; that we have to initiate the process of recruitment through advertisement and other things.
Award points if useful.
Regards,
Bhupesh Wankar
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Syed,
The above explaination must have cleared some of your doubts.
Some more inputs from my side are:
See PA30 deals with EE and PB30 deals with Applicant.
When we say position is vacant so we assign this infotype to a position not to any person thats why it does not reflect in PA or PB 30.
Regards,
Bhupesh
Hi,
You can also create IT1007 through PBAY.
All the Best.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Syed,
Following explanation will clear your doubts about Vacancy Infotype (1007)
Infotype with which you can identify positions that are currently vacant or will be vacant in the future, that is, they may be occupied again in the future.(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.
The indicator tells the system to treat all unoccupied positions as vacant. For further information see the Implementation Guide (IMG) under Organizational Management-> Infotype Settings-> Activate/Deactivate u201CVacancyu201D Infotype).
If your company distinguishes between occupied and unoccupied positions, you must maintain the Vacancyinfotype
You can mark vacancy records as historical records, once you no longer need them u2013 that is, once a position is filled. Historical records are maintained in the database, but cannot be changed or used in processing. If you use the Applicant Management component, it is helpful to keep a record of vacancies after they are filled.
The Vacancy infotype is important since the data it contains is used by more than one Human Resources component. For example, if you use Personnel Cost Planning, the system can take vacancies into account when it calculates cost projections. Vacancies are also registered in Career and Succession Planning, where, for example, they can be used when you conduct a search for suitable positions for an employee. If integration with the Personnel Administration component is active, the Applicant Management component also checks vacancy records. It is not mandatory to create the Vacancyinfotype for Organizational Management purposes. You should, however, create this infotype for positions if you want to install the following HR components: Personnel Cost Planning, Career and Succession Planning, or Applicant Administration.
If you implement the Personnel Management component, you can find more information in SAP Library under Human Resources---> Personnel Management -
> Compensation Management -
> Personnel Cost Planning.
thanks & regards
Pallavi
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
99 | |
11 | |
11 | |
6 | |
6 | |
4 | |
4 | |
3 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.