Import Semantic Model

Use the Semantic Model Import option to merge your semantic model.

Semantic Model Import option is available during initial import when Upload Multiple External Applications is disabled, and it’s always available when Upload Multiple External Applications is enabled. When Upload Multiple External Applications is disabled, use Replace Application to replace the existing application. See Replace Application.

When merging External Applications, the Upload Multiple External Applications setting determines whether the system replaces an existing application or creates an additional one.

• If Upload Multiple External Applications is disabled (Single External Application - recommended), the External Application name has no effect, and the existing application is always replaced.
• If Upload Multiple External Applications is enabled (Multiple External Applications - recommended only for important business case requirement), using the same name replaces the existing application, while using a different name creates an additional External Application and merges changes from both the current and new semantic models, combining existing customizations with newly introduced customizations.

Use environment-agnostic names for the external application semantic models. Don't use environment-specific suffixes (such as Test, Dev, and Prod) in the semantic model name because this might cause the target instance to merge the semantic model instead of replacing the semantic model.

Note:

Import a newer version of the Semantic Model for merging only if some changes are missing in your current version. Importing multiple versions can cause delays due to increased validation and merging requirements. If your updated Semantic Model already includes all the previous changes, it is recommended you replace the model rather than create additional versions. You can replace the model by disabling Upload Multiple External Applications, reusing the existing application name, or directly replacing the existing application. If multiple versions of the application were unintentionally imported, delete the older duplicate versions and disable Upload Multiple External Applications to prevent future accidental duplication. Retain only the latest version, provided it encompasses all the changes from the previous imports.

1. Sign in to your service.
2. In Oracle Fusion Data Intelligence Console, click Semantic Model Extensions under Application Administration.
3. In the External Application region, click Actions, and then click Import Application to import the external semantic model.
4. In Select Application and Content to Merge, if Upload Multiple External Applications is disabled (recommended), you can provide any application name. If Upload Multiple External Applications is enabled for a business case requirement, use the name of the existing external application to replace the application when the semantic model already includes all previous customizations and changes, or use a different name to merge changes from both current and new semantic models.
   
5. In Resolve imported content conflicts, choose the option to rename the imported objects with either a prefix or suffix when a conflict occurs.
6. Select Expose custom columns in out of the box subject areas to expose columns added to the conformed dimensions in all the applicable subject areas.
7. If you have enabled the Manual Execution of Apply System Extensions reporting global parameter to delay applying the system extensions, but now you want to reapply the system extensions, select Reapply System Extensions.

   When you select Reapply System Extensions, the newly created objects such as data augmentations, applications, and data applications (for example, Frequent Data Refresh, Descriptive Flex Fields, Configurable Account Analysis, Fusion Accounting Hub, and Supply Chain Planning Application) are made available for reference in the semantic model before the external application is imported and merged. This guarantees inclusion of all the necessary system customizations for the external application, but the overall time required for the merge process increases.

   You must Reapply System Extensions if you have extended prebuilt dimensions and have selected to Expose custom columns in out of the box subject areas.

   See Set Up the Global Report Parameters and Apply System Extensions.

8. Click Validate.
   The system validates the external semantic model and displays a report in the Validation tab. The different statuses are:

   • When you import, the status is Validation InProgress.
   • If there aren’t any errors and validation is complete, the status is Validation Successful. The system displays the Merge Application button; click it to complete the merge process.
   • If there are errors, the status is Validation Failed. The system displays the errors and doesn’t initiate the merge. You must review the validation report, fix the errors in the external semantic model, and try again. See View Validation Report.
9. On the Semantic Model Extensions page, click the Activity tab to verify that the validation process has completed and then click Merge Application.
   The initial status is InProgress; while in progress you may see it as Merged but its still running. When it finishes, you see the External Application Merge activity in Done status.