6 Customize Oracle Analytics for Applications

You can customize the semantic model and job roles.

As a modeler or modeler administrator, you can customize your semantic model. Customization enables you to make the data that you moved into the analytics warehouse more useful for reporting. As a security administrator, you create, configure, and assign custom job roles to users. See Manage Custom Job Roles.

About Semantic Model Customization

You can customize the semantic model to make the data that you moved into the warehouse more useful for reporting.

You customize your semantic model by creating branches and adding steps to those branches. You use a branch to test your changes to the model. You can apply the model from the branch to a local service instance for testing. When the changes are correct, you can merge that branch with the main branch. You can merge multiple branches with the main branch over time. When you have a set of changes finalized, you can version the main branch and promote that branch to the production environment.

You can customize the model by extending ready-to-use dimensions with additional attributes from another data source, by adding a fact to an existing subject area, and by reorganizing the ready-to-use subject areas to create a new subject area to name a few.

Create a Branch

To begin customizing your semantic model, create a branch of the main semantic model.

You can add customizations to a test instance only. After you have added and tested your customizations, you can promote them to the production environment. See Promote Your Customizations to the Production Environment.
  1. Sign in to your service.
  2. In Oracle Analytics for Applications, open the Application Navigation menu, click Console, and then click Semantic Model Extensions.
    You see the Semantic Model Extensions page listing the main branch of your semantic model file and any other branches.
  3. On the Semantic Model Extensions page, click Create on the main branch, and then click Create Branch to create a branch as an empty container.
  4. In Create a New Branch, enter a name for your branch, for example, Add Cost Center.
  5. Optionally, add a description and click OK.
    You see the new branch on the Semantic Model Extensions page under Other Branches. You can add steps to the new branch container using the Add Step button or the branch menu. See Add a Step to a Branch

Edit a Branch

Before you apply a branch to the main branch of your semantic model, you can edit the branch.

  1. Sign in to your service.
  2. In Oracle Analytics for Applications, open the Application Navigation menu, click Console, and then click Semantic Model Extensions.
    You see the Semantic Model Extensions page listing the main branch of your semantic model file and any existing branches.
  3. On the Semantic Model Extensions page, under Other Branches, hover over a branch to view the Actions menu.
  4. From the Actions menu, click Edit Branch, and then click Add Step.

Add a Step to a Branch

You can add customization types such as "Extend a Dimension" as a step to an existing unapplied branch or a new branch that you create.

  1. Sign in to your service.
  2. In Oracle Analytics for Applications, open the Application Navigation menu, click Console, and then click Semantic Model Extensions.
    You see the Semantic Model Extensions page listing the main branch of your semantic model file and any existing branches.
  3. On the Semantic Model Extensions page, under Other Branches, hover over a branch to view the Actions menu.
  4. From the Actions menu, click Edit Branch, and then click Add Step.
  5. In Add step, select a customization type such as Extend a Dimension, Add a Fact, Reorganize Subject Area.
    You see the wizard sequence to add details for the selected customization type.

Add a Dimension

