Hi,

Can you descibe the problem in more detail?

For example - what is the status on the pick list, is the material still reserved on the material line.

Even though some of the material have been picked it should be possible to proceed to issue the rest of the material, so a more detailed description of the problem is needed I think.

Sorry - there is only one material line on the work order and this item has had the pick list printed and picked

Ok, but then it has been picked to the relevant WO/Work Task or?

What do you want to do next?

They want to unpick - this was done in error

Goal is to issue the material to the work order but we get an error when trying to do this because it says it is on a pick list so we want to undo the pick list so we can issue material to work order

But if you proceed with picking the pick list then the material is issued on the work task.

Can you look what status the pick list has?

The pick list is picked

If you then go back to the material line - isn’t the material issued?

No its released

Ok, but what is the Qty Issued on the line? And what is the Qty Required?

Yes this is strange.

Have you any idea how the user ‘ picked an item off a work order’?

Is there just one line on the pick list?

Can you provide a screen shot on the pick list detail screen.

Ok, then the user picked 0…

Tested this in App10 Upd13.

Manage to get to same situation (pick list in Picked with 0 picked and material still reserved and not issued).

I could just do a manual issue on the line and then the part was issued.

Isn’t that possible for you? Is the Manual Issue command not available or what error message do you get.

We get this error when I try to issue parts to repair

Is this work task and material line part of a repair flow (do you know how the work task and material line was created)?

On what update are you?

I’m looking to see if there has been some bug corrections in this area.

It originated through CRO and we are on update 10

Ok, there was a bug correction delivered in Update 11 that I belive would help you out.

Bug ID is 157639.

You would need to take that (and I think also there is a repair script connected to the bug fix that would sort the situation out).

So get in contact with support.

Sorry, but this is the best I can do at the moment. Hope it is sorted out.