Skip Headers

Contents

23 Other Common Setup and Maintenance Tasks

This chapter contains the following:

Define Transactional Business Intelligence Configuration

Define Extensions: Define Custom Enterprise Scheduler Jobs

Customization and Sandboxes

FAQs for Other Common Setup and Maintenance Tasks

Define Transactional Business Intelligence Configuration

Define Transactional Business Intelligence Configuration: Highlights

Configure Oracle Transactional Business Intelligence for ad hoc reporting, review certain setup objects to be used in Transactional Business Intelligence, and manage the presentation catalog and currency type display.

Defining Transactional Business Intelligence Configuration

Review details about the Transactional Business Intelligence tasks. Refer to the Oracle Fusion Transactional Business Intelligence Administrator's Guide.

Define Extensions: Define Custom Enterprise Scheduler Jobs

Managing Job Definitions: Highlights

Oracle Enterprise Scheduler jobs are run in Oracle Fusion Applications to process data and, in some cases, to provide report output. A job definition contains the metadata that determines what the job does and what options are available to users who run the job. You can create and maintain job definitions for use in Oracle Fusion Applications.

Managing job definitions is fully described in the Oracle Fusion Applications Administrator's Guide. As you read content from that guide, note that the guide describes managing Oracle Enterprise Scheduler, including job definitions, from Oracle Enterprise Manager Fusion Applications Control. You can also access job definitions by starting in the Setup and Maintenance Overview page and searching for the Enterprise Scheduler job tasks for your applications.

Selecting the Appropriate Implementation Task

Each Enterprise Scheduler job definition task uses one Java EE application, which is referenced in the task name. You must use the right task because, to access the product job definition that you want to view or work on, the view objects must be contained in the application. If you do not select the right task, then the job definition will not be displayed properly or function correctly. The application name is usually the same as the product that the job definition belongs to, but not always.

For example, the Oracle Fusion Payables Java EE application contains the Oracle Fusion Expenses product view objects. To create or maintain a job definition for use in Expenses, you select the Manage Custom Enterprise Scheduler Jobs for Payables and Related Applications task.
In another example, the Oracle Fusion Payments product view objects are contained in both Oracle Fusion Payables and Oracle Fusion Receivables Java EE applications. You need to select the task appropriate to the job definition for Payments. Use the Manage Custom Enterprise Scheduler Jobs for Receivables and Related Applications task if the job is for receivables functionality, or the Manage Custom Enterprise Scheduler Jobs for Payables and Related Applications task if the job is for payables functionality.
Use the task description to see the products that correspond to the Java EE application specified in the task name. For example, the description for the Payables task lists Oracle Fusion Payables, Assets, Expenses, and Payments.

You can view task descriptions in the help window for the task, if any, or in the generated setup task lists and tasks report from the Getting Started page.
If you have access to the Manage Task Lists and Tasks page, you can also open the details for specific tasks to see the description.
For general information about product and Java EE application relationships, use Oracle Enterprise Manager Fusion Applications Control (Fusion Applications Control).
See: Topology Section

Viewing and Creating Job Definitions

You can access predefined and custom job definitions.
See: Viewing Job Definitions
You can create jobs based on Java, PL/SQL, or any other supported technology.
See: Creating a Job Definition

If you are using the Setup and Maintenance work area, then the Enable submission from Enterprise Manager check box is available for the job definition.

If you do not select this check box, then the job cannot be run from Enterprise Manager.
If you select this check box, then you can define parameters for this job definition only in Enterprise Manager. Save the rest of your work on the job definition, and then go to Enterprise Manager if you need to define parameters.

Managing List of Values Sources: Highlights

A list of values source for Oracle Enterprise Scheduler job definitions determines where a list of values comes from and what the specific values are. These lists of values are used in parameters and user properties of job definitions. For example, you can use a source of country values for a Country job parameter.

Managing list of values sources is fully described in the Oracle Fusion Applications Administrator's Guide. As you read content from that guide, note that the guide describes managing Oracle Enterprise Scheduler, including list of values sources, from Oracle Enterprise Manager Fusion Applications Control. You can also access list of values sources by starting in the Setup and Maintenance Overview page and searching for Enterprise Scheduler job tasks.

Registering and Searching for List of Values Sources

Create list of values sources to register them for use in job definitions.
See: Registering Sources for Lists of Values
Search for list of values sources to edit or delete, or to make sure a particular source does not already exist before you create it.
See: Searching for List of Value Sources

Customization and Sandboxes

Customizing Pages Using Oracle Composer: Highlights

You can customize dashboards and some work areas, where available, for all or some users based on a selected customization layer, for example only for users in a specific country or with a specific job role. When you select to customize a page from the Administration menu in the global area, you invoke Oracle Composer, which enables the customization. The Administration menu is only available if you have appropriate roles.

