4Profile Options, Lookups, and Scheduled Processes

This chapter contains the following:

Profile options, lookup types, and scheduled processes let you configure application behavior and process data.

Briefly, here's what profile options, lookup types, and scheduled processes do:

  • Profile options: Let you configure the application behavior.

  • Lookup types: Provide the lists of values in applications. Many lookup types can be modified to fit your business needs.

  • Scheduled processes: Act on data in the applications.

Get additional information on profile options, lookup types, and scheduled processes in this chapter and in the related topics.

Profile Options

Profile options let you configure and control application data centrally. Administrators and setup users manage profile options in the Setup and Maintenance work area.

Profile options store various kinds of information. This table lists some examples:

Type of Information Profile Option Setting Example

User preferences

Set preferences at the user level

Installation information

Identify the location of a portal

Configuration choices

Change UI skins and actions

Processing options

Determine how much information to log

Profile Option Hierarchy Levels

Profile options can be set at different levels, such as site level or user level. The application gives precedence to certain levels over others, when multiple levels are set. The levels that are allowed to be set are preconfigured with the application.

In the predefined profile option levels, the hierarchy levels and their precedence are:

  1. User: This level affects only the current user. It has the highest precedence, over Site and Product.

  2. Product: This level affects a product or product family. The application gives it priority over Site level. However, if the user level is set, the user level takes precedence.

  3. Site: This level affects all applications for a given implementation. The application gives it the lowest precedence when other levels are set. If no other levels are set, however, it's the highest level.

As a best practice, set site-level profile option values before specifying values at any other level (where available). The profile option values specified at the site-level work as the default until profile option values are specified at the other levels.

This table shows an example of the predefined profile option hierarchy levels and their priorities.

Level Priority Example

Site

Lowest

Currency for a site is set to Euros.

Product

Supersedes Site

Currency for the product or set of products is set to UK pound sterling.

User

Highest, supersedes Product

Currency for a user is set to US dollars.

You can find additional information about profile options in the related topics.

How can I access predefined profile options?

Search for predefined profile options using the Manage Profile Options task.

  1. In the Setup and Maintenance work area, go to the Manage Profile Options task.

  2. On the page, enter any of the search parameters and click Search.

    Tip: If you don't know the profile option code or the display name, use the Application or Module fields to filter search results.
  3. Click a profile option to view its details.

Import Profile Values

Use the Import option on the Manage Administrator Profile Values page to import profile values in bulk and associate them with a profile option.

Importing Profile Values

Before you begin, make sure that the file containing the profile values is available in the document repository of Oracle WebCenter Content.

  1. In the Setup and Maintenance work area, go to the Manage Administrator Profile Values task.

  2. In the Search: Profile Options section, search for the profile option for which you want to import the values.

  3. In the Search Results: Profile Options section, select the profile option.

  4. In the <Profile Option>: Profile Values section, click Actions > Import.

  5. On the Import User Profile Values window, select the WebCenter Content account to which the file was uploaded.

  6. Enter the name of the file containing the profile values. The name here must match with the name of the file uploaded to the selected account.

  7. Click Upload. The profile values are imported.

    Note: If the import fails, click the link to the log file on the confirmation dialog box and examine the cause of failure.

To import profile option values into the application, you create a text file with the values and upload the file to the Oracle WebCenter Content document repository. The file must follow a specific format, as described here. After the file is in the document repository, you can then import the profile values into the application following the instructions in the Importing Profile Option Values: Procedure topic.

To create a file containing the profile values, include the following headers:

  • ProfileOptionCode: The profile option code.

  • LevelName: Must contain the value (Site, Product, or User).

  • UserName: Must correspond to the registered user name in the application. Don't provide any other shortened or coded name of the user.

  • ProfileOptionValue: The profile value to be imported.

While creating the file, adhere to the following guidelines:

  • Use a vertical bar or pipe ( | ) as a delimiter between fields for both header and value rows.

  • Set the file encoding to UTF-8 without the Byte Order Mark (BOM), as per the Oracle WebCenter Content specification.

Here's a sample file that contains the header values at the beginning of the file, followed by line entries of the two profile values that are to be imported. For importing several profile values, add more line entries in a similar format.

ProfileOptionCode|LevelName|UserName|ProfileOptionValue
AFLOG_BUFFER_MODE|USER|APP_IMPL_CONSULTANT|TEST
AFLOG_LEVEL|USER|APPLICATION_DEVELOPER|FINEST

Lookup Types

Overview of Lookup Types

Lookup types in the applications provide the lists of values in application fields that are drop-down lists. For example, when closing an opportunity, salespeople can pick a reason that an opportunity was won or lost from the Win/Loss Reason field, which is a drop-down list. The values in that list are derived from the lookup type, MOO_WIN_LOSS_REASON, which has several potential values known as lookups, each with its own unique lookup code and a meaning that displays in the UI.

