Professional Documents
Culture Documents
Oracle Data Warehouse Builder Practical Index
Oracle Data Warehouse Builder Practical Index
Oracle Data Warehouse Builder Practical Index
4. Creating Dimensions
1. Creating REL_CATEGORY dimension.
2. Creating REL_TIME Dimension.
5. Creating a Cube
7. Deploying
1. Deploying External Table and Viewing Data.
2. Deploying tables, sequences, mappings and cube.
3. Running the Mappings.
4. Viewing Loaded Data in the Cube.
Run the Net Configuration Assistance as shown in above Fig to Configure the Listener
Creating a Database
Click on the Database Configuration Assistant as shown in above Screen Shot and follow the
Screenshots below to create a Database named “MCCDW”
In Step 5 for Ease of Access we enter a common password for all Account in our case password
is “oracle”
From the List we can see Oracle Warehouse Builder is installed and a database named
MCCDW will be created. If you want you can save the list as HTML file
During the installation you will be prompted with following popup with various information.
Make sure you click on Password Management button to unlock OWBSYS Schema.
In Password Management window just uncheck the blue tick beside the OWBSYS and enter the
password you want. In our case it is “oracle”. And click on OK
The Repository Assistant enables you to create a Warehouse Builder Design Repository in your
database to store the metadata definitions that describe your sources, targets, and ETL
processes.
Here the password is oracle for SYSTEM if you are following this document
Click Unblock
Click OK and you have successfully created a Repository with mcc_user as workspace user.
Design Center is the main OWB client in which you design sources, targets, ETL mapping and
transformations.
After you have logged into Design Center, Click on the Design menu and select New
From the Pop-Up Window enter the name of the Project “MCC_PRJ”
We can see a new Project is created and can be viewed in Project Explorer window
Expand the MCC_PRJ. Right-click the Files node and select New
On the Create Module Wizard: Name and Description page, enter SOURCE as the name for the
module. Click Next.
The Create Module Wizard: Connection Information page appears. In a flat file source module,
Location is the path or the directory in the file system where the flat files reside.
On the Create Module Wizard: Connection Information page, OWB creates a default location,
SOURCE_LOCATION1. Click Edit… and you will see Edit File System Location1 window Pop Up
In the Edit File System Location: SOURCE_LOCATION1 window, rename the default name
SOURCE_LOCATION1 to SOURCE_LOCATION.
Click Browse and locate the folder named “sourcefiles” In my case the folder is in D: drive
which consist of two CSV files named expense_categories.csv and export.csv
Click OK
In the Connection Information window, ensure that Import after finish is selected. Selecting this
option launches the Import Metadata Wizard. Click Next
Tip: If the check box is not selected, the Import Metadata Wizard does not launch automatically.
To launch the Import Metadata Wizard manually, in Project Explorer, expand Files, right-click the
SOURCE module, and select Import
On the Import Metadata Wizard: Filter Information page, accept the default selection All Data
Files and click Next.
On the Import Metadata Wizard: Object Selection page; expand the D:\sourcefiles node (the
location where you unzipped the setup files).
A list of files is displayed. Use >> (Add All) to move all file definitions from the Available list to
the Selected list. Click Next
On this page, you see two file definitions (expense_categories_csv and export_csv) prefixed
with a red cross.
The Red Cross indicates that there is no metadata information available for this file within the
Warehouse Builder repository.
Before importing, Warehouse Builder needs to know the structure of these files. Through the
sampling process, information about the structure is gathered.
On the Import Metadata Wizard: Summary and Import page, select expense_categories_csv file,
if it is not already selected. Click Sample.
On the Flat File Sample Wizard: Name page, accept EXPENSE_CATEGORIES_CSV as the default
file's name.
This is the name by which Warehouse Builder refers to the file after it is imported. Warehouse
Builder offers a large number of character sets, which you could use to read the data.
Accept the defaults on this page. This file has two columns: Expense Type and Expense
Categories. The wizard makes assumptions about the structure of the flat file.
The lower portion of the dialog box displays a sample of how OWB imports the rows of the flat
file data into columns in a table. Click Next.
On the Flat File Sample Wizard: Record Organization page, accept the default option of Records
delimited by carriage return (<CR>). Click Next.
On the Flat File Sample Wizard: File Format page, accept the default option of Delimited for file
format. Click Next.
On the Flat File Sample Wizard: File Layout page, accept the default values of 0 for Skip Rows.
The expense_categories.csv file is an example of a single record type file.
You can use the values in the first record for the field names, when the flat file's first record is a
header.
On the Flat File Sample Wizard: Field Properties page, select Use the first record as the field
names
In the following screenshot, notice that the field names have changed.
Click Next.
Review the summary specifications that you have defined for the expense_categories_csv file.
On the Flat File Sample Wizard: Summary page, click Finish
On the Import Metadata Wizard: Summary and Import page, in the Status field for
expense_categories_csv, the green check mark indicates that expense_categories_csv has
been sampled.
Now select the export_csv file if not already selected. Click Sample
Accept the defaults on this page. This file has 14 columns. Click Next
On the Flat File Sample Wizard: Record Organization page, accept the default option of Records
delimited by carriage return (<CR>). Click Next.
On the Flat File Sample Wizard: File Format page, accept the default option of Delimited for file
format. Click Next.
On the Flat File Sample Wizard: File Layout page, accept the default value of 0 for Skip Rows.
The expense_categories.csv file is an example of a single record type file. Select Single Record
for Record Type and click Next.
On the Flat File Sample Wizard: Field Properties page, select Use the first record as the field
names. You can choose to use the values in the first record for the field names, when the flat
files first record is a header.
Now there is an error because date is a reserved word and you have not yet renamed the date
field.
On the Flat File Sample Wizard: Field Properties page, select Date.
From the Type drop-down list, select Date. In the Mask column, enter dd-mon-yy (without
single quotation marks).
We can see Date is used as Column name which is a reserved keyword in Oracle.
We encounter another error here On the Flat File Sample Wizard: Field Properties page
Click Next. The Flat File Sample Wizard: Summary page appears
Review the summary specifications that you defined for the EXPORT_CSV file. On the Flat File
Sample Wizard: Summary page, click Finish
On the Import Metadata Wizard Summary and Import page, the green check mark in the Status
field for both EXPENSE_CATEGORIES_CSV and EXPORT_CSV indicates that both the files have
been sampled.
On the Import Metadata Wizard: Summary and Import page, click Finish.
The import begins. Importing Progress Dialog shows the import progress.
In Project Explorer, expand Files > SOURCE. You see the two tables
(EXPENSE_CATEGORIES_CSV and EXPORT_CSV) you just sampled and imported.
In the Design Center, click Save All on the toolbar. In the Warehouse Builder Warning
window, click Yes to commit your work.
To set up your target warehouse module, you perform the following steps:
In the Global Explorer panel, expand the Security node. Right-click the Users node and select
New
In the Create Database User dialog box, enter system as username and <your system account
password> as the password.
Enter EXPENSE_WH as the username for the new DB user and enter the password you want.
Accept the defaults for the tablespace properties. Click OK
Observe EXPENSE_WH has been added to the Selected Users list. Click OK
Examine the Users node. You find the EXPENSE_WH user added to the list of existing target users.
Also, in the Connection Explorer panel, expand the Oracle Locations node and note that a new
location, EXPENSE_WH_LOCATION, has been added.
You have created a new target schema, EXPENSE_WH, which will physically store your target
warehouse objects.
In the MCC_PRJ project, expand the Databases node, right-click the Oracle node, and select
New
The Create Module Wizard is launched. Click Next on the Welcome page.
On the Name and description page, enter EXPENSE_WH as the name of the module.
Accept Development as the module status and ensure that Warehouse Target is selected as
the module type. Click Next
Enter the Details as shown in above Screenshot and Click on Test Connection
Observe that all the information is already filled with the location, EXPENSE_WH_LOCATION
Observe that the EXPENSE_WH target module has been added under the Oracle node of the
MCC_PRJ project. Expand EXPENSE_WH and examine its contents.
The User and the location created are highlighted in above Screenshot.
In the previous practical, you created a flat file module in which you imported and
sampled two flat files.
To move and transform data from flat files into relational or dimensional targets, you can
use either a flat file operator or External table.
External tables enable you to represent data from file sources in relational table format
External tables allow you to directly query flat files from the Oracle database and also
query join, transform, and constrain flat files.
Here now, we create two external tables that will point to the two previously sampled flat files.
The Create External Table Wizard is launched. Click Next on the welcome page. The wizard
guides you through the creation of an external table.
On the Name and Description page, enter EXPENSE_CATEGORIES as the name of the external
table. Click Next
On the Locations page, you select the default location that is used by the external table.
Select SOURCE_LOCATION from the location drop-down box. Click Next
Now, you repeat the same steps to create an external table for the export_csv file.
Observe, that both external tables are added to the target module.
You need to configure the physical file system details for the two external tables.
Right-click EXPENSE_CATEGORIES and select Configure.
In the Configuration Properties dialog box, right-click Data Files and select Create.
Accept the default name, NEW_DATAFILE_1.
On the right side in the Configuration Properties dialog box, select SOURCE_LOCATION for the
Data File Location property.
For the Data File Name property, enter expense_categories.csv. Click OK.
Repeat the same steps to configure the EXPENSE_DATA external table. The configuration
should look as shown in the screenshot.
Click OK
You have finished creating two external tables pointing to the two sampled flat files.
Designing Dimensions
Dimensions are the primary organizational unit of data in a star schema.
A dimension consists of a set of levels and a set of hierarchies defined using these levels.
Users often analyze data by drilling down on known dimension hierarchies.
1. Dimension Attributes
2. Levels
3. Level Attributes
4. Hierarchies
Warehouse Builder enables you to not only create but also populate time dimensions. When you
create a time dimension using the wizard, Warehouse Builder automatically creates the mapping
for you to populate the time dimension.
Now, expand EXPENSE_WH, right-click Dimensions and select New > Using Time Wizard.
The Create Time Dimension Wizard is launched. Click Next on the Welcome Page.
On the Name and Description page, enter REL_TIME as the name of the dimension. Click Next.
On the Storage page, select Relational Storage (ROLAP) to specify relational implementation
of the dimension. Click Next.
On the Data Generation page, you specify the range of time data that is required for your
warehouse.
This information is used to generate a mapping that populates the time dimension.
For Start Year, enter 2003 and for Number of Years enter 3. Ensure that Calendar is selected, as
shown in the screenshot.
On the Levels page, select Normal Hierarchy and select all the levels: Calendar Year, Calendar
Quarter, Calendar Month and Day. Click Next.
On the Pre Create settings page, examine the details and click Next.
A progress bar shows the progress as the wizard creates the necessary objects.
On successful completion, click Next. On the Summary page, examine the details again and click
Finish.
Observe that the wizard has generated four objects necessary for a fully functional TIME
dimension:
If you are curious to know how REL_TIME_MAP looks like, Right-click REL_TIME_MAP under
the Mappings node and select Open Editor and this will launch the Mapping Editor
From the View menu, select Auto Layout. You can see the expanded mapping.
In the EXPENSE_WH module, right-click Dimensions and select New > Using Wizard
The Create Dimension Wizard is launched. Click Next on the Welcome Page.
On the Name and Description page, enter REL_CATEGORY as the name of the dimension. Click
Next
On the Storage Type page, select Relational Storage (ROLAP) to specify the relational
implementation of the dimension. Click Next.
On the Dimension Attributes page, you find three predefined columns, ID, NAME, and
DESCRIPTION.
Note that for the ID attribute, the identifier is set as Surrogate and for the Name attribute the
identifier is set as Business.
You can change these attributes to your liking, but must have a surrogate and a business
identifier in the list.
On the Levels page, specify the following levels for the default hierarchy in the dimension:
Click Next.
On the Level Attributes page, for each level that you have defined, you select the dimension
attributes that apply to that level. Accept the default selection and click Next.
On the Slowly Changing Dimension page, leave the default slowly changing dimension option
selected. Click Next.
Click Next.
On the Pre Create Settings Page. The Dimension Creation Progress page appears. On successful
completion, click Next. Click Finish on the Summary page.
Observe that REL_CATEGORY dimension has been added to the EXPENSE_WH target module.
With the dimension, Warehouse Builder also creates a table that implements the dimension in a
star schema and also creates a sequence to load the ID column of the dimension.
Designing Cubes
Cubes contain measures and link to one or more dimensions.
The axes of a cube contain dimension values and the body of the cube contains measure
values.
In a relational implementation, a cube is linked to dimension tables by foreign key
constraints and consists of a set of measures.
1. Cube Measures.
2. Cube Dimensionality.
Now switch to the EXPENSE_WH module, right-click Cubes, and select New > Using Wizard
The Create Cube Wizard is launched. Click Next on the Welcome Page.
On the Name and Description page, enter REL_EXPENSE as the name of the cube. Click Next.
On the Storage Type page, select ROLAP: Relational Storage to specify relational
implementation of the cube.
Click Next
On the Dimensions page, you select the dimensions that the cube will refer to. In the Available
Dimensions list, expand Dimensions, and then expand EXPENSE_WH.
Select EXPENSE_WH, and then click > to move the two dimensions REL_CATEGORY and
REL_EXPENSE to Selected Dimensions list. Click Next.
On the Measures page, enter EXPENSE in the Name field. Accept the default data type. Click
Next.
On the Summary page, review the cube details and click Finish
Observe that REL_EXPENSE cube is added under the Cubes node of the EXPENSE_WH module.
To view the cube in the Data Object editor, right-click REL_EXPENSE and select Open Editor or
double-click REL_EXPENSE.
Examine the cube, and then close the Data Object Editor.
From the Design menu, select Save All to commit your work.
So till now, we have created two external tables mapped to the two previously sampled source
flat files, two dimensions, REL_TIME and REL_CATEGORY, and a cube REL_EXPENSE linked to
the two dimensions.
Designing Mappings
Mappings extract data from the source, transform the data, and load the data into the target
module (EXPENSE_WH), which you defined in the previous Practical.
Note that you see a REL_TIME_MAP mapping, which was automatically created by OWB when
you created the time dimension REL_TIME using the Time Wizard.
In the Create Mapping window, enter REL_CATEGORY_MAP as name of the mapping. Click OK
In the Project Explorer panel, you see an entry for the REL_CATEGORY_MAP mapping under the
EXPENSE_WH module.
From the Palette, drag the Dimension operator to the canvas. The Add Dimension Operator
window appears.
In the Add Dimension Operator window, navigate to the EXPENSE_WH module and select the
REL_CATEGORY dimension. Click OK.
Alternatively, you can add existing sources and targets to a mapping through the Explorer
panel, which is on the left side of the Mapping Editor.
Expand Oracle > EXPENSE_WH > External Tables. Drag EXPENSE_CATEGORIES to the canvas.
Now there are two objects on the canvas, the EXPENSE_CATEGORIES external table and the
REL_CATEGORY dimension.
EXPENSE_CATEGORIES.OUTGRP1.EXPENSE_CATEGORY to
REL_CATEGORY.CATEGORY.DESCRIPTION
Connection lines graphically represent how the data flows from a source, through operators, and
to a target.
You have just completed designing the mapping. Now get ready to generate the code for the
mapping.
In the Mapping Editor, from the menu, select Mapping > Generate. You have now generated
the code that loads the dimension. Based on the ETL logic that you design in a mapping,
Warehouse Builder generates the code required to implement your design.
The Generation Results window is displayed. The Generation Results window displays the code
that has been generated for you.
In the Create Mapping window, enter REL_EXPENSE_MAP as the name of the mapping. Click
OK.
In the Project Explorer you see an entry for the REL_EXPENSE_MAP mapping under the
EXPENSE_WH module.
In the Explorer panel, on the left of the Mapping Editor, ensure that the Available objects tab
is selected.
Expand Oracle > EXPENSE_WH > External Tables. Drag the EXPENSE_DATA external table to
the canvas.
In the Explorer panel, ensure that the Available objects tab is selected.
Now, there are two objects on the canvas, the EXPENSE_DATA external table operator and the
REL_EXPENSE cube operator.
In the Mapping Editor, from the Palette panel, drag the Expression operator to the canvas.
In this example, the Expression operator is used to transform the EXPENSE_DATE attribute in
the EXPENSE_DATA external table from a date data type to a number data type.
The target attribute in the cube is a number data type; therefore, this data type conversion is
required to match the data type.
Right-click the expression operator EXPRESSION header and select Open Details
In the Expression Editor, click the Output Attributes tab. Click Add.
Rename the OUTPUT1 attribute to EXPENSE_DATE. Ensure that the data type is NUMBER. Click
OK.
In the Mapping Editor, click the expression operator EXPRESSION header, and select
OUTGRP1.EXPENSE_DATE.
In the Attribute Properties panel, click the field next to the Expression property and Click the
Ellipse button on the extreme right to launch Expression Builder.
In the Expression Builder, enter the following statement in Expression for EXPRESSION.
REL_EXPENSE.REL_EXPENSE.REL_TIME_DAY_CODE
REL_EXPENSE.REL_EXPENSE.REL_CATEGORY_NAME
REL_EXPENSE.REL_EXPENSE.EXPENSE
You have just completed designing the mapping. Now you can generate the code for the
mapping.
In the Mapping Editor, from the menu, select Mapping > Generate.
The Generation Results window appears. The Generation Results window displays the code that
has been generated for you.
From the toolbar, click Save All to commit your work. Close the Mapping Editor.
Deployment is the process of creating your target system from the logical design or
model.
The process includes generating scripts, such as DDL that creates data objects (such as
tables, views, and dimensions).
The process also includes generating SQL, PL/SQL, and SQL*Loader scripts that load data
into data objects.
When you deploy relational database or dimensional objects, such as sequences, tables,
dimensions or cube, the DDL scripts are generated and executed simultaneously to
physically create the objects.
When you deploy ETL mappings, the deploy procedure only generates a PL/SQL script.
You need to explicitly execute the scripts to perform ETL.
To deploy objects, Oracle Warehouse Builder provides two options: you can either use
the Control Center Manager or you can deploy objects directly from the Project
Explorer in the Design Center.
The Control Center Manager offers a comprehensive deployment console that enables
you to view and manage all aspects of deployment, including configuration and
validation.
In the Control Center Manager, you can view the deployment history of an object. The
deployment history is also used to automatically determine the default deployment
action.
These options are not available if you deploy objects from the Project Explorer tree in the
Design Center.
To deploy, you must launch the Control Center Manager. From the Tools menu, select
Control Center Manager.
The Control Center Manager is launched. The Control Center Manager console appears
as shown in the screenshot.
In the navigation tree on the left, expand and select External Tables.
In the Object Details panel on the right, check whether the Design Status is set to New
for both external tables, EXPENSE_CATEGORIES and EXPENSE_DATA.
Click Default Actions (highlighted in the screenshot) and observe that Deploy Action is
changed to Create.
To deploy the selected external tables, from the File menu, select Deploy > To Control
Center or click the Deploy
You have now successfully deployed the two external tables to the EXPENSE_WH
schema.
To check the data loaded in External table Right Click on EXPENSE_CATEGORIES and
select Data.
Check all the data from the Flat files are loaded into External Table.
We can see here 1,425 Rows are inserted into EXPENSE_DATA External Table.
Before you deploy the dimensions and the cube, you need to deploy the relational tables and
sequences that these dimensions and cube are based on.
In EXPENSE_WH, expand Tables. Expand Sequences. To deploy all the tables and sequences,
select Tables, press and hold [Ctrl], and select Sequences.
Observe the Design Status of the three tables and two sequences.
From the File menu, select Deploy > To Control Center or click the Deploy button on the
toolbar.
You can now deploy the cube. Before the cube is deployed, you should have deployed the
related dimensions.
Before you deploy the dimensions and the cube, ensure that the deployment option is set to
Deploy to Catalog Only.
To set the deployment options, right-click the appropriate dimension or cube in the design
center and select Configure from the menu. In the Configuration Properties dialog box, set the
deployment options property to Deploy to Catalog Only.
The screenshot shows Configuration Properties dialog box for REL_EXPENSE cube.
In EXPENSE_WH, expand and select Dimensions. Observe that Design Status for all the objects
is set to New.
To deploy, select Deploy > To Control Center from the File menu, or click the Deploy button
In EXPENSE_WH, expand and select Cubes. Note that Design Status for all the objects is set to
New.
To deploy, select Deploy > To Control Center from the File menu, or click the Deploy button
The REL_EXPENSE cube and the REL_TIME and REL_CATEGORY dimensions are successfully
deployed.
You have deployed the external tables, the dimensions, and the cube; you now deploy the ETL
mappings. When you deploy a mapping, Warehouse Builder generates appropriate scripts.
For mappings, you need to follow an extra step of executing these scripts to actually perform
ETL from the source to the targets.
In EXPENSE_WH_LOCATION, select Mappings. In the Object Details panel, three mappings are
selected with Design Status set to New.
From the File menu, select Deploy > To Control Center or click the Deploy button.
The mappings are deployed successfully and are ready for execution
To load data into the target dimensions and cube, you need to execute the Mappings.
To execute a Mapping, you can either select Start from the File menu or click the Start button
on the toolbar or Right click the Mapping and select Start.
Executing REL_TIME_MAP
When you click the Start button, the Control Center Jobs panel switches to the Execution tab.
To view the execution details, double-click LOAD_EXPENSE_WH in the Job column of the
Control Center Jobs panel.
Click the Execution Results tab and monitor Row Activity. You can get a count of how
many rows were inserted in respective dimensions and the cube.
Executing REL_EXPENSE_MAP
Executing REL_CATEGORY_MAP
On successful execution, all the dimensions and the cube are now loaded with data.
You can view the data loaded in the dimensions and the cube from within the Oracle
Warehouse Builder design client environment by using the Data Viewer.
To view REL_EXPENSE cube data, expand Cubes under EXPENSE_WH and right-click
REL_EXPENSE. Select Data.
Similarly you can view the cube data from Data Object Editor within the Data Viewer
tab.
At bottom you can view the data in Graphical format by clicking on small icons.
PivotTables are one of the most powerful features of Microsoft Excel. They allow large amounts
of data to be analyzed and summarized in just a few mouse clicks.
First, ensure that you have some raw data in a worksheet in Excel. So we start Excel and we load
such a list.
Once we have the list open in Excel, we’re ready to start creating the PivotTable.
What data should your new PivotTable be based on, and where should it be created?
Because we already clicked on a cell within the list (in the step above), the entire list surrounding
that cell is already selected for us.
We also need to select whether we want our new PivotTable to be created on a new worksheet,
or on an existing one. In this example we will select a new one:
The new worksheet is created for us, and a blank PivotTable is created on that worksheet:
The list of fields in the top part of the box is actually the
collection of column headings from the original raw data
worksheet.
The four blank boxes in the lower part of the screen allow us to
choose the way we would like our PivotTable to summarize the
raw data.
Oracle Warehouse Builder Practical Manual. Compiled By – Prof. Kirti Shirwayya. [208]
Mulund College Of
So far, there is nothing in those boxes, so the PivotTable is blank. All we need to do is drag
fields down from the list above and drop them in the lower boxes.
A perfect candidate for this this Value box in our sample data is the “Amount” field/column.
Notice that (a) the “Amount” field in the list of fields is now ticked, and “Sum of Amount” has
been added to the Values box, indicating that the amount column has been summed.
If we examine the PivotTable itself, we indeed find the sum of all the “Amount” values from the
raw data worksheet.
Now if we would like to see a summary of our data, where we have a row heading for each of
the different salespersons in our company, and a total for each salesperson.
To achieve this, all we need to do is to drag the “Salesperson” field into the Row Labels box:
Using “Payment Method” as a column heading. Simply drag the “Payment Method”
heading to the Column Labels box:
This allows us to filter our report based on which “holiday package” was being
purchased.
We only want to see cheque and credit card transactions (i.e. no cash transactions),
then we can deselect the “Cash” item from the column headings.
Click on the drop-down arrow next to Column Labels, and un-tick “Cash”:
First, ensure that you have some raw data in a worksheet in Excel. So we start Excel and we load
a list. Once we have the list open in Excel, we’re ready to start creating the PivotChart.
Then, from the Insert tab, click the PivotTable dropdown icon and select PivotChart:
The Create PivotTable with PivotChart box appears, asking you two questions:
What data should your new PivotTable be based on, and where should it be created?
Because we already clicked on a cell within the list (in the step above), the entire list surrounding
that cell is already selected for us.
We also need to select whether we want our new PivotChart to be created on a new worksheet,
or on an existing one. In this example we will select a new one:
Use the PivotChart Filter Pane to sort and filter the underlying data and change the
appearance of the PivotChart report.
Axis fields (Categories) box: This displays items from the Row label of the associated
PivotTable report that form individual categories for which data points are charted. Categories
appear on the horizontal (category) axis, also called the x-axis, of the PivotChart report.
Legend fields (Series) box: This displays items from the Column label of the associated
PivotTable report that form the individual data series. The names of the series appear in the
legend of the PivotChart report.
The Report Filter box: If the associated PivotTable report has one or more report filters, you can
use the Report Filter box as a convenient way to summarize and quickly focus on a subset of
data without modifying your series and category information.
To start with a pivot chart lets drag the Amount field from the Field List into the Values Box,
notice that a chart is created with a label of Sum of Amount and total amount is displayed.
Now drag Salesperson from field list and drop into the Axis Field box and notice that
salesperson is listed on the X-axis with total Amount on Y-Axis.
Similarly you have to drag Package from the Field List into the Report Filter box and Payment
method into the Legend Fields box.
You can filter the data according to Payment Method by clicking on the link on the chart and
filter out the data by ticking appropriate options.