Prior to Autogen of Person Number, EEs Did Not Get Multiple Ben Relationship Rows Created (Doc ID 1537859.1)

Last updated on AUGUST 20, 2015

Applies to:

Oracle Fusion Benefits - Version and later
Oracle Fusion Benefits Cloud Service - Version and later
Information in this document applies to any platform.


This is a question of whether 2 rows are generated for Benefits Relationship when auto generation of Person Numbers is "on" when a new employee is hired vs when a hire is done and the Person Number is included during data entry.

First scenario is of an employee who client had to manually enter/hire when they got their environment.  Person Numbers had already been assigned to employees so when they had to manually enter them in the new environment, they had to use the same Person Number. These individuals only got one Benefit Relationship row.

The second scenario is an employee who was hired after the auto generation of Person Numbers was turned back on and this person automatically received two Ben Relationship rows -- which is the desired result. Customer can (and are) updating employee records with the missing unrestricted Ben Relationship row, but customer wants to know if this is a feature of auto generation of Person Numbers. Customer is trying to ensure they don't have additional employees in the future who do not get both the DFLT and UNRST rows. This was found when trying to convert (via FBL) 401k election rows which are in an unrestricted plan and they discovered that the majority of employees were missing the UNRST row. This seems to be because of the manual hire process they had to do.

Question is why some employees did not have two rows for Ben Relationship auto generated.


Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms