How Deploying a Flexfield-Enabled Sandbox Works with Mainline Metadata

When you deploy a flexfield to a sandbox, the flexfield definition corresponds to the flexfield metadata definition in the Oracle Fusion Cloud Applications database. When the flexfield is ready for use, it must be deployed to the mainline metadata.

A flexfield-enabled sandbox uses the following components.

Flexfield metadata in the Fusion Applications database
Flexfield business components in a sandbox Oracle Metadata Services (MDS) repository
User interface modifications for the flexfield in the mainline MDS repository

The figure shows a flow in the Define Flexfields activity that includes testing the flexfield in a sandbox and possibly also making modifications to the MDS data in Oracle Composer after deploying the flexfield to the mainline metadata for access to users.

Sandbox Metadata Services Repository Data

Deploying the flexfield to a sandbox generates the Application Development Framework (ADF) business components of a flexfield in a sandbox MDS Repository for testing in isolation.

Caution:

Don't modify flexfield segment display properties using Page Composer in a flexfield sandbox as these changes are lost when you deploy your flexfield to the mainline metadata.

Mainline Metadata Services Repository Data

The Oracle Fusion Cloud Applications database stores the single source of truth about a flexfield. When the flexfield is deployed, the ADF business component objects that implement the flexfield in the run time user interface are generated in the mainline MDS Repository from this source.