Add a custom dimension table to an existing subject area and joins to a fact table.

  1. Sign in to your service.
  2. In Oracle Analytics for Applications, open the Application Navigation menu, click Console, and then click Semantic Model Extensions.
    You see the Semantic Model Extensions page listing the main branch of your semantic model file and any existing branches.
  3. On the Semantic Model Extensions page, under Other Branches, hover over a branch to view the Actions menu.
  4. From the Actions menu, click Edit Branch, and then click Add Step.
  5. In Add Step, select Add a Dimension.
    You see the wizard sequence to add a dimension.
  6. In step 1 of the wizard, enter a name for your customization step, for example, Add Point of Sale Dimension and add a brief description.
  7. Select a target subject area to which you want to add the custom dimension table. For example, Financials - AP Expense.
    You see the details of the selected subject area.
  8. Click Next.
  9. In step 2 of the wizard, select the schema, and then select the dimension table. For example, COST_CENTER_VIEW1.

    Note:

    If you don’t see the schema or table, then ensure that you have granted select permission to the OAX$OAC schema in the autonomous data warehouse. For example, grant select on <schema>.<table> to OAX$OAC. See Load Customization Data to the Autonomous Data Warehouse.
    You see the attributes available in the selected dimension table. You can use the Search and Filter fields to limit the attributes displayed for the dimension table.
  10. Select the attributes that you want to use from the dimension table and indicate an attribute to be used as the key for joining with a fact table in the target subject area.
  11. Optionally, click Create Column to add another column to your dimension table in the target subject area using these instructions:
    1. In Create New Column, enter a display name.
    2. Under Data Elements, search for a data element from the physical table of the selected dimension table.
    3. From the search results, double-click the data element to place it in the text pane.
    4. Under Functions, search for a function to construct a column using expressions. For example, search for functions like "substring" or "concatenate" to construct new expression-based columns. From the search results, double-click the applicable result to add it to the central text pane.
    5. Click Validate, and then click Save.
  12. Click Next.
  13. In step 3 of the wizard, select Skip Joins if you don’t want to join the selected dimension table to any facts. To join the selected dimension table to a fact, select the fact table, fact key, and join type. You had previously selected the dimension table key.

    Note:

    Ensure that the data types of the join key pairs match. If your data types don't match but you want to proceed, then click Yes in the message. However, if the data types can't be absolutely matched, then the server-side validation rejects that join completely and you must change the data type of custom key column to match the factory data type.
  14. Click Add Fact Table to select another fact table to link your dimension to and define the join.
  15. Click Next.
  16. In step 4 of the wizard, assemble the product hierarchy using the attributes from this dimension table with these instructions:
    1. Enter a hierarchy name. For example, Region Hierarchy.
    2. Select, drag, and drop available data elements into the Selected Data elements pane to design a hierarchy that you want. You can add multiple levels in your hierarchy by right-clicking at a level and selecting Add Child or Add ‘n’ Child Levels. For example, your Region Hierarchy can have Region Total at Level 1, Region at Level 2, Country at Level 3, State at Level 4, and City at Level 5.
    3. In the Selected Data Elements pane, click a level to update its primary key and set its display attribute in the Properties pane.
  17. Click Next.
  18. Optionally, in step 5 of the wizard, select additional subject areas to include the new dimension.
  19. Click Finish.
    You see a message that your step is being applied to the customization branch. After it's applied, you see the new customization step in the customization branch. You can now apply the customization branch to the main branch or edit it to add more steps.

Add a Fact Table

Add a fact table to an existing subject area.

  1. Sign in to your service.
  2. In Oracle Analytics for Applications, open the Application Navigation menu, click Console, and then click Semantic Model Extensions.
    You see the Semantic Model Extensions page listing the main branch of your semantic model file and any existing branches.
  3. On the Semantic Model Extensions page, under Other Branches, hover over a branch to view the Actions menu.
  4. From the Actions menu, click Edit Branch, and then click Add Step.
  5. In Add Step, select Add a Fact.
    You see the wizard sequence to add a fact.
  6. In step 1 of the wizard, enter a name for your customization step, for example, Add Travel Expense and add a brief description.
  7. Select a target subject area to which you want to add the fact. For example, Financials - AP Expense.
    You see the details of the selected subject area.
  8. Click Next.
  9. In step 2 of the wizard, select the schema, and then select the source table. For example, FCT_CALC_Extensions.
    You see the fact table for the selected source table.
  10. In the details of the fact table for the selected source table, click the Select Fact and Select Join Key check boxes for the source columns that you want to add to your new fact table in the target subject area.
  11. Optionally, click Create Column to add a new column to your new fact table in the target subject area using these instructions:
    1. In Create New Column, enter a display name.
    2. Under Data Elements, search for a data element from the physical table of the selected dimension table.
    3. From the search results, double-click the data element to place it in the text pane.
    4. Under Functions, search for a function to construct a column using expressions. For example, search for functions like "substring" or "concatenate" to construct new expression-based columns. From the search results, double-click the applicable result to add it to the central text pane.
    5. Click Validate, and then click Save.
  12. Click Next.
  13. In step 3 of the wizard, for each selected fact key column, select join type, dimension table, and dimension key column to define a join to link your new fact table to the dimensions in the selected subject area.
  14. Optionally, click Skip Joins if you don’t want to join a dimension now.
  15. Click Next.
  16. In step 4 of the wizard, select the aggregation rule for each fact column to set the aggregation behaviors.
  17. Optionally, you can set the time-balanced aggregation rule for a time dimension and hierarchy level-based aggregation rule for a dimension using these steps:
    1. For a fact column, click the Time-Balanced Aggregation icon.
    2. In the Time-Balanced Aggregation dialog, click Add Time Dimension, adjust the aggregation rule, and then click OK.
    3. For a fact column, click the Hierarchy Level-Based Aggregation icon, select the dimension and level. Click Add Dimension to add more dimensions. Click OK.

    Use a time-balanced aggregation when the added measure mustn't be "aggregated" by default across a time dimension. Oracle Analytics for Applications supports non-aggregation types like "Last" or "First" in place of the "SUM" aggregation type when required. Use a level-based aggregation when the underlying measure must always be calculated to a specific level of a predefined dimensional hierarchy. For example, if there is a product hierarchy with the following four levels, Product Total, Product Category, Product Sub-Category, and Product Details and you need to add a new measure called "Revenue". If this "Product Category Revenue" measure must always be aggregated to Product Category, then you must use the level-based aggregation and choose the right level of the Product Dimension. This setting enables Oracle Analytics for Applications to always aggregate and show the value of the measure at the Product Category level. This is useful when you need to calculate Product Revenue as a % of Category Revenue.

  18. Click Next.
  19. Optionally, select additional subject areas to add the fact.
  20. Click Finish.
    You see a message that your step is being applied to the customization branch. After it's applied, you see the new customization step in the customization branch. You can now apply the customization branch to the main branch or edit it to add more steps.

