MESSAGE_TYPE_X dump when creating a purchase order via ME21N.

[Former Member]

MESSAGE_TYPE_X dump occurs when trying to create a purchase order.

i opened the message in se91 and the message was "PRECOMMIT HAS NOT BEEN CALLED YET".

I thought this would be a functional issue and asked them but the refused saying that this is under ABAP scope since a dump occurs.

Kindly assist how can i proceed further.

[former_member195402]

Hi Rajesh,

please check SAP note 1901102.

Regards,

Klaus

[Former Member]

Hi Rajesh,

Just Debug the ME21N T-code,and observe

is there any User exits,Customer Exits, Badis are Implemented for ME21N T-code or not.

if there is any Enhancement is Implemented for ME21N just check it once is it creating Dump or not if Yes Then modify it as per the Business requirement.

just check out once it may work out..

[roberto_forti]

Hi Rajesh,

Check transaction ST22 and verify the abap code point.

There you can identify the abap object (customer exit, user exit, function module, business object).

This is important to identify how it will be fixed out.

Regards.

[Former Member]

sorry for delay in reply

the dump occurs in flag variable chk_precommit_ok in a standard SAP set flag function module. The user is trying to create RRB via ME21N. after entering the inputs when he clicks save button the dump occurs.

kindly advise on how to proceed further.

[Former Member]

If there is no custom development in the transaction, then it's a problem for OSS.

Rob

[Former Member]

hi All.

Thanks for the reply.

Finally with the help of functional people we found that the user did not have any authorization role to create an RRB via ME21N. hence this was turned.

Thank you all for your support.

[Former Member]

So you can tell your functional people that not all dumps are ABAP related

Rob