An override enables a user to customize field values and data in a code package . An override is different from a user hook, which enables users to write code and update both fields and HRMS database tables.

Within SSHR, you can use overrides in the following situations:

• To customize the fields used when loading data from Oracle HRMS tables to the Employee Directory repository tables to meet user and legislation requirements. For example, to enable single sign on for the Employee Directory you use an override to add the FND_USER field to the Employee Directory tables..

  For more information, see: Enabling Customer Overrides for the Employee Directory.

• To populate the Employee Directory with data.

  For more information, see: Legislation and Customer Overrides for the Employee Directory.

• To configure the read-only display of job and position fields in the following pages.

  • My Information and My Employee Information

    See: My Information and My Employee Information.

  • Person Header and Assignment Headers in all Manager Self-Service pages.

  • Selected Enter Process pages

    • People in Hierarchy page

      (supervisor hierarchy and position hierarchy)

    • My List page

    • Simple Search page

      Note: The overrides are not used in the Advanced Search page as the job and position fields are used for searching.

    • Person Detail page

  See: Examples of Overrides

To enable an override, you must carry out the following steps:

1. Open the required package. This package may be one of the following:

   • perwscor.pkb (for My Employee Information)

   • peredcor.pkb (for the Employee Directory)

   Note: The packages reside in the following directory:

   $PER_TOP/patch/115/sql directory

2. Modify the override flag in the package to enable the customer override. The override flag is similar to the following line of code:

   g_override_flg	BOOLEAN:=FALSE

   Change the BOOLEAN value to TRUE.

3. Insert your code for the override. For examples of code, see the documentation relevant to your function:

   • Customer Overrides for Single Sign On

   • Legislation and Customer Overrides for the Employee Directory

   • My Information and My Employee Information

4. Compile the override and apply to database.

   When the override packages are implemented, they are called by the application.

Examples of Overrides

Displaying Position or Job Names

You can use customer overrides to configure a user-defined format for displaying position or job names. For example, you can choose to replace the defined format for displaying a user's job with a user-defined name format consisting of fewer segments.

For example, instead of displaying a job as:

12345.Global Development.Development Manager.12B

you can display only the third segment (Development Manager).

To make this change, you need to modify the perwscor.pkb code package to include the following code:

FUNCTION getJobName(
		p_job_id		IN number,
		p_bg_id		IN number,
		p_value		IN varchar2//Actual MLS job name
)
return varchar2

To make a similar change to the position field, you need to modify the package to include the following code:

FUNCTION getPositionName(
		p_pos_id		IN number,
		p_bg_id		IN number,
		p_value		IN varchar2
)
return varchar2

You also need to change the job override and/or position override flag to TRUE in the package. In the following example, only the job override flag is set to TRUE.:

g_job_override_flg			BOOLEAN:=TRUE;
g_position_override_flg	BOOLEAN:=FALSE