Add a Hierarchy

Add a hierarchy to a dimension table in an existing subject area.

  1. Sign in to your service.
  2. In Oracle Analytics for Applications, open the Application Navigation menu, click Console, and then click Semantic Model Extensions.
    You see the Semantic Model Extensions page listing the main branch of your semantic model file and any existing branches.
  3. On the Semantic Model Extensions page, under Other Branches, hover over a branch to view the Actions menu.
  4. From the Actions menu, click Edit Branch, and then click Add Step.
  5. In Add Step, select Add a Hierarchy.
    You see the wizard sequence to add a hierarchy.
  6. In step 1 of the wizard, enter a name for your customization step, for example, Add Region Hierarchy and add a brief description.
  7. Select the subject area, the folder of the dimension table, and the dimension table to which you want to add a hierarchy.
    You see the existing hierarchies and the hierarchy levels in the selected dimension. If there aren’t any hierarchies, then you see a message informing you that there are no hierarchies in the selected dimension.
  8. Click Next.
  9. In step 2 of the wizard, assemble the product hierarchy using the attributes from this dimension table with these instructions:
    1. Enter a hierarchy name. For example, Region Hierarchy.
    2. Select, drag, and drop available data elements into the Selected Data elements pane to design a hierarchy that you want. You can add multiple levels in your hierarchy by right-clicking at a level and selecting Add Child or Add ‘n’ Child Levels. For example, your Region Hierarchy can have Region Total at Level 1, Region at Level 2, Country at Level 3, State at Level 4, and City at Level 5.
    3. In the Selected Data Elements pane, click a level to update its primary key and set its display attribute in the Properties pane.
  10. Click Next.
  11. Optionally, in step 3 of the wizard, select additional subject areas to include the new hierarchy.
  12. Click Finish.
    You see a message that your step is being applied to the customization branch. After it's applied, you see the new customization step in the customization branch. You can now apply the customization branch to the main branch or edit it to add more steps.

Add Session Variables

Add custom session variables that you can include in the analyses.

  1. Sign in to your service.
  2. In Oracle Analytics for Applications, open the Application Navigation menu, click Console, and then click Semantic Model Extensions.
    You see the Semantic Model Extensions page listing the main branch of your semantic model file and any existing branches.
  3. On the Semantic Model Extensions page, under Other Branches, hover over a branch to view the Actions menu.
  4. From the Actions menu, click Edit Branch, and then click Add Step.
  5. In Add Step, select Add Session Variables.
    You see the wizard sequence to add the session variables and a list of existing session variables.
  6. In step 1 of the wizard, check if any of the existing session variables serve your purpose.
    If yes, then you can exit the wizard and use the applicable existing session variables in your analyses. If no, then continue with the next steps to create the session variables that you require.
  7. Enter a name for your customization step, for example, Add a Session variable using Invoice Received Date and add a brief description.
  8. Click Next.
  9. In step 2 of the wizard, define the SQL query and create the initialization block using these instructions:
    1. Enter a name and description for the initialization block.
    2. Optionally, select a preceding initialization block.
    3. Enter the SQL query that would be executed in the autonomous data warehouse and return a value that you can use in the reports. For example, if you want to get the Exchange Rate Type that is defined in Oracle Analytics for Applications into a session variable, then you can use the following SQL script:
      SELECT PARAMETER_VALUE FROM DW_CONTENT_PARAM_CONFIG WHERE
       PARAMETER_CODE='PARAM_GLOBAL_EXCHANGE_RATE_TYPE' 
    4. Click Preview Data to view the data that is returned by the SQL query.
  10. Click Next.
  11. In step 3 of the wizard, create the session variables using the output of the initialization block created in step 2 of the wizard.
  12. Click Finish.
    You see a message that your step is being applied to the customization branch. After it's applied, you see the new customization step in the customization branch. You can now apply the customization branch to the main branch or edit it to add more steps.

