D82531GC10 Les11

These eKit materials are to be used ONLY by you for the express purpose SELF STUDY.
SHARING THE FILE IS STRICTLY PROHIBITED.
Copyright 2013, Oracle and/or its affiliates. All rights reserved.
Oracle University and (Oracle Corporation) use only.
Building a Category 1 Customization
After completing this lesson, you should be able to complete

the steps for a Category 1 customization of the Oracle
Business Analytics Warehouse (OBAW).
Oracle BI Applications 11g: Implementation Using ODI 11 - 2
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
Objectives
In a Category 1 customization, you add additional columns

from source systems that have prepackaged adapters and load
the data into existing Oracle Business Analytics Warehouse
tables.
A Category 1 customization is one of the three customization types that were initially
presented in the previous lesson titled Customizing the Oracle Business Analytics
Warehouse. Customizations are categorized based on the data source (packaged or
nonpackaged) and the desired Oracle Business Analytics Warehouse (OBAW) modification
(additional columns, tables, or rows). Category 1 customizations involve extracting additional
columns from source systems that are already mapped and loading the data into existing data
warehouse tables.
Category 1 Customization: Adding Columns to

Existing Fact or Dimension Tables
Scenario: Extract data from a column in a table in the

source database and load it into a custom column in a
dimension table in the OBAW.
Example:
Use the DESCRIPTION column in the HZ_LOCATIONS table
in the source system to capture data related to locations.
Load the data into a custom column, X_DESCRIPTION, in
the W_GEO_D dimension table in the data warehouse.
OLTP
OBAW
OBAW
HZ_LOCATIONS
W_GEO_DS
W_GEO_D
DESCRIPTION
X_DESCRIPTION
X_DESCRIPTION
This slide presents the scenario for a Category 1 customization used in this lesson. Data is
extracted from a table in a source transactional database and loaded into a custom column in
a dimension table in the Oracle Business Analytics Warehouse. This scenario is used
throughout the lesson and associated practices.
Category 1 Customization: Scenario
1. Create custom SDE and SIL folders in ODI Studio.

2. Create a version of the task folder to be customized.
3. Copy the preconfigured task folder to the custom folder.
4. Create versions of the copied task folder.
5. Create versions of the model.
6. Edit the target datastores.
7. Map the new column in the interface.
8. Generate DDL scripts.
9. Execute the DDL procedure.
10. Modify the scenario naming convention.
11. Generate scenarios.
12. Generate a load plan.
This slide and the next list the steps to perform a Category 1 customization. Each step is
presented in detail in the slides that follow.
Category 1 Customization Steps
13. Open the generated load plan.

14. Update the load plan step.
15. Execute the load plan.
16. Verify that the data is loaded.
Category 1 Customization Steps
On the Designer tab in ODI Studio, select BI Apps Project >

Mappings > New Sub-Folder to create custom SDE and SIL
folders.
Custom folder for a

preconfigured SDE adaptor
Custom folder
for SIL objects
If you want to make changes to preconfigured ODI objects, you must create a custom folder
and make the changes in it. Do not change objects in any of the preconfigured folders unless
explicitly directed by Oracle. This is because preconfigured folders and the objects within
them may be overwritten in future upgrades.
The preconfigured ODI repository does not include any custom folders. You must create your
own. You should create a custom folder for each prepackaged SDE Adaptor folder you have
deployed that will have customizations. In the example in the slide, a custom folder is created
for the SDE_ORA11510_Adaptor folder.
You should also create a separate custom folder for customizations that you want to make to
objects in the SILOS folder. Do not store customized SDE and SIL objects in the same folder.
The customization steps in the slides that follow use SDE objects as examples. The steps
apply to SIL objects as well.
1. Create Custom SDE and SIL Folders

in ODI Studio.
Before you begin customization, create a version of the

preconfigured task folder to be customized.
Accept the default
version number.
Add a description indicating that this
is the original version of this task.
Right-click and select
Version > Create Version.
Before you begin customization, enable versioning for the preconfigured task folder to be
customized. The version comment should indicate that this is the base (original) version of the
task. Subsequent patches applied to this task in the future would require increasing the
version in the comment so that it can be compared to the original task to identify any changes.
To create a version, right-click the task folder and select Version > Create Version to open the
Version dialog box. In the example in the slide, a version number and description have been
enabled for the SDE_ORA_GeographyDimension_HZLocations task folder.
2. Create a Version of the Task Folder

to be Customized.
Before you begin customization, duplicate the task folder to be

customized by copying it to the custom folder.
Copy the preconfigured task

