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

Dynamics AX 2012 Retail Demo VM 3 - POS users list

A quick and a handy reference for the Dynamics AX 2012 Retail POS users list, avoiding time consuming search in the application for the different demo stores, users and access profiles. Please note this list is applicable only for Dynamics AX 2012 R2 Demo VM version 3.0. The default password for the users is 123

Seattle (AW)

000150 - Sales associate

000154 - Store manager

000165 - Sales associate

000175 – Non-drawer

New York (AW)

000152 - Sales associate

000156 - Store manager

000159 - Sales associate

000179 – Non-drawer

Boston (Electronics)

000100 - Store manager

000110 - Sales associate

000111 - Sales associate

000120 – Non-drawer

Paris (AW)

000221 – Store manager

000222 – Sales associate

000229 – Sales associate

000225 – Non-drawer

Houston (Fabrikam)

000160 – Store manager

000161 – Sales associate

000164 – Sales associate

000168 – Non-drawer