Topic: CSAS Optional Treatment Feature Request
|By: Stephen||Posted on: Oct 23 2019 at 09:43:40 AM|
|I reviewed several posts regarding usage of CSAS type assemblies and we currently have a possible need to use the CASA Category for pre-packaged parts. A common thread in some of those posts might be addressed if the CSAS type could optionally be ignored for Viewing and Reports. Not sure how the option would work for inventory calculations though but I can see you might have a need to optionally blow out all the CSAS sub parts into a consolidated shortage list (or not!)|
If you are already in there doing other CSAS work, what do you think?
|By: Guest||Posted on: Oct 23 2019 at 02:18:37 PM|
|I suppose one idea might be to show a small [+] button beside each CSAS in the BOM. Click that to expand [-] collapse the levels inside the CSAS.|
Also a [+] at the column header to open and [-] close all of them. But, when the work orders is issued (flushed, blown or whatever you wish to call it) we'd still treat CSAS as pre-build sub assemblies and take them from inventory.
Would that work for you? Anyone else like (dislike) that idea?
|By: Stephen||Posted on: Oct 24 2019 at 07:43:50 AM|
|There might be times when you want pre-built sub assemblies OR flushed components taken from inventory. But it gets complicated. Not sure how to handle it in this case.|
|By: Steve||Posted on: Oct 24 2019 at 10:21:03 PM|
I have posted this before, what would help me if you could set the CSAS or ASSY at the BOM level.
so you could have one BOM set to CSAS and another set to ASSY.
At the moment I have to change the assembly type print the BOM then change it back again.
|By: Guest||Posted on: Oct 25 2019 at 05:25:05 AM|
|If your sub assemblies are at the 1st level - ie not nested on level 2 or lower - then leave them as ASSY and, when you create a work order and 'Allocate'. before doing the allocate go to the menu at the top of the window and select the 'Single Level' option. This collapses the BOM and allocates just that first level. The Work Order remembers this so when you go back to that work order/BOM it still shows the first level and you can issue (go to WIP) and it takes the 1st level ASSY's out of inventory.|
Obviously that can't work if you have many levels where you want 'some' ASSY's to be picked from inventory while other ASSY's should be built.
Maybe Steve's idea of the ability to switch between the CSAS/ASSY behavior within the individual work order could work. But I wonder if it would get quite complicated with the possibility to make mistakes and allocate/issue the wrong kit. Also the likelyhood that the same product on two different days has entirely different BOMs leading to more confusion. The way it works now is that it's fixed and can't be changed so might not be flexible but t's consistent.
There's maybe ways round it but needs thinking about I think.
|By: Guest||Posted on: Oct 25 2019 at 05:28:47 AM|
|What I would like is that I could set the sub assemblies as CSAS and the default would be that it would take them from stock but if there weren't any in stock or not enough in stock then to switch the rest to assy or at least flush those down through the components and build them.|
so pick any available and build the rest within the same work order.
|By: Stephen||Posted on: Oct 26 2019 at 09:03:44 AM|
|I think to "set the sub assemblies as CSAS and the default would be that it would take them from stock but if there weren't any in stock or not enough in stock then to switch the rest to assy" would be very useful. |
It may just be logic in the program versus CSAS treatment though.
But I agree because I think we have a similar situation.
Reply - add a comment to this topic.
You may enter letters, numbers and standard punctuation only. HTML and other scripts/tags will be rejected.