folder to the custom folder.
Duplicate the task folder to be customized by copying it. Paste the copied task folder to the
custom folder, and rename it by removing the 'Copy of' prefix.
In this example in the slide, you copy the preconfigured task folder,
SDE_ORA_GeographyDimension_HZLocations, in the preconfigured adaptor folder,
SDE_ORA11510_Adaptor, and then paste the copied task folder to the
CUSTOM_SDE_ORA11510_Adaptor folder. This creates a new task folder named Copy of
SDE_ORA_GeographyDimension_HZLocations, which you rename to
SDE_ORA_GeographyDimension_HZLocations.
3. Copy the Preconfigured Task Folder to the

Custom Folder.
Before you begin customization, create versions of the copied

task folder to be customized.
Create versions of the

copied task folder.
Create an original version
and a custom version.
Before you begin customization, enable versioning of the copied task folder to be customized.
The version comment should indicate that this is the original version. This versioning enables
comparison of the customized task to a copy of the original version to determine all changes
that have been introduced.
Create another version of the copied task comment so that it can be compared to the original
task to identify any changes. The version comment should indicate that this is the customized
version. To enable versioning, right-click the task folder and select Version > Create Version
to open the Version dialog box.
In the example in the slide, a version number and description have been enabled for both the
original version and the customized version of the
SDE_ORA_GeographyDimension_HZLocations task folder in the
CUSTOM_SDE_ORA11519_Adaptor folder.
4. Create Versions of the Copied Task Folder.
Before you begin customization, create versions of the model in

which the datastores to be customized exist.
Create versions of the model.

Create an original version
and a custom version.
Version the model in which the datastores to be customized exist. Submodels and datastores
cannot be versioned. The version comment should indicate that this is the base or original
version.
Create another version of the model, with a version comment indicating that this is where
customizations are introduced. The models can now be compared to show differences. If the
model ever needs to be patched, the model should be versioned again so that the patched
version can be compared to the custom and original version.
The example in the slide shows navigation to ODI Designer > Models > Oracle BI
Applications (folder) > Oracle BI Applications (model). A version number and description have
been enabled for both the original version and the customized version of the Oracle BI
Applications model. This model has the datastores that you will customize in a later step in
this lesson.
5. Create Versions of the Model.
Before you apply customizations to a task, edit the target

datastores to include the required column.
2. Click the Add Column
icon to add a new column.
1. Double-click the
datastore to open it
in the editor.
3. Set column properties.
Before you apply customizations to a task, edit the target datastores to include the required
column. In the example in the slide, you navigate to ODI Designer > Models > Oracle BI
Applications (folder) > Oracle BI Applications (model) > Dimension Stage and then edit the
W_GEO_DS dimension staging table to include the custom column, X_DESCRIPTION.
6. Edit the Target Datastores.
Double-click the interface

to open it in the editor.
Source
Target
Column
Drag the column from
the source to the target
to create the mapping.
Click the Mapping tab.
Some task folders have multiple interfaces, each of which must be customized with new
mappings. The example in the slide shows how to map the custom column,
X_DESCRIPTION, in the W_GEO_DS interface for the
SDE_ORA_GeographyDimension_HZLocations task folder. This assumes that a similar
mapping has already been completed for the W_GEO_DS_SQ_HZ_LOCATIONS interface,
which contains the source, SQ_HZ_LOCATIONS, for the W_GEO_DS interface.
To map the custom column in the W_GEO_DS interface, perform the following steps:
1. Expand Projects > BI Apps Project > Mappings > CUSTOM_SDE_ORA11510_Adaptor
> SDE_ORA_GeographyDimension_HZLocations > Interfaces.
2. Double-click the W_GEO_DS interface to open it in the editor.
3. Click the Mapping tab at the bottom of the editor.
4. Drag the DESCRIPTION column from the HZ_LOCATIONS source datastore to the
custom column, X_DESCRIPTION, in the W_GEO_DS target datastore.
Notice that the mapping indicates both the table and the column from which it comes:
SQ_HZ_LOCATIONS.DESCRIPTION.
7. Map the New Column in the Interface.
Generate DDL scripts to synchronize changes between the

ODI model and the data warehouse.
Select objects to synchronize.

ODI generates DDL
scripts in a procedure.
Right-click the model and

select Generate DDL.
When a diagram or data model is designed or modified in ODI, it is necessary to synchronize

