1. Configuring Business Intelligence Applications
  2. About Administering and Maintaining Functional Configuration Data

3 About Administering and Maintaining Functional Configuration Data

During an Oracle Business Intelligence Applications (Oracle BI Applications) deployment project, you use Oracle BI Applications Configuration Manager (Configuration Manager) and Functional Setup Manager (FSM) to manage and make changes to configuration values for Data Load Parameters, Domains and Mappings, and Reporting Parameters.

Functional Configuration Data for Oracle BI Applications is:

  • Configured using Functional Tasks in FSM.

  • Monitored and updated using Configuration Manager.

Functional Configuration Data for Oracle BI Applications is information about the following:

  • Domains and mappings

  • Data load parameters

  • Reporting parameters

Roadmap for Setup Data Maintenance and Administration

Follow this high-level roadmap for Setup Data Maintenance and Administration.

Prerequisites:

Before you configure Oracle BI Applications, you must install and set up Oracle BI Applications according to the instructions in Installing and Setting Up Oracle BI Applications in Oracle Business Intelligence Applications Installation Guide.

  1. During the Functional Configuration stage, you typically use Configuration Manager to monitor the setup data values that have been specified using Tasks in FSM.

    • To monitor Domain Mappings, in Configuration Manager, select the Manage Domain Mappings and Hierarchies link from the Tasks bar to display the select Manage Domain Mappings and Hierarchies dialog.

      Description of 103-roadmap-step1.gif follows
      Description of the illustration 103-roadmap-step1.gif

      Alternatively, in FSM, select the Go to Task link for a Task that updates a Domain or Domain Member mappings. For example, the Task name 'Manage Domains and Member Mappings for Employee Dimension' updates Domain and Domain Member Mappings.

    • To monitor Data Load Parameters, select the Manage Data Load Parameters link from the Tasks bar to display the Manage Data Load Parameters dialog.

      Description of 103-roadmap-step1b.gif follows
      Description of the illustration 103-roadmap-step1b.gif

      Alternatively, in FSM, select the Go to Task link for a Task that updates a Data Load Parameter value. For example, the Task named 'Configure Data Load Parameter Workforce Adjusted Service Date' updates a Data Load Parameter value.

    • To monitor Reporting Parameters, select the Manage Reporting Parameters link from the Tasks bar to display the select Manage Reporting Parameters dialog.

      Description of 103-roadmap-step1c.gif follows
      Description of the illustration 103-roadmap-step1c.gif

      Alternatively, in FSM, select the Go to Task link for a Task that updates a Reporting Parameter. For example, the Task named 'Configure Reporting Parameters for Year Prompting' updates a Reporting Parameter.

    Tip:

    Domain values can be used to define delivered business metrics; therefore, you must review the delivered domain member values and map them to the correct source values.

  2. During Functional Configuration of purchased Offerings, you use FSM to monitor the status of Tasks and the setup data values that have been set.

    For example, you might use the Status column in the Implementation Project page in FSM to assess the number of completed tasks.

  3. If required, you use Configuration Manager to make changes to the configuration values. See Changing Configuration Values Using Configuration Manager.
  4. If required, you use Configuration Manager to add Domains or Domain Member values. See Adding Target Domain Members.
  5. If required, you use Configuration Manager to configure Externally Conformed Domains. See Configuring Externally Conformed Domains.

About Working With Domains and Domain Mappings

Domains are pre-seeded dimensional values that help define business metrics. For example, in Financial Analytics, domains store information about the General Ledger accounts.

Domains are typically located in the source system. If domains are not available in a source system, then they can be sourced from a flat file. For example, domains for Oracle Price Analytics are loaded using the flat file file_domain_member_gs.csv. This file will also be used in order to supply source domains for Universal adaptor.

To manage Domains, you use these dialogs:

Why Are Some Domains Non-Extensible?

To maintain data integrity in Oracle BI Applications, some domains have been designed as non-extensible, and are therefore read-only.

If a domain is non-extensible, then when the domain is selected, the following options are greyed out:

  • the Edit icon in the Domain Member Mappings pane (on the Manage Domain Mappings and Hierarchies: Domain Mappings tab or Manage Domain Mappings and Hierarchies: Warehouse Domain Hierarchies tab).

  • the Add Target Domain Member button (on the Edit Domain Member Mappings dialog).

  • the Add Warehouse Domain Member button (on the Manage Warehouse Domains: Warehouse Domains tab\Warehouse Members pane).

About Domain Mappings and Domain Member Mappings

Domain Mappings specify how data in a source system is extracted and loaded into Oracle Business Analytics Warehouse. For example, the data in domain Source Group Account (BI_GROUP_ACCOUNT) extracts and loads into the domain Group Account (W_GL_GROUP_ACCOUNT).

Domain Members are the permitted values for a Source or Warehouse Domain. For example, the Domain Members for MARITAL_STATUS include D for Divorced, M for Married, S for Single, and so on.

Tip:

