2007 Jul 26 10:12 PM
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.
2007 Jul 26 10:18 PM
You cannot issue a commit in between a SELECT and ENDSELECT loop. That is why you are getting this error.
Can you bring all the contents of the table into an internal table and then do BAPI call and commit?
2007 Jul 26 10:18 PM
You cannot issue a commit in between a SELECT and ENDSELECT loop. That is why you are getting this error.
2007 Jul 26 10:30 PM
I know why this error is coming ,but i have such requirement. i am looking for altenate solution
2007 Jul 26 10:32 PM
Can you not do a commit after the ENDSELECT? That way you will either commit all or rollback all.
2007 Jul 26 10:41 PM
no i cant do so each time i will call bapi i will get differenct data .
2007 Jul 26 11:06 PM
Can you bring all the contents of the table into an internal table and then do BAPI call and commit?
| User | Count |
|---|---|
| 6 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 |