universe "Unexpected behavior" in WebI (no issue in IDT)

[former_member206621]

I have created a universe via the Information Design Tool.

This universe gets data from a table in our R/3 system (via a function module) - the table looks like:

Field	Data element	Data Type	Length	Decimal Places	Short Description
GJAHR	GJAHR	NUMC	4	0	Fiscal Year
MONAT	MONAT	NUMC	2	0	Fiscal Period
ZDCO	ZDCO	INT4	10	0	DCO
ZDDCO	ZDDCO	INT4	10	0	DDCO

If I run a query in the Information Design Tool on this universe I get the following results:

But when we try to create a WebI report we cannot run the query if we add MONAT in the query:

If we remove MONAT from the query we get:

How can we solve this issue?

Kind regards,

Lieselot

[Former Member · Accepted solution]

Issue solved in SP6

[former_member206621 · Accepted solution]

We have upgrade our BO system to BO SP6 patch 5 and with this upgrade the issue is solved.

[cgwaters · Accepted solution]

I'm encountering this same error in my BO 4.0 SP5 Patch 9 environment. Unfortunately, SP6 isn't an option for me at the moment.

Like you, I'm retrieving numerous text fields from my R/3 system via a function module / table data type. When there is a value in one particular text field, I get the error you described.

In R/3, the offending field is of type DZTERM_BEZ (CHAR 30). I have other fields of type VTEXT (CHAR 20) and BEZEI40 (CHAR 40). Within the IDT, a query that references the offending field returns without an error whether there is a value in the field or not. A second/test WebI report using the same universe produces the same error when there is a value in the offending field.

Is there no way to resolve this without upgrading to SP6? Surely there must be a way to determine why this particular field is a problem!

[Former Member · Accepted solution]

Hi,

    Am also facing same problem as shown below:

    I tried out with many attempts but unable to fix it.In Information Design Tool there is no any problem. Please if any body have solved this, request you to explain it to fix this issue.

Regards,

Mohammed Huzaifa.

[Former Member · Accepted solution]

I am running 4.1 SP6 and have this problem. What other steps did you take?

[Former Member · Accepted solution]

Did you manage to resolve this?

[former_member210032]

Hi

I am facing error while creating report in BI launch pad. PFA for the screen shot. I am using ms sql server 2012 and sap bo 4.1 sp2 environment.

i create universe in Information Design Tool

if any one know how to solve this issues please share your thought

Regards

Mustafa

[Former Member]

Try the following KBA 1803970

[former_member210032]

Hi Harah,

Thanks for quick reply but i m not understand what u say to me can u explain clearly .

Regards

Mustafa

[Former Member]

Hello,

If you go on the sap help and support, xsearch and look for the KBA 1803970.

There is a proposed solution for the error message you are getting

https://support.sap.com/kb-incidents/xsearch.html

Regards

[former_member210032]

Hi Harah,

That page is asking for username and password

Regards

Mustafa

[Former Member]

Hi Harah,

             Can u please suggest me the resolution for my issue

             Data base error (CS) : Unexpected Behaviour Cannot convert field stufe of type num to byte IES. (10901) (WIS 10901)

               Am using the version SAP BO BI 4.1 sp1 . Can I use sap bo bi 4.1 sp4 to fix this issue

Regards,

Mohammed.

[Former Member]

https://support.wdf.sap.corp/sap/support/notes/1803970

[former_member206621]

Dear all,

To solve this issue you can also try to change the DataFoundation in IDT to multisource.

Kind regards,

Lieselot

[former_member206621]

Some screenshots to show the data types - as you can see the object GJAHR has the same data type and I have no issues at all with this object in the WebI report:

I do not think there is something wrong with the connection as other universes work without issues.

Kind regards,

Lieselot

[Former Member]

Did you try testing this by building a new webi report with the four objects?existing report might retain the error sometimes if it does not reflect universe changes.

Also, try to compare and see the difference between other columns that are retrieving data and MONAT to see some difference at function module among these objects is triggering this error?

Thanks

Mallik

[former_member188911]

Hi Lieselot,

it is important to know Patch level of both environments

Also , i understand you are using a relational connection using JCO correct?

if not please provide more details

Thanks

Simone

[former_member206621]

I have used a relational connection using JCO.

We have BO SP4 patch 14 and our ERP system is EHP6.

[former_member188911]

Thanks, do you have details about the patch level BW installation?  It is important..

You would also like to get some traces from the JCO https://service.sap.com/sap/support/notes/1609534

and from the Web Intelligence Processing Server

https://service.sap.com/sap/support/notes/1335757

But before doing so you can try to create the object as a text and then create another object that converts to a number if needed.

