Will you share your effort on this in a Jira?
Jacques
Le 28/02/2014 23:32, Christian Carlow a écrit :
I've made more progress on this issue but it seems another entity might be needed to support the intended functionality. In a previous post I
suggested adding the timeEntryId field to the
I've made more progress on this issue but it seems another entity might
be needed to support the intended functionality. In a previous post I
suggested adding the timeEntryId field to the InventoryItemDetail entity
to track by-products created by production run task time entries. I
need a
After making some progress on this issue by adding the
timesheet/timeentry functionality to the production run task declaration
services, I've encountered more difficulties implementing the needed
functionality. I added a TimeEntryAssoc entity so that inspectors can
directly inspect a
I suppose the TimeEntryAssoc entity could be extended to include
quantityRejected and responsiblePartyId fields to eliminate the need for
a separate TimeEntryRejectParty entity.
On 02/27/2014 08:53 AM, Christian Carlow wrote:
After making some progress on this issue by adding the
I'm now aware of more complexity. The inspector supervisor explained
that partial inspections sometimes occur for which parts are moved from
a manufacturing dept to an inspection dept that performs partial
inspection and then sends to another manufacturing dept that ends up
sending the parts
I changed the title to be more clear.
The company ticket system has inspection functionality that allows
inspectors to declare multiple types of rejects for the quantity
specified on manufacturing tickets. This functionality doesn't seem
supported in OFBiz. I've see no way to determine that
Another related issue is how to determine the particular rejection
reasons. Inspectors may declare rejected pieces as by-products during
production run inspection steps that may be capable of rework. The
percentage good by employee report mentioned in the previous post also
displays the
Is there a reason the two Production Run Declaration
(manufacturing/control/ProductionRunDeclaration) forms cannot be
combined into a single form? If the first form is used to declare
rejections, why can't the by-products products be declared as inventory
in the same form instead of having to
My last post can be disregarded, splitting the production run
declaration into two different forms seems correct. There needs to be a
way to relate time entries created from the first form to inventory item
details created in the second form so that the types of rejects that
were produced