Skip Headers

Contents

29 Define Extensions for Customer Data Management

This chapter contains the following:

Define Custom Enterprise Scheduler Jobs

Customization and Sandboxes

FAQs for Define Extensions for Customer Data Management

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

Customizing Oracle Fusion CRM Pages Using Oracle Composer: Explained

You can customize most pages in Oracle Fusion CRM using Oracle Composer. To access Oracle Composer, navigate to one of the pages available for customization and select to customize the page from the Administration menu in the global area.

Available Customization Options

When you select to customize a page from the Administration menu in the global area, you launch Oracle Composer.

The customizations that you make are applied based on your layer selection:

Site
Your customizations are visible to all users.
Job Role
Your customizations are visible to users who have the selected job role.
External or Internal
Depending on your selection, your customizations are visible to either external or internal users. External users could be your partners or anonymous users. Internal users could be your employees.

Note

Users can customize their own dashboard pages by selecting Edit Current Page from the Personalization menu. Such customizations are visible only to the user who made the change.

Available Customization Tasks

Oracle Composer uses two different modes of Design View. The first mode, Design View: Standard mode, is selected by default in all CRM pages when opening a page with Oracle Composer with the Design button selected. The second mode, Design View: Direct Selection mode, is activated when you click the Select tab for the UI page you want to customize.

With the Design View: Direct Selection mode, you can select and edit UI components such as form fields and table columns. In Direct Selection mode, selectable UI components become apparent when you move your cursor over the UI component. Selectable UI components are highlighted and can be edited. In CRM, Direct Selection mode is available when you customize pages, but not when you personalize a dashboard page.

Examples of UI components exposed in Design View: Direct Selection mode are:

Fields (for example an input text field)

Show component (boolean attribute)
Read only (boolean attribute)
Required (boolean attribute)
Label

UI container (for example, form container)

Show or hide child components (for example, fields in the form)
Reorder child components (for example, reorder fields in a form)

UI components can be protected from update to preserve the product business logic (for example, a field is read only or not based on a security privilege already defined in the application). If protected from update, the UI components are grayed out and cannot be changed.

This table describes how you can use each mode of Oracle Composer to customize dashboard pages and other select pages*.

Customization Tasks	Design View - Standard mode	Design View - Direct Selection mode
Add content (Business Intelligence reports, CRM portlets such as Calendar)	Yes	No
Delete region	Yes	No
Move region	Yes	No
Change page layout (for example, change a two column layout to three column layout)	Yes	No

*Examples of such pages are: Partner Public Profile page, Partner Landing page, Partner Registration page, Opportunity Overview, Customer Snapshot node, and Overview Analysis tab.

This table describes how you can use each mode of Oracle Composer to customize transactional pages (all other non-dashboard pages).

Customization Tasks	Design View - Standard mode	Design View - Direct Selection mode
Default region state (open or close)	Yes	No
Manage saved searches (create and edit)	Yes	No
Hide or show field	No	Yes
Change field label	No	Yes
Make field required or not	No	Yes
Make field read-only or updateable	No	Yes
Reorder fields in a form	No	Yes
Reorder table columns	Yes	Yes
Hide or show table columns	Yes	Yes
Set table column width with the mouse	Yes	No
Set table column width and minimum width in percent or pixels	No	Yes
Make column sortable or not	No	Yes

Customization Privileges Required

The following are examples of job roles that must be assigned to you before you can make customizations using Oracle Composer:

Application	Duty Role	Job Role
CDH	Master Data Management Application Administrator	Master Data Management Application Administrator
Sales Catalog	Sales Catalog Administrator Duty	Sales Catalog Administrator
Sales	Sales Administrator Duty	Sales Administrator
Marketing	Marketing Operations Manager Duty	Marketing Operations Manager
PRM	Channel Administrator Duty	Channel Administrator
PRM	Channel Partner Portal Administrator Duty	Channel Partner Portal Administrator

Contact your security administrator for details.