Extend a Dimension

Extend ready-to-use dimensions with additional attributes from another data source.

  1. Sign in to your service.
  2. In Oracle Analytics for Applications, open the Application Navigation menu, click Console, and then click Semantic Model Extensions.
    You see the Semantic Model Extensions page listing the main branch of your semantic model file and any existing branches.
  3. On the Semantic Model Extensions page, under Other Branches, hover over a branch to view the Actions menu.
  4. From the Actions menu, click Edit Branch, and then click Add Step.
  5. In Add Step, select Extend a Dimension.
    You see the wizard sequence to extend a dimension.
  6. Enter a name for your customization step, for example, Add Cost Center Type.
  7. Select a target subject area, for example, Financials GL Profitability.
  8. In Folder, select a dimension that you want to extend, for example, Cost Center.
  9. Select a logical table, for example, Dim – Cost Center.
    You see the available attributes in the table.
  10. Click Next.
  11. Select a schema and table from the database.
    You see the available attributes in the table.
  12. Select the columns that you want to expose or use as a key for creating the join.
  13. Click in the Display Name table field to enter a new name for the column or to edit an existing one and then click Enter to accept or click Esc to cancel.
  14. Click Create Column to create a new column in the selected dimension table using these instructions:
    1. In Create a new column, enter a display name, for example, Cost Type.
    2. Under Data Elements, search for a data element from the physical table of the selected dimension table.
    3. From the search results, double-click the data element to place it in the text pane.
    4. Under Functions, search for a function to construct a column using expressions. For example, search for functions like "case" to construct new expression-based columns. From the search results, double-click the applicable result to add it to the text pane.
    5. Click Validate, and then click Save.
  15. Click Save.
  16. Click in the Source Column table field to edit the column definition.
  17. Click Save.
    You see the new column in the Data preview section in a highlighted color.
  18. Click Next.
  19. Select a join key to pair with the source column.
  20. Click Next.
  21. Select the subject areas that should use this customization.

    Note:

    The Subject Area that you initially selected is selected by default and is read-only. By default, all additional subject areas are selected. Deselect the additional subject areas that shouldn’t use this customization.
  22. Click Finish.
    You see the new customization step in the customization branch. You can now apply the customization branch to the main branch or edit it to add more steps.

Reorganize Subject Areas

Reorganize the ready-to-use subject areas to create a new subject area.

  1. Sign in to your service.
  2. In Oracle Analytics for Applications, open the Application Navigation menu, click Console, and then click Semantic Model Extensions.
    You see the Semantic Model Extensions page listing the main branch of your semantic model file and any existing branches.
  3. On the Semantic Model Extensions page, under Other Branches, hover over a branch to view the Actions menu.
  4. From the Actions menu, click Edit Branch, and then click Add Step.
  5. In Add Step, select Reorganize Subject Area.
    You see the wizard sequence to reorganize subject areas to create a subject area.
  6. In step 1 of the wizard, enter a name for your customization step.
  7. From the list of subject areas in your data warehouse, select a primary subject area to create a new subject area, and then click Next.
  8. In step 2 of the wizard, from the primary subject area, select the data elements that you want in your new subject area.
    You see the selected data elements in the Selected Data Elements pane.
  9. Optionally, you can add another subject area and then select the data elements to add to your new subject area.
  10. Click Next.
  11. In step 3 of the wizard, in the new subject area that this process creates with “Custom” prefix, such as Custom – Financials – AP Balances, drag or right-click items to organize and rename them.
  12. In step 4 of the wizard, review your new subject area with its data elements and then click Finish.
    You see a message that your step is being applied to the customization branch. After it is applied, you see the new customization step in the customization branch. You can now apply the customization branch to the main branch or edit it to add more steps.

Edit or Delete a Branch Step

