Skip to main content

We are currently using IFS 10/UPD 18.

 

We currently have all parts setup as average cost/cost per part. 

 

We also use the project system for shop order processing.

 

Our issue is that due to IFS cascading cost revaluation entries, projects we have closed completely, from the project itself to the financial project, are being created. These are due to average costing changes. We understand the cause.

 

The problem is that outside of the fact we do not want a project to be touched after it is closed, these same transactions become posting errors because the project is closed. The only way to get them to post is to open up the financial project, open up the project and open up the activity. 

 

Outside of turning on lot/batch control/changing the project after it is completed, to non-capitalization, does anyone have a superior solution?

 

Thanks,

Rich

 

@rsczerowski we are on the same Apps10 upd 18 as you and have the same issue. Did you get any feedback from IFS? We have a customization that reopens projects, processes these transactions and then closes the projects which is not ideal, and we would like to not have these transactions created in the first place.

 

How are you handling this in your environment.

Hello ​@rsczerowski ​@PIINKADAM 

Did you receive any feedback from IFS?

 

Regards.

No. The last I heard is that there are no plans to address the issue (8 months ago?). The only “fixes” I know of is to use lot batch or serial costing for manufactured parts. Even then, it doesn’t fix the entire problem if the raw materials are also on average cost as cascading entries can result. This is especially an issue when old unvouchered purchase order amounts are matched on parts that are used on numerous shop orders and projects. So each of these steps can mitigate the issue, but not 100% solve it.

As ​@PIINKADAM noted above, some customers have had customizations done to address the transactions that are created. But our ideal fix as well would be that these simply are not created, for a part attached to a closed project. 

We currently though are manually fixing every month. 

Some months we have 100s of these transactions.

 

 

 

Reply


Terms & ConditionsCookie settings