Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations wOOdy-Soft on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

BO Question

Status
Not open for further replies.

mpiana70

IS-IT--Management
Apr 23, 2008
4
EU
Question from a context:
When setting up a data query system using Business Objects, what, apart from the specifications,
is the first thing you should do ?
a) design the report layout
b) define the query interface
c) create the universe
d) analyse the disk space available for executiong reports
Anyone know the answer (a or c ?)
Thanks !
 
data query system? query interface?

This question feels like it is only partly BO related.

Focus on the universe, I'd guess..



Ties Blom

 
I though was design the report layout ....
 
You would need a proper universe to base your reports on don't you think ?

Ties Blom

 
Yes thats right, but you can also before define a report template and then the universe.
 
Sure, but your universe design will be driven by the database you are going to report against. That's a bit more important than a particular report template..

Ties Blom

 
I would say it depends how you understand the expression “design the layout”.

says:

To Create a new report using the Report Wizard:
? From the Menu bar click -> File > New
– For the Report Layout – Select Generate a Standard Report
– For the Way to Access Data – Select
? Universe and then Next
? Select the ‘Training DB in Oracle’ Universe from the list and click Finish ….

So, the first thing here is too choose between a standard layout or a template. Could this be called “Design the querry layout”, I am not sure.
At the end you can “format” your report (so this could also be called designing the layout).
 
Your initial question was on the priority of universe design versus report layout. If you are going to create reports on an existing training universe/database, then the question is academic, I guess.

'Query layout' is an ominous term. You fetch data through the query panel , which has nothing to do with layout (neither query or the report)

In BO 6.5. client the query build and the report layout are 2 seperate actions.

Ties Blom

 
I like to know what I need to achieve before I start coding/designing. Therefore, I'd design the report layouts first. This way I can design the universe with the required layout in mind.
 
Wow! I'd say, that's a horrible idea.

You don't build a universe to meet the needs of a single report. You build the universe to meet the needs of all reports against that particular subject area.

You need requirements about dimensions and measures, but you certainly don't need report specs.

Steve Krandel
Intuit
 
I can think of a requirement that involves very special reports (like monitoring an OLTP database) where the specific needs for the monitoring layout triggers a one-off universe. I built these in the past , for instance to monitor migration projects where data from old and new environment had to be compared.
However, these were usually temporary exercises and no basis for generic management reports..

Ties Blom

 
Steve, How do you know your going to meet the needs of the reports if you don't know what the reports need to look like. Where do you get reqirements? Isn't it from report specs?

Often its just verifying that the required report layout is simple enough and that there are no complications that would require special consideration. It dosn't happen very often but every now and again a user wants something that is not straight forward to achieve and some tweaking of a universe or perhaps a separate universe all together is required.

Its all about having the full picture up front in order to avoid surprises and re-work later on.

To keep users happy, you need to produce reports that meet their requirements rather than always producing reports based on generic universes.
 
You mean you expect to have a single point in time where you have the full picture up front?
If you have a user community that can be that precise in what they want for a considerable period of time, then count yourself lucky. (Never come across such an ideal situation :) )

Ties Blom

 
You don't need full report specs to build the universe. It sure is nice to have some to get started, but it is not required.

Also, users don't know what they don't know. If you only include what they ask for you've not built anything that adds value above and beyond what they asked for. I've never seen a batch of reports be the only use of a universe. They will change over time. Well built universes are used 20% for adhoc.

Steve Krandel
Intuit
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top