 |
|
Topic: UnDo Works Order not unissuing sub assembly components.
|
| By: SimonQ | Posted on: Nov 7 2022 at 09:22:13 AM | I have a top level assembly that contains a couple of sub assemblies.
One of the sub assemblies is a CSAS type, but the other was incorrectly set as an ASSY.
When I issued material (Pick Now) the top level assembly, it issued all of the components of the ASSY sub assembly as explained in the documentation.
I then realised that the 2nd sub assembly should have been set to CSAS, so I used UnDo Works Order to reset the works order for the top level assembly, changed the sub assembly type to CSAS and then reissued the top level assembly again.
However, the UnDo Works Order function did not unissue the components on the ASSY type sub assembly.
My question is should it have done so?
Thank, Simon. | |
| By: Guest | Posted on: Nov 9 2022 at 03:57:38 AM | Yes. When you UnDo a WorkOrder it should UnIssue all the components inside an ASSY sub assembly.
Now I'm not quite sure what would happen if you changed the ASSY to CSAS and then unissued it.
I'd make a backup. Change it back to ASSY and then UnDo the WO again. Then change it to CSAS and reissue it. That should fix it. If it doesn't then you have the backup. | |
| By: SimonQ | Posted on: Nov 9 2022 at 04:15:57 AM | Hi,
Thanks for your reply.
I did UnDo the works order before changing from ASSY to CSAS.
The trouble is that the change to the assembly type was done over a week ago and I have been doing other stuff since then, so I can't restore a backup from before the change and do it again as I would lose a lot of work since then. I have instead just manually booked the components back into stock.
I raised the call to check that I hadn't misunderstood. I will take more care to get the assembly type correct in future.
When I get some time, I will reproduce the process to see if it does it again (after a backup of course. :-)
Regards,
Simon. | |
| By: Support | Posted on: Nov 10 2022 at 04:05:44 AM | I'm sure that when a Work Order is UnIssued then the parts and quantities that were issued, at the time, are UnIssued even if you've made changes to the assembly since then. So even if parts are added and removed to/from the assembly it still looks back into history to see what was originally issued and it UnIssues those actual parts - ignoring the current state of the assembly.
The only thing that confused me was that if the assembly was edited to make a sub assembly into a CSAS then the UnIssue process might decide it's not necessary to look back in history for parts within the CSAS. But that wouldn't apply anyway because you're quite sure that you did the UnIssue while the sub assembly was still ASSY.
I am curious though so will run some tests in case there's a glitsch somewhere | |
| By: SimonQ | Posted on: Nov 10 2022 at 10:04:27 AM | OK, I have tried to reproduce this and I can't, so now I am doubting myself and the sequence of events.
I left the sub assembly set to ASSY, UnDid the works order for the main assembly and the sub assembly component parts were unissued.
I then did it again, but this time I changed the sub assembly to CSAS before UnDoing the works order and in this case it didn't unissue the sub assembly components.
I can only conclude that I am wrong. I apologise for any confusion.
Regards,
Simon.
| |
Reply - add a comment to this topic.
You may enter letters, numbers and standard punctuation only. HTML and other scripts/tags will be rejected.
|
|
|
