Runtime error while saving in j1if01 tranaction.

[Former Member]

we r facing Dump error while saving in j1if01...pls find log below/.

Runtime Error MESSAGE_TYPE_X

Date and Time 31.07.2011 09:06:23

User and Transaction

Client.............. 500

User................ "EXE_PROCURE"

Language key........ "E"

Transaction......... "J1IF01 "

Program............. "SAPMSSY0"

Screen.............. "SAPMJ1IFN 0200"

Screen line......... 17

Information on where terminated

The termination occurred in the ABAP program "SAPMSSY0" in "%_ROLLBACK".

The main program was "SAPMJ1IFN ".

The termination occurred in line 505 of the source code of the (Include)

program "SAPMSSY0"

of the source code of program "SAPMSSY0" (when calling the editor 5050).

Source Code Extract

Line SourceCde

475 ENDIF.

476 ENDIF.

477 ENDFORM. "%_get_vb_key

478

479 *----

---

480* FORM %_CALL_ROLLBACK

481 * Call ROLLBACK-Handling

482 * To be called by kernel code to perform rollback handling in ABAP

483 *----

---

484 FORM %_call_rollback. "#EC *

485 * Save SUBRC for returncode after EXCEPTION ERROR_MESSAGE

486 LOCAL: sy-subrc, sy-msgty, sy-msgid, sy-msgno,

487 sy-msgv1, sy-msgv2, sy-msgv3, sy-msgv4.

488 * Perform ROLLBACK with all registered rollback hooks

489 ROLLBACK WORK.

490 ENDFORM. "%_call_rollback

491

492 * -

---

493* R O L L B A C K

494* rollback work

495 * when called within CALL DIALOG --> no effect i.e. symmetrical to

496* COMMIT WORK

497 * -

---

498 FORM %_rollback. "#EC *

499 DATA: txend TYPE c.

500 DATA: l_oncom LIKE sy-oncom.

501

502 * forbid ROLLBACK if already in ON COMMIT/ROLLBACK handling

503 CALL 'GET_SWITCH_TXEND' ID 'STATE' FIELD txend.

504 IF txend = 'C' OR txend = 'R'.

>>>>> MESSAGE x086(00).

506 ENDIF.

507

508 CHECK sy-oncom <> 'N' AND sy-oncom <> 'V' AND

[former_member184473]

Hello Ketan,

The error message occurs if a rollback of the session timeout is triggered. The system does not find saved changes in the project during the rollback and outputs message MESSAGE_TYPE_X.

This cannot be solved unfortunately by a report or program as the Short Dump is not activated automatically, but by the ABAP statement "Message X" as response to "Discarding" of unsaved data and other problems occuring during the saving. To intercept the timeout-error possibly (there is no Basis-functionality for specific error-processing for timeout).

One way around this is to tweak the timeout parameter settings as described in note [824554|https://service.sap.com/sap/support/notes/824554]. Then the probability of getting the termination MESSAGE_TYPE_X because of timeout will be reduced.

Regards,

Eduardo Rezende