Performing Functional Configuration of OTBI … Parameters to open the Manage Data Load Parameters...

Copyright © 2014, Oracle and/or its affiliates. All rights reserved. 1

Copyright © 2014 Oracle and/or its affiliates. All rights reserved. |

Performing Functional Configuration of OTBI Enterprise for HCM Cloud Service

Copyright © 2014, Oracle and/or its affiliates. All rights reserved.

The goal of this training is to enable implementers to configure and deploy Oracle® Transactional Business Intelligence Enterprise for Human Capital Management Cloud Service. An implementer is responsible for performing the initial setup and configuration of Oracle® Transactional Business Intelligence Enterprise for Human Capital Management Cloud Service. This may be done by the customer or by an implementation partner.

2


Objective• After completing this lesson, you should be able to use Configuration

Manager (CM) and Functional Setup Manager (FSM) to perform functional configuration for OTBI Enterprise for HCM Cloud Service.



Prerequisite• Before completing this topic and the associated practice, please complete

the topic “Performing Initial Configuration of OTBI Enterprise for HCM Cloud Service” and its associated practice.

Please note: Work with your Oracle BI Product Management contact, who can provide a spreadsheet of seeded configuration values that need to be reviewed. You will only need to perform a configuration if you are changing the seeded value.



Overview• During an OTBI Enterprise for HCM Cloud Service deployment project, you

use Configuration Manager (CM) and Functional Setup Manager (FSM) to manage and make changes to configuration values for: – Domains and mappings– Data load parameters– Reporting parameters

• Domains are typically located in the source system. For example, in Oracle Human Resources Analytics, domains store information about Payroll.

• The screenshot shows the Domain Mappings tab. You access this tab by selecting Tasks > Domains Administration > “Manage Domain Mappings and Hierarchies” in Configuration Manager.

• This tab shows how data fields in the source system map to data fields in OTBI Enterprise for HCM Cloud Service. The domain mappings specify how data in a source system is extracted and loaded into OTBI Enterprise for HCM Cloud Service.

• For example, the data in the source domain Source Assignment Primary Flag (ASSIGNMENT_PRIMARY_FLG) extracts and loads into the target domain Assignment Primary Flag (W_ASSIGNMENT_PRIMARY_FLG).

• Notice that you can search for domain mappings by source instance, offering, fact group, dimension group, domain name, and so on.



Domains and Domain Mappings• Domains are pre-seeded dimensional values that help define business

metrics.

Set search criteria.

Source domains Target domains

Domain mappings

• There are two types of domain member mappings:

– Regular domains have members consisting of a single value. These single values map to single member values in the target system.

– Band domains have members consisting of two values (Range Start and Range End) that specify a range.

• In the screenshot, Source Country is an example of a regular domain.



Domain Member Mappings• Domain member mappings specify how domain member data in a source

system is extracted and loaded into domain member data in the target.

Select domain mapping…

…to view domain member

mappings.

The screenshot shows the Manage Source Domains page. To navigate to this page, select Tasks > Domains Administration > Manage Source Domains in Configuration Manager. Source domains displayed on the Source Domains tab are read-only.



Source Domains• Data fields in a source system application are referred to as source

domains.

Source domain values are read-only.


• On the Source Domains page, you can select a source domain to view its members in the lower pane. In the example in the slide, you select the Source Country domain to view its domain members. Domain members are the permitted values for a source domain.

• Notice that you do not have the ability to edit and add domain members in this pane. To maintain data integrity, some domains have been designed as non-extensible, and are, therefore, read-only.



Source Domains: Domain Members• Select a source domain to display domain members in the lower pane.

The screenshot shows the Manage Warehouse Domains page. To navigate to this page, select Tasks > Domains Administration > “Manage Warehouse Domains in Configuration Manager.”



Warehouse Domains• Data fields in the target are referred to as warehouse domains.


• In the example in the slide, you select the Country warehouse domain to view its warehouse members. Warehouse members are the permitted values for a warehouse domain.

• Notice that, unlike when working with source domain members, you have the ability to edit and add warehouse members in this pane.



Warehouse Domains: Warehouse Members• Select a warehouse domain to display warehouse members in the lower

pane.

Select warehouse domain…

…to view or edit warehouse members.

