Has anyone done a customization to the End Activity screen to allow the entry of multiple scrap qty’s with different reason codes during a single end productivity entry? I would want up to 8 possible entries of Scrap Qty’s and Reason Codes. If more than 8, the Operator would Start & End Activity again to complete more Scrap Qty’s and Reason Codes.
I was using 8 as a benchmark but it could be less; like 4. As you know with the standard End Activity, you have 1 chance to enter a scrap qty with 1 reason code. If they need to enter more than that, it’s another start and end activity. If they have 4 different reason codes, it’s 4 start and end activities.
You might want to look at the Report Quantity functionality. There are two ways to do Report Quantity. The first is if you have activity stared and hit Report Quantity, it basically takes the amount you put in and adds it to the Labor Detail. If you continue to hit report quantity, it just accumulates it in the LaborQty until you end activity. This way won’t do much for you. This way does not create a new LaborDtl record for every time you hit RptQty - it just accumulates on one.
The other way is you can Report Quantity without starting the activity. It basically creates a LaborDtl record without any labor/burden time. So, if I sat there and hit Report Quantity 8 times, I’m going to get 8 LaborDtl records with just the quantities on them, and I won’t have to start/stop the activity 8 times. The great part about this way - you have the scrap each on it’s own LaborDtl record and you’re staying within the business logic.
The standard Report Quantity screen has just the Quantity on it, there’s no place for scrap or reason codes. But, it’s using the same LaborDtl dataset. So, it might be possible to customize it so it has the scrap quantity on the screen. I don’t know if the Report Quantity business object would allow you to create this with a scrap quantity but no labor quantity, so that might be a challenge.
A quick solution might be to see if you can customize the Report Quantity screen with the scrap. The process would be they end activity as normal with one of the scrap quantities, and worst case they have to then run Report Quantity for all their other scrap reasons.
A more complex solution would be to build the End Activity program so they enter a Scrap Quantity and reason code on the screen, and it calls the Report Quantity business object in your code to add the scrap. I’m not sure though, if you have an active Labor transaction going if it would try to simply add the quantity to that one.
Hopefully this points you in a direction that might give you a solution.
Report Qty is only for “Good” Qty. I am looking to report multiple Scrap Qty’s with the different scrap reason codes; all in 1 End Activity. Currently, the Employees are doing multiple end activities.
I am thinking I will need to build a custom tab/panel card to allow the multiple entries (custom qty fields & custom reason code fields) and have them add up and total in the natural Scrap Qty field (grayed out) so that it doesn’t allow a different total scrap qty from the individual scrap qty’s recorded.
Yes and no. We have multiple opportunities per operation. If an operation is tin and solder wire, but there are 100 wires per assembly there are 100 opportunities for a defect per assembly for that operation. This does not get sent to scrap with reason codes, but it could. I write to a table for analysis and I add a rework operation for the failures to the job. The grid can grow as needed and the Defect Code has thousands of selections.
I opened a Kinetic Idea a few months ago and it has 139 votes. There is definitely interest! If this is something your organization needs, please go vote:
KIN-I-3647
