Creating a requisition using a position should be simple. But recruiters often need to manually check two important details:

• Who should be the Hiring Manager?
• Does the position have enough available headcount?

With Oracle Recruiting Cloud 26D, Oracle has introduced two useful enhancements to address these gaps directly within the Redwood requisition creation process.

Let’s understand how these features work using a simple business scenario.

A Simple Business Scenario

A Senior Finance Analyst position has an approved headcount of three. Two employees are already holding the position, which means only one vacancy is currently available.

The position reports to the Finance Manager position.

When a recruiter selects the Senior Finance Analyst position while creating a requisition, Oracle can now:

• Default the Finance Manager as the Hiring Manager
• Confirm whether the position has available headcount
• Validate the requested number of openings
• Display an error or warning if the requested openings exceed the available headcount

These two enhancements work together to make position-based recruitment more accurate.

What Is New in 26D?

Both enhancements are available as part of the Redwood requisition experience.

1. Default the Hiring Manager from the Position

Oracle Recruiting can now default the Hiring Manager based on the position selected by the recruiter.

Administrators can configure the Hiring Manager to be derived from:

• The manager associated with the selected position
• An incumbent of the parent position

The recruiter can still review and change the defaulted person before completing the requisition.

Available Configuration Options

Navigate to:

Setup and Maintenance > Manage Administrator Profile Values

Search for the following profile option:

Default Hiring Manager on Job Requisition

ORA_IRC_DEFAULT_HM_ON_JOB_REQ

The following values are available:

If multiple employees are holding the parent position, the recruiter can select the appropriate person.

How Does Oracle Decide the Hiring Manager?

Oracle follows a specific defaulting order:

1. Visual Builder Studio business rule
2. Position-based defaulting
3. Hiring Manager defined in the requisition template
4. Current user creating the requisition

For example, if a Visual Builder Studio business rule has already defaulted the Hiring Manager, the position-based profile option will not override it.

This is important for customers who already use business rules to control the Hiring Manager field.

Recruiter Experience

The recruiter can:

1. Select Create Requisition.
2. Choose Position in the How to start section.
3. Select the required position.
4. Navigate to the Hiring team section.
5. Review the defaulted Hiring Manager.
6. Update the person if required.

Points to Remember

• This defaulting applies only when the requisition is started using a position.
• It does not apply when starting from a job, requisition template, existing requisition or blank requisition.
• The recruiter can change the defaulted Hiring Manager.
• Visual Builder Studio business rules have a higher priority.
• Oracle also states that this enhancement applies when requesting a new position, requesting a position change, and updating, correcting or duplicating a position.

2. Validate Available Position Headcount

The second enhancement validates whether the selected position has sufficient available headcount.

Using our earlier example, the Senior Finance Analyst position has only one available headcount. If the recruiter tries to create a requisition with two openings, Oracle will identify the mismatch.

The validation is performed at two stages.

How to start

When the recruiter selects the position, Oracle checks whether the position has at least one available headcount.

This validation is performed regardless of the defaulted number of openings.

Basic info

When the recruiter enters or reviews the number of openings, Oracle compares it with the available position headcount.

For example:

• Available headcount: 1
• Requisition openings: 2

Oracle will display a warning or error based on the position configuration.

Warning or Error?

The result depends on whether overlap is allowed for the position.

This allows organisations to maintain strict position control while still supporting approved exceptions where overlap is permitted.

How to Enable Headcount Validation

Step 1: Enable Position Incumbent Validation

Navigate to:

Setup and Maintenance > Manage Enterprise HCM Information

In the Position Incumbent Validation section, enable:

Apply Incumbent Validation

Step 2: Enable the Recruiting Profile Option

Navigate to:

Setup and Maintenance > Manage Administrator Profile Values

Search for:

Apply Requisition Position Incumbent Validation

ORA_IRC_REQ_POS_INCUMBENT_VAL

Set the site-level value to:

Y

Step 3: Review the Future Days Profile Option

Oracle also provides the following optional profile option:

ORA_IRC_REQ_POS_HEADCOUNT_FUTURE_DAYS

This determines the number of days after the requisition creation date that Oracle uses as the effective date for retrieving position and assignment headcount.

The default value is 30 days.

For example, if the requisition is created on 1 October and the value is 30, Oracle uses 31 October as the effective date for evaluating the headcount.

Organisations should review this value based on their normal recruitment lead time and future-dated workforce transactions.

Important Redwood Consideration

This validation should be enabled only after confirming that the organisation uses the Redwood requisition experience.

Oracle recommends not enabling the profile option if recruiters are still using the Responsive UI. The validation is not handled in the Responsive UI, but it can still affect requisitions created through that experience.

What Should You Test?

Before enabling these features in production, test the following scenarios:

• Position with a position manager
• Parent position with one incumbent
• Parent position with multiple incumbents
• Position with sufficient available headcount
• Position without available headcount
• Openings exceeding the available headcount
• Position where overlap is allowed
• Position where overlap is not allowed
• Requisition with an existing Visual Builder Studio rule
• Future-dated position and assignment changes

Conclusion

These two Oracle Recruiting 26D enhancements address practical challenges in position-based recruitment.

The Hiring Manager can now be derived from the selected position, while position headcount validation ensures that the requested openings align with the available workforce structure.

For organisations using position-controlled recruitment, these changes can reduce manual checks, avoid incorrect Hiring Manager assignments and prevent requisitions from being created beyond the approved headcount.