Click to add warehouse domain members.

Domain hierarchies are displayed in inverted format. In the example in the slide, W_COUNTRY is the parent of child W_REGION.



Warehouse Domain Hierarchies• Warehouse domain hierarchies are domains that have been organized into

hierarchies to enable the data to be more effectively analyzed.

• Select a domain mapping in the hierarchy to display domain member mappings in the lower pane.

• Use the field next to Source Domain Members to display mapped, unmapped, or all source domain members.



Warehouse Domain Hierarchies: Domain Member Mappings• Select a domain mapping in the hierarchy to display domain member

mappings in the lower pane.

Select domain mapping…

…to view domain member mappings.

Display all, mapped, or unmapped.

• OTBI Enterprise for HCM Cloud Service ships with default domain value mappings that map the seeded domain values to the seeded configuration data. If you want to use these default categories, you do not need to make any changes to these mappings before you start your load plan processes. The example in the slide shows the member mappings for Account Employee Size.

• If you want to edit a domain member mapping, click the Edit icon to display the Edit Domain Member Mappings dialog box. Use this dialog box if you want to make changes to default domain-mapping values. For example, you could change the range values or click Add Range Domain Member Mapping to create a new range.



Editing Domain Member Mappings

Select domain mapping.

Click Edit.

Edit domain member mapping.

• Using batch edit is useful for large domains with many member mappings that require the same value. In the Tasks bar, click Manage Domains and Mappings, display the Domain mappings tab, select the Domain that you want to edit, and then click the Edit Domain Member Mappings icon in the Domain Member Mappings pane to display the Edit Domain Member Mappings dialog box.

• To use batch edit, select one or more rows in the table, select a value from the Batch Edit drop-down list, and then click Change to apply the value selected in the Batch Edit drop-down list to all specified members.



Using Batch Edit• You can set up a target domain by using the Batch Edit option to update

multiple target domain members with the same value.Multi-select one or more rows in the table. Select a value from the Batch Edit drop-down list.

Click Change to apply the selected value to all specified members.

• In some scenarios, you might not know what target domain member values should be when you deploy.

• 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.



Using Sync To Source• 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.

• To view and manage data load parameters, select Tasks > Data Load Parameters Administration > Manage Data Load Parameters to open the Manage Data Load Parameters page in Configuration Manager. Use the Search section to specify source instance, offering, fact group, and so on. In the example in the slide, data load parameters are shown for the Oracle Human Resources Analytics offering.

• Data load parameters can be either global or application-specific.

• Global parameters apply to all applications and are indicated by the (ab) and globe icon. Global data load parameters can also be associated with specific fact groups or dimension groups.

• Application-specific parameters apply to specific applications and are indicated by the (ab) icon. Application-specific data load parameters are always associated with one or more fact groups or dimension groups.

• Some parameters have a warning icon that indicates that this parameter value must be set before running a full load.

• Some parameters have a read-only icon that indicates that this parameter value cannot be edited.



Data Load Parameters• Data load parameters are configuration values that specify how source

system data is loaded into OTBI Enterprise for HCM Cloud Service.

Global parameter Warning icon

• In the example in the slide, the Slowly Changing Dimension Flag parameter is selected. This parameter indicates whether the slowly changing dimension type 2 flag is set for dimensions or dimension groups.

• Notice that this is a global parameter and the Global Parameter Value is set to No. 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.

• Please note the following regarding tasks in the implementation project task list in OTBI Enterprise for HCM Cloud Service release 8.1:

– You should ignore some tasks that appear in the implementation project task list. Please see Appendix A in this lesson for more information.

– Some tasks that must be configured are missing from the implementation project task list. Please see Appendix B in this lesson for more information.



Editing Data Load Parameters

1. Select a data load parameter and click Edit.

2. A warning message is displayed for global parameters.

3. Use Edit Dialog to edit the parameter.

• In the example in the slide, the Slowly Changing Dimension Flag data load parameter is selected, and the Group Specific Parameter Values pane is visible. This pane shows the value of the Slowly Changing Dimension Flag parameter for specific dimension groups within the selected offering.

• In this example, the Business Location Dimension group-specific parameter value is selected.

