Enabling Customer Overrides for the Employee Directory

You can use overrides with the Employee Directory to customize the fields available when you synchronize the data from Oracle HRMS tables with the Employee Directory repository tables. For example, to enable single sign on to self-service applications from the Employee Directory, you can perform a customer override to add your FND_USER names to the directory. This means that the Employee Directory repository tables are modified in line with the customer or legislation override.

Note: If legislation and customer overrides exist, customer overrides take precedence over legislation overrides.

All customer override package bodies are in the peredcor.pkb file, in the $PER_TOP/patch/115/sql directory.

For more information on overrides, see: Legislation and Customer Overrides.

arrow icon   Set up Customer Override for Single Sign On:

  1. Open the package body PER_EMPDIR_PEOPLE_OVERRIDE in a text tool.

  2. Modify the line

         g_override_flg BOOLEAN := FALSE;

    to

         g_override_flg BOOLEAN := TRUE;

    This change enables the override package.

  3. Add the following code into the before_dml procedure:

    IF p_srcSystem = 'PER' THEN 
       per_empdir_ss.personTbl.person_key(p_rec_locator) := 
                upper(per_empdir_ss.personTbl.attribute26(p_rec_locator)) 
                ||' '||per_empdir_ss.personTbl.person_key(p_rec_locator) 
                ||' '||substr(personTbl.work_telephone(p_rec_locator), 
                                    length(personTbl.work_telephone(p_rec_locator))-4, 4); 
       per_empdir_ss.personTbl.user_name(p_rec_locator) := 
                upper(per_empdir_ss.personTbl.attribute26(p_rec_locator)); 
    END IF;

    Instead of "attribute26", use the attribute name you used to configure the segment in the Additional Personal Details Descriptive flexfield.

    The preceding code assigns the user name to an available column in the repository. In addition it adds the user name to the person_key, which enables searches on the user name.

    It also formats the work telephone number and adds it to the person_key, enabling searches on a preferred telephone format. This is where you can determine how the telephone number is formatted for the simple search field.