Jump to: navigation, search

BO Documentation

BOE 3.1 and BI 4.1 are created and documented by SAP. SAP provides detailed information about the operation of the Universe Design Tool, Information Design Tool, Web Intelligence, InfoView, Designer, and other BO or BI applications. Access this SAP documentation from the following sources:

  • from the SAP BusinessObjects Business Intelligence Platform Documentation CD,
  • if you are a direct SAP customer, from the SAP website,
  • if you obtained BO software through Genesys, from the SAP website.




Glossary

A B C D E F G H I J K L M N O P Q R S T U V W X Y Z

Genesys Interactive Insights

Also known as GI2. A presentation layer that extracts data from the Genesys Info Mart database, and presents it in readable reports to enable business and contact center managers to make better business decisions for streamlining operations, reducing costs, and providing better services.

For Genesys Cloud customers, depending on the release of Genesys Cloud that you are using, historical reporting is available through either the Genesys Interactive Insights (GI2) interface, or through Genesys CX Insights.



Glossary

A B C D E F G H I J K L M N O P Q R S T U V W X Y Z

Creating Week-Level Reports

GI2 includes no weekly reports, although the Genesys Info Mart server regularly aggregates and populates week-level data in the AG2_*_WEEK tables in the Info Mart database. You can use these tables as the source for week-level GI2 reports that you can create, either:

  • Drillable week-level reports
  • Week-level-only reports

If you want week-level-only reports without the ability to drill-up or drill-down functionality to the other aggregation levels, follow the steps in Week-Level-Only Reports to replace the time dimension that is used in the reports with the Week dimension.

Drillable Week-Level-Reports

For drillable week-level reports, you must do the following:

[+] Show Steps

Week-Level-Only Reports

The Week dimension is omitted from the Time hierarchy in GI2 reports, which disables drilling up or down for week-level results. You can, however, create new copies of some of the reports and customize them to summarize contact center activity in week-only time buckets. For Week-level-only reports, you cannot drill along the Time hierarchy. You can enable week-level reporting in all reports except those reports in the Details folder.

To create Week-Level-Only Reporting:

Customize a copy of a GI2 report as follows:

[+] Show Steps

Creating a Week-Compatible Day Dimension

You must create a week-compatible day dimension if you intend to enable your report users to drill up from or drill down to day-level results in the reports that you customize. In the default configuration, the Day dimension in the Time class is a month-compatible day, sourced from the LABEL_YYYY_MM_DD column of the DATE_TIME table. This field references the particular day with respect to the month and year in which the day falls; days are consequently numbered as 01 through 31. To reference a particular day within a given week, source the Day dimension from the CAL_DAY_NUM_IN_WEEK field of this table, which stores the day number of a week—starting with 1 for the first day of the week and ending with 7 for the last day of the week.

To this end, within the Information Design Tool, you can do either of the following:

  • Redefine the existing Day dimension. If you choose this method, the new definition affects the results of all other reports that provide day- and month-level results.
  • Create and define a new dimension, such as Day in Week. If you choose this, you must substitute the new dimension, in both the query panel and report layout, in all reports for which you want to generate week-level results.

When you have finished customizing the universe, you must export your work to the BI repository so that this redefined or new dimension is made available to report users. This procedure is described in the "Linking the Universe to Your Data Mart > Publishing the Universe Back to the Repository" section of the Genesys Interactive Insights Deployment Guide.

Understanding Week Boundaries

The boundaries of 15-minute, hour, day, month, quarter, and year aggregation levels are very well defined within any given Gregorian calendar year because each denomination represents an integral fraction of that year; there are four whole quarters in a year, 12 full months, 365 (or 366) complete days, and one year in a year. No single hour splits in such a way that part of the hour resides in one year and the other part in the next, as is precisely the case for the beginning and/or ending weeks of any given year.

Over and above this dual membership in each year, your system locale settings specify your preferred date-related conventions, which include the definition of a week and on which day the week begins. Different cultures observe different date conventions. As such, these variations in what constitutes a week merit special discussion.

Week Boundaries, as Defined in Genesys Info Mart

The beginning of whole weeks in the Info Mart database is determined by the settings of the [date-time]/first-day-of-week Genesys Info Mart configuration option in the [date-time] section. By default, each week begins on Sunday and ends on Saturday. If report users specify any other week range in the User Prompt Input area of the week reports that you create in Web Intelligence, such as Monday to Sunday (when the default settings are used), the generated results display data for two partial weeks instead of one seven-day period.

[+] More Information

Feedback

Comment on this article:

blog comments powered by Disqus
This page was last modified on 25 May 2017, at 05:58.