• To edit the group-specific parameter value, click the Edit icon on the toolbar to open the Edit Dialog box. Notice that you can change the parameter value by selecting from a list of values: Yes or No in this example. The fields that are displayed in this dialog box are different, depending on the type of parameter being edited. For example, the parameter data type might be Boolean, date, multi-value select list of values, number, single-value select list of values, string, and so on. It is also possible to edit more than one group-specific parameter value by using the Edit All icon (two pencils).



Editing Group-Specific Parameter Values

1. Select a data load parameter.

2. Click Edit for an associated group-specific parameter value.

3. Edit the parameter value.

In the Tasks bar, select Manage Reporting Parameters to view or edit reporting parameters. In the example in the slide, the Global tab is selected. Global parameters apply to all applications. Application-specific parameters apply to specific applications. To edit a reporting parameter, select the parameter in the parameter list, and then either click the Edit icon or click the value in the Parameter Value column.



Reporting Parameters• Reporting parameters are configuration values that specify how data is

presented in OTBI Enterprise for HCM Cloud Service dashboards.

Select Manage Reporting Parameters.

Click to edit.

Click to edit.

• You can use the Reports panes on the Overview page to monitor setup data. For example:

– Use the System Setups list to monitor which Offerings have been enabled for deployment.

– Use the Parameters By Offerings report to monitor visually the number of parameters that have been configured.

– Use the Load Plan Executions report to monitor load plans.

– Use the “Domain Mappings by Offerings” report to monitor domain mappings.

• You can drill into each report for more detailed information. For example, drilling on the Parameters bar graph in the Parameters By Offerings report will take you to a list of parameters by offering. Drilling on the “Parameters with no values” bar in the graph will open a page where you can view and edit parameters with unassigned values.



Monitoring Setup Data• Use the Overview page to monitor setup data to ensure that your offerings

are correctly configured.

Drill into reports for more detail.



Summary• In this lesson, you should have learned how to use Configuration Manager

and Functional Setup Manager to perform functional configuration for OTBI Enterprise for HCM Cloud Service.



Appendix A: Tasks to Ignore in Implementation Project• In release 11.1.1.8.1, the following tasks appear in the implementation

project task list in Functional Setup Manager. You can ignore each of these tasks, because they do not apply to OTBI Enterprise for HCM Cloud Service release 11.1.1.8.1:– Configure Data Load Parameters for PeopleSoft Tree History Support– Configure Data Load Parameters for PeopleSoft Department Tree– Configure Data Load Parameters for PeopleSoft Company (Business Unit) Tree– Specify the Ledger or Set of Books for which General Ledger Data is Extracted– How to Set Up HR Position Hierarchy Based Data Security– How to Set Up Department Based Data Security– How to Set Up Manager Hierarchy Base Security for Peoplesoft

Oracle Confidential – Internal/Restricted/Highly Restricted 22



Appendix B: Tasks Missing from Implementation Project• In release 11.1.1.8.1, the following tasks are missing from the

implementation project task list in Functional Setup Manager:– Configure Global Currencies– Configure Initial Extract Date– Configure Data Load Parameters for Leveraging a Source Dependent Store– Manage Domains and Member Mappings for Currency Exchange Rate General

• It is still important that you configure the parameters associated with these tasks. You can configure the parameters directly using Configuration Manager.

• The steps to complete these tasks are shown on the slides that follow.


Steps to complete the Configure Global Currencies task:

• Click “Manage Data Load Parameters” in Configuration Manager.

• In the Search area, select Category in the Parameter drop-down box.

• Enter Global Currencies Setup in the Parameter search box and click Search.

• Thirteen parameters will appear. If necessary, change each default value to be specific to your implementation.



Appendix B: Configure Global Currencies


1. Click Manage Data Load Parameters in

Configuration Manager.

2. Select Category in the Parameter list.

3. Enter Global Currencies Setup in the Search field.

5. Select parameter to edit.

4. Click Search.7. Edit parameter value.

6. Click Edit button.

Steps to complete the Configure Initial Extract Date task:


• In the Search area, select Code in the Parameter drop-down box.

• Enter INITIAL_EXTRACT_DATE in the Parameter search box and click Search.

• One parameter will appear. If necessary, change the default value to be specific to your implementation.



Appendix B: Configure Initial Extract Date