Configuring Lookup Types

You can configure many lookup types to fit your business needs. The level at which a lookup type is extensible determines whether the lookups in that lookup type can be edited. The levels are: User, Extensible, and System.

The following table shows which lookup management tasks are allowed at each level.

Allowed Task User Extensible System

Deleting a lookup type

Yes

No

No

Inserting new codes

Yes

Yes

No

Changing the wording that displays on the page (Meaning field)

Yes

Yes

Yes

Updating start date, end date, and enabled fields

Yes

Yes, only if the code isn't predefined data

No

Deleting codes

Yes

Yes, only if the code isn't predefined data

No

Updating tags

Yes

No

No

Updating module

Yes

No

No

If a product depends on a lookup type, the configuration level must be System or Extensible to prevent deletion. After the configuration level is set for a lookup type, it can't be modified. The configuration level for lookup types created using the Define Lookups page is by default set at User level.

Sales Lookup Types

You find lookup types by accessing the associated task in the Sales offering in the Setup and Maintenance work area. Here are some of the common sales lookup tasks or task lists:

To access sales lookup types:

  1. Sign in as a setup user and navigate to the Setup and Maintenance work area.

  2. In Setup and Maintenance, go to the Sales offering.:

  3. In the list of functional areas, click the area where the lookup appears. See the list at the end of this procedure for more information.

    A list of tasks for the area is displayed.

  4. In the list of tasks, click the lookups task.

  5. In the lookup types page, modify the lookup type as needed.

The following are the Sales lookup type tasks and the functional areas where they appear:

  • Sales Foundation functional area:

    • Manage Geography Lookups

    • Manage Applications Core Standard Lookups

    • Manage Activity Standard Lookups

  • Users and Security functional area:

    • Manage Resource Role Lookups

    • Manage Resource Lookups

  • Accounts and Contracts functional area

    • Manage Group Lookups

    • Manage Source System Lookups

    • Manage Hierarchy Lookups

    • Manage Trading Community Common Lookups

    • Manage Party Usage Lookups

    • Manage Relationship Lookups

    • Manage Contact Point Lookups

    • Manage Trading Community Organization Lookups

    • Manage Trading Community Location Lookups

    • Manage Trading Community Person Lookups

    • Manage Contact Lookups

    • Manage Customer Account Lookups

    • Manage Customer Center Lookups

  • Sales Catalog and Products functional area:

    • Manage Product Group Lookups

  • Sales Campaigns functional area:

    • Manage Marketing Standard Lookups

  • Leads functional area:

    • Manage Sales Lead Standard Lookups

    • Manage Set Enabled Lookups

  • Opportunities functional area:

    • Manage Set Enabled Lookups

  • Territories functional area:

    • Manage Territory Management Non-extensible Lookups

  • Business Plans functional area:

    • Manage Business Plan Non-extensible Lookups

    • Manage Objectives Non-extensible Lookups

  • Partners functional area:

    • Manage Partner Lookups

Set-Enabled Lookup Types

Several applications support lookup types at the reference set level, allowing you to present different lists of values for different business units. You can find these in the Manage Set Enabled Lookups task within the functional area that supports these lookup types.

How can I access predefined lookups?

Search for predefined lookups using any of the manage lookups tasks.

  1. In the Setup and Maintenance work area, go to any of the following tasks that contains the lookups you're looking for:

    • Manage Standard Lookups

    • Manage Common Lookups

    • Manage Set-enabled Lookups

  2. Enter any of the search parameters and click Search. If you don't know the lookup type or the meaning, use the Module field to filter search results.

  3. Click a lookup type to view its lookup codes.

    Tip: Click the Query By Example icon to filter the lookup codes.

On any of the Manage Lookups pages, you can edit the existing lookup codes of a lookup type or add new lookup codes. You can edit lookups using the following tasks in the Setup and Maintenance work area:

  • Manage Standard Lookups

  • Manage Common Lookups

  • Manage Set-enabled Lookups

Each task contains a predefined set of lookup types that are classified and stored. Open a task to search and edit the required lookup. However, you may not be able to edit a lookup if its configuration level doesn't support editing.

Lookup types are classified using tasks that involve a group of related lookups, such as Manage Geography Lookups. Each task gives you access only to certain lookup types. However, the generic tasks provide access to all lookups types of a kind, such as common lookups associated with the Manage Common Lookups task.

If the lookup types in an application are available in the standard, common, or set-enabled lookups view, they're are central to an application. However, lookup types defined for a specific application are managed using the task for that application.

Import Lookups