changes between the ODI model and the data warehouse. This operation is performed with
DDL scripts.
For example, you need to synchronize the X_DESCRIPTION custom column that you created
in the BI Applications ODI model with the physical tables in the data warehouse. The example
in the slide shows the steps to synchronize the X_DESCRIPTION column with the W_GEO_DS
table:
1. To generate DDL scripts, right-click the Oracle BI Applications model folder and select
Generate DDL.
2. When processing completes, the Generate DDL Editor appears with the differences
detected.
3. Click the check box in the Synchronization column for the objects that you want to
synchronize. The example in the slide shows a check box in the Synchronization column
for X_DESCRIPTION.
4. When you click OK to generate the DDL script, ODI generates the DDL scripts in a
procedure, opens the procedure in the editor in the right pane, and stores the procedure
in a designated location.
8. Generate DDL Scripts.
Execute the DDL procedure to run the DDL scripts.

Execute the procedure.
Monitor the procedure.
Confirm the changes.
Procedure
Navigate to the location in Designer where the DDL procedure is stored and execute the
procedure. Use the Operator tab to monitor the procedure and verify that it completes
successfully. Use a SQL query tool to confirm that the physical tables are modified as
expected. In the example in the slide, the X_DESCRIPTION custom column has been added
to both the W_GEO_DS dimensions staging table and W_GEO_D dimension table in the data
warehouse.
9. Execute the DDL Procedure.
Prior to generating scenarios, ensure that the Scenario Naming

Convention user parameter has a value of
%FOLDER_NAME(2)%_%OBJECT_NAME%.
Select ODI > User Parameters.
Modify the Scenario Naming Convention parameter.
Prior to generating scenarios, ensure that the Scenario Naming Convention user parameter
has a value of %FOLDER_NAME(2)%_%OBJECT_NAME%. This ensures that generated
scenarios are easily identified as custom scenarios because the custom folder is included in
the naming convention.
1. In ODI Studio, select ODI > User Parameters.
2. Scroll to locate the Scenario Naming Convention parameter.
3. Change the value to %FOLDER_NAME(2)%_%OBJECT_NAME% from the default value
%OBJECT_NAME%.
Newly generated scenarios now will be named according to the modified Scenario Naming
Convention user parameter.
10. Modify the Scenario Naming Convention.
Generate scenarios for any new custom objects.

1. Right-click the custom task folder
and select Generate All Scenarios.
2. Set scenario
generation parameters.
3. Scenarios are generated

for all underlying objects
using the naming convention
set in User Parameters.
When a component is finished and tested, you can generate the scenario corresponding to its
actual state. Generating a scenario for an object compiles the code for this object for
deployment and execution in a production environment. When a set of packages, interfaces,
procedures, and variables grouped under a project or folder is finished and tested, you can
generate a group of scenarios.
Generate scenarios for any new custom adaptors, using the option to generate the scenario
as if all underlying objects were materialized. The scenario will be generated reflecting the
custom adaptor name. In the future, if you make changes to any of the interfaces or the
package, you can either regenerate the existing scenario or generate a new scenario.
The example in the slide shows how to create a group of scenarios for the objects in the
SDE_ORA_GeographyDimension_HZLocations custom task folder.
In the Scenario Generation dialog box, select the Creation generation mode. This creates for
each object a new scenario with the same name as the last scenario version and with an
automatically incremented version number. If no scenario exists for an object, a scenario
named after the object with version number 001 is created. Select Generate scenario as if all
underlying objects are materialized. In the Objects to Generate section, select Packages,
Interfaces, and Procedures. Scenarios are generated for all underlying objects with the
naming convention set in User Parameters.
11. Generate Scenarios.
Use known techniques to create and generate a load plan.
Use the techniques you learned in Lesson 9, Managing Load Plans, to create and generate
a load plan. In the example in the slide, the GL Revenue SDE Custom load plan has been
generated successfully.
12. Generate a Load Plan.
Open the generated load plan in ODI Studio Designer and

locate the step that you want to update.
1. Navigate to Designer >
Load Plans and Scenarios >
Generated Load Plans.
2. Open the generated

load plan in the editor.
3. Use the Search field
4. to locate the step that you want to update.
Open the generated load plan in the Designer editor and use the search field to locate the
step that you want to update. In this example, navigate to Designer > Load Plans and
Scenarios > Generated Load Plans and open the GL Revenue SDE Custom load plan. Use
the Search field to locate the step
SDE_ORA11510_ADAPTOR_SDE_ORA_GEOGRAPHYDIMENSION_HZLOCATIONS.
13. Open the Generated Load Plan.
Update the load plan step in the generated load plan to

reference the custom scenario.
In the Property Inspector for the

