Skip to main content
Question

Unit Cost updated from esimated shop order cost

  • November 20, 2024
  • 6 replies
  • 113 views

Forum|alt.badge.img+5

Hi All, 

When using the inventory cost setting; Standard Cost, Cost per Part, Zero Cost Forbidden
In previous releases of IFS, you was forced to calculate cost and copy to cost set one, before receipt of the part as inventory value zero was not allowed. The calculation of cost and set standard cost is a fundamental concept for many companies. 

We are now running IFS Cloud 23R2 and notice that you are not forced to calculate and set standard cost anymore, is that a new parameter implemented to get old logic to be used?
I have read release notes from App 10 and later but haven’t found anything related to this issue.

 
To set Unit Cost based on estimated shop order cost when first received is not accepted by all controlers.

Forum|alt.badge.img+10
  • Hero (Employee)
  • November 20, 2024

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,

 


Forum|alt.badge.img+5
  • Do Gooder (Customer)
  • November 21, 2024

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?  


Forum|alt.badge.img+14
  • Hero (Employee)
  • November 21, 2024

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


Forum|alt.badge.img+5
  • Do Gooder (Customer)
  • November 21, 2024

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  
 


Forum|alt.badge.img+4
  • Do Gooder (Customer)
  • February 11, 2025

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? 


Forum|alt.badge.img+14
  • Hero (Employee)
  • February 13, 2025

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


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings