(Replying outside of JIRA)

Adrian,

Sounds good -- we are really just getting started with the manufacturing component / work effort component. The trouble I am running into (and this is pretty typical of working in any new ofbiz area) is understanding the data model coupled with the standard workflow. The UI tends to be CRUD based so it is difficult to figure out what things I should be providing with each step of a standard production run. The second problem is that we have last merged ofbiz about six months ago, and it appears a number of enhancements have gone into ProductionRunServices, so the behaviour I see in our solution is different from what I see on ofbiz-trunk demo.

The things that are troubling my little brain now are ...

- why is there no option to assign a party to a routing task in a PRun
- it appears the changeProductionRunStatus and changeProductionRunTaskStatus do not enforce the StatusValidChange entity - we not only have "assembly" of products but also "disassembly"; not sure how I am going to do that ... logically it is just the inverse of an assembly, so I may consider "producing" multiple products of type RAW_MATERIAL from one or more FINISHED_GOODS - from data modeling v2 it appears that a services business may work with an "engagement" entity and/or a sub-class of order for "service order" ... ofbiz has neither of these, so I am unclear on how I am going to support straight service requests that have work effort involved


On Apr 14, 2010, at 12:21 PM, Adrian Crum (JIRA) wrote:


[ https://issues.apache.org/jira/browse/OFBIZ-3700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12856948 #action_12856948 ]

Adrian Crum commented on OFBIZ-3700:
------------------------------------

Bob,

Thank you for the information. I will work on this issue this weekend if no one beats me to it.

I am about to deploy Manufacturing where I work, so I'm learning it as well. Maybe between the two of us we can get some documentation on the Wiki and work out any kinks we encounter.

Reply via email to