I have finally gotten around to doing some mapping and I have a question about TRU_ASSOCIATION_MAPPING.
I have several rows in this table that are blank in Cur Xref Type but have a value in Cur Other Xref Type.
I understand that if there is a value in Cur Xref Type and no value in Cur Other Xref Type, this represents a soft association, but what does the opposite mean?Dale
Dale,
This generally means that you have some malformed associations in the table possibly from a data conversion or something other load of associations. If you want some help you may want to put in a help ticket and include the offending rows from TRU_ASSOCIATION_MAPPING and the rows in TX_XREF for the xref types in question and we can have a look at your specific issue.
Anna
Thanks Anna,
We do indeed have a great deal of malformed data from our original conversion but I hadn't realized the extent until I opened the mapping table. We have a bunch of entries in tx_xref where the customer_no and associate_no are generally correct but the xref_no_inv numbers are all crazy.
Would you generally recommend that I just do the mapping now to the data as is and cleanup later or should I try and get this cleaned up first?Dale
Dale - these are ones where you should probably do the cleanup since there my be some affect on the migration. The choices are to try and cobble together the proper connections between the associations or if they are truly bad data then you may remove them from the table. That is going to be a bit up to you.
We've successfully converted out TEST system to v11 and while our inital mapping table did look "off" - I'm sure it was from converted data (we converted in January of 11 and now have to upgrade to 12), the issue we're having on duplicate associations is stumping me.
One pair of records I'm looking at as a reference is duplicated on each record so that customer A is associated to customer b 8 times in v11. Looking at TX_XREF, they have only two rows with matching assoc_id's and such and I'm not sure if we "over" mapped TRU_ASSOCIATION_MAPPING in zeal to get no errors on our database check or if the bad converted data is at play here. Any quick way to tell?
Followup question - is there a way to "wipe" the TRU_ASSOCIATION_MAPPING table and repopulate it via code now that we know what we're doing better so we can remap from the beginning?