2. Select Code in the Parameter list.

3. Enter INITIAL_EXTRACT_DATEin the Search field.


4. Click Search.

6. Click Edit button.

7. Edit parameter value.

Steps to complete the Configure Data Load Parameters for Leveraging a Source Dependent Store task:


• In the Search area, select Code in the Parameter drop-down box.

• Enter IS_SDS_DEPLOYED in the Parameter search box and click Search.

• 1 parameter will appear. If necessary, change default value to be specific to your implementation.



Appendix B: Configure Data Load Parameters for Leveraging a Source Dependent Store




2. Select Code in the Parameter list.

3. Enter IS_SDS_DEPLOYEDin the Search field.


4. Click Search.

6. Click Edit button.7. Edit parameter value.



Appendix B: Manage Domains and Member Mappings for Currency Exchange Rate General• Steps to complete the Manage Domains and Member Mappings for

Currency Exchange Rate General task:– Click “Manage Domain Mappings and Hierarchies” in Configuration Manager.– In the Dimension Group drop-down, select Currency Exchange Rate General. – If necessary, change default value to be specific to your implementation.




Practices– Performing “Manage Domains and Member Mappings” Configuration Tasks– Performing “Data Load Parameter” Configuration Tasks


Page 1 of 11

Performing “Manage Domains and Member Mappings” Configuration Tasks

Overview In this practice, you learn how to perform specific “manage domains and member mappings” configuration tasks for a typical implementation of OTBI Enterprise for HCM Cloud Service. Configuration tasks can be accessed by navigating to Manage Implementation Projects > [Implementation Project] > Task Lists and Tasks in Functional Setup Manager. Please note that for release 11.1.1.8.1, some tasks that must be configured are missing from the implementation project task list. It is still important that you configure the parameters associated with these tasks. You can configure the parameters directly using Configuration Manager. The steps to complete these tasks using this method are shown in the next practice. This practice shows you how to access the task list for a given implementation project, and then provides examples of some of the “manage domains and member mappings” configuration tasks that you need to perform. Please note screen shots are for training purposes only and may not exactly match the data in your environment.

Time 20 minutes

Tasks 1. Navigate to an implementation project task list.

a. Sign in to Configuration Manager using the credentials provided by Oracle Cloud Ops. b. In the Tasks list, click Perform Functional Configurations to open Functional Setup

Manager. c. Sign in to Functional Setup Manager using the same credentials you used to sign in to

Configuration Manager d. In the Tasks list, select Manage Implementation Projects to open the Manage

Implementation Projects screen in the right pane. e. If necessary, search for your implementation project. f. In the Search Results, drill on the desired implementation project to open the Task

Lists and Tasks page. g. Expand the implementation project to view the tasks associated with this

implementation project. Administrators will be able to see all tasks. Developers will see only those tasks to which they are assigned.

h. Notice that each task has a link in the Go to Task column. You use this link to navigate to, and complete, configuration tasks. The remainder of this practice provides examples of some of the “manage domains and member mappings” configuration tasks you need to perform for a typical implementation of OTBI Enterprise for HCM


Page 2 of 11

Cloud Service.

2. Complete the “Manage Domains and Member Mappings for Employment Dimension” task.

a. In the Task search field, enter Employment Dimension and click the search button to locate the “Manage Domains and Member Mappings for Employment Dimension” task.

b. Click on the task to navigate to it in the task list. c. Click the Go to Task button. d. Click the Domain Mappings tab. This tab shows how data fields in the source system

map to data fields in OTBI Enterprise for HCM Cloud Service. Domain mappings specify how data in a source system is extracted and loaded into OTBI Enterprise for HCM Cloud Service. For example, the data in the source domain Source Assignment Primary Flag (ASSIGNMENT_PRIMARY_FLG) extracts and loads into the target domain Assignment Primary Flag (W_ASSIGNMENT_PRIMARY_FLG).

e. Select the Source Employee Category source domain in the list. f. Scroll down if necessary to view domain member mappings. Domain member

mappings specify how domain member data in a source system is extracted and loaded into domain member data in OTBI Enterprise for HCM Cloud Service. There are two types. Regular domains have members consisting of a single value. These single values map to single member values in the target system. Band domains have members consisting of two values (range start and range end) that specify a range.


