Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Reg: RSQL error 13

Former Member
0 Likes
689

Moderator message: do not offer points

Hello All,

I am getting RSQL error 13 runtime error when I am inserting records into the database table from the internal table of the same structure.

"Insert ZPAY_TABLE form table GT_PAY_TABLE accepting duplicate keys"

I tried even Modify and Update statements Modify is giving 'Invalid Request' error.

Please tell me the reason for the error and how to rectify it.

<<text removed>>

Thanks in advance

Regards,

Suganya.

Edited by: Matt on Feb 18, 2009 8:29 AM

1 ACCEPTED SOLUTION
Read only

Former Member
0 Likes
593

I would imagine it has something to do with those duplicate keys - try looping & modifying ZPAY_TABLE from GT_PAY_TABLE .

Moderator message: do not offer points

Hello All,

I am getting RSQL error 13 runtime error when I am inserting records into the database table from the internal table of the same structure.

"Insert ZPAY_TABLE form table GT_PAY_TABLE accepting duplicate keys"

I tried even Modify and Update statements Modify is giving 'Invalid Request' error.

Please tell me the reason for the error and how to rectify it.

<<text removed>>

Thanks in advance

Regards,

Suganya.

Edited by: Matt on Feb 18, 2009 8:29 AM

3 REPLIES 3
Read only

Former Member
0 Likes
594

I would imagine it has something to do with those duplicate keys - try looping & modifying ZPAY_TABLE from GT_PAY_TABLE .

Read only

former_member156446
Active Contributor
0 Likes
593

Hi Welcome to SDN,

if you can hit a F1 on Insert statement, there is a link called prerequisites check that or ..

Prior to Release 6.10, this raises an exception that cannot be handled; as of Release 6.10, this raises the exception that can be handled CX_SY_OPEN_SQL_DB.

Read only

mvoros
Active Contributor
0 Likes
593

Hi,

this error usually means that you hit the limit for a size of the SQL query. SAP system rewrites your OpenSQL command into SQL query and sends it to DB. The problem is that there is a limit for the size of the SQL query. Hence in some cases SAP system generates larger query than this limit. If you check ABAP documentation for your SQL query then you can find the following sentence there.

Mass insert: Inserts all lines of table itab in a single operation.

SO I assume that SAP rewrites it into one big INSERT command. So haw many lines does your table have? If there are too many lines you can try to split it into smaller chunks. You can read more about SQL size restriction in this OSS note 635318.

Cheers