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

Announcements
Join us in Toronto Sept 9th for Qlik's AI Reality Tour! Register Now
cancel
Showing results for 
Search instead for 
Did you mean: 
Anonymous
Not applicable

tsapinfocubinput error: Next data package could not be requested (related to Z_TLDBI74_READ_INFOPROV)

Dear talend support,

I am using Talend Studio 6.5.1 and have a very simple job based to extract data from SAP using  tSAPInfoCubeInput . The job fails and produces the stacktrace below. Is it possible there is still a bug in this component?

 

STACKTRACE=

 

Exception in component tSAPInfoCubeInput_1 (infoobject)
[FATAL]: bridgestonedev.infoobject_0_1.infoobject - tSAPInfoCubeInput_1 Next data package could not be requested: SAPException@426b6a74 [
  errorCode=40
 ,errorGroup=0
 ,errorKey=null
 ,errorMessage=<BAPIRET2><TYPE>E</TYPE><ID>DBMAN</ID><NUMBER>257</NUMBER><MESSAGE>SQL Error: INVALID_CURSOR</MESSAGE><LOG_NO></LOG_NO><LOG_MSG_NO>000000</LOG_MSG_NO><MESSAGE_V1>INVALID_CURSOR</MESSAGE_V1><MESSAGE_V2></MESSAGE_V2><MESSAGE_V3></MESSAGE_V3><MESSAGE_V4></MESSAGE_V4><PARAMETER></PARAMETER><ROW>0</ROW><FIELD></FIELD><SYSTEM>BIDCLNT001</SYSTEM></BAPIRET2>
 ,bapiName=Z_TLDBI74_READ_INFOPROV
]
java.lang.RuntimeException: Next data package could not be requested: SAPException@426b6a74 [
  errorCode=40
 ,errorGroup=0
 ,errorKey=null
 ,errorMessage=<BAPIRET2><TYPE>E</TYPE><ID>DBMAN</ID><NUMBER>257</NUMBER><MESSAGE>SQL Error: INVALID_CURSOR</MESSAGE><LOG_NO></LOG_NO><LOG_MSG_NO>000000</LOG_MSG_NO><MESSAGE_V1>INVALID_CURSOR</MESSAGE_V1><MESSAGE_V2></MESSAGE_V2><MESSAGE_V3></MESSAGE_V3><MESSAGE_V4></MESSAGE_V4><PARAMETER></PARAMETER><ROW>0</ROW><FIELD></FIELD><SYSTEM>BIDCLNT001</SYSTEM></BAPIRET2>
java.lang.RuntimeException: Next data package could not be requested: SAPException@426b6a74 [
  errorCode=40
 ,errorGroup=0
 ,errorKey=null
 ,errorMessage=<BAPIRET2><TYPE>E</TYPE><ID>DBMAN</ID><NUMBER>257</NUMBER><MESSAGE>SQL Error: INVALID_CURSOR</MESSAGE><LOG_NO></LOG_NO><LOG_MSG_NO>000000</LOG_MSG_NO><MESSAGE_V1>INVALID_CURSOR</MESSAGE_V1><MESSAGE_V2></MESSAGE_V2><MESSAGE_V3></MESSAGE_V3><MESSAGE_V4></MESSAGE_V4><PARAMETER></PARAMETER><ROW>0</ROW><FIELD></FIELD><SYSTEM>BIDCLNT001</SYSTEM></BAPIRET2>
 ,bapiName=Z_TLDBI74_READ_INFOPROV
]
    at org.talend.sap.impl.bw.readable.SAPBWLayoutBasedTableData.nextRow(SAPBWLayoutBasedTableData.java:145)

Labels (4)
14 Replies
Anonymous
Not applicable
Author

Hello,

We have sent an email to CustomerCare@talend.com with your issue and credentials.

Is there any response? Don't hesitate to post your issue here.

Best regards

Sabrina

Anonymous
Not applicable
Author

Increasing the memory for the table space on the sap side resolves this issue.​

SebastienA
Contributor
Contributor

Hi,

I have exactly the same error retrieving data from a TSAPInfocubeInput.
Can you tell me which SAP parameter has been increased on the SAP side, please ?

We already tried to increase these 4 SAP parameters to 6Go (large enough !) :

abap/heap_area_dia
abap/heap_area_nondia
ztta/roll_extension_dia
ztta/roll_extension_nondia

 

But it is still failing with the same error  : Next data package could not be requested

 

Help would be much appreciated !
Thanks you

ABAT
Contributor
Contributor

Can anyone help me with the parameters which needs to be amended in SAP?

jackjoxon
Contributor
Contributor

You're hitting an INVALID_CURSOR error with tSAPInfoCubeInput, likely due to a backend issue in the custom BAPI (Z_TLDBI74_READ_INFOPROV). Try reducing the data package size, check BAPI stability, and test with a standard extractor. Also, updating Talend might help.

Sometimes SAP errors are trickier than decoding pure desi foods—but a few tweaks should fix it!