Unit Cost updated from esimated shop order cost

Hi , this is the same in APPS10 too, we get this warning and usage if the estimated Cost when no unit cost is available is informed,

OK, I missed that but the question still open, is there a parameter that prevent estimated cost to be used and cost in cost set one must be set?  

Hi ​@MUNAJANSE 

You could enter this as an idea here in the community. I think it would be a small thing to implement. It would be interesting to know if other companies also are interested in this increased cost control.

Thanks for the input

-Mats

Hi Mats,

A conceptual change like this is usualy implemented with a parameter which enable the current IFS user to run the function as before. However, since the parameter exists we get a Unit Cost from first received part fetching the Est Shop Order Cost. 
When using cost calculation and copy to cost set one, you get a cost history, cost built-up analyze or and you can identify the source of the cost. 
Now when the unit cost is updated from shop order OOREC, no history exist in costing and “Zero Cost warning for included components”  or an easy way to find the source of the cost. You need to find the first OOREC for each part, find the shop order, analyze the estimated cost in detail. 
Is Non-Consumed compnents included in Estimated Cost?
 

The new way of get cost makes it easier in some business but require other precesses in the business and other ways to find information. 

From my experiance in the area, I would like to see a Cost Parameter at site level to force cost set 1 to be updated or fetch cost from estimated SO Cost. Cost Control is crusial in all companies.
Similar concept for purchase parts even if more companies use WA for purchase parts.

/Anders  
 

Our company is also looking for ways to require that a part that is identified as a Standard Cost setting, must have cost set 1 calculated before any transactions can occur.  Reading through this, I don’t believe there is one - correct? 

You are correct ​@KrisBrmml 

Actually I went back as far to Applications 9 and it is working the same there as well.

Upon Release of a shop order the user will get the info message:

“If inventory value is not set for part XYZ site 123 configuration ID * prior to receipt, then the estimated cost will be used.” (copied from Applications 9 ShopOrd.plsql file - Do_Release___ method)

Again, if you really want a “show stopper” based on a parameter setting, create an Open Idea for it, and we will see what we can do.

-Mats