With Vacancy Infotype, 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.
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.
Self test questions:
1) A vacancy can be created in an Organization Unit by:
a. Making settings in customizing, to make all unoccupied positions to be made vacant.
b. Flagging a position as vacant by using the Vacancy Infotype.
c. Creating a vacancy for a position, which is either occupied or unoccupied.
d. By delimiting the object type Position
e. None of the above.
2) If Organization Management is having integration with the Recruitment component, then:
a. Vacancy needs to be maintained by making settings in customizing, to make all unoccupied positions to be made vacant
b. Vacancy needs to be maintained using Infotype 1007
c. Both (a) and (b) should be used.
d. Position has to be flagged as Obsolete.
e. None of the above.
Answers:
1) a, b, c
2) b