Page 3 of 11

The screenshot shows an example of a regular domain.

g. Under Domain Mappings, click the Query By Example icon to display the query by

example fields. Query By Example enables you to locate parameter values using a free-text search.

h. Enter *Employee* in the Name field for Source Domains and press Enter to retrieve source domain members that include the word Employee.

i. Click the Clear All button to clear the query. You can also clear the text in the Query By Example field and press Enter again. You can use Query By Example to search for objects throughout Configuration Manager and Functional Setup Manager.

3. Explore how to edit a domain member mapping. a. Select Source Employee Category. b. Scroll down to the Domain Member Mappings pane. OTBI Enterprise for HCM Cloud

Service ships default domain value mappings that map the seeded domain values to the seeded configuration data. If you want to use these default categories, you do not need to make any changes to these mappings before you start your load plan execution.

c. Click the Edit icon to display the Edit Domain Member Mappings dialog box. You

would use this dialog box if you want to make changes to default domain-mapping values. Depending on the domain member mapping type, you can manually edit domain values, click Add Range Domain Member Mapping to create a new range for band domains, or use the Batch Edit field to update multiple domain members with the


Page 4 of 11

same value.

d. When you are done with your edits, click Save and Close to return to the Manage

Domain Mappings and Hierarchies page. 4. Explore warehouse domain hierarchies.

a. Click the Warehouse Domain Hierarchies tab. Warehouse domain hierarchies are domains that have been organized into hierarchies to enable the data to be more effectively analyzed.

b. Select W_WORKER_SUBTYPE to display domain member mappings in the lower pane.

c. Use the field next to Source Domain Members to display mapped, unmapped, or all source domain members.


Page 5 of 11

Performing Data Load Parameter Configuration Tasks

Overview In this practice, you learn how to perform specific data load parameter configuration tasks for a typical implementation of OTBI Enterprise for HCM Cloud Service. Please note that all configuration tasks can be accessed by navigating to Manage Implementation Projects > [Implementation Project] > Task Lists and Tasks in Functional Setup Manager. Please note that for release 11.1.1.8.1, some tasks that must be configured are missing from the implementation project task list. It is still important that you configure the parameters associated with these tasks. You can configure the parameters directly using Configuration Manager. The steps to complete these tasks using this method are shown in this practice. This practice shows you how to access the task list for a given implementation project, and then provides examples of some of the data load parameter configuration tasks that you need to perform. Please note screen shots are for training purposes only and may not exactly match the data in your environment.

Time 20 minutes

Tasks 1. Navigate to an implementation project task list.

a. If necessary, sign in to Configuration Manager. b. In the Tasks list, click Perform Functional Configurations to open Functional Setup

Manager. c. Sign in to Functional Setup Manager. d. In the Tasks list, select Manage Implementation Projects to open the Manage

Implementation Projects screen in the right pane. e. If necessary, search for the desired implementation project. f. In the Search Results, drill on the desired implementation project to open the Task

Lists and Tasks page. g. Expand the implementation project to view the tasks associated with this

implementation project. Administrators will be able to see all tasks. Developers will see only those tasks to which they are assigned.

h. Notice that each task has a link in the Go to Task column. You use this link to navigate to, and complete, configuration tasks. The remainder of this practice provides examples of some of the data load parameter configuration tasks you need to perform


Page 6 of 11

for a typical implementation of OTBI Enterprise for HCM Cloud Service.

2. Specify Gregorian Calendar Date Range. This task is used to specify the range of dates for

which the Gregorian calendar is generated. a. Select the “Go to Task” link for the Specify Gregorian Calendar Date Range task to

navigate to the Manage Data Load Parameters page. b. You should see two global data load parameters:

Gregorian Date Range End Date Gregorian Date Range Start Date

c. The parameter Gregorian Date Range End Date (END_DATE) is used to specify the

end of the Gregorian Calendar Date Range. The Gregorian calendar will be generated till the date specified by this parameter. Customers should generally pick a value that covers at least 10 years forward.

d. The parameter Gregorian Date Range Start Date (START_DATE) is used to specify the start of the Gregorian Calendar Date Range. The Gregorian calendar will be generated from the date specified by this parameter. Customers should generally pick a value that covers the entire range for which they plan to load data into Enterprise for HCM Cloud Service.


