Delivery has not yet been put away / picked (completely)

[Former Member]

Hello SDNers,

I have a Batch program that is calling VL02n for Delievry Picking ,Pcking & PGI....

This batch program runs in Background

For Some Delivery it is giving this Error Message "Delivery has not yet been put away / picked (completely)"

...But When i run the same program in foreground delivery got Processed Well.

CAN U PLS HELP ME

>Why this Happening

>In what scenarion we genearally get this message(we dnt have TO Confirm Step in our Process)

>even i Analyze the Program of VL02n ...This message is not there

From Where this message is comming

Thx in advance

PLS RPLY ASAP

[Former Member]

The update of pick qty and PGI will be happening in two separate database updates. The modules/code which do picking and then PGI will be working consecutively. If custom programs were written (BDCs, calling SAP update functions in Z program for pick, PGI etc), this kind of problem arises.

It is because, sometimes depending on systems conditions, even when before the PICK request is committed to database, the PGI will try to happen and not finding PICK qty it will error out. Since this depends on system load etc, this will occur quite randomly.

Ever tried to open a delivery in VL03N right after saving? The system will not allow you till the update is completed. Similar is the case here, the PGI call is happening rarely even before pick update is completed

Ask your developer to verify if there is COMMIT WORK AND WAIT statement once the picking update is done before proceeding to PGI

[Former Member]

thx,

Vishnu ..it 's really a very helpful suggestion....

but can u please tell me what Module/Include..for doing all this..i mean it is sys generated message...i have checked /debugged the CODE of VL02n(SAPMV50A)

but i didn't find it ...even it comes promptly...

...it would be helpful..

...if help me in locating the code from whr this message

"Delivery has not yet been put away / picked (completely)"

is triggering

thx in advance

Kuldeep

[Former Member]

After reading again through your messages, I understand that you are doing both PICK and PGI in single update BDC call to VL02N.

This is NOT correct way to do this, as this does not ensure that PICK values are committed first and then only PGI is attempted. We did face similar problems and have solved it by separating PICK and PGI in to two calls separated by COMMIT WORK AND WAIT.

I would suggest you to split your BDC into two calls. One which does only PICK and save and then followed by COMMIT WORK AND WAIT and then followed by another which does PGI and save. This should avoid the problem altogether.

Why it is not happening in foreground mode is it does not happen so quickly as in background. Even a split second can make a difference, that is why I would want you to split up both PICK and PGI update in two separate CALL TRANSACTION VL02N

I am not sure if it would help to know where the "Delivery has not yet been put away / picked (completely)" message is raised, as it is raised withing SAPs PGI routines, and it is mandatory that ONLY picked values are used for PGI.

I can only say that the message is given under id VL and no 609, it should be embedded somewhere in the PGI call, why don't you try to PGI without picking and put a watchpoint SY-MSGNO = 609