Hello, 

The project connection refresh will collect the cost elements, costs, hours and revenues again and updates to the project. So, if this makes a change it would mean that there are some changes happened from the moment the transactions originally happened and now. I am not exactly sure the reasons, but it may be due to cost elements mapping changes, erroneous transactions that were corrected later on, a fail in the background job that update from projects costs from a temporary table to the main table (this is how the performance improvements are handled related to project cost updates) etc.

Earlier on (before Apps10) the project connection refresh was introduced to be run after an upgrade to update project costs. But this was changed later on, due to large upgrade times it required to refresh all project connections. However, the functionality was kept and added various filter so that it is possible to refresh a limited number of project connections if needed.

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