Domain values can be used to define delivered business metrics; therefore, you must review the delivered domain member values and map them to the correct source values.

Domain Mappings specify how entities in a Source System application are loaded into Oracle Business Analytics Warehouse.

The screenshot shows example domain mappings for Oracle Financial Analytics.

Description of 103-domain-mapping.gif follows
Description of the illustration 103-domain-mapping.gif

Domain Member Mappings specify how domain member data in a source system is extracted and loaded into domain member data in Oracle Business Analytics Warehouse. For example, in Oracle HR Analytics, domain Gender (W_SEX_MF_CODE) has a source value 'Male' that is mapped to a domain member value 'M' in Oracle Business Analytics Warehouse.

About Regular Domains and Band Domains

There are two types of Domains.

Regular Domains

Regular Domains have members consisting of a single value. For example, members for a Purchase Order Status domain might have the following members:

  • Cancelled

  • Closed

  • Incomplete

These single values map to single member values in the target system. For example, Cancelled maps to Cancelled, Closed maps to Closed, and so on.

Band Domains

Band Domains have members consisting of two values (Range Start, and Range End) that specify a range. For example, an Account Employee Size domain might have the following members:

  • 1, 5000

  • 5001, 10,000

  • 10,001, 1,000,000.

Each range maps to a single target Domain Member. For example, 1, 5000 maps to Small, 5001, 10,000 maps to Medium, and so on.

About Source Domains

Data fields in a Source System application are referred to as Source Domains.

The screenshot shows example source domains for Oracle Financial Analytics. Source Domains displayed on the Source Domains tab are read-only.

Description of 103-source-domains.gif follows
Description of the illustration 103-source-domains.gif

About Warehouse Domains

Data fields in Oracle Business Analytics Warehouse are referred to as Warehouse Domains.

The screenshot shows example warehouse domains for Oracle Financial Analytics.

Description of 103-warehouse-domains.gif follows
Description of the illustration 103-warehouse-domains.gif

About Warehouse Domain Hierarchies

Warehouse Domain Hierarchies are Domains that have been organized into hierarchies to enable the data to be more effectively analyzed. For example, in Oracle HR Analytics, you might need to have a workforce event hierarchy: Event Group -> Event Sub-group -> Event Detail.

Domain Hierarchies are displayed in inverted format, that is in the following format:
<Child 1>\
     <Child n>\
          <Parent>

Viewing Domain Hierarchies

To view Domain Hierarchies, select the Manage Domain Mappings and Hierarchies link on the Tasks bar, then display the Warehouse Domain Hierarchies tab.

The screenshot shows example warehouse domain hierarchies for Oracle Financial Analytics.

Description of 103-domain-hierarchies.gif follows
Description of the illustration 103-domain-hierarchies.gif

In the screenshot, the child node AP Transaction Subtype is shown above and to the left of the parent node AP Transaction Type. Domain Hierarchies are read-only. However, you can change the domain mappings.

For Warehouse Domains Hierarchies dialog field-level help, see Manage Domain Mappings and Hierarchies: Warehouse Domain Hierarchies Tab in Oracle Business Intelligence Applications Functional Configuration Reference.

About Setting Up Domain Member Mappings

Oracle BI Applications ships default domain value mappings that map the seeded BI Application domain values to the seeded configuration data in Oracle Enterprise Resource Planning applications.

When you configure your Offerings, you review the default mappings for domain values, and if necessary update them to suit the categories that you want to use to report on your data.

For example, in Oracle HR Analytics, the default domain values for Performance Range might be similar to the following:

0 - 50: PERF_RANGE_1

50 - 60: PERF_RANGE_2

60 - 70: PERF_RANGE_3.

If you want to use these default categories, you do not need to make any changes to these mappings before you start your ETL processes.

For example, you might want to change the range for PERF_RANGE_1 from 0 - 50 to 0 - 100. Or you might want to add a new category named PERF_RANGE_4 and assign the range 100 - 500 to the new PERF_RANGE_4 category.

Editing a Domain Member Mapping

You can edit a Domain Member Mapping if you need to change it from the default values.

  1. Navigate to the Domain that you want to edit.

    To display the Domain Mapping tab:

    • In Configuration Manager, select Manage Domain Mappings and Hierarchies in the Tasks pane, display the Domain Mappings tab, then select a Domain.

    • In FSM, select the Go to Task link for a Task that updates a Domain or Domain Member Mappings.

  2. Scroll down to the Domain Member Mappings pane.
  3. Click the Edit Domain Member Mappings icon.
  4. Edit the domain mapping values.

    Note:

    If you change existing values, then the records already loaded in the data warehouse are not modified and only new records are changed. Because new records are changed in this way, you must run a full load. However, if the change involves a new source member that is imported from the source, then all dimension records impacted due to that import are new. Because the dimension records are new, you need not run a full load.
Adding a Range Member Mapping

