Hey Jacques,
Yes, I was going to use the functionality to generate a department load
report to indicate what and when production work needs to take place
from customer orders. The functionality is especially important for
displaying assembly elements of order items.
For example, for an order for 10 of an item requiring 2 of an assembly
element scheduled 5 one day and 5 for another, there doesn't seem to be
an easy way to determine how much of the assembly element needs to be
produced to meet the schedule due date. The report uses
workEffort.estimatedCompletionDate as the due date but requires a
separate WorkEffort for each OrderItemShipGroupAssoc. But having more
than one production run per OrderItem is not supported due to
WorkOrderItemFulfillment primary keys.
On Fri, 2015-01-16 at 13:26 +0100, Jacques Le Roux wrote:
> I guess if you asked this question is because you have a need?
>
> If it's the case, could you please explain it?
> Examples always ease to think about a topic ;)
>
> Jacques
>
> Le 16/01/2015 02:10, Christian Carlow a écrit :
> > Does an additional entity need to be created to extend
> > WorkOrderItemFulfillment to support relations to more than one
> > OrderItemShipGroupAssoc? WorkOrderItemFulfillment excludes
> > shipGroupSeqId from the primary key so only 1 production run to be
> > related OrderItem. Should something like WorkOrderShipFulfillment be
> > created as a copy of WorkOrderItemFulfillment but includes
> > shipGroupSeqId as part of the primary key?
> >
> >
Locked
