Fusion Apps Composers Explained

While discussing composer functionality for extending Fusion Applications I encountered many questions about the four Composers provided by Oracle

•     The Application User Interface, supported by the Page Composer
•     The Application Data Model, supported by the Data Composer
•     Business Process Management, supported by the Process Composer
•     Business Analytics, supported by the BI Composer

There is a very goog blog The Four Fusion Application Composers Explained written by Richard Bingham. That explains different composers and their use cases. 

Happy Reading.....

Cheers

Fusion Apps Oracle Composer Migration in SaaS environment

Introduction

In an Oracle Cloud Application Services (OCAS) environment for HCM, you can tailor your
implementation using several capabilities that enable customization and extension of business
objects (data), the user interface (UI), and business intelligence reports (BI). For instance, you
can use Oracle Composer customization features to modify the UI to meet your business
needs.
When considering your extensibility implementation approach in an OCAS deployment, Oracle
suggests using a test environment to finalize customizations and extensions before migrating
them to production. The specific purpose of this article is to step you through the
recommended best practices for migrating Oracle Composer customizations between
environments.
Supported Fusion Releases: Release 6 and prior
OCAS-enabled: Yes. Direct Customer-enabled Transaction.

Special Considerations

• If you have Oracle Composer customizations that include deployed flexfields, ensure that
you migrate those flexfields to the target environment prior to migrating UI customizations.
• If you decide to use more than one sandbox to capture Oracle Composer customizations,
ensure that you don’t make changes to the same page in more than one sandbox because
this can cause collision issues when publishing those sandboxes.

Prerequisites

• Ensure source and target OCAS environments (e.g.Test and Production) are at the same
patch level.
• Ensure that you have not published the sandbox. Important: Once you publish a sandbox, it
can no longer be used for migration purposes and it is not possible to recover from this
action.

Here is the oracle White Paper which explains in detail.
Guidance for Managing Customizations in Oracle Cloud Application Services: Oracle Composer Migration [ID 1510578.1]

Cheers.....

BI Migration in SaaS environment

Introduction

In an Oracle Fusion HCM Oracle Cloud Application Services (OCAS) environment, you can
tailor your implementation using several capabilities that enable customization and extension
of business objects (data), the user interface (UI), and business intelligence (BI) reports. For
instance, you can use Reports and Analytics features to customize reports to meet your
business needs.
When considering your extensibility implementation approach in an OCAS deployment, Oracle
suggests using a test environment to finalize customizations and extensions before migrating
them to production. The specific purpose of this article is to step you through the
recommended best practices for migrating BI customizations between environments.
Supported Fusion Releases: Release 6 and prior
OCAS-enabled: Yes. Direct Customer-enabled Transaction.

Prerequisites

• Ensure source and target OCAS environments (e.g. Test and Production) are at the same
patch level.
• Ensure that all reports have been customized, tested, and approved in the source
environment.

There is a very good Oracle White paper on this, which explains in detail the step-by-step operations needed to migrate the custom/modified BI Reports
Guidance for Managing Customizations in Oracle Cloud Application Services: Business Intelligence Migration [ID 1510577.1]