You can add a Range Member Mapping to a domain for which you can specify ranges.

  1. Navigate to the Domain that you want to edit.

    To display the Domain Mapping tab:

    • In Configuration Manager, select the Manage Domain Mappings and Hierarchies link in the Tasks pane, display the Domain Mappings tab, then select a banded (or ranged) Domain.

    • In FSM, select the Go to Task link for a Task that updates a banded or ranged Domain or Domain Member Mappings.

  2. Scroll down to the Domain Member Mappings pane.
  3. Click the Edit Domain Member Mappings icon to display the Edit Domain Member Mappings dialog.
  4. Click the Add Range Domain Member Mapping icon and specify values in the Range Start, Range End, and Target Domain Members - Code fields.

    Tip:

    Before you create a new range, you might first want to use the Add Warehouse Member button to first create a target Warehouse Member, which is then available as an option in the Target Domain Member - Code list. For example, you might add a Warehouse Member called 'Greater than 250,000' to map to the range 250,000 to 1,000,000.
Adding a Target Domain Member

You add Target Domain Members to extend Oracle Business Analytics Warehouse.

  1. Navigate to the Domain that you want to edit.

    To display the Domain Mapping tab, do one of the following:

    • In Configuration Manager, select the Manage Domain Mappings and Hierarchies link in the Tasks pane, display the Domain Mappings tab, then select a Domain.

    • In FSM, select the Go to Task link for a Task that updates a Domain or Domain Member Mappings.

  2. Scroll down to the Domain Member Mappings pane.
  3. Click the Edit Domain Member Mappings icon to display the Edit Domain Member Mappings dialog,
  4. Click the plus sign (+) icon (Add Warehouse Domain Member) to display the Add Target Domain Member dialog, which enables you to specify a Name, Code, and optional Description.
    Description of 103-add-target-domain-member3.gif follows
    Description of the illustration 103-add-target-domain-member3.gif

    For example, you might add a Warehouse Member called 'Greater than 250,000' to map to the range 250,000 to 1,000,000.

    If the Add Target Domain Member option is grayed out or not displayed, then the domain is non-extensible.

    When you click OK to return to the Edit Domain Member Mappings dialog, you can map a Source Domain to the Target Domain that you just created.

Localizing a New Domain Member

If you added a new domain member and it requires localization, you can add string localizations for Configuration Manager metadata.

  1. Open a database administration tool, and connect to the Oracle Business Analytics Warehouse schema.
  2. Query for the table C_DOMAIN_MEMBER_TL and the new domain member record you added in Adding a Target Domain Member.

    You can query for the new domain member record by using the query filter on the columns CREATED_BY and CREATION_DATE. Each new domain member record will have 28 rows in the C_DOMAIN_MEMBER_TL table.

  3. Update the LANGUAGE_CODE column to match the localized deployment language.
    1. Identify the language code for the localized language using the following SQL:
      SELECT LANGUAGE_CODE, NLS_LANGUAGE, NLS_TERRITORY
FROM FND_LANGUAGES_B
WHERE INSTALLED_FLAG IN ('B', 'I');
    2. Update the domain member name, description, and source language code strings for the localized language using the following SQL:

      In this example, the localized language is Arabic, and the LANGUAGE_CODE is AR.

      UPDATE C_DOMAIN_MEMBER_TL
SET DOMAIN_MEMBER_NAME = '<Arabic translated string for domain member name>', DOMAIN_MEMBER_DESCR = '<Arabic translated string for domain member description>', SRC_LANGUAGE_CODE = 'AR'
WHERE DOMAIN_KEY = '<Domain key value for the record you want to update>'
AND DOMAIN_MEMBER_CODE = '<Domain member code value for the record you want to update>'
AND LANGUAGE_CODE = 'AR';
  4. Exit the database administration tool.
  5. Restart the Oracle WebLogic Server.
Adding String Localizations for Oracle BI Repository Metadata

If you added a new domain member, you can add string localizations in the Oracle BI Repository metadata.

  1. Stop the OPMN services.

    Use the command: opmnctl stopall.

  2. Open a database administration tool, and connect to the Oracle Business Analytics Warehouse schema.
  3. Identify the strings for the following presentation objects:
    • Subject area
    • Presentation table
    • Presentation hierarchy
    • Presentation level
    • Presentation column

    For example, for the subject area Payables Invoices - Prepayment Invoice Distributions Real Time, enter the following strings:

    String Presentation Object

    Payables Invoices - Prepayment Invoice Distributions Real Time

    Subject area

    Time

    Presentation table

    Date - Year

    Presentation hierarchy

    Total

    Presentation level

    Year

    Presentation level

    Calendar Year

    Presentation column
  4. For each subject area, externalize the strings for localization and generate custom names for the presentation objects:
    1. In the Oracle BI Administration Tool, right-click the subject area and select Externalize Display Names, and then select Generate Custom Names.
    2. Save your work.

    See Localizing Metadata Names in the Repository in System Administrator's Guide for Oracle Business Intelligence Enterprise Edition.

  5. Check the consistency of the repository, and remove any inconsistencies.

    See Checking the Consistency of a Repository or Business Model in Metadata Repository Builder's Guide for Oracle Business Intelligence Enterprise Edition.

  6. Enter the custom name of one of the presentation objects into the table C_RPD_MSGS:
    INSERT INTO C_RPD_MSGS(MSG_ID, CREATED_BY, CREATION_DATE)