Customizing Oracle Fusion CRM Applications Using Oracle Fusion CRM Application Composer: Explained

The Oracle Fusion CRM Application Composer provides a series of task flows which let you customize and extend an Oracle Fusion CRM application according to the needs of your users. For example, you can create new fields for an existing standard object, and expose those new fields on the object's work area. Or, create a brand new custom object and related fields, then create a work area where that object and its fields are exposed to users. The task flows available to you are dependent upon the CRM application that you are customizing. This topic provides an overview of which CRM Application Composer task flows are available for use in each CRM application.

This topic addresses extensibility for these CRM applications:

Oracle Fusion Common CRM
Oracle Fusion Customer Center
Oracle Fusion Marketing
Oracle Fusion Sales
Oracle Fusion Sales Catalog

You can also refer to the product-specific implementation guides to learn more about how a particular application works with the Application Composer.

Oracle Fusion Common CRM

The creation of custom objects is not supported for the Oracle Fusion Common CRM application.

For Oracle Fusion Common CRM standard objects, you can do the following in the Application Composer:

Customization Task Flow	Trading Community Org Contact	Trading Community Resource Profile	Trading Community Organization Profile	Trading Community Address	Activity Task	Interaction	Note
Create and expose custom fields on existing pages that are available for extensibility	Yes	Yes	Yes	Yes	Yes	Yes	Yes
Edit display label and help text of standard fields	Yes	Yes	Yes	Yes	Yes	Yes	Yes
Create custom currency fields	No	No	No	No	No	No	No
Index custom fields	Yes	Yes	Yes	Yes	No	Yes	Yes
Add custom buttons (Groovy script or URL) to selected pages	No	Yes	No	No	No	Yes	Yes
Add links (URL) to selected pages	No	Yes	No	No	No	Yes	Yes
Create and expose custom child objects on an object's details page	No	No	No	No	Not applicable	Not applicable	Not applicable
Create custom field-level and object-level validation logic (Groovy scripts)	Yes	Yes	Yes	Yes	No	Yes	Yes
Create custom logic at various object trigger points (Groovy scripts)	Yes	Yes	Yes	Yes	No	Yes	Yes
Create custom saved searches at the site level	Yes	Yes	Yes	Yes	No	Yes	Yes
Provide Mobile page support	Yes	No	No	No	No	No	No
Create custom relationships	Yes	Yes	Yes	Yes	No	No	No
Manage object workflows	No	Yes	No	No	No	No	No
Web services	Yes	Yes	Yes	Yes	Yes	Yes	Not applicable
Import data using file-based import	Yes	Yes	Yes	Yes	Yes	Yes	Yes
Export data using bulk export	Yes	Yes	Yes	Yes	Yes	Yes	Yes
Create custom subject areas	No	Yes	No	No	No	No	No

Oracle Fusion Customer Center

You can create custom objects for the Oracle Fusion Customer Center application.

For Oracle Fusion Customer Center's standard object, you can do the following in the Application Composer:

Customization Task Flow	Sales Account Profile
Create and expose custom fields on existing pages that are available for extensibility	Yes
Edit display label and help text of standard fields	Yes
Create custom currency fields	No
Index custom fields	Yes
Add custom buttons (Groovy script or URL) to selected pages	No
Add links (URL) to selected pages	No
Create and expose custom child objects on an object's details page	Yes
Create custom field-level and object-level validation logic (Groovy scripts)	Yes
Create custom logic at various object trigger points (Groovy scripts)	Yes
Create custom saved searches at the site level	No
Provide Mobile page support	No
Create custom relationships	Yes
Manage object workflows	Yes
Web services	Yes
Import data using file-based import	Yes
Export data using bulk export	Yes
Create custom subject areas	Yes

Oracle Fusion Marketing

You can create custom objects for the Oracle Fusion Marketing application.

For Oracle Fusion Marketing standard objects, you can do the following in the Application Composer:

