ABAP runtime errors DBIF_RSQL_INVALID_CURSOR

[Former Member]

The system generated a short dump after I run the transaction "SCMA"

Please take a look in the dump file :

What happened?

The current ABAP/4 program "SAPLSCMA " had to be terminated because

one of the statements could not be executed.

This is probably due to an error in the ABAP/4 program.

Unable to perform database selection fully.

record.

............................

Error analysis

One of the database selections included a database commit.

The selection was then supposed to continue. Before a

database commit, however, all outstanding database selections must be

concluded.

Possible causes in the application program:

Within a loop (SELECT/LOOP/EXEC SQL), one of the following

statements is used:

- MESSAGE (apart from MESSAGE S...)

- COMMIT WORK

- ROLLBACK WORK

- CALL SCREEN

- CALL DIALOG

- CALL TRANSACTION

- SUBMIT

- BREAK-POINT

- WAIT

................

The error occurred in a statement in which table "SCMAOFFICE " is accessed.

..............

If the error occurred in a non-modified SAP program, you may be

able to find a solution in the SAP note system.

If you have access to the note system yourself, use the following

search criteria:

"DBIF_RSQL_INVALID_CURSOR"

"SAPLSCMA " or "LSCMAF11 "

"GET_LONGTEXTS_FROM_CLIENT_000"

-

---

I'm not in debugging mode so I'm not paste the debugging related.

I try to search for "SAPLSCMA " or "LSCMAF11 "

"GET_LONGTEXTS_FROM_CLIENT_000" but there's nothing like this in marketplace.

With "DBIF_RSQL_INVALID_CURSOR" , there're quite a lot of results but not any in SCMA area.

Would you guys please take a look and advise,

Thanks

[Former Member]

look at the coding in Include LSCMAF11

FM 'SCMA_OFFICE_DOCUMENT_COPY' is called in between

select .. endselect ..

And at some point a message is raised/commit workis used

deep inside this FM ...

SELECT * FROM scmaoffice INTO ls_scmaoffice

WHERE profile = l_profile.

CALL FUNCTION 'SCMA_OFFICE_DOCUMENT_COPY'

EXPORTING

id_document_id = ls_scmaoffice-document_id

id_document_class = gc_bds_classname_task

id_client_from = '000'

id_client_to = sy-mandt

IMPORTING

ed_document_id_new = ls_scmaoffice-document_id

EXCEPTIONS

function_cancelled = 1

office_integration_error = 2

OTHERS = 3.

IF sy-subrc EQ 0.

UPDATE scmaoffice FROM ls_scmaoffice.

ENDIF.

ENDSELECT.

[Former Member]

Thanks for the information,

Could you please be more specific about the issue ? I'm totally green in SAP.

What can I do with this issue ? How to avoid a short dump generate when trying to access to SCMA

Thanks & regards,

Thuy Nguyen

[Former Member]

There are many notes available on this. You will have to check which is the note sutiable to your scenario.

1. 0.360 XX-CSC-GR-MM 750305 Transfer '32' to '20': Runtime error 11.03.2005

2. 0.340 PA-PA-FR 156285 Short Dump in MP006400 14.06.1999

3. 0.340 SCM-APO-MD 336749 /SAPAPO/DELETE_LC_ANCHORS: DBIF_RSQL_INVALID_CURSOR 10.11.2000

4. 0.330 PM-PRM-TL 534689 Maintenance task list:Runtime error DBIF_RSQL_INVALID_CURSOR 08.07.2002

5. 0.320 PE-LSO-TM 952614 LSO: Booking relationship harmonization 30.11.2006

6. 0.320 BW-BCT-PY 621233 0HR_PY_PP_2 DataSource: Short dump with select statement

Best regards,

Prashant

[Former Member]

Try to Regenerate the program .

If first time running SCMA gets short dump, you can try to regenerate SAPLSCMA. This solved my problem.