From the same menu, you can also:

Customize the global area at the site layer.
Access the Customization Manager, which displays a list of components in the current page and details about the layers in which each component is customized.
Access sandboxes from the Administration menu, to make customizations to a runtime use session before deploying your changes to the mainline.

Customizing pages using Oracle Composer, the Customization Manager, and sandboxes are described in the Oracle Fusion Applications Extensibility Guide.

Editing Pages

Customizations that you can make to existing pages include adding content and changing layout.
See: Editing a Page in Oracle Composer
You can also update display and other options for specific components within the page.
See: Editing Component Properties in Oracle Composer

Customization Manager

Use Customization Manager to analyze and diagnose customization metadata, and to perform customization related tasks that cannot be done in the user interface, for example to revert customizations to a previous version. You can also do direct customization by manipulating the metadata and uploading it back.
See: Using Customization Manager to Manage Runtime Customizations

Sandboxes

Create or select an appropriate sandbox, and set it as active to capture your customizations using Oracle Composer. When you are ready, you publish the sandbox to make your changes available to users.
See: Using the Sandbox Manager

Sandboxes: Highlights

Use a sandbox to commit customizations to a runtime use session for validation before deploying changes to the mainline. Administrators create and manage sandboxes. An active sandbox isolates changes from the mainline and other users.

Sandboxes can contain the following types of customization changes.

Metadata, such as non-flexfield UI page customizations
Data security
Generated flexfields business components

Metadata changes are captured in a metadata sandbox. Data security changes are additionally captured in a data security enabled sandbox. Changes to a flexfield are captured in a flexfield that is deployed as a single flexfield sandbox. Once you are ready to make sandbox changes available in the mainline, you either publish the metadata or data security sandbox, or deploy the flexfield. Only metadata and data security sandboxes can be downloaded as a sandbox file for import to another Oracle Fusion Applications instance.

The following table lists the differences among the types of sandboxes.

Type of Changes	Type of Sandbox	Method for Making Changes Available in Mainline	Downloadable?
Metadata	Sandbox	Publish sandbox	Yes
Data security	Sandbox enabled for data security changes	Publish sandbox	Yes
Flexfield	Flexfield deployed as a flexfield-enabled sandbox	Deploy flexfield	No

Only one sandbox can be active at a time. Changes made while a sandbox is active are captured in that sandbox.

For more information on using the Sandbox Manager, and customizing and securing pages, business objects, data, and custom objects in a sandbox, see the Oracle Fusion Applications Extensibility Guide.

Managing a Page Customization Sandbox

You can make metadata (MDS) type changes in a sandbox, including menu customizations, changes to the personalization menu, implicit ADF customizations, or changes made with Oracle Composer or CRM Application Composer.

If you are entitled to do so, manage sandboxes in the Sandbox Manager.
See: Using the Sandbox Manager

Implement customizations on an existing page to change the metadata of a sandbox before deploying the changes to the mainline.
See: Customizing Existing Pages
Using CRM Application Composer, customize business objects in a sandbox before deploying the changes to the mainline.
See: Customizing Objects

Managing a Data Security Sandbox

You can create a sandbox for data security testing, or designate an existing sandbox to become enabled for data security testing.

If you are entitled to do so, manage data security-enabled sandboxes in the Sandbox Manager.
See: Using the Sandbox Manager

If you customize business objects in CRM Application Composer, you may need to define data security policies to make them accessible to users.
See: Defining Security Policies for Business Objects
If you create new business objects, you need to secure them.
See: Customizing Security for Custom Business Objects

Managing a Flexfield Sandbox

You create a flexfield-enabled sandbox by deploying one flexfield to a sandbox using the Manage Flexfield task flow. The flexfield sandbox gets its name from the flexfield you deploy. You cannot test two flexfields in the same sandbox. Once you deploy a flexfield as a sandbox, you must sign out and back in to view how the sandbox runtime reflects the flexfield changes, such as new segments. You can redeploy the same flexfield to the same sandbox repeatedly as you make incremental changes to the flexfield setup.

Since a flexfield sandbox cannot be published, any page customizations or data security in the flexfield sandbox cannot reach the mainline when the flexfield is deployed to the mainline. If you have entitlement to do so, see Deploying a Flexfield to a Sandbox: Points to Consider.
If you are entitled to do so, manage flexfield-enabled sandboxes in the Sandbox Manager.
See: Using the Sandbox Manager

FAQs for Other Common Setup and Maintenance Tasks

How can I change the web mapping service for displaying contextual addresses?

Edit the Mapping Service for Contextual Addresses profile option value. A contextual address is marked with an orange square icon that can be clicked to display the address on a map. The profile option value represents the web mapping service used to display the map. To update this value, use the Manage Administrator Profile Values task in the Setup and Maintenance work area.