when source contains surrogate key instead of natural key

How to design dimension and facts when my source system table itself contains surrogate key (i mean auto generated id).......

for example:
EMP {
id PK
name
salary
designation
}

id is autogenerated sequence....... my dimension will contain this id as surrogate key but no natural key ...is it right?
if it is right then i cannot create key map table for my dimension

A natural key is what the business uses to identify an entity. If the business is using this auto-generated number as the employee ID, then that is the natural key. It doesn't matter where the value comes from. Assign a surrogate key as you would with any natural key.

ngalemmo wrote:A natural key is what the business uses to identify an entity. If the business is using this auto-generated number as the employee ID, then that is the natural key. It doesn't matter where the value comes from. Assign a surrogate key as you would with any natural key.

Thank You so much