cancel
Showing results for 
Search instead for 
Did you mean: 

Unable to Delete HU assignment in Outbound Delivery after PGI

Former Member
0 Kudos

Hello All,

I want to delete the assignment of a HU in Outbound Delivery after the goods issue has already been posted.

My steps are:

1. I am working with handling units

2. The goods issue has been posted with VLO2N

3. I canceled the goods issue with VL09, the HU is on st. type 916, which is OK

4. VL02N – Pack

5. And then I am getting this error:

Handling unit  has the status "goods issue posted", cannot be changed

Message no. HUGENERAL017

Diagnosis

Goods issue was already posted for handling unit , meaning that the handling unit can no longer be changed. Therefore, it is not possible to assign it to packing-data processing.

6. I press F3, and then I can see the packing dialog.

7. I mark the HU and the press “delete assignment” – so far so good

8. But the when I try to save the changed assignment I get this error:

Within the delivery, posting change not possible for stocks

Message no. HUDIALOG107

Diagnosis

During current processing, materials have been packed or unpacked that refer to a HU-managed storage location. During delivery processing, it is not possible to make a transfer posting of stock between HU-managed and non-HU-managed storage locations.

System Response

It is not possible to go back to delivery. The data cannot be saved.

Procedure

Pack the quantity that has before been unpacked or unpack this quantity again.

9. And then a message pop ups: “Packing situation does not allow exit”. I can choose between:

a) Cancel b) Pack

I know that my procedure is correct, because in a different warehouse with Hus the procedure works just fine.

So there is something misconfigured.

I would appreciate any help.

Thank you very much in advance,

M

Accepted Solutions (0)

Answers (3)

Answers (3)

Former Member
0 Kudos

The Issue is solved in the past replys, but i want to explain it in more detail

Steps

1.- Enter to the delivery

2.-Go to packing

3.. Select menu HU -> Delete Assignment

4.- Go to Menu

5.-Copy Pack Quantities As Dlv Quantities

6.- Save Delivery

Former Member
0 Kudos

Hey Marko

Did you figure out what was wrong with those deliveries? Was it something missing in SPRO? I have come across the same issue recently in our system.

Would be great if you could share your findings..

Cheers

Former Member
0 Kudos

Hello

Could you tell me how you resolved this issue

..i also facing the same issue...I reversed the out bound delivery using VL09.

HU status is 01(assigned to out bound delivery.) stocks lying in 916 storage type.

How to de assign the HU from delivery...and how to move the stock from 916 to original destination.

Former Member
0 Kudos

Done by delete assignment icon in the packing screen of DN at VL02n and then DN deleted

former_member182609
Active Contributor
0 Kudos

I hope you reversed the delivery through VL09 right.

Step 1 :In outbound delivery first delete assignment then save the goods.

Step 2.In vl02 n transaction go to EDIT option select copy pack qtys as delivery qtys then save the delivery.After you can cancel the delivery.

Former Member
0 Kudos

Thank you four your answer, but it does't actually help. My procedure is exactly the same as you suggested - but i can't do that, because of the error in step 01.

Everything was done correctly with VL09 - The exact same procedure works in a different warehouse.

So there is something misconfigured in SPRO or some OSS note is missing.

former_member182609
Active Contributor
0 Kudos

Can you tell me what is the Handling unit status ?Is it 03 or some other satus ?I think the handling unit satus is stopping to cancel the delivery.Check the handling stutus in HU03 transaction.

Former Member
0 Kudos

Hello Sridhar,

Thank you for your effort.

I don't know exactly to which status are you referring.

If you mean this field: VEKP_TXT-SYS_STATUS in HU03, then the statuses are two:

PHEX Physically Exists

WHSE In Warehouse

Regards,

Marko

former_member182609
Active Contributor
0 Kudos

If you GO HU 03 transaction enter the handling unit then select TTL content tab.In this screen if you go last column (Object) then you can see the status of your handling unit.If it is asigned to the delivery then it should be 03.Please see what is the status.

Former Member
0 Kudos

Ah you mean the field VPOBJ. Yes it has 01, which is the outbound delivery.

and the VPOBJKEY, has the outbound delivery number assigned.

former_member182609
Active Contributor
0 Kudos

I Guess is there any movements happen to handling units at warehouse level.

Check the all the handling units available in 916 location in LS26.

Check UU history what was the last movements Is it cancel the Outbound delivery material document or any ?.

Former Member
0 Kudos

Thank you for your respond.

The last movement for the HU is "Material Document Cancellation".

There are some other HUS of the same material on 916, but for different Outbound Deliveries - the GI has not been posted yet, for those...

former_member182609
Active Contributor
0 Kudos

I am looking your point no 5 how the error are you getting.Is all uyour handling units available in 916 & all HU history has material cancelation movement last movement ?.

Handling unit  has the status "goods issue posted", cannot be changed.

It should not give above message at all .I think some ware some loop is missing.Can you try one one one un assign the handling unit from the delivery ,So that we will find out which HU has problem.

Former Member
0 Kudos

This is a new Outbound Delivery recreated in our test system. Only this one an only one HU is assigned to the delivery.

I have made at least 10 deliveries with different HUS and it is always the same scenario and the same error message.

There must have been something in SPRO missing...

former_member182609
Active Contributor
0 Kudos

check this sap Notes 381773 &430161

If these are not relevent for you only option to debug why it is throwing error.

Former Member
0 Kudos

Thank you for your effort, but it must be something else, because we are on a much newer system:

SAP_BASIS7000025SAPKB70025
SAP_APPL6000020SAPKH60020
former_member182609
Active Contributor
0 Kudos

I tried lot am not able to find proper root cause.Are you able to debug the problem ?.Please debug which  processed one and not processed one so that we will get some clue.