Posted by
Adrian Crum on
URL: http://ofbiz.116.s1.nabble.com/OFBiz-Dev-Why-Work-Order-tp166129p166132.html
Work Orders would be necessary for service-oriented companies, or a company with
a service department.
Our warranty-service dept uses work orders to specify repairs to be done and the
parts needed to do the repairs. Line items could be labor or parts.
Behind the scenes, it's just like a sales order I guess. The only difference is,
work orders won't appear on sales reports and vice-versa. Also, each line item
has a "Completed" field (logical) that indicates if the work was done. Once all
line items are completed, then the entire work order is considered completed and
it is closed.
David E. Jones wrote:
>
> Why do we have a work order? I think it was put in originally due to a
> misunderstanding, but I see some newer artifacts that use the OrderType
> of Work Order.
>
> What does this mean? It seems like from the code that it is just a
> sales order, but I don't think it makes any sense to have a work order
> separate from a sales order, and it is more flexible in general to just
> have sales orders and we can always use the Work Order Item OrderItemType.
>
> Does anyone have any issues with just removing the Work Order
> OrderType? I think it would be less confusing...
>
> -David
>
>
>
> ------------------------------------------------------------------------
>
>
> _______________________________________________
> Dev mailing list
>
[hidden email]
>
http://lists.ofbiz.org/mailman/listinfo/dev_______________________________________________
Dev mailing list
[hidden email]
http://lists.ofbiz.org/mailman/listinfo/dev