OLAP Adapters

In this section:

This section describes new features for OLAP adapters.


Top of page

x
DBA Support for Level Hierarchies

FOCUS DBA features have been implemented to provide additional security on a file-by-file basis for non-FOCUS data sources, such as SAP/BW, Microsoft Analysis Services 2005/2008, Oracle-Hyperion Essbase 9.x, and other cube adapters.


Top of page

x
Adapter for Essbase: Requests From Web Console Displayed in Session Log

When requests generated by adapter MDX requests are run from the Web Console, they are displayed in the Web Console Session Log window. This can provide better debugging. The requests can also be filtered in the Session Log window when the SQL/MDX filter option is checked.


Top of page

x
Adapter for SAP BW

In this section:

This section describes new features for the Adapter for SAP BW.



x
Reversing the Sign When Displaying a Measure

You can create a synonym that specifies that a measure should display with reversed signs on report output.

In a BEX query, one of the options available for a measure is to display its values with reversed plus (+) and minus (-) signs. If you know that the BEX query has specified that a measure should be displayed with reversed signs, you can use the DMC to create a synonym that enables display of that measure on WebFOCUS reports with reversed signs. This is done by adding the REVERSE_SIGN=ON attribute to the field declaration for that measure.

The signs are reversed whenever this attribute is present, whether the BEX query specified a reversed sign or not, so you must know the data and the query definition before applying this attribute. This attribute has no effect on the stored values of the measure, just the display.



x
Syntax: How to Display a Measure With Reversed Signs

Add the following attribute to the FIELD declaration for the measure to be displayed with reversed signs:

REVERSE_SIGN=ON


Example: Displaying a Measure With Reversed Signs

In the following partial listing of the ZMINUS synonym, the measure CM_1 has the REVERSE_SIGN=ON attribute. This attribute has been added because the BEX query specifies reversed signs for measure CM_1:

FILENAME=ZMINUS, SUFFIX=BWBAPI  , $ 
  SEGMENT=ZMINUS, SEGTYPE=S0, $ 
$ MEASURES FOR CUBE 0SD_C01/ZMINUS    
  FIELDNAME=CM_1, ALIAS=4KN324NNXDL1055YDEO17L0L8, USAGE=D18.2,
    ACTUAL=D8, MISSING=ON,  TITLE='CM 1',     
      REFERENCE=SUM, PROPERTY=MEASURE, REVERSE_SIGN=ON, $  
  FIELDNAME=COST_OF_SALES____, ALIAS=4KN324VCGC6QIRPEJ8QDHMZB0,
    USAGE=D18.5, ACTUAL=D8, MISSING=ON,  TITLE='Cost of Sales (%)', 
      REFERENCE=UNKNOWN, PROPERTY=MEASURE,  $ 
 DIMENSION=[0MATERIAL], CAPTION='Material', $   
  HIERARCHY=[0MATERIAL], CAPTION='Material', HRY_DIMENSION=[0MATERIAL],
    HRY_STRUCTURE=STANDARD, $
  HIERARCHY=[0MATERIAL                   001], CAPTION='Material class', 
    HRY_DIMENSION=[0MATERIAL], HRY_STRUCTURE=RECURSIVE, $

The following request against the ZMINUS synonym prints the measures CM_1 and Cost_of_Sales:

TABLE FILE ZMINUS
PRINT CM_1 COST_OF_SALES
BY MATERIAL_NAME
END

The partial output follows. The measure CM_1 is displayed with reversed signs:

Removing the REVERSE_SIGN=ON attribute from the synonym produces the following output for the same request:



x
Custom Exit to Set the Value of the MYSAPSSO2 Cookie

In certain scenarios where users navigate through multiple systems requiring multiple authentications, a customer-specific, MYSAPSSO2 custom login module may be used to implement the authentication process and allow the processing of the MYSAPSSO2 SAP Login Ticket in a way that best suits the security architecture. Using this custom exit to set the value of the MYSAPSSO2 cookie relies on an external procedure to obtain the MYSAPSSO2 cookie. The feature allows the installation to develop an exit that obtains the cookie that can be passed to the SAP RFC connection.


Top of page

x
Adapter for Microsoft SQL Server Analysis Services: Support for Key Performance Indicator (KPI)

Reference:

If a Microsoft SQL Server Analysis data source has Key Performance Indicators (KPIs) defined, you can access and display these performance measures in a WebFOCUS report.

A KPI is a calculation or set of calculations against measures in the cube that typically represent a value, status, trend, or goal. It is stored with properties that enable the organization to set and track progress toward a specified level for the KPI goal. The KPI Value represents the current state of the indicator, and the KPI Goal represents the state toward which the organization is aiming. The KPI Status and KPI Trend are derived by comparing the Goal with the Value.

If the cube has KPIs defined, any synonym created will automatically contain metadata for those KPIs.



x
Reference: KPI Metadata in a Synonym

The metadata for a KPI starts with the following KPI declaration in the Master File:

KPI=kpiname,
   CAPTION=kpi_caption,
   KPI_STATUS_ICON='kpi_status_graphic', 
   KPI_TREND_ICON='kpi_trend_graphic'
   [,PARENT=kpi_parent_kpiname] ,$ 

where:

kpiname

Is the name of the KPI.

kpi_caption

Is the caption for the KPI.

kpi_status_graphic

Is the graphic assigned to the KPI Status property.

kpi_trend_graphic

Is the graphic assigned to the KPI Trend property.

kpi_parent_kpiname

If the KPI is part of a hierarchy of KPIs, this is the name of the parent KPI.

Field declarations describing the KPI properties follow the KPI declaration. Only the VALUE field is required, the GOAL, STATUS, and TREND fields are optional.

The following field declaration describes the KPI Value property and is required:

FIELDNAME=kpiname_KPI_VALUE, 
   ALIAS='[Measures].[kpiname]', USAGE=Ann, ACTUAL=Ann, MISSING=ON,
   TITLE='kpi_value_title', 
   REFERENCE='kpiname', 
   PROPERTY=KPI_VALUE, $ 

where:

kpiname_KPI_VALUE

Is the field name for the KPI Value property.

kpiname

Is the name of the KPI.

kpi_value_title

Is the column title for the KPI Value field.

The following field declarations represent the KPI Goal, Status, and Trend properties. One or more of them may be present, but they are not required:

FIELDNAME=kpiname_KPI_GOAL, 
   ALIAS='[Measures].[kpiname]', USAGE=Ann, ACTUAL=Ann, MISSING=ON,
   TITLE='kpi_goal_title', 
   REFERENCE='kpiname', 
   PROPERTY=KPI_GOAL, $ 
FIELDNAME=kpiname_KPI_STATUS, 
   ALIAS='[Measures].[kpiname]', USAGE=Dn.m, ACTUAL=D8, MISSING=ON,
   TITLE='kpiname_status_title', 
   REFERENCE='kpiname', 
   PROPERTY=KPI_STATUS, $ 
FIELDNAME=kpiname_KPI_TREND, 
   ALIAS='[Measures].[kpiname]', USAGE=Dn.m, ACTUAL=D8, MISSING=ON,
   TITLE='kpiname_trend_title', 
   REFERENCE='kpiname', 
   PROPERTY=KPI_TREND, $ 

where:

kpiname_KPI_GOAL, kpiname_KPI_STATUS, kpiname_KPI_TREND

Are the field names for the KPI Value, Status, and Trend properties.

kpiname

Is the name of the KPI.

kpi_goal_title, kpi_status_title, kpi_trend_title

Are the column titles for the KPI Goal, Status, and Trend fields.



Example: Sample Growth in Customer Base KPI for the Adventure Works Cube

The following declarations define the Growth in Customer Base KPI for the Adventure Works cube:

KPI=Growth in Customer Base, 
   CAPTION='Growth in Customer Base', 
   KPI_STATUS_ICON='Road Signs', 
   KPI_TREND_ICON='Standard Arrow', $ 
FIELDNAME=Growth_in_Customer_Base_KPI_VALUE, 
   ALIAS='[Measures].[Growth in Customer Base]', USAGE=A20, ACTUAL=A20, MISSING=ON, 
   TITLE='Growth in Customer Base Value', 
   REFERENCE='Growth in Customer Base', 
   PROPERTY=KPI_VALUE, $ 
FIELDNAME=Growth_in_Customer_Base_KPI_GOAL, 
   ALIAS='[Measures].[Growth in Customer Base Goal]', USAGE=A20, ACTUAL=A20, MISSING=ON, 
   TITLE='Growth in Customer Base Goal', 
   REFERENCE='Growth in Customer Base', 
   PROPERTY=KPI_GOAL, $ 
FIELDNAME=Growth_in_Customer_Base_KPI_STATUS, 
   ALIAS='[Measures].[Growth in Customer Base Status]', USAGE=D5.2, ACTUAL=D8, MISSING=ON, 
   TITLE='Growth in Customer Base Status', 
   REFERENCE='Growth in Customer Base', 
   PROPERTY=KPI_STATUS, $ 
FIELDNAME=Growth_in_Customer_Base_KPI_TREND, 
   ALIAS='[Measures].[Growth in Customer Base Trend]', USAGE=D5.2, ACTUAL=D8, MISSING=ON, 
   TITLE='Growth in Customer Base Trend', 
   REFERENCE='Growth in Customer Base', 
   PROPERTY=KPI_TREND, $ 


Example: Sample Request Using the Growth in Customer Base KPI

The following request displays the Growth in Customer Base KPI value by fiscal year:

TABLE FILE ADVENTURE_WORKS 
WRITE GROWTH_IN_CUSTOMER_BASE_KPI_VALUE/A6 
BY FISCAL_YEAR 
END 

The output is:

Fiscal Year Growth in Customer Base Value 
----------- ----------------------------- 
FY 2003     0.4605 
FY 2004     4.4040 
FY 2005     -0.946 

WebFOCUS