title: ODI Why not show Unique Key as option for incremental or merge (why PK only)?
body: <p>When doing a mapping in ODI, when we are going to perform an incremental load it gives me the option to only use Primary Key (PK), but we use the PK in the table's unique identifier columns (the sequences - ID_COLUMN).</p>
  <p>And for the unique keys we use the fields that will be used as keys for the table to insert or update the data.</p>
  <p>That is, using PK in ODI would be wrong, because it is a sequential column. Is it possible to use the Unique Key? Because ODI does not offer this option.</p>