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
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
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
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
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
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
Add a comment