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

ERROR : DBIF_RSQL_INVALID_CURSOR

Former Member
0 Likes
753

Hi ,

I am getting dump "DBIF_RSQL_INVALID_CURSOR " when i am trying to update bapi inside select endselect.

can any one tell me alternate logic. i am dealing with 100,00,000 data.

I cant do commit bapi after loop as all data in bapi will not get commited.

My logic is some what like

select * from but000

INTO TABLE it_gpart PACKAGE SIZE 10000.

CALL FUNCTION 'BAPI_CTRACCONTRACTACCOUNT_CLR'.

CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'

EXPORTING

wait = 'X'.

endselect.

1 ACCEPTED SOLUTION
Read only

Former Member
0 Likes
664

You cannot issue a commit in between a SELECT and ENDSELECT loop. That is why you are getting this error.

5 REPLIES 5
Read only

Former Member
0 Likes
665

You cannot issue a commit in between a SELECT and ENDSELECT loop. That is why you are getting this error.

Read only

0 Likes
664

I know why this error is coming ,but i have such requirement. i am looking for altenate solution

Read only

0 Likes
664

Can you not do a commit after the ENDSELECT? That way you will either commit all or rollback all.

Read only

0 Likes
664

no i cant do so each time i will call bapi i will get differenct data .

Read only

0 Likes
664

Can you bring all the contents of the table into an internal table and then do BAPI call and commit?