Customization Settings

How to:

The following topics describe advanced set commands that allow you to customize your Adapter for SAP BW.


Top of page

x
Syntax: How to Specify Empty Report Cell Settings
x
ENGINE BWBAPI SET EMPTY {ON|OFF}

where:

ON

Indicates that empty cells are included in a report and all data is shown whether it is associated with a dimension member or not.

OFF

Indicates that empty cells are excluded from a report (if measures are referenced) and dimension data is not shown if no fact data is associated with the dimension member (if measures are not referenced). OFF is the default value.

Tip: You can change this setting from the Web Console by clicking Data Adapters in the navigation pane, clicking the name of a configured adapter, and choosing Change Settings from the menu.


Top of page

x
Syntax: How to Specify Member Sampling Settings
x

During the synonym creation, member sampling is used to create Master File fields for dimension levels that precisely fit dimension member captions.

ENGINE BWBAPI SET MEMBER_SAMPLING {ON|OFF}

where:

ON

Indicates that the adapter will select all members of a hierarchy level to determine the optimum length for the field, and also the cardinality. The default value is ON.

Note: Depending on the data volume, this may take a long time. If synonym creation takes too long, you may wish to turn the MEMBER _SAMPLING OFF.

OFF

Indicates that all field lengths for the hierarchy levels are set to alphanumeric 60 and the cardinality information will be missing.

Tip: You can change this setting from the Web Console by clicking Data Adapters in the navigation pane, clicking the name of a configured adapter, and choosing Change Settings from the menu.


Top of page

x
Syntax: How to Specify Block Size
x

SAP recommends fetching large row and cell sets by portions in order to avoid crashes in the SAP server. The BLOCK_SIZE setting sets the size of a portion.

ENGINE BWBAPI SET BLOCK_SIZE n

where:

n

Sets the size of a portion. 0 is the default value, which means all members of the result set are returned in one portion.

The value of this setting should not be changed unless there is a timeout. Contact Information Builders high-level tech support for further information on how to use this option.

Tip: You can change this setting from the Web Console by clicking Adapters, right-clicking the configured adapter, and choosing Change Settings. The Change Settings pane opens.


Top of page

x
Syntax: How to Specify Property Restrictions
x

The ability to query on attribute values in the MEMBERS row set was made available with SAP BW 3.0B. (For details, see the SAP OSS Note 609314.)

ENGINE BWBAPI SET PROPERTY_RESTRICTIONS {ON|OFF}

where:

ON

Indicates that any tests on a dimension attribute will be sent to SAP.

It is recommended that you set PROPERTY_RESTRICTIONS to ON if your SAP BW release and patch level support the specifying restrictions on user-defined properties as selection tables. (Contact SAP support for exact list of releases and patch levels.)

OFF

Indicates that the filtering will be done on the WebFOCUS server. OFF is the default value.

Tip: You can change this setting from the Web Console by clicking Adapters, right-clicking the configured adapter, and choosing Change Settings. The Change Settings pane opens.


Top of page

x
Syntax: How to Specify Unassigned Member Settings
x

Sometimes dimension members are not explicitly arranged in a hierarchy. In SAP BW, assigned members are considered to be descendants of a root node named All, and unassigned members are considered to be children of a second root node named All Not Assigned. By default, Not Assigned members are not included in a report. You can include them using the INCLUDE_UNASSIGNED setting.

ENGINE BWBAPI SET INCLUDE_UNASSIGNED {OFF|ACTIVE|ALL}

where:

OFF

Does not include Not Assigned members belonging to an active hierarchy in a target report. OFF is the default value.

ALL

Includes all Not Assigned members belonging to an active hierarchy in a target report.

ACTIVE

Includes Not Assigned members belonging to an active hierarchy in which the lowest level is referenced. Individual unassigned members are listed at the lowest level of the hierarchy. This value is supported for level hierarchies only.

If the query does not include the lowest level, the summary for the Not Assigned nodes will not be shown unless there is a specific WHERE/IF statement at the lowest level.

Tip: You can change this setting from the Web Console by clicking Adapters, right-clicking the configured adapter, and choosing Change Settings. The Change Settings pane opens.


Top of page

x
Syntax: How to Disable the Checking of Aggregation Operators
x

If you specify prefix operators in the request, the adapter, by default, checks that they are compatible with the measure aggregators in the BW data. If any are not, a message is returned and the request is not processed. You can prevent the adapter from checking whether your operation matches the measure aggregator by issuing the CHECKAGGR OFF command

ENGINE BWBAPI SET CHECKAGGR {ON|OFF}

where:

ON

Validates each prefix operator against the corresponding measure aggregator in BW. If a prefix operator does not match the corresponding measure aggregator, a message displays and the request is not processed. ON is the default value.

OFF

Does not validate prefix operators against measure aggregators.

Tip: You can change this setting from the Web Console by clicking Adapters, right-clicking the configured adapter, and choosing Change Settings. The Change Settings pane opens.


Top of page

x
Syntax: How to Report Against Time-Dependent Hierarchies

When you report against a synonym with a time-dependent hierarchy, you use the ENGINE BWBAPI SET KEY_DATE command to set a key date for subsequent TABLE requests.

ENGINE BWBAPI SET KEY_DATE yyyymmdd 

where:

yyyymmdd

Is the key date for the TABLE requests that follow. If you do not specify the key date, the current date is used as the key date. If you do not specify a correct key date (the one within the time period associated with the specified concurrent version of the hierarchy), your report will fail with an error message indicating absence of the specified hierarchy.


Top of page

x
Syntax: How to Enable Support for Increased Number of Instances in a Request

SAP has introduced a new set of OLAP BAPIs that support requests with more than one million instances per axis. The SET USE_RSR_MDX command enables the Adapter for SAP BW to take advantage of these new BAPIs.

ENGINE BWBAPI SET USE_RSR_MDX {OFF|ON} 

where:

OFF

Does not support requests with more than one million instances per axis. OFF is the default value.

ON

Supports requests with more than one million instances per axis.


Top of page

x
Syntax: How to Build SAP VARIABLES Clauses Using Literal Strings

There are two different ways the adapter generates a SAP VARIABLES clause:

Using literal strings is perceived as more efficient because in this case the Adapter does not have to interact with the BW server in order to read the members of the hierarchy to obtain their unique names. However, generation of literal strings may or may not be possible depending on the types of tests against the variable fields and/or the type of the associated hierarchy and the variable selection type. Also, the success of an MDX request with literals depends on BW internal aspects which are not clearly documented by SAP.

The following setting controls whether the adapter will attempt to build a SAP VARIABLES clause using literals before resorting to the technique with member unique names:

ENGINE BWBAPI SET USE_SAP_VARIABLE_LITERALS {ON|OFF}

where:

ON

Instructs the adapter to attempt to build a SAP VARIABLES clause using literals.

OFF

Instructs the adapter to build a SAP VARIABLES clause using member unique names. OFF is the default value.


iWay Software