VL01N performance Issue

[Former Member]

Hi,

I am experiencing a peculiar issue.

When i create a Delivery , it displays that delivery successfully created. But when i go to to VL02N to change/Display(Vl03N) delivery, the mesage displyed is "The Delivery does not exist or has been archived". Sometimes the message is "It is currently being processed." For this i log off from the system and log in again, then also the same Message, that delivery is currently being processed.

But when i check after sometime(5-10mins), i am able to see the delivery which i created.

I am not sure what could be the issue.

Can anyone help me on this.

Let me tell you that, we have recently upgraded oour system from 4.7 to 6.0.

Please Advise.

Regards,

Saurabh

[HermannGahm]

Hi,

check SM13 if your delivery is in the update requests which have not been processed yet.

On a busy system and maybe few UPD processes it is likely you will find it there while VL20N

tells you: "The Delivery does not exist or has been archived." or "It is currently being processed.".

Kind regards,

Hermann

[Former Member]

Hi,

I have checked the SM13. It shows me an update process.

What should be my next step???

Regards,

Saurabh

[ThomasZloch]

> It shows me an update process.

Just one? Or many?

If you see many, there might be a bottleneck in the update processes as Hermann described, also check SM50 if the UPD processes are constantly busy.

Thomas

[HermannGahm]

Hi,

so you found your update request. That explains while it is not in VL20N immediatelly.

Question now is...

1.) how long is your request in the queue till it is served (wait time)

2.) how long does it take to process your request (service time)

Regarding 1st.: overall system performance should be checked... how much update requests are there... are there enough UPD processes configured... and so on...-> talk with your system administrators

Regarding 2nd.: your update proces may contain userexits or not... in any case you can trace

the processing of your upd request with SE30/ST12 context trace. (SAP profile parameter rstr/accept_remote_trace (dynamically switchable) needs to be set to true -> check with system administration as well). You will receive a additional trace file for your update request which can

be openened and analyzed with SE30/ST12.

So both... 1.) and / or 2.) may be responsible for the delay till you see your Delivery in VL20N.

Kind regards,

Hermann

[Former Member]

Before saving your delivery, debug the user exit for saving delievry.

Find out where the problem is ..

[Former Member]

Thank you all for your suggestions.

The problem is resolved now. Actually there was an issue from the basis side.

As an ABAP'er, i could see something wrong in ST02.

The SWAPS column in ST02 had some large values and was showing in RED.

My Basis person tuned the system and the issue is Resolved.

Thanks for all the suggestions.

Regards,

Saurabh