On each page pertaining to the tasks of managing the Standard, Common, and Set Enabled lookups, use the Import option to import the lookup type and lookup code information.

Prerequisite

The separate files containing the lookup types and lookup codes are already available in the document repository of Oracle WebCenter Content.

Importing Lookups

To import lookups:

  1. In the Setup and Maintenance work area, go to the Manage Standard Lookups task. Depending on the lookup you want to import, you may select the other lookup tasks.

  2. In Search Results, from the Actions menu, select Import.

    The Import Lookups dialog box appears.

  3. Select the WebCenter Content account to which the files were uploaded.

  4. Enter the names of the separate files containing the lookup type and lookup code information. The names here must match with the names of the files uploaded to the selected account.

  5. Click Upload. The lookup details are imported.

    Note: If the import fails, click the link to the log file on the confirmation dialog box and examine the cause of failure.

File Format for Importing Lookups

To import lookups into an application, you create separate text files containing the lookup types and lookup codes and upload them to the Oracle WebCenter Content document repository. The files must follow a specific format, as described here. After the files are in the document repository, you can then import the lookup types and lookup codes into the application following the instructions in the Importing Lookups: Procedure topic.

While creating the file, adhere to the following guidelines:

  • Use a vertical bar or pipe ( | ) as a delimiter between fields for both header and value rows.

  • Set the file encoding to UTF-8 without the Byte Order Mark (BOM), as per the Oracle WebCenter Content specification.

The following sections contain details about the specific lookup types and codes.

Prerequisite

You must have worked with lookups in Oracle Cloud applications.

Standard and Common Lookups

The lookup types and codes are similar for standard and common lookups. To create a file containing the lookup types, include the following headers:

  • LookupType: The lookup type.

  • Meaning: The display name of the lookup type.

  • Description: The description of the lookup type. This header is optional.

  • ModuleType: The module with which the lookup type is associated.

  • ModuleKey: The module code.

Here's a sample file that contains the header values at the beginning of the file, followed by line entries of the two lookup types that are to be imported. For importing several lookup types, add more line entries in a similar format.

LookupType|Meaning|Description|ModuleType|ModuleKey
AFLOG_22APR_1|Log1|AFLOG_desc_1|APPLICATION|FND
PROD_22APR_2|Product1|PROD_desc_2|APPLICATION|FND

To create a file containing the lookup codes, include the following headers.

  • Required headers:

    • LookupType: The lookup type.

    • LookupCode: The lookup code associated with the lookup type.

    • DisplaySequence: The sequence position at which the lookup code appears in the list of values.

    • EnabledFlag: Indicates the status of the lookup code, whether it's enabled for display or not.

    • Meaning: The display name of the lookup code.

  • Optional headers:

    • StartDateActive: Beginning of the date range during which the lookup code is active and visible on the page. The format is dd/M/yyyy.

    • EndDateActive: End of the date range during which the lookup code is active and visible on the page. The format is dd/M/yyyy.

    • Description: Description of the lookup code.

    • Tag: Any tag associated with the lookup code that may be used for a quick reference or retrieval of information.

    • Seg: The name of the API used for a global segment defined for the descriptive flexfield associated with the lookup.

    • CONTEXT_ATTRIBUTE: The context value specified in the CSV file for a particular descriptive flexfield.

    • ctxSeg: The name of the API for a context sensitive segment defined for a context attribute.

Here's a sample file that contains two lookup codes:

LookupType|LookupCode|DisplaySequence|EnabledFlag|StartDateActive|EndDateActive|Meaning|Description|Tag|Seg|CONTEXT_ATTRIBUTE|ctxSeg
TASK_22APR_1|Code1_1|1|Y|25/12/2014|25/5/2015|TASK_22apr_1|Task_desc_1|Tag1_1|testSeg1|TEST_CTX1|ctx1Seg1
TASK_22APR_1|Code1_2|2|N|25/1/2014|25/11/2015|TASK_22apr_2|Task_desc_2|Tag1_2|testSeg1TEST_CTX1|ctx1Seg1
TASK_22APR_2|code2_1|3|N|25/12/2012|25/7/2015|TASK_22qpr_2_1|Task_desc_2|tag2_1|testSeg2|TEST_CTX2|ctx2Seg2
TASK_22APR_2|code2_2|3|Y|25/12/2012|25/7/2015|TASK_22qpr_2_2|Task_desc_2_2|tag2_2|testSeg2|TEST_CTX2|ctx2Seg2

Set Enabled Lookups

To create a file containing the set enabled lookup types, include the following headers:

  • LookupType: The lookup type.

  • Meaning: The display name of the lookup type.

  • Description: The description of the lookup type. This header is optional.

  • ModuleType: The module with which the lookup type is associated.

  • ModuleKey: The module code.

  • ReferenceGroupName: Name of the reference group that contains the reference data set.

