Couple of questions about the TRU_ASSOCIATION_MAPPING process:
1) We have a number of "duplicates" in the association table, which, as I understand it, are simply the soft association versions of the "originals". But this has concerned my colleague in Development who wonders if these entries need to carry over into v11. I'm guessing they need to, but I see no facility for changing that other than to delete them from the table all together which sounds like bad DBA practice.
2) There are associations that we simply mean to inactivate and would prefer they do not carry over into v11 at all. By this, I do not mean existing associations (as in entries in TX_XREF - apparently there are none), but rather the association types (i.e. "Gave Benefits"). My colleague wondered if simply leaving the other columns NULL (cur_other_xref_type, new_assoc_type, new_other_assoc_type & new_affil_type) would keep them from porting over? I'm not even sure if that matters if there are no actual corresponding records in TX_XREF anyway.
Thoughts? Anyone else dealing with this sort of thing? Or am I just crazy? The little man that lives in my eyebrow seems to think so...
Thanks Tessiturians.