Dump while creating delivery VL01N

[former_member182805]

Dear gurus,

I am getting the following dump while creating a delivery:

After investigating, we found the following:

At the time of sales order creation, there was enough stock for one of the materials in the sales order and the corresponding schedule line was confirmed.

Later, during delivery creation, the stock of the material became 0 and no stock was available. It seems this happened due to back order processing or some other reason.

When the user tried to create a delivery for such a sales order, the above dump occurred.

We could replicate the same error in a quality system and were able to do so.

I tried finding if anyone else has got this error and how they solved it, but couldn't. I tried looking for a SAP note, but couldn't.

Is there any solution in terms of SAP note or otherwise to the above dump?

[rob_ariaans · Accepted solution]

I've seen this issue before, where it occured because the confirmed quantity of the sales order has been used already on another order. You could check Note 2677170 and subsequent notes.

If I remember correctly, to solve it:

You can try and perform a new availability check on the sales order.

Second, I believe on the selection screen of VL01N it helps if you enter both the From and To item number (even if they are the same item, both fields shoud be filled).

[former_member244427]

Hello,

Check Following KBA

2730449 - Runtime error MESSAGE_TYPE_X occurs when creating a delivery from a Sales Order

Also below notes if the above KBA does not help

2500159 - MESSAGE_TYPE_X issued during delivery creation

2677170 - Runtime error MESSAGE_TYPE_X occurs in VL01N transaction

Regards

Abhishek

[former_member576734]

Hi,

Dump at message printing ?

Try to desactivate immediate printing at delivery save.

[former_member183501]

Even if, stock is zero during delivery creation, upon clicking on PGI, system will show an error i.e 'Deficit of qty xxx in plant xxxx' but dump is not expected.

Please check in ST22 and see the complete information there.

Also check if any enhancement is causing this dump.

If possible, take help of an ABAPer during ST22 analysis.

Any positive resolution, please update here also.

Regards

Kamlesh