Page 7 of 11

e. To edit a parameter, click the value or select the parameter in the Data Load Parameters list and click the Edit icon to open the Edit Dialog box.

f. Modify the Parameter Value and click Save and Close. g. Click Done to close the Manage Data Load Parameters page and return to the

implementation project task list. h. If the Assigned To field was blank before, it is now updated with the name of the

developer who made the change. i. If desired, click the Status link to set the status for the task.

3. Configure Data Load Parameters for File Based Calendars. This task is used to configure

data load parameters for file based calendars. a. Select the “Go to Task” link for the Configure Data Load Parameters for File Based

Calendars task to navigate to the Manage Data Load Parameters page. b. You should see two global data load parameters:

13 Period Calendar Id 4-4-5 Calendar Identifier

c. The parameter 13 Period Calendar Id (13P_CALENDAR_ID) is used to define which of the file based calendars is a 13-period calendar. The default value is 10001.

d. The parameter 4-4-5 Calendar Identifier (445_CALENDAR_ID) is used to define which of the file based calendars is a 4-4-5 calendar. The default value is 10000.


Page 8 of 11



implementation project task list. 4. Specify the Enterprise Calendar. This task is used to define which calendar from which

source will be used as the Enterprise calendar or the common reporting calendar. a. Select the “Go to Task” link for the Specify the Enterprise Calendar task to navigate to

the Manage Data Load Parameters page. b. You should see two global data load parameters:

GBL_CALENDAR_ID GBL_DATASOURCE_NUM_ID

c. The Enterprise Calendar Identifier parameter (GBL_CALENDAR_ID) can be set to one of the calendars extracted from the source or to one of the warehouse generated calendars. The format is: For Generated Calendars: enter <CALENDAR_ID> For Calendars sourced from the OLTP Fusion Applications: enter <PERIOD_SET_NAME~PERIOD_TYPE>

d. The parameter Enterprise Calendar DSN Identifier (GBL_DATASOURCE_NUM_ID) can be set to the datasource_num_id of the source whose calendar is being configured as the Enterprise Calendar.



implementation project task list. 5. Configure Slowly Changing Dimensions. This task is used to configure data load

parameters related to Slowly Changing Dimensions. a. Select the “Go to Task” link for the Configure Slowly Changing Dimensions task to

navigate to the Manage Data Load Parameters page. b. You should see two global data load parameters:

TYPE2_FLG UPDATE_ALL_HISTORY

c. The Slowly Changing Dimension Flag (TYPE2_FLG) parameter indicates if the Slowly Changing Dimension type 2 is enabled. The default is NO. If the flag TYPE2_FLG is set to YES for a given dimension group, that dimension becomes a type 2 slowly changing dimension and history is tracked. This parameter should be a YES for all dimensions where the initial load is bringing history from source.

d. The Update All History Flag (UPDATE_ALL_HISTORY) parameter is used to determine if the Slowly Changing Dimension update map should update all historical rows for type 1 columns. This parameter is used to configure Slowly Changing Dimensions along with the TYPE2_FLG parameter. This parameter controls the behavior of the type 1 attributes of a type 2 dimension. The default setting is NO. If this UPDATE_ALL_HISTORY is set to YES for a given dimension group, then all the type 1 attributes of the historical records of a dimension member will be updated with the values from the current record.



Page 9 of 11


implementation project task list. 6. Configure Enterprise List. This task is used to configure the list of Enterprises from which

data will be extracted from the Fusion Source into OTBI Enterprise for HCM Cloud Service. If no value is picked, then all Enterprises are included. a. Select the “Go to Task” link for the Configure Enterprise List task to navigate to the

Manage Data Load Parameters page. b. You should see one global data load parameter:

ENTERPRISE_LIST. c. Select the “Enterprise List” parameter in the Data Load Parameters section. The

parameter values are displayed in the Group Specific Parameter Values for: Enterprise List section. The default is “All Selected Values”.

d. To edit the parameter, click the value or select the parameter in the Data Load Parameters list and click the Edit icon to open the Edit Dialog box.

e. Move the desired value(s) from Available Values to Selected Values. f. Click Save and Close. g. Click Done to close the Manage Data Load Parameters page and return to the

