BAPI_GOODSMVT_CREATE in Update Task (BG)

Da_l · ‎2012 Oct 11

Hello Team.

I need run the BAPI_GOODSMVT_CREATE in update task(BG)

The BAPI doesn't have this option. Then I create a FM to fill the structure and call the BAPI inside my FM.

All see good, but after give a back. Send me a message express with the error.

When I'm review the error in the SM13 and the ST22

show me the next error message:

Runtime Errors MESSAGE_TYPE_X

Occurred on 11.10.2012 at 15:09:09

The current application triggered a termination with a short dump.

...

Error analysis

Short text of error message:

Nested call of PERFORM ON COMMIT: NESTED_PERFORM_ON_COMMIT caller: SAPLM

BRE program: SAPLMBRE form: DELTA_PUT

Technical information about the 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

Message classe...... 00

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

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

Variable 2.......... "caller: SAPLMBRE"

Variable 3.......... "program: SAPLMBRE"

Variable 4.......... "form: DELTA_PUT"

Variable 3.......... "program: SAPLMBRE"

Variable 4.......... "form: DELTA_PUT"

Some idea to solve this topic.

Best Regards

David

gouravkumar64 · ‎2012 Oct 12

Hi,

I think,

From 4.6 release nesting of PERFORM ON COMMIT is not allowed .

See this link for your reference

http://help.sap.com/abapdocu_702/en/abapperform_subr.htm

Hope it helps.

Thanks

Gourav.

kesavadas_thekkillath · ‎2012 Oct 12

Hi,

I think so you are calling this FM in the badi or customer exit. This fm uses the function MB_GOODS_MOVEMENT_CREATE and the transactions like MIGO,MB01 etc also uses the same function call internally. This function must not be called twice in a single LUW. You can call the bapi in background task as seperate unit if required.

Before that please let us know where you are calling this bapi and what is your exact requirement .

Kesav

former_member194152 · ‎2012 Oct 12

Are you calling commit 2 times, because on commit routine will call update function module and inside that function module did you call BAPI_TRANSACTION_COMMIT, if yes then that might be cause for the dump.

Da_l · ‎2012 Oct 12

Thanks Team.

Both calls are in update task. But i have the dump in the first call. this is used from RF functionality. We see in the SM13 the 2 step in green color, but the general status is Error.

And send the error. We are trying modify the Call in Update Task. If you hace any other idea, please post it ! Thans