25A Redwood New Hire Assignment number doesn't match person number - known bug

Summary:

We are on 25A on Redwood new hire pages.
We have around 30 employees for whom the person number is say 1234 but the assignment number is NOT E1234.

Instead Oracle is assigning random person numbers like E1236 or E1237.

Also, when you try to search for the person number of the incorrect assignment number, that person number is missed from the sequence. So the entire sequence is now messed up.

This will cause issues in conversion activities in future.

Client's expectation is that the person number and assignment numbers should be in sync.

Note - We have confirmed it with the HROs, and they are NOT manually updating and assignment number. This is happening automatically.