Edit a step to modify the details or delete it if it's no longer required.

  1. Sign in to your service.
  2. In Oracle Analytics for Applications, open the Application Navigation menu, click Console, and then click Semantic Model Extensions.
    You see the Semantic Model Extensions page listing the main branch of your semantic model file and any existing branches.
  3. On the Semantic Model Extensions page, under Other Branches, click a branch to display the steps.
  4. Hover over a step to view the Actions menu.
  5. Click Edit Step and update the details.
  6. Click Delete Step to remove it from the branch.

Copy Steps from One Branch to Another

Use these instructions to copy steps from a customization branch to another customization branch

  1. Sign in to your service.
  2. In Oracle Analytics for Applications, open the Application Navigation menu, click Console, and then click Semantic Model Extensions.
    You see the Semantic Model Extensions page listing the main branch of your semantic model file and any existing customization branches.
  3. On the Semantic Model Extensions page, under Other Branches, click a branch whose steps you want to copy.
  4. On the Branch page, click Manage Steps.
  5. Select the check box for the steps that you want to copy and click Copy.
  6. In Copy Steps, select the target branch to which you want to copy the selected steps and click OK.
    You see a confirmation message that the steps have been successfully copied.

View Details of Failed Branch Steps

You can view the reasons why a branch step had failed and then correct the errors.

  1. Sign in to your service.
  2. In Oracle Analytics for Applications, open the Application Navigation menu, click Console, and then click Semantic Model Extensions.
    You see the Semantic Model Extensions page listing the main branch of your semantic model file and any existing branches.
  3. On the Semantic Model Extensions page, under Other Branches, click the branch with the Failed icon to view the details.
  4. On the Branch details page, click the Failed status for a step that has failed and view the error details.

Merge Other Branches with the Main Branch

Merge the other branches with the main branch to use the customization steps as the sequence of steps.

The main branch lives in the test environment. When you edit a branch, the system automatically locks it to prevent another user from simultaneously editing the same branch. As you complete each step or reorder the steps, the system unlocks the branch, saves it, and notes the change in the change log tab.
  1. Sign in to your service.
  2. In Oracle Analytics for Applications, open the Application Navigation menu, click Console, and then click Semantic Model Extensions.
    You see the Semantic Model Extensions page listing the main branch of your semantic model file and any existing branches.
  3. On the Semantic Model Extensions page, under Other Branches, hover over a branch to view the Actions menu.
  4. From the Actions menu, click Merge to Main Branch, and then click Ok.

    The system updates the time stamp on the main branch and you see an indicator on the main branch that changes have been applied since the last version was saved.

    While applying a branch to the main branch, if the system detects that a new version has since been saved, then your check-in is out of synchronization. You see a message explaining that the system has detected a conflict while synchronizing. For example:
    1. You create a branch based on main branch version 1.0.
    2. You add steps to your branch.
    3. Meanwhile, a new version of main branch saved as 1.1.
    4. You attempt to check in your branch.
    5. The system detects a conflict while synchronizing and notifies you.

Reorder Steps of Other Branches

You can reorder the steps in a branch that has been applied or is yet to be applied to the main branch.

  1. Sign in to your service.
  2. In Oracle Analytics for Applications, open the Application Navigation menu, click Console, and then click Semantic Model Extensions.
    You see the Semantic Model Extensions page listing the main branch of your semantic model file and any existing branches.
  3. On the Semantic Model Extensions page, under Other Branches, click a branch to display the steps.
  4. Click Reorder Steps to enable Drag mode to reorder the steps.
    You see the drag handles appear on each row. The branch menu and Add Step button aren’t available during the reorder process.
  5. Drag and drop the steps in the new order that you want.
  6. Click Done Reordering.
    You see a validation message and after the validation is complete, the branch menu, Add Step, and Reorder Steps buttons are available.
  7. Click Merge to Main Branch to re-apply this branch and update the main branch with the changes.

Create a Version of the Main Branch

Once you have a set of customizations ready for promotion and merged them with the main branch, you must version the main branch.

You later promote the version to the production environment. See Promote Your Customizations to the Production Environment.
  1. Sign in to your service.
  2. In Oracle Analytics for Applications, open the Application Navigation menu, click Console, and then click Semantic Model Extensions.
    You see the Semantic Model Extensions page listing the main branch of your semantic model file and any existing branches.
  3. On the Semantic Model Extensions page, click Create on the main branch, and then click Create Version.
  4. In the Create a New Version dialog, enter a name of the main branch version.
  5. Select a merged branch that you want to include in this version.
  6. Click OK.

Edit or Delete a Main Branch Step

