Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Discover how organizations are unlocking new revenue streams: Watch here
cancel
Showing results for 
Search instead for 
Did you mean: 
Anonymous
Not applicable

SAP error Message when empty rows returned since TOS 3.1.3

Hello,
since i've updated my TOS from 3.1.1 to 3.1.3, i changed my tSAPInput components to work with the new configuration.
And i've got a major problem because when tSAPInput returned some values it works fine, but when it does not return values i've got the following error message :
Exception in component tSAPInput_3
com.sap.mw.jco.JCO$Exception: (106) JCO_ERROR_RESOURCE: Trying to access row values in a table which does not have any rows yet
In my job it can happend that SAP returns no values (one query to SAP is for a period from 01/01/2009 to today (there's always values returned), the other is from yesterday to today (it can happend that no values are returned)) and it worked well in 3.1.1...
The job is dying with the error message.
Is there a solution ? Please help me !
Fabrice
Labels (2)
6 Replies
Anonymous
Not applicable
Author

up please...
Anonymous
Not applicable
Author

Hello, I test it as you said, find it is a bug(when the return table is empty).
It have been fixed at: http://talendforge.org/trac/tos/changeset/26764
if you are anxious on this bug, please modify the file as the same svn commit:26764 in your local file:
TOS-All-r26090-V3.1.3\plugins\org.talend.designer.components.localprovider_3.1.3.r26090\components\tSAPInput\tSAPInput_begin.javajet
for more convenient, you can download this file(26765) to replace the old file.
(It also support the "deactivate some output connction" for tSAPInput)
http://talendforge.org/trac/tos/browser/trunk/org.talend.designer.components.localprovider/component...
Anonymous
Not applicable
Author

wyang, thanks for your help.
I will try the new file next week and post comments.
Anonymous
Not applicable
Author

Okay, I have tried and the JCO ERROR disappeared. Thanks for the fix !
I have discovered another error that didn't exist in 3.1.1 version.
When you specify a schema in the outputs of the tSapInput component which contains a Date field, you've got the following compilation error :
"ParserUtils.parseTo_java cannot be resolved"
Do you want me to post in the bugtracker ?
Anonymous
Not applicable
Author

Do you want me to post in the bugtracker ?

Yes, please !
Thx for your support !
Anonymous
Not applicable
Author