topic Re: ERROR : DBIF_RSQL_INVALID_CURSOR in Application Development and Automation Discussions

ERROR : DBIF_RSQL_INVALID_CURSOR

Former Member — Thu, 26 Jul 2007 21:12:35 GMT

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.

Former Member — Thu, 26 Jul 2007 21:18:40 GMT

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

Former Member — Thu, 26 Jul 2007 21:30:00 GMT

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

Former Member — Thu, 26 Jul 2007 21:32:30 GMT

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

Former Member — Thu, 26 Jul 2007 21:41:52 GMT

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

Former Member — Thu, 26 Jul 2007 22:06:59 GMT

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