Oracle® Fusion
Applications Workforce Deployment Implementation Guide 11g Release 5 (11.1.5) Part Number E20379-05 |
Contents |
Contact Us |
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.
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.
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:
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.
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.
Using the Manage Custom Objects task, you can create a custom object, add and manage the object's attributes, as well as add the new custom object to an existing top-level object. Adding custom objects to existing ones enables you to extend delivered business objects with custom objects so that you can tailor Oracle Fusion HCM to suit your business needs.
Note
Before using the Manage Custom Objects task, refer to the Oracle Fusion Applications Extensibility Guide to learn more about customization, including the customization development life cycle, and how to use the Sandbox Manager and Customization Manager.
To add custom objects, you add child objects to existing top-level objects. For example, you can add child objects to the Locations object. The list of available top-level objects appears on the Manage Custom Objects page. You cannot add additional top-level objects
After you create a custom object, you add fields to capture the necessary information about the object. For each field that you add, you define how the field appears and behaves, such as whether the field is required, searchable, whether a default value for the field is provided, and so on.
Several types of fields are available to add to the custom object, including:
Text
Number
Date
Check box
Percentage
Date and time
Choice list (fixed)
Choice list (dynamic)
Formula
For the fixed choice list field type, you can either associate an existing lookup type or create a new one.
After you define the custom object and add fields to it, you use the Resource Catalog within the Page Composer to add the object to a page and expose it to your users.
This example shows how to customize an existing business object by adding a child object to it.
InFusion Corporation has several different locations. For each location, they want to include information about the property management company that is associated with that location.
The information that InFusion wants to include for each location is: name of the property management company, contact person, and a phone number.
InFusion first examines the possibility of adding flexfields to the Locations object but realizes that this will not work because they need to be able to capture more information than flexfields allows. InFusion decides to create a child object called Property Management, add it to the Location object, and add fields to capture the property management company, contact person, e-mail address, phone number, and preferred contact method.
To create the Property Management business object, InFusion must complete the following setup tasks:
Create a child object called Property Management for the Locations parent object.
Add five fields to the Property Management object.
Use the Resource Catalog in the Page Composer to add the Property Management object to the Create Locations page.
The following table describes how to define the Property Management child object.
Display Label |
Description |
---|---|
Property Management |
Business object to capture property management details for company locations. |
The following table describes how to define the five fields for the Property Management object.
Field Type |
Display Label |
Name (internal) |
Updateable? |
---|---|---|---|
Text |
Property Management Company Name |
PM Company Name |
Selected |
Text |
Contact Name |
PM Contact Person |
Selected |
Text |
Contact Number |
PM Contact Phone Number |
Selected |
Text |
|
PM E-mail address |
Selected |
Choice List (fixed) |
Preferred Contact Method |
PM Preferred Contact Method |
Selected |
For the choice list field, add a new lookup type called PREFERRED CONTACT METHOD and add two values: Phone and E-Mail.
After the Property Management object has been created, the next step is to add the object to a page using the Resource Catalog in the Page Composer so that you can expose it to users.