Do you REALLY want people on the floor deciding which whse/bin reported nonconforming Job OP WIP Qty's should go? (Sounds like a recipe for disaster.)
Better to have enough fully defined reason codes in place to cover 95% of your typical issues (I would think).
Inspection would probably be better equipped to then do any WIP whse/bin movement within the (timely) inspection process.
If you're paradigm is physical location based and you simply MUST shuttle the non-conforming WIP (physically & systemically) to specific inspection pending whse/bins, you may find the capability is there (but just hidden).
I don't think you indicated if you were using MES End Activity (Time & Qty reporting), MES Qty Reporting (Qty only reporting) or Vantage Labor Entry (capable for all types).
Whatever app it is, open it up in dev mode, go to data tools and look at all the app's dataviews. You may find one of the views supports specifying the to Whse/Bin.
If not, you're screwed (short of adding the necessary BO & FKVs to support editing these 'to' whse/bins).
If so, step one would be to place suitable pull down selection controls on the form next to Non-conforming qty (& reason code selection) & link the controls to the appropriate tableview/field.
Make sure the controls (check in the properties window) are not disabled & that the tableview/fields are not read only. If they are, they can be set to be active and read/write (unless user profiles are set up to force read only at the db level) with some simple vb client code.
Save the customization and test it to verify you've truly provided user control as to WHERE the WIP goes and waits for inspection (as it is now in the OP inspection queue).
If it worked, your golden. If not, you'll have to really dig into the customization (no fun with the lame editor with no watch values and set/break point stepping capability!) and try to end run the base app's logic. (At this point it might be easier to change your physical process.)
Also if it worked, consider adding custom client code to 'hard code' auto-selection of the 'to' whse/bin based upon the reason code selected. That will eliminate many entry errors opening these fields up for user entry will likely result in. (Be careful what you wish for!)
Please let me know if any of that helps and any progress you make (or if you get stuck somewhere). They are generic recommendations as your inquiry question didn't contain a lot of needed detail (version, optional modules licensed, pending inspection whse/bin schema you are trying to preserve - and why, etc.,).
A month or two ago we did some similar customizations - only we chose to do it in the DMR module where we felt we'd have better 'people success' rate at executing the process reliably.
...Be glad to share any code snippets or basic things we learned while doing that.
Rob
Better to have enough fully defined reason codes in place to cover 95% of your typical issues (I would think).
Inspection would probably be better equipped to then do any WIP whse/bin movement within the (timely) inspection process.
If you're paradigm is physical location based and you simply MUST shuttle the non-conforming WIP (physically & systemically) to specific inspection pending whse/bins, you may find the capability is there (but just hidden).
I don't think you indicated if you were using MES End Activity (Time & Qty reporting), MES Qty Reporting (Qty only reporting) or Vantage Labor Entry (capable for all types).
Whatever app it is, open it up in dev mode, go to data tools and look at all the app's dataviews. You may find one of the views supports specifying the to Whse/Bin.
If not, you're screwed (short of adding the necessary BO & FKVs to support editing these 'to' whse/bins).
If so, step one would be to place suitable pull down selection controls on the form next to Non-conforming qty (& reason code selection) & link the controls to the appropriate tableview/field.
Make sure the controls (check in the properties window) are not disabled & that the tableview/fields are not read only. If they are, they can be set to be active and read/write (unless user profiles are set up to force read only at the db level) with some simple vb client code.
Save the customization and test it to verify you've truly provided user control as to WHERE the WIP goes and waits for inspection (as it is now in the OP inspection queue).
If it worked, your golden. If not, you'll have to really dig into the customization (no fun with the lame editor with no watch values and set/break point stepping capability!) and try to end run the base app's logic. (At this point it might be easier to change your physical process.)
Also if it worked, consider adding custom client code to 'hard code' auto-selection of the 'to' whse/bin based upon the reason code selected. That will eliminate many entry errors opening these fields up for user entry will likely result in. (Be careful what you wish for!)
Please let me know if any of that helps and any progress you make (or if you get stuck somewhere). They are generic recommendations as your inquiry question didn't contain a lot of needed detail (version, optional modules licensed, pending inspection whse/bin schema you are trying to preserve - and why, etc.,).
A month or two ago we did some similar customizations - only we chose to do it in the DMR module where we felt we'd have better 'people success' rate at executing the process reliably.
...Be glad to share any code snippets or basic things we learned while doing that.
Rob
--- On Fri, 1/23/09, jimlmm24521 <jimlmm24521@...> wrote:
From: jimlmm24521 <jimlmm24521@...>
Subject: [Vantage] no bin option in MES for non-confomring
To: vantage@yahoogroups.com
Date: Friday, January 23, 2009, 7:52 AM
We would like our operators during their end activity to report their
non-conform quantities. The parts automatically go to inspection, but
with no option to pick a bin. We have many inspection areas that
parts could go to. Any ideas on how to work around this? We don't
want operators to have to go into the non-conformance screen and fill
out the information.