Anil,

How does that relate to my question on tying PO/SO to shipment and to 
WorkEffort (production runs)?

Are you saying that there can be a tree of production runs, the upper nodes being dependent on the lower leaves?

So, I would have the following production runs:

1. Production run to manufacture a bicycle frame

2. To paint bicycle frame

3. To assemble bicycle

Production run 3 will be top level, and will depend on production run 2, which will in turn require 1 to be performed first?

Seems like an odd way to break up a production run. More convenient to have all 3 production runs above be made routing tasks instead, routing tasks that all reside within a single production run.

I'd say the more user-friendly way, but more complex at coding level, is to have the sub-contracted routing task (painting) automatically tie to a PO buying painting services.

Let me know if I understand you correctly?

Jonathon

Anil Patel wrote:
Yesterday I applied a patch to Jira Issue for Deep copy of WorkEffort. Its
based on Idea of Create a Template WorkEffort (can have Assocs) , Then use
deep copy service to create instance of  it. This deep copy service can be
extended to even copy POs associated with WorkEffort.

Any Ideas!

Regards
Anil Patel



On 1/19/07, Jonathon -- Improov <[EMAIL PROTECTED]> wrote:

Chris,

I've confirmed that OFBiz doesn't do anything near as complicated as what
I described below (in
1st post in thread). (Even the routing task type of Sub-contracting
doesn't do anything?).

I'd like to ask the community for advice of "best practices" before I
submit an enhancement. How
would you usually go about:

1. Starting production run.

2. Task1: Produce some parts.

3. Task2: Ship parts to vendor for painting.

4. Task3: Assemble painted parts.

For Task2 (step 3 above), I'm proposing we have a PO for the painting
service, complete with a
link from PO to routing task, an outgoing shipment of pre-painted parts,
and an incoming shipment
of painted parts.

Has anyone done this yet (not merged into OFBiz)? Is it something that a
sizable majority of the
community would need? How would such a majority propose I do the above?

TIA for inputs!

Jonathon

Jonathon -- Improov wrote:
> Chris,
>
> Yeah, I read that. Nothing on what I'm talking about here.
>
> Let me try to get the requirements streamlined or simplified, and see if
> OFBiz can handle then.
>
> Jonathon
>
> Chris Howe wrote:
>> I don't do any manufacturing in my day to day stuff so
>> this may not fit your bill exactly, but have you read
>> over this:
>>
>> http://ofbizwiki.go-integral.com/Wiki.jsp?page=Manufacturing
>> ?
>>
>> --- Jonathon -- Improov <[EMAIL PROTECTED]> wrote:
>>
>>> Say I want to send some parts over to a vendor for
>>> painting services.
>>>
>>> Is there a way to:
>>>
>>> 1. Create a product of type "service" named
>>> PAINTING,
>>>
>>> 2. Create a PO to purchase this service,
>>>
>>> 3. Attach to this PO an outgoing shipment ferrying
>>> my parts to my vendor,
>>>
>>> 4. Receive the PO and have my painted parts in my
>>> inventory rather than the
>>>     product PAINTING.
>>>
>>> I've tried product associations like "Product
>>> Manufactured As", "New Version, Replacement" and "Equivalent or
>>> Substitute". Tried associations in
>>> both directions. No go.
>>>
>>> I can't "manufacture" PAINTING to produce the
>>> painted parts. Nor can I purchase PAINTING to receive the painted
parts.
>>>
>>> Any ideas?
>>>
>>> Jonathon
>>>
>>
>>
>
>




------------------------------------------------------------------------

No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.5.432 / Virus Database: 268.17.0/639 - Release Date: 1/18/2007 6:47 
PM

Reply via email to