Skip to Content
-2

System_on_commit_iterrupted dump error?

Jan 22 at 09:15 AM

137

avatar image
Former Member

I have Z program calling Transation VA01 using CALL TRANSATION 'VA01', after creating sales order i wrote statement WAIT 3 SECONDS and then i am committing some my Z table updates using COMMIT statement, but this COMMIT in my Z program giving dump(SYSTEM_ON_COMMIT_INTERRUPTED) only in few times, not sure what is the reason, can anyone answer

Below Dump details:

Category ABAP Programming Error

Runtime Errors SYSTEM_ON_COMMIT_INTERRUPTED

ABAP Program SAPLSTXD

Application Component BC-SRV-SCR

Short Text COMMIT WORK processing cannot be interrupted.

What happened? Error in the ABAP Application Program The current ABAP program "SAPLSTXD" had to be terminated because it has come across a statement that unfortunately cannot be executed.

What can you do? Note down which actions and inputs caused the error. To process the problem further, contact you SAP system administrator. Using Transaction ST22 for ABAP Dump Analysis, you can look at and manage termination messages, and you can also keep them for a long time.

Error analysis The following are executed during the COMMIT WORK statement - the routines registered for this with the PERFORM .. ON COMMIT statement, - the methods registered for the events in the object services and possibly also local updating (SET UPDATE TASK LOCAL). An exception has occurred and has been caught. This causes the normal sequence of the routine to be interrupted, with the result that the program is continues before the COMMIT WORK call. As this can cause inconsistencies, normal processing cannot be continued.

How to correct the error: If the error occurred in your own ABAP program or in an SAP program you modified, try to remove the error.

In include LSTXDFXX dump is coming after error message at line no:489

477 form io_error using object

478 name

479 id

480 language.

481

482 call function 'SAPSCRIPT_MESSAGE_DEF'

483 exporting no = 607

484 v1 = object

485 v2 = name

486 v3 = id

487 v4 = language.

488 message e607 with object name id language raising io_error.

489 >>>>> endform.

10 |10000 characters needed characters left characters exceeded

What if the update takes 4 seconds?

1
Former Member
Mike Pokraka

How can we track the Update time, can you please explain?,

Thanks in advance.

0

Nothing to explain, my response was a comment not an answer. You assume it takes 3 seconds, but it can take longer.

If you would use BAPIs then the update would be under your control.

0

The answer is in the short dump, in the SAP notes, in the ABAP documentation, in the web.

0
Former Member
Sandra Rossi

I have already searched for this but i could not able to find it, Can you please provide me the SAP Note number.

Thanks in advance!

0

hmmm 431961 - Runtime error SYSTEM_ON_COMMIT_INTERRUPTED

(the answer is in the short dump too)

0
Former Member
Sandra Rossi

Thanks Sandra,

Is it something related to basis team to look?, i don't see any code lines in the provided SAP note.

Can you please assist on this.

0

It can also help you find the issue in your code. The basis team should have already searched the SAP notes. SAP notes can be of various categories, not only corrections ; this one is "Help for error analysis". It also has a correction by a kernel patch (apply the kernel). It is valid only up to release 6.20.

But as I said, the answer is in the short dump too. Why don't you attach it? (text, zipped)

0
Former Member
Sandra Rossi

Category ABAP Programming Error

Runtime Errors SYSTEM_ON_COMMIT_INTERRUPTED

ABAP Program SAPLSTXD

Application Component BC-SRV-SCR

Short Text COMMIT WORK processing cannot be interrupted.

What happened? Error in the ABAP Application Program The current ABAP program "SAPLSTXD" had to be terminated because it has come across a statement that unfortunately cannot be executed.

What can you do? Note down which actions and inputs caused the error. To process the problem further, contact you SAP system administrator. Using Transaction ST22 for ABAP Dump Analysis, you can look at and manage termination messages, and you can also keep them for a long time.

Error analysis The following are executed during the COMMIT WORK statement - the routines registered for this with the PERFORM .. ON COMMIT statement, - the methods registered for the events in the object services and possibly also local updating (SET UPDATE TASK LOCAL). An exception has occurred and has been caught. This causes the normal sequence of the routine to be interrupted, with the result that the program is continues before the COMMIT WORK call. As this can cause inconsistencies, normal processing cannot be continued.

How to correct the error: If the error occurred in your own ABAP program or in an SAP program you modified, try to remove the error.

In include LSTXDFXX dump is coming after error message at line no:489

477 form io_error using object

478 name

479 id

480 language.

481

482 call function 'SAPSCRIPT_MESSAGE_DEF'

483 exporting no = 607

484 v1 = object

485 v2 = name

486 v3 = id

487 v4 = language.

488 message e607 with object name id language raising io_error.

489 >>>>> endform.

0
Show more comments
* Please Login or Register to Answer, Follow or Comment.

2 Answers

Horst Keller
Jan 22 at 10:34 AM
2
Show 1 Share
10 |10000 characters needed characters left characters exceeded
Former Member

Hello Keller,

I could not able to find what i am doing wrong in my case, can you please explain how i can solve my error.

Thanks in advance.

0
Raymond Giuseppi
Jan 23 at 10:19 AM
0

Your code triggered an error message (TD 607, IO error) during a SAP Script FM execution in update task (can be COMMIT_TEXT or SAVE_TEXT) so dump is triggered. (Look at ST22 and SM13 to analyze)

Show 7 Share
10 |10000 characters needed characters left characters exceeded
Former Member

Yes you are right, But this error is only happening in production system(Not in test environment) only few times and don't know the reason, can you please suggest me the solution to fix this.

Thank you.

0
  • You wrote 'i am committing some my Z table updates', is your program also scheduling the update of those texts?
  • Can you see some errors in SM13, in this case, if executed again from SM13, is the error raised again (if no could have been data buffering or lock) if yes try to debug.
  • Else provide much more information on what you exactly perform in your Z program (update same data than VA02, or?)
0
Former Member

I din't see any errors in SM13,

After VA02 creation, in my Z program i am trying to update Ztables and Sending mail about the created sales order and then i am using COMMIT , then this commit is giving me the error.

0

You could try to add some break-point in text FM like COMMIT/SAVE_TEXT, you could also use FM like FREE_TEXT_MEMORY to perform some 'cleanup' in your code.

0
Former Member

The problem here is it is not replicating in test environment to debug, only production we see this issue in some cases.

0

No hints in the dump, like text id which triggered the error?

0
Raymond Giuseppi

488 message e607 with object name id language raising io_error.

The error message is TD607, it is sent if an UPDATE, INSERT or DELETE fails on STXH table.

0