Why is it needed to perform a refresh of project connections

Hello Athulya,

thanks a lot for your answer, i understand now why some customer schedule such refresh periodically.

KR

This is an older response from RnD but still applies today - 

The intention of running Refresh Project Connections is to recalculate cost, revenue and hours information when there's a cost element setup change (which could usually happen during an upgrade) related to Projects in the application. This is expected to be a one-time job as changing the cost element setup, which will affect projects is not considered to be common.

Hi Jane,

thanks a lot for your answer 

KR

Is there anything that could be done to unwind it once executed? It ran manually in our environment and there are at least a few projects now where it appears to be doubling the project revenue and cost to the project. Just in the used and actual cost fields within project monitoring, not within the GL or project transactions. 

It has been like 10 years since I worked in this area, but as I remember, I could give some information. As I remember there is no way to undo the project connection refresh. However, project connections refresh it self does not double the cost or revenue as it removes the earlier project reported values and use the same logic as it was reported in the first place to fetch the most recent values. However there is a temporary table in place that captures daily transactions and a background job exists to update these temporary lines to the main tables each night (this was done to improve performance). It may be the case that the same values can now exists in both the temporary table and the main tables, which could show double values in the project screens. This should not have happened if everything went as designed but there could be an exception, like the background job is stopped or may be even a new bug introduced etc. Hope this helps you to solve the problem!

Thanks for the quick response ​@ATSI, much appreciated! 

Is there a background job that needs to run to clear out the temporary table? I can confirm that it’s not actually doubling the values in those fields, but it’s confusing to our users. We are working in 24R1 SU4 

We will hide that page to prevent it going forward, but we expected it to remove the old connections and rebuild the new connections. However, it looks like the system simply went out and added additional connections. 

Thank you! 

Hi ​@leadingzeros  You could run the Refresh Project Connections for one Project and see if this resolves the issue for that Project.  Once the Used and Actual match, the Project should be ready to be closed if needed.

Actual cost is the sum of the used costs that has been updated in General Ledger.  If Used does not match Actual, you will need to transfer Project Costs to the GL.

If after running the Refresh Connections for one Project, if you still think the values are not correct, please enter a case and we can investigate this for you.  Thanks!  Jane