Requisitions for job postings are entered with a special status and are uniquely identified within an entity by a posting code. Requisitions may be very general or detailed and may be for a department, location, unit, group, job or position; however, they MUST be associated with a job profile.

Requisitions should state the required FTE, a suggested wage or salary range and the desired assignment start date. Only jobs and positions that are active ‘as of’ the assignment start date can be associated to the requisition, further, any associated positions must also be approved and not abolished to be valid.

When a requisition is created for a position, the FTE is checked to ensure that the position will not become overfilled. If the requested FTE plus the currently filled FTE exceeds the authorized FTE as of the assignment start date, a warning or error is issued in accordance with the position’s FTE override rule. FTE errors cause the requisition to be rejected.

If encumbrance accounting is being used, wages of approved postings will be encumbered instead of the position wages, for the portion of the FTE represented in the postings.

The addition, modification or removal of requisitions can trigger activities such as a notification to the budget owner that they are to authorize a pending requisition, with the requisition details attached.

The budget owners must approve requisitions before the recruiting activity can proceed. The module also allows you to implement multi-level approvals for requisition.

The approval of a requisition can trigger activities such as a notification to the manager to proceed with the recruitment activity. In addition, the rejection of a requisition can also trigger activities such as a notification to the manager to cease the recruitment activity.

Approved requisitions automatically become open postings.

Requisitions are entered as postings through the Maintain Postings (IRPO) screen.

---

Notes #

Click to create a new notes page