implementation project task list. 7. Configure Prune Days. This task is used to configure parameter PRUNE_DAYS. Prune

days is the number of days prior to the last load plan run to include in the load plan extract window. This parameter is used in calculating LAST_EXTRACT_DATE which identifies those records to be extracted in an incremental load plan run. Essentially it extends the window of time for records to be evaluated for extraction beyond just those that have changed or were created since the last load plan run. a. Select the “Go to Task” link for the Configure Prune Days task to navigate to the

Manage Data Load Parameters page. b. You should see one global data load parameter:

PRUNE_DAYS. The default value is “1”. c. To edit the parameter, click the value or select the parameter in the Data Load

Parameters list and click the Edit icon to open the Edit Dialog box. d. Modify the Parameter Value and click Save and Close. e. Click Done to close the Manage Data Load Parameters page and return to the

implementation project task list. 8. Continue to use the “Go to Task” link on the Implementation Project page to navigate to,

and complete, the configuration tasks for your project. Be sure to refer to the OTBI Enterprise Customer Configuration Workbook for notes and special instructions for completing tasks. For example, there are some tasks you should ignore, and some tasks that must be completed using Configuration Manager. Please refer to Appendix A and Appendix B in this lesson for more information. If you do not know where to locate the OTBI Enterprise Customer Configuration Workbook, please contact the person in Oracle BI Product Management who has been assigned to assist you with your implementation.

9. Set the initial extract date. This task is used to configure the parameter INITIAL_EXTRACT_DATE, which indicates how far back customer wants to extract data from the source for their implementation. For example, customers may choose to extract data from last 3 years. The initial extract date is required when you extract data for a full load. It reduces the volume of data in the initial load. The specified initial extract date is used as a filter on the creation date of source data in the selected full extract mapping.


Page 10 of 11

When you set the Initial Extract Date parameter, make sure that you set it to the beginning of an accounting period and not to a date in the middle of an accounting period. Please note: As mentioned in the Overview section of this practice, for release 11.1.1.8.1, some tasks that must be configured are missing from the implementation project task list. It is still important that you configure the parameters associated with these tasks. You can configure the parameters directly using Configuration Manager. “Configure Initial Extract Date” is an example of one of these tasks. The steps to complete this task using this method are shown here. For more information, refer to Appendix B in this lesson. a. Open Configuration Manager. b. In the Tasks list, select Manage Data Load Parameters to open the Manage Data Load

Parameters page in the right pane. c. In the Parameters Configuration section, select Code in the Parameter list. d. Enter INITIAL_EXTRACT_DATE in the Search field. e. Click Search. The Initial Extract Date global parameter is visible in the Data Load

Parameters section. f. To edit the parameter, click the value or select the parameter in the Data Load

Parameters list and click the Edit icon to open the Edit Dialog box. g. When you receive the Warning message, click Yes to continue. h. In the Edit dialog box, enter the desired dated in the Parameter Value field. The default

value is 1/1/70. i. Click “Save and Close.” j. In the Data Load Parameters list, confirm that the Initial Extract Data for ETL parameter

is updated. k. Click Done.

10. Export and import setup data. You export and import setup data for Configuration Manager to do the following: • 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.

a. Return to Configuration Manager. b. On the Tasks bar, select Export Setup Data. c. Click the Export icon to display the Export dialog box. d. Accept the default name for the export file name. e. Use the Export dialog box to specify the setup objects that you want to export.

Please note: When you export setup data, you export only the changes that you have made to the values of the following objects: − Data Load Parameters − Domains and Mappings − Reporting Parameters − System Setups − Load Plan Definitions

Unchanged configuration values are not exported. In other words, if you only


Page 11 of 11

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'. In this example, there are no changes. This is for training purposes only.

f. Click Export. g. When the File Download dialog box is displayed, select Save File and click OK to save

the zip file to a location that you specify. h. The Export Setup Data pane is updated with information about the export. i. To import setup data you would select Tasks > Import Setup Data and follow a similar

process to import an exported file. When you import 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.

Performing Functional Configuration of OTBI … Parameters to open the Manage Data Load Parameters...

Documents

Transcript of Performing Functional Configuration of OTBI … Parameters to open the Manage Data Load Parameters...