data buffer exceed error while retrieving SAP table

[#1]

Exception in component tSAPTableInput_1 (SAP_VBRK_FILTER)
SAPException@2f67a4d3 [
errorCode=13
,errorGroup=126
,errorKey=DATA_BUFFER_EXCEEDED
,errorMessage=DATA_BUFFER_EXCEEDED
,errorMessageNumber=000
,errorMessageText=
,bapiName=RFC_READ_TABLE
,tableName=VBRK
]

[Anonymous]

Hello,

Are you getting this issue with big table? Have you checked the option "Set max length for variable length type when api.use_z_talend_read_table parameter is true" in advanced setting of tSAPTableInput?

 Here is online component reference about: TalendHelpCenter:tSAPTableInput.

Best regards

Sabrina

[#3]

hi @xdshi,

        i set that in my talend settings, but i even get that error

---

@xdshi wrote:

Hello,

Are you getting this issue with big table? Have you checked the option "Set max length for variable length type when api.use_z_talend_read_table parameter is true" in advanced setting of tSAPTableInput?

 Here is online component reference about: TalendHelpCenter:tSAPTableInput.

Best regards

Sabrina

---

[Anonymous]

Hello,

Could you please indicate on which talend build version you got this issue?

Best regards

Sabrina

[ANZMike]

Hi,

We are also experiencing this issue- are there any further suggestions.Or better still some examples - perhaps using a  common table like MARA.

Mike

[ANZMike]

we are on ver 7.2

[Anonymous]

We are facing this issue. I check the checkbox Set max length for variable...

We are on version 7.2.1. Its a showstopper. Please help

[akumar2301]

https://help.talend.com/reader/pYOrzmMCalIIgh7aoWwc5g/U8TLETI9KHm52_3R0k9TTw

Did you install transport function for SAP.

[ANZMike]

Hi

We are on 7.2.1, basically we installed TEDK900345, ensure you follow the instructions in the readme.txt

https://help.talend.com/reader/wh1zYQcgn7ZUg0vjIwdaFQ/b1KLUE8zhpa8RGEQJP2FJQ

After we imported TEDK900345, I created a new connections in Talend, copying exactly the previous connections and it works………

• I then created a job with two extractions from the same table, one using the old connection and the other the new connection, old failed & new works.
• I then was able to compare the code and realised that I had misspelled the use_talend_z_read_table. It should be api.use_z_talend_read_table. I think that is occurred because of the Talend Web page I was looking at was wrong…..https://help.talend.com/reader/EjmsC0DyG4R_u1NIpo27BA/MYwvGYp7vPGe_rgVzeEecA

We still have issues with trying to load more than a Million Records, But are making progress.