Last but not least, if this last suggestion doesn't work you may wish to open an incident with support, if you can

Many thanks

Best regards

Simone

[former_member207342]

I suspect there is a unsupported datatype in IDT which is causing this issue.

IDT might have mapped it to closest possible e.g. TEXT or CHAR and thats why you do not see any issue in IDT while doing integrity check but thows an error when actual query is executed while running a report.

--Kuldeep

[Former Member]

Verify that you have the correct ODBC driver version installed.

If ORACLE_HOME missing in system environnment variables, add ORACLE_HOME in the system environnment variables. Verify that the environnment variable PATH is also populated with the oracle path.

--------------------------------------------------------------

As per SAP Note  1847214 - Unable to create or refresh Web Intelligence document in BI Launchpad

Cause

ORACLE_BASE and ORACLE_HOME environment variables were not set to the correct 64 bit path.

Resolution

1.   Set ORACLE_HOME and ORACLE_BASE to the correct paths.

eg. ORACLE_BASE=<Oracle_client_install_folder>/product/11.2.0/client_1/BIN

ORACLE_HOME=<Oracle_client_install_folder>/product/11.2.0/client_1

2.   Reboot the Server machine.

--------------------------------------------------------------

As per SAP Note  1763000 - BI 4.0 WebI Error - Unexepected Behavior Invoking getFieldName()

Cause

The table referenced by the object does not exist in the database.

Since it's in the universe, it must have existed at some time, so the table has been either deleted or renamed.

Resolution

Change the references to a table that exists.

--------------------------------------------------------------

As per SAP Note  1700653 - Database error: (CS) "Unexpected behavior : com.sap.connectivity.cs.core.CSError:Bad Value for Field" . (IES 10901)

Cause

The issue has been identified and logged under Problem Report ID ADAPT01544888.

Resolution

This issue is scheduled to be fixed with future Service Pack/ Fix Pack

--------------------------------------------------------------

As per SAP Note 1713741 - Error: "com.sap.connectivity.cs.core.CSError: Bad Value for Field. (IES 10901)"

Cause

The session mode is defaulting to an incorrect value.

Resolution

    Edit the teradata.sbo file found by default in the $INSTALL_DIR$\SAP BusinessObjects Enterprise XI 4.0\dataAccess\connectionServer\jdbc folder on the machine where the Information Design Tool (IDT) has been installed.

    Add tmode=System to the end of the "URL Format" value:

    <Parameter Name="URL Format">jdbc:teradata://$DATASOURCE$/COMPAT_DBS=TRUE,COMPAT_ISSIGNED=TRUE,tmode=System,charset=UTF8</Parameter>

Note: there are separate URL Format entries for "Teradata 12" and "Teradata 13".  Ensure you modify the correct setting.

A new Connection created in the IDT and published to the CMS will take on the tmode=System setting.

A pre-existing Connection already published to the CMS must be modified to take on the tmode=System setting, as follows:

    In the IDT, log onto the CMS in the "Repository Resources" frame.

    Open the Connection, and Edit.

    Modify the "Server (host:port)" setting.  Modify it back to the original "Server (host:port)".

    Save the Connection back to the CMS repository.

The modification of the "Server (host:port)" leads to a change in the $DATASOURCE$ value, forcing the IDT to re-read the "URL Format" setting and updating the Connection metadata.

Hope this helps

Thanks

Sandeep

[former_member188911]

i don't think oracle is coming into play here ...

and FYI Oracle with ODBC is not supported in BI

thanks

Simone

[Former Member]

As a first check, try building same query in IDT queries section of business layer and confirm if you have the same issue. As next check see if the MONAT object in IDT is able to show LOV without errors when you click on show list of values button.

If any of the above return same error message, then check the data type of MONAT in ECC is supported data type in IDT/Webi.

Thanks

Mallik

[former_member206621]

As I already stated I have no problems when I build a query in IDT.  I also get results for the MONAT object.

I only get the error message when I try to create a WebI report

Kind regards,

Lieselot

[former_member182521]

Hi Lieselot,

Could you please let us know Object properties from Business layer? Also try create a variable referencing MONAT object  converted to Integer?

Regards,

Mani

[Former Member]

Is your universe object data type and database column type same for MONAT?

[former_member188911]

Hi,

The properties of the object definition in IDT would help.

However it is important to know Patch level of both environments

Also , i understand you are using a relational connection using JCO correct? if not please provide more details

Thanks

Simone

[Former Member]

I am getting this exact error message. I was already on 4.1 SP6 but have just upgraded to 4.1 SP8 in the hope that would resolve it but the error still persists. Can you let me know how you managed to resolve this please?