Oracle's Fusion SaaS applications cloud is built on a single data model that connects end-to-end business processes across Human Capital Management (HCM), Enterprise Resource Planning (ERP), Customer Experience (CX) and Supply Chain Management (SCM) functionalities.
While Oracle is providing a common extension and configuration framework across all Fusion SaaS applications, every pillar has also provided additional purpose-built tools and utilities that supports easier and faster deployment.
Objective for this blog, is to provide you with a high-level overview of implementation setup, configuration and migration considerations during your Fusion SaaS application implementation.
Customization and extensions that are available using Oracle Platform as a Service (PaaS) services are not covered in this article.
Oracle Fusion SaaS application supports all configurations and extensions to be performed at run time using browser-based configuration and administration tools. Users with the administrative privilege can access most of the runtime configurations. The recommended best practice is all configurations must be done in a TEST environment, and migrate the configurations to PRODUCTION environment.
Functional Setup Manager (“FSM”) is the core component of Oracle Fusion applications that allows developers/administrators to manage application offerings and design objects. It provides an efficient and consistent implementation process experience for all Fusion applications across CX, ERP, HCM and SCM pillars.
With FSM, you can
Browser-based composers and tools are used to perform run-time configurations and extensions within Oracle Fusion applications to modify user interface, navigation, security, reports & analytics, and help based on your business requirements.
The table below provides high level summary of all configuration and administration tools.
|Setup and Maintenance||Functional setup manager used to manage the implementation projects and tasks.||Manage Offerings, Enterprise Structures, Adding additional flex fields for key objects, pre-packaged lists/tasks for every module.|
|Page Composer||Browser based run-time page editor tool used to modify User Interface pages and components to suit your business needs.||Add/Hide fields, add validations, change default content, save queries.|
|Application Composer||Browser based design and run-time tool used to extend object model changes and user interface.
- Preferred tool for Engagement Cloud
- Also used in ERP & SCM Cloud for selected modules & objects
|Add new fields to standard objects, create global functions, custom objects, relationships, security, workflows/approvals, email templates, etc.|
|Structure||Configure navigator and springboard preferences for home page.||Create groups and page entries;
Show or hide functional / feature components / objects in home page
|Appearance||To change look and feel of the application pages.||Change logo, background image, color, Icons, home page display, etc.|
|User Interface Text||To change a specific term across all pages.||Change “Buyer” to “Customer” OR “Account” to “Companies”.|
|Application Help||Make comprehensive replacements of words or phrases that appear in messages, labels, and other areas of your user interface.||Change label “Accounts” to “Companies” in all screens.|
|Alerts Composer||Enables you to send informational notifications to HCM cloud users by email and work list.||Recruiting workflow notification|
|BI Composer||Used to create/modify reports, layouts, filters and subject areas.||Reports, Data exports for integrations|
|Personalization||End user tool to customize application look and feel without affecting other users.||Dashboards, application pages|
An interpreted objected oriented programming language for Java Virtual Machine (“JVM”).
- Widely used and supported in Engagement Cloud
- Very limited use in other modules
|Validation rules, triggers to objects/fields|
Sandboxes are testing environments for developers/configurators/administrators and users can’t see. Sandbox configurations will be available to all users after publishing the configurations to mainline code. Sandbox allows developers/configurators/administrators to test application extensions in an isolated environment. Sandbox stores temporary copies of portions of metadata used to test the configurations before deploying them.
Applications metadata changes and data security changes are stored in a sandbox, and are validated before publishing the configurations to the mainline.
The diagram and table below provide you with a high-level mapping of tools across pillars as a guideline. It is recommended that you review the latest documentation and plan your implementation and configuration tools accordingly.
Note that Application Composer is widely used in Engagement Cloud, and for selected objects of ERP and SCM.
The configuration set contains configurations from all product families. Configuration set contains most of the application changes performed with Application Composer, Page Composer, Appearance, User Interface Text, Structure, Page Integration and application core setup data configured using FSM such as messages, look-ups, data security, flex fields, value sets, attachments, deep links, changes to Enterprise scheduler service (ESS) jobs, and others.
The diagram below shows a high-level view of migrating configurations and extensions between environments.
|Configuration Set Migration (“CSM”)||
Compressed file containing artifacts from modifying application. Used for migrating (Create, download & upload and import) configurations across all product families between environments with same patch level. CSM migration would only migrate customization.
|Enterprise roles, new duty roles, and role hierarchy changes, which are made directly in Security Console aren't migrated.|
|FSM Export & Import||
To move configurations and extensions to another environment, such as the production environment.
|Move functional setup data such as descriptive flex fields, value sets, lookups,etc.|
|Environment Refresh||Environment Refresh is the service entitlement that you should request to migrate data from a source environment to a target environment.||
From a production environment to a non-production environment (P2T).
From a non-production environment to another non-production environment (T2T).
Oracle Applications Cloud Service Definition - Environment Refresh (Doc ID 2015788.1)