Dump NESTED_PERFORM_ON_COMMIT occurs while saving BP

[James4044]

Hi,experts,

Short dump NESTED_PERFORM_ON_COMMIT occurs while saving a business partner after chaning a field value.

ST22:

Short text of the error message:

Nested call of PERFORM ON COMMIT: NESTED_PERFORM_ON_COMMIT caller: SAPLB

UPA_BADI_CALL program: SAPLBUPA_BADI_CALL form: BADI_CALL

Long text of the error message:

Diagnosis

During processing of a routine called using PERFORM ... ON COMMIT,

the system attempted to call PERFORM ... ON COMMIT again. Nesting

of this is not allowed.

System Response

Procedure

The program indicated after "Caller:" must be changed. This is the

program that calls the routine indicated after "Form:" during

COMMIT processing. This routine is part of the program indicated

after

"Program:".

Procedure for System Administration

Technical information about the message:

Message class....... 00

Number.............. 081

Variable 1.......... NESTED_PERFORM_ON_COMMIT

Variable 2.......... caller: SAPLBUPA_BADI_CALL

Variable 3.......... program: SAPLBUPA_BADI_CALL

Variable 4.......... "form: BADI_CALL"

The termination occurred in ABAP program or include "SAPMSSY0", in

"%_ORDER_FORM_LEVEL". The

main program was "SAPLBUPA_DIALOG_JOEL".

In the source code, the termination point is in line 101 of include "SAPMSSY0".

include "SAPMSSY0".

Can anyone tell me how to solved it.

Thanks!

[raymond_giuseppi]

• Did you look for a relevant OSS note?
• If none found, look for a wrongly coded BAdI/Exit/Enhancement

[James4044]

thank for you help ,but I find some notes,like 3106208 ,3080404 , but it's no effect.

And I can't find wrongly coded ,can you tell me how to find it quickly.

[raymond_giuseppi]

Go to debug mode to identify the first code to trigger a COMMIT WORK.

(Did you alreadty look for every implementaton of PARTNER_UPDATE, methods CHANGE_BEFORE*)

[James4044]

the commit work statement is a standard code and i can't change it.

[raymond_giuseppi]

You didn't display the COMMIT WORK statement...

[Sandra_Rossi]

Please post the whole short dump as a text file attachment, instead of just the first few lines.

But, before that, do what the Short Dump suggests (same as what Raymond suggested).

[James4044]

thank for you help,

I have added some dump pictures. Could you tell me how to find them?

[Sandra_Rossi]

Better attach the short dump as a text file because there are lots of interesting parts in a short dump.

[Sandra_Rossi]

(menu Utilities > List > Save > Local file > To clipboard, then paste it in a text file)

[Sandra_Rossi]

Just to say, you can check in your system if custom code is executed:

• ABAP trace (SAT)
• Layer-Aware Debugging in NW 7.0 EHP2 | SAP Blogs

If no custom code is executed, then you can contact SAP support.