I was using the PSTL vendor combine tool last week and it was unable to perform the expected task because of a Violation of Duplicate Key issue. Turns out there were four tables in this series that had 'both' of the vendors I wanted to combine and the PSTL tool could not do that.
But, after asking Leslie and Richard, and doing a reasonable amount of searching on Google and PartnerSource I had to give up on finding out what application was utilizing those tables.
So I'm reaching out to the community to see if anyone knows about the AMS tables in these queries.
select * from AMS00100 where vendorid in ('18153','10637') 17 rwos – only vendor 18153
select * from AMS00200 where vendorid in ('18153','10637') 45 rows mix of both vendors
select * from AMS10100 where vendorid in ('18153','10637') 2 distince rows - Nothing in them only NoteINDX
select * from AMS10200 where vendorid in ('18153','10637') 138 rows mix of both vendors
select * from AMS20100 where vendorid in ('18153','10637') 92 records but NO VendorID records
select * from AMS20200 where vendorid in ('18153','10637') 1275 records but NO VendorID records
select * from AMS20200 where vendorid in ('18153','10637') 1275 records but NO VendorID records
select * from AMS30100 where vendorid in ('18153','10637') 2341 records but NO VendorID records
select * from AMS30200 where vendorid in ('18153','10637') 0 records but NO VendorID records
select * from AMS70100 where vendorid in ('18153','10637') 0 records but NO VendorID records
select * from AMS70100 where vendorid in ('18153','10637') 0 records but NO VendorID records
select * from AMS70200 where vendorid in ('18153','10637') 0 records but NO VendorID records
Thank you,
Mike Lupro