Enable Security for Value Sets

A value set is a group of valid values that you assign to a flexfield segment. When you enter a value for that flexfield segment, the value is validated against the value set.

Use the Manage Value Sets for Global Human Resources task in the Setup and Maintenance work area to manage value sets. This topic describes how to enable security for value sets so that they're available to specific users or processes only. It also summarizes how secured access to value sets is implemented.

Enable Security

When you create a value set where the Validation Type is Independent, Dependent, Subset, or Table, then you can enable security for that value set. When you're enabling security on table-validated value sets, the value set must be based on a single table or view. On the Create Value Set page, you:

  1. Select the Security enabled option. This selection enables data security policies to control user access to the values in the value set.

  2. Enter a name in the Data Security Resource Name field. This value identifies the value set that you want to secure. Typically, this value is the same as the Value Set Code.

    Tip:

    You need the Data Security Resource Name value later when securing access to the value set on the Security Console.

Define Data Security Policies to Secure Access to Value Sets

When security is enabled for a value set, you can create a data security policy for the data set. You grant the data security policy to a predefined duty role. The role that you use for this purpose is Custom Data Security Policies for Application Identities (ORA_HRC_APPLICATION_IDENTITY_CUSTOM_DSPS). These predefined APPIDs inherit this duty role:

  • FUSION_APPS_HCM_ESS_APPID

  • FUSION_APPS_HCM_ESS_LOADER_APPID

  • FUSION_APPS_HCM_SOA_APPID

  • FUSION_APPS_OBIA_BIEE_APPID

Note:

An APPID is a predefined user to which specific types of access, such as permission to run batch processes, is granted.

Processes that require access to secured value sets can then access those value sets. For example, access to value sets in the Cost Allocation Key Flexfield for payroll processes is secured in this way.