Topics:

Universe Details
Tables

domine

Hierarchies

Tpyes of Reports Generated

Complex Reports - Year Wise Consolidated Report

Complex Reports - Country wise invoice and Sales Revenue Report

Challenges Faced
1. Performance Issues
2. Linking/ Merging Dimensions
3. Ambiguous Queries

Issues
o

Nested Conditions

Error Messages

Project Explenation:
Project: Executive Dashboard
Client: Powerwave Technologies, Inc., Santa Ana , CA
Duration: July 2007 to Date

The Project is mainly to meet the reporting requirements of Power Wave

Technologies. Power Wave Technologies is one of the leading companies which
provides end to end wireless solutions to the wireless net work communications. It
trades nearly with 75 countries around the Glob.

The primary objective of this project is to ensure that Power Wave technologies,
effectively meet its current and future reporting requirements. The system addresses
all reporting aspects for management reviews, state level reporting and field level
report generation.
This system utilizes data from powerwave data warehouse. The source for the data
warehouse is the financial transactions, populated from Application data that is Oracle
11i , people soft .
The main objective of the project is to provide powerwave technologies with a new
reporting tool for management reports, Field Report, and State level Reports. The
system provides alerts and Thresholds to the field and management over a given
period.
This Project is much useful to the Powerwave Technologies

To assist the sales force in tracking and anolyzing key compliance

metrics.
To reduce the time for compiling and verifying data manually to
generate reports and allow time for more strategic initiatives to be
pursued.

To Provide analytical reporting capabilities to the groups.

To empower the business users to add and customize the business rules /
solution with minimum IT investment.

Here we have created reports which answer many questions of the managerial team in
their decision making process. Like how many orders are in pipeline, how many
shipments and how many backlogs. Majority of the information is presented in a
tabular form, in which it can be sliced and diced by various dimensions such as
region, country & location. Another view of this is based on what kind of items and
product groups. The drill-down is applied on each dimension to get to the bottom
information. For example the backlog orders report, the drill-down can be done to see
by region, country and location. Similar reports are also created to show by sales
representatives to calculate their commissions.
Different trend analysis reports to know the trending of particular product or orders
placed by a particular customer are created to provide decision power to executive
team. These trending reports are again drilled down to provide data by year, quarter,
weeks, product groups and sales persons wise etc.

In this project i have involved in analysing requirements, Creating Universes, Crating

reports, Testing reports i.e Unit testing.

Universe Details
MULTI STAR SCHEMA is used.
Data base size is around 250 GB.
Tables in the schema are nearly 170 in The Universe.
Name some tables in your schema:

Sales order header

Sales item facet

Product hierarchy

Customer hierarchy

Country

Time hierarchy

What is the Domine of the Project:It is not exactly one domine

It deals with finance, sales, Manufacturing and HR but the main focus is on sales.
The UNIVERSE DETAILS :-

There are three universes in the Projects

Pwdm01.unv(power wave sales),

pwdm02.unv(Power wave manufacturing),

pwdm03.unv(Power wave HR)

Name : Powerwave sales (PWDM01.unv)

No of classes : 75
Hidden Classes : 10

No of Objects : 630

Hidden : 176

Visible : 463

Total Joins : 156

Total Context paths : 9

o

Sales context, invoice context, Backlogs context etc

No of Aliases : 53

Hierarchies :- No of hierarchies : 4
Time Hierarchy
Year,Physical Year,callender Year half, Season, Quarter, Month
Geographical Hierarchy
Out let name, Address, city, Region, Country, zip Code, Continent
Product Hierarchy
Model, Model Description, Package type, Quality, catogory....etc
Customer Hierarchy
Name, Compani name, Business Grade, Address, Phone, zip Code, City, region,
Country, Continent.
classes and objects:
Account Dim,Account lines fact,Act Detais

Batch creation date

o Batch ID
o

Bill code

Invoice no

Invoice type

Supplier name

Supplier number ..

Other classes like

Analitical dimension ,Batch Dim, Buyer Dim, Comodity dim ,Discount dim,
Ependeture dim, Invoice date, Invoice dim, Item dim, Item type dim, Payment dim,
Payment method dim, Project dim, Project quantity dim, Receipts dim, Tax code dim,
Tax details facts,Vendor Dim, Vender site Dim, Address and other details

Types of reports generated :

Total reports created are around 140 from Sales Universe.
Created many Master detail reports, cross tabs, tables, business tables, charts with
multipe filter and formating options both in webi and Deski.
To name some of them are

Country wise product wise time based Reports

Product wise discount reports

Sales persons wise product wise Reports

Country wise model wise reports

Order cansalation reports

Order delevary Reports

Location listing

Country of Origin Report (by Region)

Country of Origin Report (by supplier)

Buyers Listing

Buyers Requisition action Required report

Cancled purchase order Report

Cancled requisition report

Payments of orders reporting(by Buyer)

quotation action required request

supplier purchasesummary report

