Import the Semantic Model

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

When you merge external applications, set a unique name. If you use the same name, the system replaces the application. Merging integrates changes from the current and new semantic model, combining the existing customizations with newly introduced customizations.

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 reusing the existing application name or by directly replacing the application.

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, enter a new distinct description name, or use the name of an existing external application to replace it in External Application Description, select Semantic Model Import, and click Select Semantic Model to import the applicable Oracle Analytics Cloud semantic model from your local machine, and enter the password that you use to encrypt the semantic model file.
   
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 custom data configurations (for example, 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 fix the errors in the external semantic model and try again.
     
     
     
     

   See How do I resolve inconsistent activated modules between the environment and the semantic model template?

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.