Vendor Cards being created mysteriously

(0) Share

Report

Posted on by Community Member

We have some Vendor IDs that are being created somehow. The have all Xs for the data (like you would see when printing an alignment form). The first record that showed up was vendor ID "XXXXXXXXXXXXXXX", then another showed up with "XXXXXXXXXXXXXXY". It continues to grow at a slow pace replacing the final X with a Y. They are all marked Inactive. We use FastPath Audit Trail and oddly enough, the users that are reflected as having added the records do not have Security access to Vendor Cards. I have seen similar behavior with Purchase Orders too.

*This post is locked for comments

I have the same question (0)

All responses (6)

Answers (0)

Sort by

George_YYC 175 on at

Like (0)

Report
Copy link

Link copied!

Is there any pattern when the vendor card was created? For example, if it happens every Wednesday, and your check run is on Wednesday, you might be able to use that as a start..

Was this reply helpful? Yes No
Tim Wappat 5,715 on at

Like (1)

Report
Copy link

Link copied!

I agree with George, and I'd be setting up a SQL job to check every min for new ones and send an email so that you can "ask around" what everyone was doing immediately that it happened.

Need to narrow it down to an operation in the system and a notification helps enormously to find the pattern.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report
Copy link

Link copied!

Following this thread. I've seen the XXXXXXXXXXXXXX PO number before and couldn't figure it out either.

Was this reply helpful? Yes No
Suggested answer

KirkLivermont 5,985 on at

Like (1)

Report
Copy link

Link copied!

Jeff and Michael,

I once asked Victoria Yudin why one of her SOP Views excluded these records. The answer is probably the same in your environment. Her response is below.

Regards,

Kirk

Kirk Livermont Reply February 25, 2015 at 12:44 pm

Thank you so much Victoria. This will work great for us.

In looking at your original view I am puzzled why this piece is necessary.

AND SD.ITEMNMBR not like ‘XXXXXXXXXXXXXXX%’

I tested it without this section and didn’t have any unexpected results. Care to enlighten me?

Thanks again,

Kirk

Victoria Yudin Reply February 25, 2015 at 2:32 pm

Hi Kirk,

Good catch! Sometimes when alignment forms are printed in GP and not correctly cleared out, you get transactions in the system with X’s for all the fields. It does not happen often, but I have one customer that I’ve done a lot of reporting for that has these, so I got used to putting that clause in my code. I don’t think it would hurt anything for most companies to take that out.:-)

-Victoria

victoriayudin.com/.../sql-view-for-rolling-12-months-of-sales-by-item-in-dynamics-gp

Was this reply helpful? Yes No
Suggested answer

Bryan R on at

Like (0)

Report
Copy link

Link copied!

We had the same issue and use FastPath Audit Trails, so it was somewhat of a stumper for us, but with the suggestion of alignment forms is how we found it and replicated it. When in PO Entry, select the Print option, then alignment form - the VENDORID = XXXXXXXXXXXXXXX is created and once the print view is closed the VENDORID = XXXXXXXXXXXXXXX is deleted.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report
Copy link

Link copied!

Thanks Bryan -

I am sure you are correct concerning alignment forms. I cannot figure out why the XXXXXXXXXXXX vendor is SOMETIMES NOT deleted. At least you have pointed me in the right direction. I appreciate it!

Was this reply helpful? Yes No