Dear all,
Does anyone know in which scenarios it is necessary to perform a refresh of project connections? I have a customer who occasionally experiences issues that are resolved with such a refresh, but this occurs very rarely. What I’d like to know is what can cause disturbances in project connections that require this kind of refresh to prevent issues.
Thanks for your help.
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
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.