Hi Kevin_Coulter 

I didn't run any tests. But in the on-line help from the function WIP cost without WO (inquiry FUNWIPBOM), it is stated that the cost would be grouped under a fictitious WO (1 per month maybe?), so I assume you should have new records in WIPCOST table. At least using this inquiry you should be able to view the fictitious WO number and query if the matching records exist in the WIPCOST table.

I hope this input is helping ;).

Keep me posted.

Hi Julien,

Thanks for the feedback I'll give that function a try.  I was able to institute the model by turning off the WIP accounting in the parameter values and then setting the STKEO and STKMC auto journals on the Time tracking plan entry transaction.  With this approach the accounting activity ran through the stock accounting interface. 

Regards,

Kevin

Kevin_Coulter said:

I believe this approach is designed for process manufacturers that don't have a series of distinct jobs but rather just a continuous stream of product being produced on a daily basis. 

Hi Kevin_Coulter 

Btw: this is not the usual business case for tracking w/o work order.

It is a very simple solution but I would advise to move to using a work order (once every month or every week?), to enable some features such as:

• To manage projected available stock (MRP for instance) on both released products and components stock
• Capacity management
• Traceability
• WO actual cost calculation (with possible update of the stock value in case of AVC)
• Production efficiency reporting

Maybe you can consider this evolution in phase 2 of the project. Creating a work order can be quite simple especially with reordering method such as ROP, frequency or MRP.

Julien thanks for your perspective on this you raise some good points.

If it a continuous delivery process, I image they are working MTS so you can simply set sales forecast per month to define how much you want/expect to produce every month (via SOS import template this is easy). Then everything can be automated: MRP with week or month bucket (via a recurring batch) and the work order creation (via FUNMAUTR that can be set as a recuring task as well). Of course you need the manual tracking (but similar to what you designed already with the tracking w/o work order) for material and released product. Time tracking can be created upon closure. And finally Closure and costing can be automated as well using again a recurring task (FUNDTUCLO).

In a nutshell a both more configuration but on the end-user site they simply need to build an Excel Spreadsheet to define how much to produce per product / every month, so you can import this as a forecast.