Financial Reporting for the top level finance management

Tax reporting for the corporate personal or tax management team

Inventory visibility and other visibility for inventory personal

Reports:
A complex Report :Year wise consolidated Report
This report contains
County | Region | Product | Item | Quarter | Month | Sales Revenue | etc..
Report explanation:

For this year wise consolidated report we have columns like country, region,
product, model, quarter, month and sales revenue.
Here we have two sections on country and region.

Under region section we have two blocks.

One cross tab and one chart.

The crass tab is 4 dimensional. That means on top two headers which shows
data quarter wise and month wise.

At right side we have two column heading product wise model.

In the body of the cross tab we are showing the sales revenue mesure.

The left columns have multiple sorts by product and by model.

Then the horizontal and vertical breaks are applied and sub totals are calculated
on all breaks.

Then the grand totals are calculated on sections and on report level.

All the total are highlighted according to the user specifications.

To differentiate the section wise data sections wise backgrounds are formatted.

In the other block, by the side of the cross tab one more 3D chart is displayed
which shows product wise, model wise and quarter wise revenue.

To restrict data to a particular year and to allow user to select the year from the
list of values query prompts are used.

Finally user selected values is displayed in the header section.

Here understanding the requirement is a major task than creating the report.

Strategy Reoprts :

Country wise invoice and sales revenue

Expected collection report

Cash collection summary report

Project over view report etc.

1. Country wise invoice and sales revenue report:

With drill options

Provided upto 3levels down scope of analysis

One section

With two blocks with one table and one chart

These information can be slice and dice such as region | country | location etc.
Another forms of this is based on kind of items and product groups. And even it
facilitates us to see the information on time hierarchy. All amounts are converted into
local US Dollars.
Similar reports are also created to show by sales representatives to calculate their
commissions etc.

Different trend analysis reports are also created to know the trends of particular
product or orders placed by particular customer are created to provide decision power
to the executive team.
These trending reports are again drilled down to provide data from different angles
like year | Quarter | week | Continent | country and region.
Challenges Faced:
1. Performance Issues
2. Linking/ Merging Dimensions
3. Ambiguous Queries
Performance Issues :
Performance issues for some reports where in which the reports are taking more time
to run. We have analyzed the SQL provided by Business Objects and then we found
out some tables that are not needed for the query are getting into the query. We have
eliminated this problem by modifying the universe like the join conditions, we have
used aliases and context paths to over come the problems.
Linking/ Merging Dimensions:
For some reports we had to get data from 5 different data providers from 3 different
universe. Which took nearly 15 days to finalize the problem. When we merge
dimensions some objects use to become incompatable to the other dimensions. So
finally with the help of ETL team we could able to solve the problem.
Ambiguous Queries:
In one report when we create a report we were getting much erroneous data. When we
verified in Bo generated SQL we found ambiguous queries. It is due to some join
problems in the universe structure schema. With the help of universe designers we
resolved this problem.
Others:
Even there are some technical issues where I face some problems. But those are miner
which are solved by going through the PDFs, R&D, going to forams etc.
Ex: Drill with multiple blocks, Cascading Prompts etc.

Issues:
Nested Conditions: In one report I am asked to use nested conditions by using 5 conditions.
But in spects instead of one order they sent me the different ordered conditions spects.
It is due to small confusion in attaching the spects copy . Instead of attaching
corrected document copy, he sent just attached old copy which caused problem and
report carried different set of incorrect data.
While testing he found it and asked me to verify the conditions. My argument was that
it is correct and even I sent back his mail for reference.
He then realized the actual problem and sent a new mail with correct spects document.
Finally we could able to solve the problem with in an hour with mutual co-opiration
and understanding.
Error messages:Want some regular error messages we face in day to day work environment.

Users of the Exeutive Dash Board : -

There are mainly three groups of users who would use the EDB(Executive Dash
Board).
1. Field Force :- The field force consis of the Sales Representatives (SR) and District
Managers (DSM).
They have access to a limited set of data, which is more specific to their
requirements. They are restricted to use the predefined reports that are provided to
them.
SR : -

They have access to the data accessible to individual SRs reproting to them.
They also have access to the aggregated data for their region and overall figures at
national level. These allow them to comare themselves with their papers.
DSM :-

2. Management:- The management Users will be accessing the system in online

mode and would have the ability to access a greater amount of data. These will be
power users who will have the ability to create new reports on their own use (Adhoc
reports)

The RBAs (Reginal Business Analysts)

The (RSDs)Reginal sales Director / (ASD)Area Sales
Director / (NSD)National Sales Director

The Business Central Leaders (BCL)

3. State Reporting Group:- The State compliance users will be accessing the system
in online mode and would have the ability to access a great amount of data. These will
be the power users who will have the ability to create state driven compliance reports
for their State Legislation submission as well as their own use. Different users here are

State Compliace Team

The Legal Department for State Compliance

The State Compliance Managemment Team