Here's a sample that contains two set enabled lookup types:

LookupType|Meaning|Description|ModuleType|ModuleKey|ReferenceGroupName
CODE_22APR_1|CODE_22apr_1|Code_desc_1|APPLICATION|FND|BU_APAC
CODE_22APR_2|CODE_22qpr_2|Code_desc_2|APPLICATION|FND|BU_APAC

To create a file containing the set enabled lookup codes, include the following headers.

  • Required headers:

    • LookupType: The lookup type.

    • LookupCode: The lookup code associated with the lookup type.

    • DisplaySequence: The sequence position at which the lookup code appears in the list of values.

    • EnabledFlag: Indicates the status of the lookup code, whether it's enabled for display or not.

    • Meaning: The display name of the lookup code.

    • SetName: Name of the reference data set.

  • Optional headers:

    • StartDateActive: Beginning of the date range during which the lookup code is active and visible on the page. The format is dd/M/yyyy.

    • EndDateActive: End of the date range during which the lookup code is active and visible on the page. The format is dd/M/yyyy.

    • Description: Description of the lookup code.

    • Tag: Any tag associated with the lookup code that may be used for a quick reference or retrieval of information.

Here's a sample file that contains the header values at the beginning and lists four set enabled lookup codes to be imported. For importing several lookup codes, add more entries in the same format.

LookupType|LookupCode|DisplaySequence|EnabledFlag|StartDateActive|EndDateActive|Meaning|Description|Tag|SetName
DATA_22APR_1|Code1_1|1|Y|25/12/2014|25/5/2015|DATA_22apr_1|Data_desc_1|Tag1_1|TEST SET CODE 2
DATA_22APR_1|Code1_2|2|N|25/1/2014|25/11/2015|DATA_22apr_2|Data_desc_2|Tag1_2|TEST SET CODE 3
DATA_22APR_2|code2_1|3|N|25/12/2012|25/7/2015|DATA_22qpr_2_1|Data_desc_2|tag2_1|TEST SET CODE 2
DATA_22APR_2|code2_2|3|Y|25/12/2012|25/7/2015|DATA_22qpr_2_2|Data_desc_2_2|tag2_2|TEST SET_ERR_CODE_Z

Scheduled Processes

Scheduled processes do tasks that are too complex or time-consuming to do manually, for example importing data or updating many records. You can run processes on a recurring schedule and send notifications based on how the process ends. Some scheduled processes give you printable output. Those processes might have Report in their name.

Jobs and Job Sets

Each scheduled process that you run is based on a job. The job is the executable that controls what the process can do and what parameters and other options you have for the process. A job set contains multiple jobs.

You or your administrator can create job definitions for Oracle Business Intelligence Publisher reports so that people can run the reports as scheduled processes.

Process Sets

A process set is a scheduled process that's based on a job set. So, when you submit a process set, you're running more than one job.

Note: When you submit certain scheduled processes, the job logic causes other processes to automatically run. But in this case, you're not submitting a process set that includes those other processes.

Submission

When you submit a scheduled process, you can use its parameters to control which records are processed and how. For example, a process includes only the transactions that were edited by the person you select for a Last Updated By parameter. Some processes don't have parameters.

As part of the submission, you can also set up a schedule for the process, for example to run once a week for two months. Every time a process runs, there's a unique process ID.

Output

Some scheduled processes provide output in PDF, HTML, and other formats. For example, a process can import records and also produce output with details about those records. There are many types of output, for example a tax document or a list of transactions.

View Details About Predefined Scheduled Processes

To use web services to run predefined scheduled processes, you require details about the processes. View job definitions that the processes are based on, for example to get information about parameters. You might also need to find security requirements for running the scheduled process.

Job Definitions

A job definition contains the metadata that determines how a scheduled process works and what options are available during submission.

To view job definitions:

  1. Go to the Setup and Maintenance work area.

  2. From the Application Extensions functional area, open any of these tasks as appropriate:

    • Manage Enterprise Scheduler Job Definitions and Job Sets for Financial, Supply Chain Management, and Related Applications

    • Manage Enterprise Scheduler Job Definitions and Job Sets for Human Capital Management and Related Applications

    • Manage Enterprise Scheduler Job Definitions and Job Sets for Customer Relationship Management and Related Applications

  3. In the Manage Job Definitions tab, select your job definition and click Edit.

    Note: Predefined job definitions are marked with an asterisk.
  4. Cancel after you get the information you need.

Security

Privileges provide the access required to run specific scheduled processes. Privileges are granted to duty roles, which are granted to job roles. To see which job roles inherit the required privileges, use the Security Console or the security reference manuals for the appropriate product family.