By using this website, you agree to our Terms of Use (click here)
Strange one here: I have a vendor that I am trying to locate in the Vendor profile GI and cannot locate it using search feature for vendor# or portion of vendor name. The vendor has been used in Bills/Adjustments and I can open the vendor profile from a closed bill, the profile shows as active. When I try to create a new bill, the vendor is available for usage and again I can access the vendor's profile with use of the edit feature in Bill transaction screen.
Why can't I find the vendor in the GI with no filters or conditions applied when it is is obviously still in active in Acumatica?
Thank you!
Does the vendor use any special characters within it's name?
Are you searching by clicking on a column heading or searching using the search box in the upper right-hand corner?
If you are using the search box in the upper right-hand corner, make sure that the Use in Quick Search checkbox is checked on the RESULTS GRID tab of the Generic Inquiry (SM208000) screen
Solution found, though I am still not sure why the error happened in the first place.
Determined that it was related to the vendor location info. The override option was selected and that caused it to not show on the GI. Unchecking it allows it to show on GI. Acumatica shows this vendor last updated by the system rather than a staff member but I am not sure if that is related to this option.
Reviewing the Generic Inquiry tables and relations shows that an update was needed in the parent relationship to better relate location ID and updating it now allows the vendor to show in the Vendor GI even with the override option selected. The GI was not update recently except for the addition of grouping by vendor # so that only one entry will show on the GI as multiple would show based on the different locations assigned to a vendor.
As a further FYI, the vendor in question only has one location listed in the profile.
Thanks all for your input as it is much appreciated. If you have any insight into why the issue may have cropped up in the first place, I welcome it.