VALUES('<CUSTOM NAME OF PRESENTATION OBJECT>', 'CUSTOM', SYSTIMESTAMP);
COMMIT;

    To view the values for custom names and logical columns in the Oracle BI Administration Tool, right-click the presentation object and select Properties. The data in the Custom display name field appears in the format VALUEOF(NQ_SESSION.VALUE, where VALUE is the custom name for a presentation object, or the logical value for a presentation column. This value is the value that you need to enter in the VALUES section of the SQL statement above.

  7. Enter the localized string for the presentation object in the previous step into the table C_RPD_MSGS_TL:
    INSERT INTO C_RPD_MSGS_TL(MSG_ID, MSG_TEXT, LANGUAGE_CODE, CREATED_BY, CREATION_DATE)
VALUES('<CUSTOM NAME OF PRESENTATION OBJECT>', '<LOCALIZATION OF THE STRING'>, '<LANGUAGE CODE FOR TRANSLATED LANGUAGE>', 'CUSTOM', SYSTIMESTAMP);
COMMIT;

    To identify the language code for a particular language, use the following SQL:

    SELECT LANGUAGE_CODE, NLS_LANGUAGE, NLS_TERRITORY
FROM FND_LANGUAGES_B
WHERE INSTALLED_FLAG IN ('B', 'I');
  8. Enter additional details about the presentation object into the table C_RPD_MSGS_REL as indicated by the following SQL:
    INSERT INTO C_RPD_MSGS_REL(MSG_ID, MSG_NUM, MESSAGE_TYPE, CREATED_BY, CREATION_DATE)
VALUES('<CUSTOM NAME OF PRESENTATION OBJECT>', '<TRANSLATION OF THE STRING'>, '<LANGUAGE CODE FOR TRANSLATED LANGUAGE>', 'METADATA','CUSTOM', SYSTIMESTAMP);
COMMIT;
  9. Repeat steps 6 through 8 for each presentation object requiring localization.
  10. Validate that the physical connection of the session initialization block INIT_USER_LANGUAGE_CODE is operable:
    1. In the Oracle BI Administration Tool, select Manage, Variables, Session Initialization Block.
    2. Right-click INIT_USER_LANGUAGE_CODE.
    3. In the Properties dialog, click Edit Data Source.
    4. Click Test, and input the value for the language code. Then, click OK.

      For example, for Arabic enter 'AR'.

      The value USER_LANGUAGE_CODE = '<language code>' should be returned.

      If this value is not returned, the TNS entry for the data source is not properly configured.

  11. Restart the OPMN services.
  12. Verify the localized strings in Oracle BI Answers. On the login page, specify the appropriate language.
Synchronizing a Target Domain with a Source Domain

In some scenarios, you might only know what target Domain member values should be when you deploy Oracle BI Applications.

For example, in Order Management or Supply Chain Analytics, UOM (Unit of Measurement) is typically not known until deployment time. You can set up a non-ranged target domain using the Sync to Source option to automatically synchronize a target domain with values from the source domain. This process inserts new target members from the source domain, and automatically generates 1:1 mappings. This is useful for large domains with many member mappings that might otherwise take a long time to set up.

Sync to Source is only available for extensible non-ranged Domains.

  1. Navigate to the Domain that you want to synchronize.

    If you are in Configuration Manager, from the Tasks bar click Manage Domains and Mappings, display the Domain mappings tab, select the Domain that you want to edit, then click the Edit Domain Member Mappings icon in the Domain Member Mappings pane to display the Edit Domain Member Mappings dialog.

    If you are in FSM, when you click Go to Task for the Task that is updating a Domain, you display the Edit Domain Member Mappings dialog.

    Description of 103-sync-source1.gif follows
    Description of the illustration 103-sync-source1.gif
  2. Click Sync to Source.

    Target Domain member values are generated. In the example below, the target codes for "Year" are automatically synchronized with the source domain member codes.

    Image displays the target domain member values that are generated when you click the Sync to Source button.
Updating Multiple Target Domain Member Values

You can set up a target domain using the Batch Edit option to update multiple target domain members with the same value. This is useful for large domains with many member mappings that require the same value.

  1. Navigate to the Domain that you want to edit.

    If you are in Configuration Manager, from the Tasks bar click Manage Domains and Mappings, display the Domain mappings tab, select the Domain that you want to edit, then click the Edit Domain Member Mappings icon in the Domain Member Mappings pane.

    If you are in FSM, click Go to Task for the Task that is updating a Domain.

    Description of 103-batch-edit-domain-member-mapping.gif follows
    Description of the illustration 103-batch-edit-domain-member-mapping.gif
  2. Ctrl + click to multi-select one or more rows in the table.
  3. Select a value from the Batch Edit drop-down list.
  4. Click Change to apply the value selected in the Batch Edit drop-down list to all specified members.

Modifying a Warehouse Domain Hierarchy

Oracle BI Applications Warehouse Domains are organized into hierarchies. You might want to modify a hierarchy to enable data to be more effectively analyzed. For example, you might change the order of items in a hierarchy.

  1. In the Domain mappings list, select the Domain Mapping that you want to edit.
  2. Use the options at the top of the Domain Mapping list to change the hierarchy.

Configuring Externally Conformed Domains

You can manage and create conformed domains in Oracle Business Analytics Warehouse that are based on definitions in a source system. For example, you might want to configure Units of Measure (UOMs) that are sourced from a pre-defined master product-line (typically Fusion) source domain.

  1. In Configuration Manager, select the Manage Externally Conformed Domains link in the Tasks pane to display the Manage Externally Conformed Domains dialog.
  2. Use the Product Line drop-down list to select a source system.

    When a source system is selected, domains for that source system are displayed.

    Description of 103-externally-conformed-domains2.gif follows
    Description of the illustration 103-externally-conformed-domains2.gif

    Note:

    If your implementation requires user-conformed domains that don't have default predefined values other than Not Applicable and Unassigned, then you can add applicable values using the Manage Warehouse Domains page. Search for the applicable domain and select it from the search results. This enables the Add (+) button. You can then use the Manage Externally Conformed Domains page to enter the domain values and later use the Manage Domain Mappings and Hierarchies page to map the values.
  3. In the domains list, select the Domain that you want to configure and click Configure Domain to start the configuration wizard.

    Note:

    If a domain has already been configured, before you can configure the domain using the wizard, you must first delete the existing configuration by clicking Delete Domain Configuration.

    If a domain has already been configured, a green tick is displayed in the Configured? field, and the unique ID of the data source is displayed in the Referenced Data Source field.

  4. Follow the on-screen instructions on the configuration wizard.
  5. Click Save.

    If you include the configured domain in a Load Plan for ETL, the data is loaded into Oracle Business Analytics Warehouse from the specified source domain.

About Working With Data Load Parameters

Data Load Parameters are configuration values that specify how Source System data is loaded into Oracle Business Analytics Warehouse. For example, the cost time grain parameter COST_TIME_GRAIN specifies whether costs are aggregated weekly, monthly, or quarterly, during the data loading process.

When you work with Data Load Parameters in Configuration Manager, note the following key points:

  • Data Load Parameters can be either Global or Application Specific, as follows:

    • Global parameters apply to all applications, and are indicated with the (ab) and globe icon:

      This graphic is described in surrounding text.

      Global Data Load Parameters can also be associated with specific Fact Groups or Dimension Groups.

    • Application Specific apply to specific applications, and indicated with the (ab) icon:

      This graphic is described in surrounding text.

      Application Specific Data Load Parameters are always associated with one or more Fact Groups or Dimension Groups.

  • If a Global Data Load Parameter is associated with one or more Fact Groups or Dimension Groups, then each Fact Group or Dimension Group can have a different value. For example, the value of Slowly Changing Dimension Flag for Absence Event Dimension might be Yes, and the value of Slowly Changing Dimension Flag for Asset Dimension might be No.

    Values for Global Group-specific parameters are always overridable, and are indicated by the Overridable Parameter icon (that is, the (ab) icon with a pencil):

    This graphic is described in surrounding text.

    The example below shows the Slowly Changing Dimension Flag global parameter with associated Group-specific values displayed in the lower pane.

    Description of 103-global-parameter.gif follows
    Description of the illustration 103-global-parameter.gif

  • For Application Specific Data Load Parameters, values for associated Fact Groups or Dimension Groups can either be Overridable or Non-Overridable, as follows:

    Overridable - each associated Fact Group or Dimension Group can have a different value. Overridable parameters are indicated by the Overridable Parameter icon (that is, the (ab) icon with a pencil):

    This graphic is described in surrounding text.

    Non-Overridable - each associated Fact Group or Dimension Group must have the same value. Non-Overridable parameters are indicated by the Parameter icon (that is, the (ab) icon without a pencil):

    This graphic is described in surrounding text.

    The example below shows the Application Specific parameter 'Subledger Module List' with associated Group-specific values displayed in the lower pane. Note that the Group-specific values in this example cannot be overridden.

    Description of 103-nonoverridable-parameter.gif follows
    Description of the illustration 103-nonoverridable-parameter.gif

About Editing Data Load Parameters

You edit Data Load Parameters (whether they are Global or Application Specific) using the Data Load Parameters dialog, which is displayed in FSM when you edit a Data Load Parameter (see the following screenshot). The Data Load Parameters list above (or master table) displays the parameters and values, and the Group Specific Parameter Values list below displays associated Fact Groups or Dimension Groups (if there are any).

Description of 103-editing-data-load-p.gif follows
Description of the illustration 103-editing-data-load-p.gif

To display Data Load Parameters in Configuration Manager, select the Manage Data Load Parameters link on the Tasks bar to display the Manage Data Load Parameters dialog.

Description of 103-working-data-load-p1.gif follows
Description of the illustration 103-working-data-load-p1.gif

About Editing Global Data Load Parameters

To edit the value of a Global Parameter, select the record in the Data Load Parameters master table, and then either click the Edit icon in the table toolbar or click on the link in the Global Parameter Values column.

If the Global Parameter that you edit is associated with Fact Groups or Dimension Groups, then a warning message is displayed to verify that you want to update the value for all associated Fact Groups and Dimension Groups. If you click Yes at the warning message, then the values of all occurrences of the parameter at the Group level will be updated to the new value.

For example, if you click the Edit icon or the link in the Parameter Value column for the parameter "Slowly Changing Dimension Flag" in the Data Load Parameters master table, then you see the following warning:

Description of 103-working-data-load-p2.gif follows
Description of the illustration 103-working-data-load-p2.gif

Clicking Yes allows you to continue with the edit of the parameter value. A change to the parameter value is applied to all parameter occurrences at the Group level.

To change the value of a parameter for a specific Fact Group or Dimension Group, select the Global Parameter in the Data Load Parameters master table, and then select the parameter in the Group Specific Parameter Values for: <Parameter Name> detail table. Click on the Edit icon in the table tool bar or the link in the Parameter Value column to open the Parameter Value Edit dialog.

Description of dlp3.gif follows
Description of the illustration dlp3.gif

Changing the parameter value in the above Edit dialog updates the parameter value for the Slowly Changing Dimension Flag parameter associated with the Absence Event Dimension Group.

About Editing Application Specific Parameter Values

You use the Edit option to change the value of a Fact Group or Dimension Group that is associated with an Application Specific parameter (if the parameter is overridable).

You use the Edit All option to edit the value of all Fact Groups and Dimension Groups that are associated with an Application Specific parameter.

If you attempt to edit the value of a specific Fact Group or Dimension Group, then:

  • if the parameter is overridable at the Group level, then you update only that specific Fact Group or Dimension Group.

  • if the parameter is Non-Overridable at the Group level, then a Warning dialog displays a list of Fact Groups and Dimension Groups that will be affected if you click Yes to edit the value.

    Description of 103-working-data-load-p3.gif follows
    Description of the illustration 103-working-data-load-p3.gif

Editing a Data Load Parameter Value

You can edit Data Load Parameters using the Manage Data Load Parameters dialog.

  • In Configuration Manager, select the Manage Data Load Parameters link in the Tasks pane.

  • In FSM, select the Go to Task link for a Task that updates a Data Load Parameter (for example, Configure Initial Extract Date).

  1. Select the parameter in the Data Load Parameters list.

    If the parameter is a Global parameter, then the Global Parameter Value field displays the actual value (for example, 'MONTHLY').

    If the parameter is a non-Global parameter, then the Global Parameter Value field displays the text 'Group Specific').

  2. Do one of the following:

    • To update a Global parameter, in the Data Load Parameters list click the value displayed in the Global Parameter Value field to display the Edit Parameter Value Dialog (Data Load Parameters), and edit the value. Alternatively, select the row and click the Edit icon.

      Description of dlp_glob_edit.gif follows
      Description of the illustration dlp_glob_edit.gif

      If a Global parameter is associated with Fact Groups or Dimension Groups, you can override the Global value for specific Fact Groups or Dimension Groups by editing the parameter value in the Group specific Parameter Values for pane.

    • To update an Application Specific parameter, select the parameter in the Data Load Parameters list, scroll down to the Group Specific Parameter Values for list, and click either the Edit icon, or the value in the Parameter Value column (or select the parameter row and click the Edit icon).

      Description of dlp_nonglob_edit.gif follows
      Description of the illustration dlp_nonglob_edit.gif

      If the parameter is overridable at the Group level, then you update only that specific Fact Group or Dimension Group using the Edit Parameter Value dialog.

      Description of edit_dlp_dialog.gif follows
      Description of the illustration edit_dlp_dialog.gif

      If the parameter is Non-Overridable at the Group level, then a Warning dialog displays a list of Fact Groups and Dimension Groups that will be affected if you click Yes to edit the value.

      Description of 103-working-data-load-p3.gif follows
      Description of the illustration 103-working-data-load-p3.gif

    • To update the parameter value for all Fact Groups and Dimension Groups in the Group Specific Parameter values for list, click Edit All to display the Edit Parameter Value dialog.

      Description of edit_dlp_dialog.gif follows
      Description of the illustration edit_dlp_dialog.gif

