Neither "ROU_ASSEMBLING", "ROU_MANUFACTURING", nor "ROU_SUBCONTRACTING"
were found to be used in any business logic. I couldn't find any
documentation about them in the DMRB either. I'll just tell the users
to leave that field blank if the task doesn't involve actual
manufacturing or assembling.
On 02/03/2014 09:15 AM, Pierre Smits wrote:
> Christian,
>
> You could do a search on anly of the types (the
> associated workEffortPurposeTypeId) to see whether these are referenced in
> services and to evaluate what these services do.
>
> Regards,
>
> Pierre Smits
>
> *ORRTIZ.COM <
http://www.orrtiz.com>*
> Services & Solutions for Cloud-
> Based Manufacturing, Professional
> Services and Retail & Trade
>
http://www.orrtiz.com>
>
> On Mon, Feb 3, 2014 at 3:52 PM, Christian Carlow <
[hidden email]
>> wrote:
>> Does it make sense to add "Inspection" as a Routing Task Type? Currently,
>> "Manufacturing", "Assembly", and "Sub-contracting" are the three values
>> available which doesn't account for inspection-only tasks. The purpose
>> type could just be left blank but I'm not entirely sure of the use of the
>> field and if its worth adding the Inspection task.
>>