A user profile is a set of changeable options that affects the way your application runs. You can set user profiles at different levels. The levels below are used by the standard security hierarchy type:

• Site level: These settings apply to all users at an installation site.

• Application level: These settings apply to all users of any responsibility associated with the application.

• Responsibility level: These settings apply to all users currently signed on under the responsibility.

• User level: These settings apply to individual users, identified by their application usernames.

Values set at a higher level cascade as defaults to the lower levels. Values set at a lower level override any default from a higher level.

You use the System Profile Values window to set profile options at each level. If you change a user profile option value, your change takes effect as soon as your users log on again or change responsibilities.

Profile Options Summary

The following table lists the profile options available for Oracle Succession Planning and the levels at which the profile options can be set.

• SP: Maximum Plans for a Successor: Determines the maximum number of succession plans that can be created for a worker in an enterprise. As a profile option value, enter a numeral, for example, 3. In this example, only 3 succession plans can be created for a worker. When a manager tries to create the 4th plan, the application displays an error message. When counting the number of succession of plans that a worker can belong to, the application considers plans that are at the Active status only. If you leave the profile option blank, then any number of succession plans can be created for workers. As this profile option applies to all workers in an enterprise, system administrators can define the maximum number of plans for which workers can be identified as successors.

• SP: Show Terminated Worker Details: Controls search for terminated workers who are selected as probable successors or terminated workers for whom succession plans are created. This profile option and not the pEnableTerms function parameter governs the display of terminated worker records in the succession plan search. To enable managers to search for records of terminated workers, set the profile option value to Yes. If you leave the profile option value blank or set it to No, then managers cannot view records of terminated workers who are selected as probable successors or terminated workers for whom succession plans are created. The default value is No.

  If the profile option is set to Yes, then HR Professionals and managers can create succession plans to identify probable successors for terminated workers. You can identify probable successors for the terminated worker only if the termination date is later than the system date or equal to the system date. You cannot create succession plans for terminated workers if the termination date is earlier than the system date. For example, the system date is June 30, 2011 and the termination date of a worker is June 15, 2011. In this scenario, you cannot create a succession plan for the terminated worker.

• SP: Select Successors for Contingent Workers: Determines whether managers can create succession plans for contingent workers. Set the profile option value to Yes to create succession plans for contingent workers and identify potential successors for contingent workers. If you leave the profile option value blank or set it No, then managers cannot create succession plans for contingent workers. The default value is Yes.

• SP: Approval Required: Determines whether succession plans must go through the approval process. Set the profile option value to Yes to route succession plans through an approval process.

  Important: Create rules to route succession plans for approvals using Oracle Approvals Management (AME). The application does not automatically route succession plans for approvals if you just set the SP: Approval Required profile option to Yes. You must define AME rules. See: Setting up the Succession Planning Functionality

  The application uses supervisor hierarchy to route the plans for approval. Oracle Succession Planning provides a predefined workflow approval process for succession plan approvals. See: Succession Planning Approval Process

• SP: Use Talent Matrix: Allows plan administrators and talent managers to use the Talent Matrix tool. The Talent Matrix tool is not displayed in the application, by default. If required, system administrators must set this profile option value to Yes and then complete additional implementation steps to enable this tool. See: Enabling Talent Matrix.

  Oracle Succession Planning displays talent matrixes, which are built on Oracle Applications Development Framework (ADF). If you have implemented ADF and set the SP: Use Talent Matrix profile option to Yes, then the application displays talent matrixes. If you set this profile option to No, then the application provides an option to download or save PDF reports of talent matrixes instead of displaying them. For more information, see Using the Default Nine Box Matrix Templates to Assess Workforce.

  For implementation details, see: Implementing Default Nine Box Matrix Templates

• SP: Default Talent Matrix Template: Enables plan administrators to select a default Talent Matrix template in the View Talent Matrix page. When viewing the Talent Matrix, managers and plan administrators can select a template that is different from the default one.

For information on profile options in Oracle HRMS, see: User Profiles