Skip to main content
Solved

ETC calculation when connection resource forecast to project forecast

  • October 10, 2024
  • 2 replies
  • 58 views

Forum|alt.badge.img+4

Hi IFS-experts,

I am experience something strange when connecting a resource forecast to a project resource. On the Project Forecast the ETC value is 0 and, on the Resource Forecast the ETC value is also 0. When I make the connection between the Project Forecast and Resource Forecast the ETC value is recalculated to -99.382.

My expectation was that it would be the same as the ETC in Resource Forecast and Project Forecast. I am trying to understand how the logic is working in IFS. If someone can enlighten my knowledge about how this should be working, then I would be very glad about that.

Best answer by Johan Lagerström

Hi @EqeDenniD,

Which update level are you on? This looks similar to a bug that was corrected in Apps 10 UPD 24, where in some very specific circumstances you would end up with a negative ETC when connecting a resource forecast to a project forecast.

If you are not already on UPD 24, would it be an option to update to verify if it’s the same issue?

Hope this helps.

Kind regards,
Johan

 

 

View original
Did this topic help you find an answer to your question?

2 replies

Forum|alt.badge.img+9

Hi @EqeDenniD,

Which update level are you on? This looks similar to a bug that was corrected in Apps 10 UPD 24, where in some very specific circumstances you would end up with a negative ETC when connecting a resource forecast to a project forecast.

If you are not already on UPD 24, would it be an option to update to verify if it’s the same issue?

Hope this helps.

Kind regards,
Johan

 

 


Forum|alt.badge.img+4
  • Author
  • Do Gooder (Partner)
  • 11 replies
  • October 14, 2024

Hi @Johan Lagerström,

In the environment where the issue has been notated is on an older version.  

We are currently in the process of updating to UPD 24.

Luckily, we have a test environment currently running on UPD 24. I have taken the steps for reproducing the issue. The issue did not represent there. So I think and hope that it has been solved by updating to UPD 24.


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