Customization Task Flow	Sales Lead	Marketing Campaign	Marketing Budget	Marketing Response	Marketing List	Marketing Treatment	Marketing Event Activity	MarketingAdvertising Activity	Marketing Claim	Marketing Claim Settlement (child)	Marketing Budget Entry	Marketing Budget Fund Request
Create and expose custom fields on existing pages that are available for extensibility	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes
Edit display label and help text of standard fields	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes
Create custom currency fields	No	No	No	No	No	No	No	No	No	No	No	No
Index custom fields	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes
Add custom buttons (Groovy script or URL) to selected pages	Yes	No	Yes	No	No	No	No	No	Yes	Yes	Yes	Yes
Add links (URL) to selected pages	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes
Create and expose custom child objects on an object's details page	Yes	No	Yes	Yes	No	No	No	No	Yes	Not applicable	No	Yes
Create custom field-level and object-level validation logic (Groovy scripts)	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes
Create custom logic at various object trigger points (Groovy scripts)	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes
Create custom saved searches at the site level	Yes	Yes	Yes	Yes	Yes	Yes	No	No	Yes	No	Yes	Yes
Provide Mobile page support	No	No	No	No	No	No	No	No	No	No	No	No
Create custom relationships	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	No	Yes	Yes
Manage object workflows	Yes	No	Yes	No	No	No	No	No	Yes	Yes	Yes	Yes
Web services	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes
Import data using file-based import	Yes	Yes	Yes	Yes	Yes	No	Yes	Yes	No	No	No	No
Export data using bulk export	Yes	No	Yes	No	No	No	No	No	No	No	No	No
Create custom subject areas	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes

Oracle Fusion Sales

You can create custom objects for the Oracle Fusion Sales application.

For Oracle Fusion Sales standard objects, you can do the following in the Application Composer:

Customization Task Flow	Opportunity	Sales Competitor	Partner	Opportunity Resource (child)	Opportunity Revenue (child)
Create and expose custom fields on existing pages that are available for extensibility	Yes	Yes	Yes	Yes	Yes
Edit display label and help text of standard fields	Yes	Yes	Yes	Yes	Yes
Create custom currency fields	Yes	No	No	No	Yes
Index custom fields	Yes	Yes	Yes	Yes	Yes
Add custom buttons (Groovy script or URL) to selected pages	Yes	Yes	Yes	Yes	Yes
Add links (URL) to selected pages	Yes	Yes	Yes	Yes	Yes
Create and expose custom child objects on an object's details page	Yes	Yes	Yes	Not applicable	Not applicable
Create custom field-level and object-level validation logic (Groovy scripts)	Yes	Yes	Yes	Yes	Yes
Create custom logic at various object trigger points (Groovy scripts)	Yes	Yes	Yes	Yes	Yes
Create custom saved searches at the site level	Yes	Yes	Yes	No	No
Provide Mobile page support	Yes	Yes	Yes	Yes	Yes
Create custom relationships	Yes	Yes	Yes	No	No
Manage object workflows	Yes	Yes	Yes	No	No
Web services	Yes	Yes	Yes	Not applicable	Not applicable
Import data using file-based import	Yes	Yes	Yes	Yes	Yes
Export data using bulk export	Yes	Yes	Yes	Yes	Yes
Create custom subject areas	Yes	Yes	Yes	Yes	Yes

Oracle Fusion Sales Catalog

The creation of custom objects is not supported for the Oracle Fusion Sales Catalog application.

For Oracle Fusion Sales Catalog's standard object, you can do the following in the Application Composer:

Customization Task Flow	Product Group
Create and expose custom fields on existing pages that are available for extensibility	Yes
Edit display label and help text of standard fields	Yes
Create custom currency fields	No
Index custom fields	Yes
Add custom buttons (Groovy script or URL) to selected pages	No
Add links (URL) to selected pages	No
Create and expose custom child objects on an object's details page	No
Create custom field-level and object-level validation logic (Groovy scripts)	No
Create custom logic at various object trigger points (Groovy scripts)	No
Create custom saved searches at the site level	No
Provide Mobile page support	No
Create custom relationships	No
Manage object workflows	No
Web services	No
Import data using file-based import	Yes
Export data using bulk export	Yes
Create custom subject areas	No

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 Define Extensions for Customer Data Management

