BO XI R3.1 Missing operators from Webi SQL

[Former Member]

Hi,

I'm using SAP BO XI R3.1. My universe has an ODBC connection to IBM Infosphere Optim Archive. While trying to create a WebI report and pulling in objects into the condition pane, the following operators are not showing up - IN, NOT IN, LIKE, NOT LIKE in the SQL.

Going by the following discussion - http://scn.sap.com/thread/3223302, I check out the odbc.prm file on my machine. All the operators seem to be correctly defined there. Below is the text from the file.

<Operators>

  <Operator Arity="1" ID="ADD" Type="Numeric">+</Operator>

  <Operator Arity="1" ID="SUBSTRACT" Type="Numeric">-</Operator>

  <Operator Arity="1" ID="MULTIPLY" Type="Numeric">*</Operator>

  <Operator Arity="1" ID="DIVIDE" Type="Numeric">/</Operator>

  <Operator Arity="0" ID="NOT_NULL" Type="Logical">IS NOT NULL</Operator>

  <Operator Arity="0" ID="NULL" Type="Logical">IS NULL</Operator>

  <Operator Arity="1" ID="SUP" Type="Logical">&gt;=</Operator>

  <Operator Arity="1" ID="INF" Type="Logical">&lt;=</Operator>

  <Operator Arity="1" ID="EQUAL" Type="Logical">=</Operator>

  <Operator Arity="1" ID="DIFF" Type="Logical">&lt;&gt;</Operator>

  <Operator Arity="1" ID="STRICT_SUP" Type="Logical">&gt;</Operator>

  <Operator Arity="1" ID="STRICT_INF" Type="Logical">&lt;</Operator>

  <Operator Arity="1" ID="IN_LIST" Type="Logical">IN</Operator>

  <Operator Arity="1" ID="NOT_IN_LIST" Type="Logical">NOT IN</Operator>

  <Operator Arity="1" ID="MATCH" Type="Logical">LIKE</Operator>

  <Operator Arity="1" ID="NOT_MATCH" Type="Logical">NOT LIKE</Operator>

  <Operator Arity="2" ID="BETWEEN" Type="Logical">BETWEEN  AND</Operator>

  <Operator Arity="2" ID="NOT_BETWEEN" Type="Logical">NOT BETWEEN  AND</Operator>

</Operators>

The mentioned operators work fine when creating a report in DeskI/Webi Rich Client. I've requested for a copy of the odbc.prm file from the team that manages the BO Servers. Any other ideas/help will be appreciated.

Regards,

F

[Former Member]

We've checked the following and are still facing this issue:

1. Checked the actual prm and sbo files being loaded in Designer. Verified the parameters.

2. Re-created the .prm file and restarted the connection server.

3. Created a new connection using ODBC driver instead of ODBC3 driver.

We've isolated the issue being on the server as while creating a webi report using WRC locally, we don't face the missing operator issue, but while doing this on the server, we see the issue.

A ticket was raised with SAP by the server team but support was refused stating that the Optim was not supported.

This seems to be more of an issue with the driver rather than the DB. There are other connections on the same server to Optim archive which are functioning fine, which is quite strange. Any other idea/help will be much appreciated.

[Former Member]

Hi Farida,

Do you see operators while using InfoView ?

You said, operators are visible while using WebI rich client/DeskI. But on which machine ? You local machine or on server?

[Former Member]

Hi Hardik,

While using Infoview --> You mean on the query panel? Yes, I can see In list, Not in list, Matches pattern and Does not match pattern. Only when I click on SQL button, I see that the operators are not applied.

Regarding Webi rich client/Deski --> On the local machine.

The team that manages the servers responded with the prm file on the server and it seems to be fine.

[former_member188911]

Can you please provide exact SP/FP level and also type version and middleware of  the DB?

thanks

Simone

[Former Member]

This message was moderated.

[Former Member]

Hi Simone,

Previous reply did not get posted, reposting:

Business Objects version - SAP BOXI R3.1 SP3.

Database - IBM Infosphere Optim Archive

ODBC connection is established through Optim thin client - Optim Connect ODBC 2.5 Thin Client 5.3.2.24

I should also mention that other users have created connections previously on the same server and version and there seems to be no issue with the reports.

Thanks,

F

[former_member188911]

You are probably using Generic ODBC, which has some limitations.

I have moved this to the Semantic Layer discussions

thanks

Simone Caneparo

SCN Discussions Moderator

[Former Member]

Hi Simone,

Yes, I'm using Generic ODBC, but as explained already, other users are able to create and use connections without this particular issue cropping up.

Thanks,

F