Error Msg: AP Vendor Address Does Not Exist

For months now we have been encountering a major problem when trying to release a PO on PO20. Patches were recommended and we applied them to our production environment last Saturday. To our dismay, the error message reared its ugly head again this week. We are not able to create the issue on demand or to find a common denominator.

The purchase order can be old (requiring a change to close it) or it can be freshly created that day. The buyer goes to 'Release' the PO, and the system pops up the message: "AP Vendor Address does not Exist". And it is random. This is happening with vendors who have been in our system a long time. Before putting in the patches, they could wait a half hour and then it would release. They are able to release them on PO22, just not from PO20.

We have tried looking at timing of jobs being run by AP, of scheduled PO jobs in our recdef. It is not always the same vendor. It is not always the same day or same time. We reached out to GSC and several webexes have been done with very strong Infor GSC techs, who really know Lawson. All to no avail.

We use MHC, EDI and Fax Integrator for processing PO's. We are on 9.0.1.10 apps and LSF9 environment.

Has anyone else out there encountered this???
Vicky

Find more posts tagged with

Comments

Legacy Contributor

We had this. I will see if our current AP folks know what it did. I want to say that from one upgrade to the next a date field appeared and for existing vendors, it didn't populate?

I don't think it was as buggy as yours though - it was consistently same vendors.

Legacy Contributor

I work on the Finance side and have not seen your issue but one thing I have seen is the APVENADDR table sometimes does not update the addresses correctly. Meaning, the current address flag "Y" does not update and is left blank, especially on remit to's. I think this happens when the address button is not used and the screen is changed. This has caused us to bomb out when looking at a vendor or it will throw reports off if you use current address.

Probably nothing but thought it wouldn't hurt to let you know.

Legacy Contributor

Our dates also did not update the same as KatVila. I am not sure if that caused us issues but the issue came from the same place.

Stace Webley

Victoria - This happens at our facility as well. We also cannot reproduce it and have not found any pattern with it. We have all of the same signs as you...old vendors, new PO's, old PO's, etc...We have found that it releases for us as well after an unknown amount of time (20 min, 30 min, ??). I have tried many things with the addresses in AP10.X and on the PO, but none of proven to fix the problem on demand. Only waiting and trying later has proven to work. This is an issue though if the PO is EDI and needs to be released.

Wichtige Lösungen in der Wissensdatenbank April 2013.pdf

Legacy Contributor

Kat: Thank you. After several months our AP supervisor did mention this, and we found that the associate entering was not entering this data. We are wondering if this field is somehow related. But this was supposedly no longer an issue, as we were told they changed their process. But I will explore that again with them.

Jason: Thank you. This is another avenue to explore and review. I really appreciate your response.

Vicky

Stace Webley

I will say that I think we have been getting less of it since our AP department started running AP109, Vendor Current Address Update. The form help says: Use Vendor Current Address Update (AP109) to update vendors with the most current address based on the effective date. The form can be run for a range of vendors and a range of dates.

Legacy Contributor

The AP109 sometimes worked for us. I don't think it fixed all addresses if the current address flag was messed up and there were no dates. My work around was actually to go in manually and add the address correctly for each vendor address that was incorrect using the button with an address. A pain but worked. Also, difficult to identify all of the problem addresses.

Legacy Contributor

Stace: I will check with our AP Supervisor to see if they are running AP109. This was very helpful. If we find a final solution I will let you know. It has been very frustrating. Yesterday, the buyer could not release PO's in PO20 no matter how long he waited. Thank goodness they release with PO22. V

dechevar

Article KB 1202279 mentions this and lists the patches that should be installed to resolve tis issue. We had the issue as well and it went away after applying the patch. We do not run AP109.

Legacy Contributor

Thanks djechevarr. I work with Vicky and I just reviewed this KB and we have higher versions of all installed. Thanks all for your input!

Copyright © 2025 Infor. All rights reserved.