‎2009 Jul 30 9:17 AM
Hi All,
I am getting a short dump with the error message
''The current application triggered a termination with a short dump ' in the production system.
The order of callig the objects is as follows:
Web Dynpro Component ZWD_ERT
Web Dynpro Controller EXTERNAL_ONBOARD calls method ONACTIONSAVE_EXTERNAL_DETAIL -> calls FM ZXR_HR_EXTUPDATE_EDIT
calls below forms ->
FORM SAPLZXR_ERM_UPDATE_EDIT
PROCESS_INFOTYPE
FORM SAPLZXR_ERM_UPDATE_EDIT
OTHER_INFOTYPE
FUNCTION SAPLZXR_ERM_UPDATE_EDIT -> calls FM HR_INFOTYPE_OPERATION ->which inturn calls FM HR_MAINTAIN_MASTERDATA ... which calls some sap standard classes and the error occurs in
Termination occurred in the ABAP program "SAPMSSY0" - in "%_ORDER_FORM_LEVEL". |
The main program was "SAPMHTTP ".
In the source code you have the termination point in line 89
of the (Include) program "SAPMSSY0".
Short text of error message:
Nested call of PERFORM ON COMMIT: NESTED_PERFORM_ON_COMMIT caller: SAPLB
| UBA_4 program: SAPLBUBA_4 form: GENERAL_BADI_CALL
Can any one faced this kind of problem?
what is the solution for this?
Regards,
Lakshmi.
‎2009 Jul 30 9:32 AM
‎2009 Jul 30 9:32 AM
‎2009 Jul 30 10:34 AM
Hi,
Thanks for your reply. Here the dump comes from the standard objects as shown in the error log.(in my earlier query ).
You are asking me to add a check in the BADI. but that BADI is not a customized one.. and it is called by sap standard program.
Now could you please tell me how avoid this dump.? The dump comes from the 89 line of standard program (subroutine pool ) SAPMSSY0.
Regards,
Lakshmi.
Edited by: Lakshmi Atukury on Jul 30, 2009 11:35 AM
‎2009 Jul 30 11:00 AM
The standard SAPMSSY0 "System Exits" does not trigger the error it receives it from another program. The error is triggered somewhere in form GENERAL_BADI_CALL of Function group BUBA_4, this form manages the call of CHANGE_BEFORE_UPDATE method in BADI implementation, that is why I suspected an implementation of BADI, which cause the error which is a PERFORM ON COMMIT when the luw is already in COMMIT.
If you don't find any BADI or Caller "error", look at OSS, there is a note with the same symptom, look at [Note 962094 - SAP-BP: BUPA_CENTRAL_EXPL_SAVE_HR (no performs on commit)|https://service.sap.com/sap/support/notes/962094]
Regards,
Raymond
‎2009 Aug 04 12:16 PM
Hi Raymond,
Thanks for your quick reply. The note which you gave is for the component ( sap_aba ) release 7.0
But in our environment it is 7.1 release. How do i get the same note for the release 7.1.
Could you please tell me how to go ahead?
Regards,
Lakshmi
‎2009 Aug 04 12:25 PM
‎2009 Aug 06 10:46 AM
Hi ,
We have raised an OSS message to SAP. we got the following relpy..
The reason for the short dump is normally that you call a
perform_on_commit although you are already in a perform_on_commit phase.Please check that in your program.
Furthermore, please also implement following notes as your maintained
SP level is very low:
1116033, 1107221, 1108931.
So now how to check the program where it calls perform_on_commit phase,as i don't have debugging access in production .
This dump issue can't be replicated in Development or quality. What are necessary steps to be taken to solve this issue?
please suggest me how to go ahead?
Regards,
Lakshmi.
‎2009 Aug 07 12:19 PM
‎2009 Aug 18 6:46 AM
Hi ,
my problem not yet solved.I am not able to find how the BADI being called in this program.
Could please help me how to find the badi and the method being called?
Regards,
Lakshmi.