Convert Independent / Dependent Value Set to Translatable

Somteimes, the LOV's attached to your value set displays the code values instead of the meanings and this confuses users. One of the reason is that you have a Independent / Dependent Value Set when it should have been Translatable Independent / Dependent. This happens because the translatable value field on the flex field value window is disabled for non translatable type value sets and the translatable value field for all recors is set to same as the value field. This prevents users from entering the translatable value. In order to resolve this issue you can convert the independent / dependent value set to a translatable one, which would then allow you to edit the translatable value for the records. In order to do so run

1. $FND_TOP/sql/afffupg1.sql script
2. Select the option #8 'Convert an Independent/Dependent value set to a Translatable Independent/Dependent value set '.
3. Enter the name of the value set

Once the script has run you can go in and change the translatable values.

How to Define a Custom SSHR Menu Function

To include a new cutom SSHR menu option, use the following instructions.

1. Create the Custom Workflow as per the business process. Create a form function (copy a seeded ESS function) for ESS process. Make the following changes to the definition
a. Change parameter pProcessName so that it refers to the desire workflow process
b. Change parameter pCalledFrom so that it includes the internal name of the function being created
c. Change the value passed to OAFunc (HTML Call) to include the internal name of the function being created

2. Create a Form function for MSS based on any seeded MSS function. Change the value of the parameter pCalledFrom so that it refers to the internal name of the ESS function

3. Include the newly created ESS and MSS form functions in "Global Self Service Functions Custom" menu

4. Include the newly created ESS function in "Manager Actions Menu"

5. If the process is required in the ESS menu Include the newly created ESS form function in the Employee Self Service Menu

6. If the process is required in the MSS menu Include the newly created MSS form function in the Employee Self Service Menu

Please note that these steps are only relevant for SSHR. They may not work for other modules.

Understanding Self Service Menu Functions

In Self Service you define two menu function for accessing the same process from within ESS and MSS menus. The ESS function allows users to perform actions on the person assigned to the logged in user. Whereas the MSS equivalent of the function allows managers to perform actions on a people in their reporting hierarchy.

The ESS function includes information about the workflow, AME and other process related details. The workflow controls the sequence of screen available in the process and AME (if enabled) manages the Approval logic for the function.

The MSS function on itself only displays the Employee Hierarchy page. It needs to be associated to an ESS function, which controls the underlying process flow and approval management. It only includes a reference to the ESS function that controls the process.

All properties of the functions are controlled by the parameter values defined in the function definition. You can control the process by changing the value of any of the parameters. For e.g. if you want to change the underlying workflow for a process, simply change the value of parameter pProcessName in the ESS function definition to view the changes. Similarly, for a MSS function, changing the value of parameter pManagerEnabled to N would prevent manager to perform action on their own records. Every parameter has a specific role and its very intuitive to guess the utility of the parameter.

It took me a while to understand on how SSHR functions behave. These details should certainly help you to understand SSHR functions. I will later explain how you can define a custom process in SSHR and include it SSHR menus.