About Working With Reporting Parameters

Reporting Parameters are configuration values that specify how data is presented in Business Intelligence dashboards.

There are two categories of Reporting Parameter:

  • Global, which apply to all applications. These are displayed on the Global tab.

  • Application Specific, which apply to specific applications. These are displayed on the Application Specific tab.

You manage and edit Reporting Parameters using the Manage Reporting Parameters: Global/Application Specific tab.

Description of 103-working-reporting-parameters.gif follows
Description of the illustration 103-working-reporting-parameters.gif

You display the Manage Reporting Parameters: Global/Application Specific tab by doing one of the following:

  • In Configuration Manager, select the Manage Reporting Parameters link in the Tasks pane.

  • In FSM, select the Go to Task link for a Task that updates a Reporting Parameter.

To edit a Reporting Parameter, select the parameter in the parameter list, then either click the Edit icon, or click the value in the Parameter Value column.

About Monitoring Setup Data

During a functional configuration project, you monitor Setup Data to ensure that your Offerings are being correctly configured. For example, you might use the Parameters By Offerings report on the Overview page to visually monitor the number of parameters that have been configured.

You can monitor the setup data in the following ways:

  • In Configuration Manager, you can monitor the status of the underlying set up data values, as follows:

    • Use the pages and tabs in the Setup Data Maintenance and Administration area on the Tasks bar.

      From the Tasks bar, select one of the links in the Setup Data Maintenance and Administration area. For example, select the Manage Data Load Parameters link to display the Manage Data Load Parameters page.

      Description of 103-working-data-load-p1.gif follows
      Description of the illustration 103-working-data-load-p1.gif

    • Use the Reports panes on the Overview page.

      For example, you might use System Setups list to monitor which Offerings have been enabled for deployment.

      Description of 103-what-is-cm.gif follows
      Description of the illustration 103-what-is-cm.gif