What's the difference between Oracle Composer and Oracle Fusion CRM Application Composer?

Oracle Composer is an Oracle Fusion tool you can use to modify Oracle Fusion user interface (UI) pages and components for all products designated for use with Oracle Composer. Oracle Composer uses two different modes of Design View. The first mode, Design View: Standard mode, is selected by default in all CRM pages when opening a page with Oracle Composer with the Design button selected. The second mode, Design View: Direct Selection mode, is activated when you click the Select tab for the UI page you want to customize. In CRM, Direct Selection mode is available when you customize pages, but not when you personalize a dashboard page. With the Design View: Direct Selection mode, you can select and edit UI elements such as form fields and table columns. In Direct Selection mode, selectable UI components become apparent when you move your cursor over the UI component. Selectable UI components are highlighted and can be edited.

This table describes how you can use each mode of Oracle Composer to customize dashboard pages and other select pages (such as the Partner Public Profile page, Partner Landing page, Partner Registration, Customer Snapshot, and Customer Overview - Analysis tab), and customize transactional pages (all other non-dashboard pages):

Use Cases	Design View - Standard mode	Design View - Direct Selection mode	Page Type
Add content (Business Intelligence reports, CRM portlets such as Calendar)	Yes	No	Dashboard and other select pages
Delete region	Yes	No	Dashboard and other select pages
Move region	Yes	No	Dashboard and other select pages
Change page layout (for example, change a two column layout to three column layout)	Yes	No	Dashboard and other select pages
Default region state (open or close)	Yes	No	Transactional pages (all non-dashboard pages)
Manage save queries (create and edit)	Yes	No	Transactional pages (all non-dashboard pages)
Hide or show field	No	Yes	Transactional pages (all non-dashboard pages)
Change field label	No	Yes	Transactional pages (all non-dashboard pages)
Make field required or not	No	Yes	Transactional pages (all non-dashboard pages)
Make field read-only or updateable	No	Yes	Transactional pages (all non-dashboard pages)
Reorder fields in a Form	No	Yes	Transactional pages (all non-dashboard pages)
Reorder table columns	Yes	Yes	Transactional pages (all non-dashboard pages)
Hide or show table columns	Yes	Yes	Transactional pages (all non-dashboard pages)
Set table column width with the mouse	Yes	No	Transactional pages (all non-dashboard pages)
Set table column width and min width in percent or pixels	No	Yes	Transactional pages (all non-dashboard pages)
Make column sortable or not	No	Yes	Transactional pages (all non-dashboard pages)

The Oracle Fusion CRM Application Composer also lets you make UI changes at runtime. However, the types of UI changes that you can make using the Application Composer are quite different. Specifically, your primary focus when using the Application Composer is to make actual object model changes. For example, you can create a new business object and related fields, and then create new application pages where that object and its fields are exposed to users. The ability to make these types of object model extensions is available only in Oracle Fusion CRM applications. Also, using the Application Composer, you cannot access the Resource Catalog to add new content to a page. With Application Composer, administrators can make customizations at the site level only.

This table describes some of the primary differences between Oracle Composer and the Application Composer:

Customization Task	Available in Oracle Composer (site, job role, external or internal level)?	Available in Oracle Fusion CRM Application Composer (site level only)?
Make object model extensions and expose your customizations by creating or modifying work area pages	No	Yes
Reorder subtabs	No	Yes
Customize dashboard pages	Yes	No
Add content from the Resource Catalog	Yes	No
Simple field customizations (show, hide, make read only, make required)	Yes (WYSIWYG - what you see is what you get)	Yes (non-WYSIWYG)
Select the MDS layer where you want to author customizations, such as at the site layer or job role layer	Yes	No
View results of customizations immediately	Yes, in the Oracle Composer design interface	Yes, in the CRM application that you are customizing