Oracle Fusion Redwood allows automatic Person Number generation

Dhyan Patel Contributing Author

September 24, 2026 | 7 minute read

Oracle Fusion HCM provides standard functionality to automatically generate Person Numbers using a single enterprise-wide sequence. During one of our Oracle Fusion Redwood implementations, we came across a business requirement where each Business Unit needed its own Person Number sequence instead of sharing a common one.

Person Number Auto Generation based on Business Unit in Oracle Fusion HCM Redwood.

To address this requirement, we customized the Redwood hiring pages using Visual Builder Action Chains, JavaScript, and Oracle Fusion REST APIs. The solution automatically generates the next available Person Number based on the selected Business Unit and populates it during the hiring flow, while keeping the overall Redwood user experience unchanged.

In this blog, we’re sharing the approach and implementation that we used to solve this requirement in a real Oracle Fusion Redwood project.

Why was this Customization required?

The requirement did not come from a technical limitation—it came from a business customization requirement.

Oracle Fusion standard functionality can generate Person Numbers automatically, but it does not natively support maintaining multiple independent sequences based on Business Units in the Redwood hiring experience.

Business Requirement

Example Scenario

This allows each Business Unit to maintain its own numbering convention while users continue using the same Redwood pages.

Where does this customization work?

The same solution was implemented across multiple Redwood hiring flows.

The customization works on:

• Hire an Employee
• Add Pending Worker
• Add Contingent Worker
• Add Nonworker

The user experience remains identical across all pages.

Technology Stack

End-to-End Workflow

Step 1 – HR User Opens a Redwood Hiring Page

The HR user starts creating a worker using any supported Redwood page.

At this point, no Person Number is entered manually.

Step 2 – Business Unit Selection Triggers the Action Chain

The customization is event-driven.

Once the Business Unit is selected, the Visual Builder Action Chain executes automatically.

Responsibilities of the Action Chain:

• Capture Business Unit value.
• Invoke REST API.
• Wait for response.
• Pass response to JavaScript.

This makes the process completely automatic for HR users.

Step 3 – Fetch Existing Person Numbers

The customization calls Oracle Fusion REST APIs to retrieve workers belonging to the selected Business Unit.

APIs Used

The response contains existing Person Numbers that belong to the selected Business Unit.

Step 4 – JavaScript Generates the Next Sequence

The core logic is implemented using JavaScript inside the Redwood extension.

The logic performs the following operations:

1. Extract all Person Numbers.
2. Filter numbers for the selected Business Unit.
3. Identify the highest numeric value.
4. Increment by 1.
5. Attach Business Unit prefix (if configured).

Generation Logic

Filter

Keep only Person Numbers that belong to the selected Business Unit.

Find Maximum

Identify the highest existing sequence number.

Increment

Increase the value by one.

Apply Prefix

Append the Business Unit prefix when required.

Example Output

The prefix is completely configurable according to business requirements.

Step 5 – Person Number is Automatically Populated

The generated Person Number is written back into the Redwood page.

From the HR user's perspective:

• No manual typing.
• No lookup required.
• No duplicate checking required.

The field is populated before the worker is submitted.

Supporting Multiple Business Unit Sequences

This is the key difference between Oracle Fusion's standard functionality and this customization approach.

Business Rule Examples

Because the sequence logic is driven through JavaScript and REST responses, additional Business Units can be introduced without changing the overall Redwood user experience.

Duplicate Generation Handling

A common concern with auto-generated numbers is duplicate generation when multiple HR users create workers simultaneously.

The customization includes logic to handle duplicate generation scenarios.

How the customization Handles It

• Retrieves the latest available Person Number.
• Generates the next sequential value.
• Applies validation before populating the field.
• Prevents duplicate generation through implemented sequence logic.

This ensures that generated Person Numbers remain unique within the Business Unit sequence handled by the customization logic.

Validation Included

The goal is to avoid incomplete worker creation because of sequence generation failures.

Advantages of This Approach

This keeps the customization lightweight while extending Redwood functionality.

Frequently Asked Questions (FAQs)

Does Oracle Fusion already support automatic Person Number generation?

Yes. Oracle Fusion supports automatic Person Number generation through standard functionality. This customization addresses a customization requirement where businesses need multiple independent sequences based on Business Units.

Which Redwood pages support this customization?

The implementation works across Hire Employee, Add Pending Worker, Add Contingent Worker, and Add Nonworker Redwood pages.

What technologies were used?

The customization uses Oracle Fusion Redwood Page Extensions, Visual Builder Action Chains, JavaScript, and Oracle Fusion REST APIs.

How is the next Person Number calculated?

The customization fetches the highest existing Person Number for the selected Business Unit and generates the next sequential value by incrementing it.

Can prefixes be customized?

Yes. Business prefixes can be configured according to organizational requirements, such as Business Unit, country, or legal employer.

What happens if the REST API fails?

The customization performs validation and displays an appropriate error instead of populating an incorrect Person Number.

Final Thoughts

Oracle Fusion Redwood provides a modern hiring experience, but enterprise implementations often require business-specific behavior beyond standard functionality. This Auto Increment Person Number customization demonstrates how Redwood extensibility can introduce Business Unit-specific numbering without changing Oracle Fusion's core hiring process.

Using Visual Builder Action Chains, JavaScript, and Oracle Fusion REST APIs, the solution automatically generates the next available Person Number, applies Business Unit-specific prefixes when required, validates API responses, and populates the Redwood page before worker creation.

For organizations adopting Redwood HCM while maintaining custom HR numbering standards, this approach provides a scalable and reusable customization pattern across multiple worker creation flows.