annual salary

I am currently calculating annual salary and bringing it in my salary fact. Now I have another model where annual salary is not calculated and is like an attribute of an employee. Should I still keep it in the fact to be consistent or can I have annual salary in my employee dimension?
Thank you,

If you need the calculated annual salary, then call it something different than the non-calculated salary.

Jeff Smith wrote:If you need the calculated annual salary, then call it something different than the non-calculated salary.

I think the problem is where to store it, not what to call it.

If you don't need to aggregrate the salary then I don't see why it can't be an attribute of the employee.

Correct the issue that I have is that I am not sure where to store it. If i store it in my employee dimension( conformed dimension) then I will have the same field in the dimension as well as the fact.

Most folks will create a salary band dimension to classify salaries for reporting. In rare cases, aggregate metrics can also be stored in the dimension when needed for filtering. The challenges with doing this should be self evident.