alucches 2700012QJC Tags:  bilog ibmeam adhoc maximo analysis birt v7 report cognos data compare 8,021 Views
Pam Denny wrote an interesting blog post in the Asset Management blog about the Tivoli process automation engine 7.x reporting tools. Her post compares BIRT and Cognos for two of their reporting components, which are Operational and Ad Hoc Reporting. For more information, see her post.
alucches 2700012QJC Tags:  qbr ld v7 ros hoc collection configure ad report data bilog 9,498 Views
Over on the Asset Management blog, Pam Denny wrote a helpful post about how to include long descriptions in ad hoc reports.
PamDenny 270000BXV7 Tags:  report localization ibmpa v7 translation bilog data analysis bi 10,243 Views
When disasters like the massive earthquake earlier this year
in Japan, or the deadly earthquake
that hit Haiti
in 2010, people and organizations from all over the world work together to help
and rebuild these devastated areas.
I am very lucky to have the opportunity to help locally by rebuilding houses for people in need thru Habitat thru Humanity. Recently, I worked with an amazing team of individuals, including Power Company Employees, a school teacher, housewife, retired architect, and high school teenagers, in rebuilding a property that will soon house 10 families. Although our knowledge of sister joists and smart squares was minimal, with some explanations we were all quickly on the path of using our universal knowledge of crowbars, hammers and nails.
So how does rebuiliding tie into today’s BiLog entry on localization? Some icons like hammers and nails speak a universal language. Similar universal icons exist in Version 7 to communicate functionality, like the save, edit, delete and print icons. The functionality enabled thru these icons does not have to be explained in words – their images symbolize their functionality.
However, other items must be explained in a language the user understands. Whether it is breaking down the concept of a sister joist to a to a group on non-tradesmen, or detailing the description of an asset or ticket in the language of the user – we often need to enable text in localized languages in V7 and in V7 reports.
V7 reporting has unique requirements, as there are four very different components which must be enabled for localized text values. These include
1. Report Description displayed in Maximo Session
2. Report Request Page displayed in Maximo Session
3. Report Titles/Labels displayed in the Report
4. Report Data displayed in the Report
Each one of these four components is enabled for
localization in a unique way. Whether it
is it thru the corresponding L_Database tables, or thru the use of unique
scripting code within the report design file, the applicable report
description, parameters, titles, labels and data can all display within the
user’s specified language. You can find
information on how each of these components is enabled here.
To enable localization, there are a few key setup steps which you must enable if you have a multiple language environment which are detailed here
And finally, if you have created
custom reports, information on how you can enable them for localization is
This report localization information can also be found in the Report Localization Reference Guide, which contains more details and screenshots, along with detailed sample use cases explaining how you can enable custom report localization. This is listed, along with other report reference guides on this V7 wiki site.
Please comment back if you have any feedback on this, or other topics you’d like to hear about. Thank you!
PamDenny 270000BXV7 Tags:  report ros bilog analysis ad ibmpa cardinality qbr data hoc v7 8,089 Views
This BiLog entry discusses
the key items to consider when defining maxrelationships in your ROS.
One of its major components is
cardinality, which is used to define the type of the database relationship. In the case of reporting, there are two types: One-to-one (1:1) or single relationships, or One-to-many (1:N) or Multiple Relationships.
To highlight the differences in cardinality, let’s use an example from the Purchase Requisition application.
The relationship between a Purchase Requisition and a Company is a single relationship, as only a single Company can be associated to a single PR.
However, the relationship between a Purchase Requisition and Purchase Requisition Lines is a multiple relationship, because for each PR (single) there can be multiple PR Line records (multiple).
When creating or modifying Report Object Structures (ROS) for your QBR reports, you will need to evaluate and define the cardinality of the relationship as either single, multiple or undefined. If you use the values of undefined or multiple, the relationship will be treated as a 1:N relationship.
So why is cardinality so important to the ROS definition? As your users begin adding fields to their own QBR reports, the relationships of those fields are evaluated to determine if they are single or multiple relationships. Depending on whether your user has selected a Summary or Detail Style report, will determine if they can add their selected fields.
For summary reports
- You can select any number of 1:1 relationships
- You can select only one 1:N relationship
For detail reports
- You can select any number of 1:1 relationships
- You can select any number of 1:N relationship
To enable maximum ‘cardinality’ flexibility in QBR Report
creation, you may want to recommend your users select the Detail Report Styles.
You can find more details on cardinality in the Version 7 QBR Ad Hoc Reporting Guides in the section titled 'Understanding Database Joins and Cardinality'. To access this document, click here for the QBR Report Wiki Page or here for the Report User Reference Material Page.
PamDenny 270000BXV7 Tags:  analysis qbr ad report utilization upgrade data bilog hoc ibmpa custom 9,398 Views
How many custom reports do you have? Do you have 25, 50 – or is your number in the range of 100 to 250 custom reports? Or are you in the category where you don’t know how many custom reports you have because your users are creating their own uncontrolled reports in tools like Microsoft Access or Microsoft Excel?
The topic of custom reports leads to a myriad of questions including –
- Is each custom report utilized?
- What determines if a custom report is approved, and then developed?
- Should super users be given database and report development access?
- What mechanisms are in place to insure that correct data is being returned in the custom reports?
- How much do custom reports cost -- in terms of design, development, test, administration, maintenance dollars and resources?
As John Heywood told us back in the 16th century that ‘Rome was not built in one day’. … my thoughts in the 21st century are that we can’t answer all those questions in today’s BiLog. However, we can start a plan to give you ideas on how you can reduce your number of custom reports.
One of the first and directly actionable means to reduce your custom reports is to begin using V7’s Ad Hoc Reporting feature, QBR. By using QBR within any V7 application, you and/or your users can quickly create reports that can include complex where clauses, filters, sorting, grouping, and parameters.
QBR functionality enables key features including -
· - Enabling users to quickly create their own reports for their unique business needs
· - Does not require technical, development skills, like Java, or database knowledge to create the report
· - Does not consume development hours in creating and maintaining large numbers of unique reports, which may only be used by a very small number of users
The cornerstone of QBR functionality are Report Object Structures, ROS. ROS enable users to select fields from multiple categories (objects) for their ad hoc reports. ROS are designed to enable users to quickly visualize their hierarchies and parent/child relationships. They are created in the Object Structure application of V7, and in the next BiLog, we’ll discuss their key attributes and how to extend them.
PamDenny 270000BXV7 Tags:  ibmpa ad hoc data v7 reports clients analysis bilog qbr 7,011 Views
On Tuesday, September 20th, I had an amazing opportunity to host a web conference for our Maximo and Version 7 clients. This session shared the latest information on Business Intelligence and Reporting, but most importantly - was opened up for over 60 minutes to give you - our clients - the opportunity to ask questions.
With representatives from over 15 companies, you asked tremendous, detailed questions on reporting strategy and functionality. Your questions led others to ask questions - so you quickly learned information and best practices from each other.
If you missed the session, the questions clients asked are detailed here
You can also locate this page by scrolling down to the FAQ section of the Report Wiki Page located here
Please comment back if you would like similar web conferences in the future - or if you have any other reporting questions. Thanks!
QBE (Query by Example), also known as Data Download, is an excellent way for you to quickly take the results of your application query and/or filters and export them to Microsoft Excel. You can then view each of the list tab fields, and perform additional analysis, combine the data with other queries, print, or save.
However, often your users want to see additional fields in the exported data. And the fields that one user may want to see are not the same as fields another user may want to see. You can modify the list of fields that displays with the Application Designer. However, this involves resources, planning, and space limitations.
You can provide your users the ability to
Apply application filter and/or query
Select their unique fields or database attributes
Define sorting, grouping, filters and parameters
Directly Download to Microsoft Excel
Without Application Designer Modifications
thru QBR (Query Based Reporting). QBR is available from essentially any application, and provides powerful, flexible ad hoc reporting capability as shown in the sample below.
With QBR report creation process, you can quickly export your report results directly to Microsoft Excel with a few simple clicks. Additionally, you can choose whether to execute your report a single time – and discard it – or to save your QBR report and execute it regularly in the future. You can also schedule the QBR so the results appear in your email inbox – along with others - on a preconfigured time period.
You can find more details on the QBR functionality, including more details on its use and how to extend for your unique environment, at this url.
Additional detailed information, including screenshots, can be found in the reference materials referenced in this url