Changing Configuration Values Using Configuration Manager

If you need to make configuration changes after an Implementation Project has been completed in FSM, you can use Configuration Manager to update setup data.

To change setup data values, you use the options in the Setup Data Maintenance and Administration area on the Tasks bar.

  1. In Configuration Manager, use options in the Setup Data Maintenance and Administration area on the Tasks bar:

    • To make changes to domain mappings, select Manage Domains Mappings and Hierarchies and display the tab for the domain type that you want to edit. To edit a Domain Mapping, select a domain in the Domain Mapping list and click the Edit icon in the Domain Member Mappings pane.

      Description of 103-add-target-domain-member1.gif follows
      Description of the illustration 103-add-target-domain-member1.gif

    • To make changes to data load parameters, select Manage Data Load Parameters and use the Search pane to locate the parameters that you want to edit. To edit the value of a Global Data Load Parameter, click the value in the Global Parameter Value column (or select the row then click the Edit icon).

      Description of dlp_glob_edit.gif follows
      Description of the illustration dlp_glob_edit.gif

      For Application Specific parameters, select the parameter in the Data Load Parameters list, scroll down to the Group Specific Parameter Values for list, and click either the Edit icon or the value in the Parameter Value column (or select the parameter row and click the Edit icon).

      Description of dlp_nonglob_edit.gif follows
      Description of the illustration dlp_nonglob_edit.gif

    • To make changes to reporting parameters, select Manage Reporting Parameters, and display either the Global tab or the Application Specific tab. To edit the value of a Reporting Parameter, click the value in the Parameter Value column (or select the row then click the Edit icon).

      Description of 103-working-reporting-parameters.gif follows
      Description of the illustration 103-working-reporting-parameters.gif

    Tip:

    To locate unmapped domain values, see Locating Unmapped Domain Values in Configuration Manager.