step, update the Scenario field
to reference the
custom scenario.
14. Update the Load Plan Step.
Use known techniques to execute and monitor the load plan.
Use the techniques you learned in Lesson 9, Managing Load Plans, to execute and monitor
the load plan. In the example in the slide, the GL Revenue SDE Custom load plan has been
executed successfully.
15. Execute the Load Plan.
Use a SQL query tool to verify that the data loaded as

expected.
16. Verify That the Data Is Loaded.
Which of the following statements about customization is not

true?
a. If you want to make changes to preconfigured ODI objects,
you must create a custom folder and make the changes in
it.
b. Preconfigured folders and the objects within them are
typically not overwritten in future upgrades.
c. The preconfigured ODI repository does not include any
custom folders.
d. You should create a custom folder for each prepackaged
SDE Adaptor folder that you have deployed that will have
customizations.
Answer: b
Quiz
Which of the following should be versioned before beginning

customization?
a. The task folder to be customized
b. The copied task folder
c. The model
d. The target datastores
Answer: a, b, c
Quiz
You should not create a separate custom folder for SILOS

customizations. Store customized SDE and SIL objects in the
same folder.
a. True
b. False
Answer: b
You should create a separate custom folder for customizations that you want to make to
objects in the SILOS folder. Do not store customized SDE and SIL objects in the same folder.
Quiz
Generate DDL scripts to:

a. Edit the target datastores
b. Create mappings in interfaces
c. Synchronize changes between the ODI model and the
data warehouse
d. Modify the scenario naming convention
Answer: c
Quiz
In this lesson, you should have learned how to complete the

steps for a Category 1 customization of the Oracle Business
Analytics Warehouse (OBAW).
Summary
In these practices, you will perform the tasks for a Category 1

customization:
11-1: Enabling Versioning for an SDE Customization
11-2: Creating a Custom SDE Mapping
11-3: Enabling Versioning for an SIL Customization
11-4: Creating a Custom SIL Mapping
11-5: Generating DDL Scripts
11-6: Running a Customized SDE Load Plan
11-7: Running a Customized SIL Load Plan
Practices

D82531GC10 Les11

Încărcat de

Informații document

Descriere originală:

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

D82531GC10 Les11

Încărcat de

Drepturi de autor:

Formate disponibile

These eKit materials are to be used ONLY by you for the express purpose SELF STUDY.

SHARING THE FILE IS STRICTLY PROHIBITED.

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

Oracle University and (Oracle Corporation) use only.

Building a Category 1 Customization

After completing this lesson, you should be able to complete

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

Oracle BI Applications 11g: Implementation Using ODI 11 - 2

Oracle University and (Oracle Corporation) use only.

In a Category 1 customization, you add additional columns

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

Oracle BI Applications 11g: Implementation Using ODI 11 - 3

Oracle University and (Oracle Corporation) use only.

Category 1 Customization: Adding Columns to

Scenario: Extract data from a column in a table in the

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

Oracle BI Applications 11g: Implementation Using ODI 11 - 4

Oracle University and (Oracle Corporation) use only.

Category 1 Customization: Scenario

1. Create custom SDE and SIL folders in ODI Studio.

Oracle BI Applications 11g: Implementation Using ODI 11 - 5

Oracle University and (Oracle Corporation) use only.

Category 1 Customization Steps

13. Open the generated load plan.

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

Oracle BI Applications 11g: Implementation Using ODI 11 - 6

Oracle University and (Oracle Corporation) use only.

Category 1 Customization Steps

On the Designer tab in ODI Studio, select BI Apps Project >

Custom folder for a

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

Oracle BI Applications 11g: Implementation Using ODI 11 - 7

Oracle University and (Oracle Corporation) use only.

1. Create Custom SDE and SIL Folders

Before you begin customization, create a version of the

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

Oracle BI Applications 11g: Implementation Using ODI 11 - 8

Oracle University and (Oracle Corporation) use only.

2. Create a Version of the Task Folder

Before you begin customization, duplicate the task folder to be

Copy the preconfigured task

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

Oracle BI Applications 11g: Implementation Using ODI 11 - 9

Oracle University and (Oracle Corporation) use only.

3. Copy the Preconfigured Task Folder to the

Before you begin customization, create versions of the copied

Create versions of the

and a custom version.

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

Oracle BI Applications 11g: Implementation Using ODI 11 - 10

Oracle University and (Oracle Corporation) use only.

4. Create Versions of the Copied Task Folder.

Before you begin customization, create versions of the model in

Create versions of the model.

and a custom version.

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

Oracle BI Applications 11g: Implementation Using ODI 11 - 11

Oracle University and (Oracle Corporation) use only.

5. Create Versions of the Model.

Before you apply customizations to a task, edit the target

3. Set column properties.

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