This brief article is intended to clarify what you can and cannot do to Fusion Applications (Release 5) that are deployed as Software-as-a-Service (SaaS) via the Oracle Cloud. We’ve seen lots of questions on this subject and this article is intended to provide some clarity. This does not cover options for private or hybrid Cloud deployments, such as through Oracle Managed Cloud / Oracle On-Demand. These dedicated environments may permit deeper system access, such as connections via JDeveloper, and therefore it is possible to perform more invasive customization work. For SaaS deployments personalization and customization is performed using the Composer family of tools, accessible from within Fusion Applications itself.
Oracle’s cloud services are evolving at a rapid pace, and as such where possible we have marked the applicable release. We will create new posts similar to this with any significant changes in each new release.
In addition, customers and partners are working on solutions outside the standard services and products, and these may include addition options for tailoring and extending the core functionality. An example of which is a recently deployed custom J2EE application in the Oracle Cloud Java Service that is integrated (via webservices) to an Oracle Cloud Fusion HCM instance.
The following is a short list of activities that are commonly part of tailoring an Enterprise Application and provides confirmation if this is possible for an Oracle Cloud / SaaS deployment, and in which release.
|Flexfields||Manage Descriptive Flexfields (DFF) and Manage Extensible Flexfields via FSM tasks||Y|
| ||Import flexfield seed data||Y|
| ||Include DFF in OTBI reports (a deployment option), but not EFF yet||Y|
| ||Migrate flexfields from T2P via FSM export/import||Y|
| || || |
|Business Processes||Edit or add SOA Composite Applications||N|
| ||Edit existing Approval Rules||Y|
| ||Add new approval processes to existing BPEL processes||N|
| ||Use all standard AMX routing options||N|
| || || |
|BI & Reporting||Add-to or edit the seeded BI Publisher (PDF) reports||Y|
| ||Add-to or edit the BI Analytics reports||Y |
| ||Edit the existing OTBI charts embedded in pages||N |
| ||Add new all reports content to the custom folder of the BI Catalog||Y|
| || || |
|ESS||Add a report to an new ESS Job Definition||Y|
| ||Manually schedule a new ESS Job||Y |
| ||Edit the VO-based input parameters used in an ESS Job||N |
| ||Edit the application logic to use a new ESS job definition||N |
| || || |
|User Interface||Change the regions of the UI Shell (although some options exist in the CRM Application Composer)||N|
| ||Make a page personalizable if it is not by default, or change what can be personalized||N|
| ||Change the Fusion Applications Skin – the look-and-feel including logos and colors||N (coming soon)|
| ||Change the standard Fusion Applications Menu items||N|
| ||Edit mobile-specific pages||N|
| ||Translate text added via customization||N|
| ||Change the seeded ADF task flows||N|
| ||Add an entirely new page||N|
| ||Change existing pages and workareas, including labels, layouts, and hide/show fields||Y|
| ||Add/edit existing ADF Business Object field use on a page||Y|
| ||Add Expression Language code to page components to extend validation logic||Y|
| ||Change and extend the User Assistance / Help content (although not the embedded page content)||Y|
The table above is intended to answer some of the more common questions around what you can and cannot do in a SaaS-Cloud deployment of Fusion Applications. Of course there are many more options and features available than are listed here, and items that are not currently possible may be possible in the future. If you have business cases for any of these please let us know.
A more comprehensive list of what you can do with each of the Fusion Applications tools (Composers and JDeveloper) is provided in Tables 1-2 to 1-8 in Chapter 1 of the Fusion Applications Extensibility Guide.
There are some useful tips and recommendations in the MyOracleSupport notes entitled ‘Guidance for Managing Customizations in Oracle Cloud Application Services’, such as 1510580.1, 1510578.1, 1510577.1, and 1510288.1.