SQL Synchronization Errors

I was facing some AX synchronization issues this week for my R2 instance which had Projects module license configuration off. Below are the errors that were generated during the sync from AOT.

ProjJournalTransHourUnpostedView	Error	Synchronize database Specified field Qty of datasource ProjJournalTrans does not exist in the database or the configuration key on the field or on Extended Data Type used by the field is off. The view ProjJournalTransHourUnpostedView can not be created in the database.
ProjTransBudgetCube	Error	Synchronize database Specified field StatementPLHourCost of datasource ProjParameters_1 does not exist in the database or the configuration key on the field or on Extended Data Type used by the field is off. The view ProjTransBudgetCube can not be created in the database.
ProjTransBudgetCube	Error	Synchronize database Specified field StatementConsumpHourCost of datasource ProjParameters_1 does not exist in the database or the configuration key on the field or on Extended Data Type used by the field is off. The view ProjTransBudgetCube can not be created in the database.
ProjTransPostingCube	Error	Synchronize database Specified field StatementPLHourCost of datasource ProjParameters_1 does not exist in the database or the configuration key on the field or on Extended Data Type used by the field is off. The view ProjTransPostingCube can not be created in the database.
ProjTransPostingCube	Error	Synchronize database Specified field StatementConsumpHourCost of datasource ProjParameters_1 does not exist in the database or the configuration key on the field or on Extended Data Type used by the field is off. The view ProjTransPostingCube can not be created in the database.

All the errors are pertaining to the views created in the backend for the Projects module. Did the usual checks for the ProjJournalTrans.Qty field and the related EDT config settings, but still the errors were not resolved. Also explored turning on/off for each of the nodes in Configurations form to check if the error can be removed and direct queries to the SQLDictionary table. Then checked in the AX forums and came to know that this is a known issue in Dynamics AX 2012 R2, and can be safely ignored as AX checks the Project module configurations for these views. However there is no data loss due to these views hence this issue is not quite serious.

The original explanations can be found under these links at support forum.

https://community.dynamics.com/ax/f/33/p/70070/127960.aspx