Locating Unmapped Domain Values in Configuration Manager

You locate unmapped Domain Values to enable you to make sure that you have mapped all of your source system domain values.

You can also use the Alerts pane on the Overview page in Configuration Manager to identify target domains with one or more unmapped source members. Display the Overview page, and navigate to the Domain Maps with Unmapped Source Members pane.
  1. Start Configuration Manager.
  2. Do one of the following:

    • From the Tasks bar, select Manage Domains and Mappings to display the Manage Domains and Mappings dialog.

      Display the Manage Domain Mappings and Hierarchies: Domain Mappings tab.

      In the Domain Member Mappings pane, select Unmapped from the Source Members list.

      Description of 103-unmapped-domain-values.gif follows
      Description of the illustration 103-unmapped-domain-values.gif

    • From the Tasks bar, select Manage Domains and Mappings to display the Manage Domains and Mappings dialog.

      Display the Manage Domain Mappings and Hierarchies: Warehouse Domain Hierarchies tab.

      In the Domain Member Mappings pane, select Unmapped from the Source Members list.

      Description of 103-unmapped-domain-values2.gif follows
      Description of the illustration 103-unmapped-domain-values2.gif

Locating Data Load Parameters with No Values in Configuration Manager

You locate Data Load Parameters with no values to check all Tasks in FSM relating to Data Load Parameters have been completed correctly.

  1. Start Configuration Manager.
  2. Do one of the following:

    • From the Overview page, use the Data Load Parameters with no Values list in the Alerts pane.

    • From the Tasks bar, select Manage Data Load Parameters to display the Manage Data Load Parameters dialog, which enables you to view and edit parameters.

Adding Target Domain Members

