Page tree
Skip to end of metadata
Go to start of metadata


This wiki page is on common issues using the ODBO connector to access SAP BPC NetWeaver data to use in BusinessObjects XI Enterprise Web Intelligence Reports, and how to correct these issues.


The ODBO connector is required to connect to a SAP BPC NetWeaver cube, and display the data in a SAP BusinessObjects XI Enterprise Web Intelligence report. Common issues that arise are errors received such as

"A database error occurred. The database error text is: The data type (8) is not compatible with the data retrieve function used (WIS 10901)."

While this typically means the data was queried as a different type (NUM, STRING) than what was returned, it could be thrown any time the incorrect version level of the ODBO connector is used. Other behavior that may occur is the data will return successfully sometimes, and other times it will return no data or only partial data.

To isolate the issue, here are some steps you can follow:

  • You are using the latest version of the ODBO connector. This connector is updated on an as needed basis, and BPC product upgrades (Service Packs) may require the latest version.
  • Are you able to retrieve data within the Universe Designer against the ODBO connection to BPC? Example: Create a parameter within the Universe Designer and choose the field in question and see if the data can be retrieved or if errors are generated.
  • Does this error occur only when a specific data type is selected? (Date, Number, String, e&)
  • If you select a single field (string or number) does the error occur?
  • Using the WebI Thick Client and enable SOFA/MDA tracing to eliminate as many variables as possible:
  1. Make sure the ODBO connector is installed on a client machine.
  2. Use Universe Designer to test and make sure the Universe can connect to BPC.
  3. Use SAP Knowledge Base Article 1260004 to enable SOFA/MDA/MDX tracing.
  4. Create and save a new universe based upon the factory default APSHELL application set using the ODBO connector. Open WebI Thick Client and create a simple report using 1 dimension member and one measure and verify successful data retrieval. Add members and measures one at a time to see if you can identify if a specific member/measure causes the issue.
  • Another method would be to remove all filters contained in the query, then add one at a time, and run against each added filter to see if the issue can be isolated to a filter or data type. If/when you discover a failure, trace the WebI server in use to capture this information in a log.