Oracle® Fusion
Applications Workforce Deployment Implementation Guide 11g Release 1 (11.1.2) Part Number E20379-02 |
![]() Contents |
![]() Previous |
![]() Next |
This chapter contains the following:
Define Custom Enterprise Scheduler Jobs
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.
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.
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 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. You can also 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.
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.
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.
You can create a sandbox for data security testing, or designate an existing sandbox to become enabled for data security testing.
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.