You add Target Domain Members to extend Oracle Business Analytics Warehouse.

For example, you might want to create a new salary category called 'Range 5' so that you can map salary values to this new category.

  1. Display the Warehouse Domains tab.

    In FSM, the Warehouse Domain tab is displayed when you perform a Task that edits a Warehouse Domain value.

    In Configuration Manager, from the Tasks bar, select Manage Domains Mappings and Hierarchies to display the Manage Domain Mappings and Hierarchies dialog.

  2. In the Domain Member Mappings pane, click Add Warehouse Domain Member to display the Add Warehouse Domain Member/Add Target Domain Member dialog.
  3. Use this dialog to specify the details.
  4. Click OK to save the details and close the dialog.

About Exporting and Importing Setup Data for Configuration Manager

You export and import the setup data Data for Configuration Manager.

You export and import the setup data to:

  • Make a backup of your configuration settings for security purposes. For example, you might keep a record of the configuration changes that you have made.

  • Migrate the setup data for Configuration Manager from one environment to another environment. For example, you might move the configuration changes that you have made from a Test environment to a Production environment.

What Data is Exported?

When you export the setup data, you export the changes that you have made to the values of the following objects:

  • Data Load Parameters

  • Domains and Mappings

  • Reporting Parameters

You export all changes that are different from the default values each time. The export process does not export the unchanged configuration values. In other words, if you only change the value of DEFAULT_CURRENCY from USD to Euro and then you export your data, then the export ZIP file that is produced will only contain columns for 'DEFAULT_CURRENCY=Euro'.

Note:

Other Configuration Manager details such as the configuration settings of the source system and Oracle Business Analytics Warehouse aren't included in the export files. In other words, before you import on the target system, you must first respecify the source system and Oracle Business Analytics Warehouse. Also, externally conformed domains aren't exported.

What Data is Imported?

When you import the setup data from a ZIP file, you import whatever configuration changes were exported to that ZIP file. For example, if you first export only Reporting Parameters to a ZIP file, then you import only the changes that were made to Reporting Parameters.

About Migrating Setup Data

To migrate the setup data, you do the following:

  • In the source environment, export the Configuration Manager setup data as a ZIP file. See Exporting Setup Data.

  • Copy the ZIP file from the source environment to the target environment.

  • In the target environment, import the Configuration Manager setup data from the ZIP file. See Importing Setup Data.

    Note:

    For a successful migration, the data source number (DSN) in the target system must be the same as the DSN in the source system.

About Backing Up Setup Data

To back up the setup data, you do the following:

  • In the source environment, export the Configuration Manager setup data as a ZIP file.

  • Store the ZIP file in a secure location.

  • In the target environment, make sure that you have installed Configuration Manager, which installs the default setup data. The data source number in the target system must be the same as the data source number in the source system.

  • To restore the backed up data, you import the Configuration Manager setup data from the ZIP file.

Exporting Setup Data

You can export the setup data to back up or migrate a Configuration Manager environment.

  1. In the source environment, start Configuration Manager.
  2. From the Tasks bar, select Export Setup Data to display the Export Setup Data dialog.
  3. In the Export Setup Data dialog, click the Export icon Export icon to display the Export Data dialog.
  4. Specify the setup objects that you want to export.
  5. Click Export.
  6. When the File Download dialog is displayed, click Save to save the ZIP file to a location that you specify.

    If you first click Open at the File Download dialog to open the ZIP file, then make sure that you save the ZIP file in the ZIP program that you are using.

The Export Setup Data table is updated with the export details.

Importing Setup Data

You import the setup data to restore or migrate the setup data. Before you import the setup data, you must copy the previously exported ZIP file to a file location that is accessible from the machine that is running the Configuration Manager client.

When you import the setup data, the data source number in the target system must be the same as the data source number in the source system.
  1. In the source environment, start Configuration Manager.
  2. From the Tasks bar, select Import Setup Data to display the Import Setup Data dialog.
  3. In the Import Setup Data dialog, click the Import icon Import icon to display the Import Data dialog.
  4. Specify the location and name of the ZIP file that contains the configuration changes that you want to import.
  5. Click OK.

The setup data is imported from the ZIP file, and the Import table is updated with the details.

Customizing a Product Hierarchy

You can customize product hierarchies by associating Dimension Groups or Fact Groups with Offerings and Functional Areas.

  1. From the Tasks bar, select Manage Business Intelligence Application Offerings.
  2. In the Business Intelligence Application Offerings list, select the Offering that you want to customize.
  3. In the Associated Fact and Dimension groups area below, do one of the following:

    • To add a Fact Group, choose Actions, then Create Fact Group to display the Create/Edit Fact Group dialog.

    • To add a Dimension Group, choose Actions, then Create Fact Group to display the Create/Edit Dimension Group dialog.

  4. If necessary, use the Edit and Delete options to modify the Dimension Groups or Fact Groups that you have added.

Note:

You can only edit or delete Fact Groups or Dimension Groups that you have created. You cannot edit or delete default groups that are provided on installation.