As a modeler administrator, you can edit and delete all steps that have been either applied or have failed. With modeler permissions, you can edit and delete only failed steps.

  1. Sign in to your service.
  2. In Oracle Analytics for Applications, open the Application Navigation menu, click Console, and then click Semantic Model Extensions.
    You see the Semantic Model Extensions page listing the main branch of your semantic model file and any existing branches.
  3. On the Semantic Model Extensions page, click the Main Branch to view the details.
  4. Hover over a step to display the options.
  5. Click Edit Step and update the details.
  6. Click Delete Step to remove it from the main branch.

Create a Version of the Main Branch

Once you have a set of customizations ready for promotion and merged them with the main branch, you must version the main branch.

You later promote the version to the production environment. See Promote Your Customizations to the Production Environment.
  1. Sign in to your service.
  2. In Oracle Analytics for Applications, open the Application Navigation menu, click Console, and then click Semantic Model Extensions.
    You see the Semantic Model Extensions page listing the main branch of your semantic model file and any existing branches.
  3. On the Semantic Model Extensions page, click Create on the main branch, and then click Create Version.
  4. In the Create a New Version dialog, enter a name of the main branch version.
  5. Select a merged branch that you want to include in this version.
  6. Click OK.

Test a Branch

You can test the main development branch and the other branches to ensure that there are no errors.

  1. Sign in to your service.
  2. In Oracle Analytics for Applications, open the Application Navigation menu, click Console, and then click Semantic Model Extensions.
    You see the Semantic Model Extensions page listing the main branch of your semantic model file and any existing branches.
  3. To test the main development branch, select the Main branch, click Actions menu, and then click Test Model.
    You can select the main branch, or a version of the main branch, or select the option to reset the main branch to the original state before any customizations were merged with the main branch.
  4. To test the other branches, select a branch, click Actions menu, and then click Test Branch.

Load Customization Data to the Autonomous Data Warehouse

You can load your customization data to the autonomous data warehouse provisioned with your Oracle Analytics for Applications instance.

  1. Connect to the autonomous data warehouse corresponding to your Oracle Analytics for Applications instance.
    You need the autonomous data warehouse wallet and credentials of the administrator. The credentials of the administrator are same as what you had mentioned for the autonomous data warehouse resource while creating the Oracle Analytics for Applications instance. See Create an Oracle Analytics for Applications Subscription Instance.
  2. Create a custom schema to store the customization data.

    Syntax: create user <custom_schema-name> identified by <custom_schema-password>;

    Example: create user example_schema identified by abcDEF123654;

  3. Create one or more tables in the custom schema that you created.

    Syntax: CREATE TABLE <custom_schema-name>.<custom_extent_table_name> (<parameters>));

    Example: CREATE TABLE example_schema.ABC_EXTN ("DATE" DATE, "CATEGORY" VARCHAR2(1024 BYTE) , "MANAGER" VARCHAR2(1024 BYTE) );

  4. Populate the required data and grant select permissions to the OAX$OAC schema in the autonomous data warehouse using this script:

    Syntax: grant select on <custom_schema-name> to OAX$OAC;

    Example: grant select on example_schema.ABC_EXTN to OAX$OAC;

  5. Commit the changes to the autonomous data warehouse and disconnect.

Promote Your Customizations to the Production Environment

Once you have a set of changes to the semantic model, customized job roles, and customized KPIs ready for promotion, you can version the main branch, and then promote the version to the production environment. You can also reset the last promoted main branch with the original main branch before any customizations were merged with it.

  1. Sign in to your service.
  2. In Oracle Analytics for Applications, open the Application Navigation menu, click Console, and then click Promote Objects.
    You see the Promote Objects page.
  3. On the Promote Objects page, select the target environment to which you want to publish your customizations.
  4. Select the customized objects that you want to promote to the target environment.
    For example:
    • Select the Semantic Model Extensions check box and the saved version of the main branch or the original main branch.
    • Select the Security Customizations check box to promote the customized job roles.
    • Select the KPIs check box, click Choose KPIs, search for and select the customized KPIs that you want to promote, and then click OK.
  5. On the Promote Objects page, click Promote.
  6. Click Check Status to view the progress.

View Activity History

View an audit of all activities performed on the semantic model.

  1. Sign in to your service.
  2. In Oracle Analytics for Applications, open the Application Navigation menu, click Console, and then click Semantic Model Extensions.
    You see the Semantic Model Extensions page listing the main branch of your semantic model file and any existing branches.
  3. Click Activity History to view an audit of all activities performed on the semantic model.
  4. Hover over an activity to view details of the activity.