Address does not exist for AP vendor

Sort:
You are not authorized to post a reply.
Author
Messages
Louis Brockinton
Basic Member
Posts: 8
Basic Member
    We have an issue on PO20 where upon release of a PO we receive the message "Address does not exist for AP vendor". The situation is this. We create a new vendor on AP10 making sure an address is added and the purchasing department creates a PO for this new vendor as soon as it is set up in AP10. Then we receive the message listed above when trying to release the PO. The work around has been to change the Effective date under the New Address link on the AP10 screen to the prior day. However, this work around is not working all the time now. Any idea as to where to begin looking for the bug? We are an iseries client running 8.0.3.3 in Portal. Thanks.
    John Henley
    Senior Member
    Posts: 3348
    Senior Member
      Sorry you didn't get an answer to this yet....I could swear that I posted something but I guess not. When you say "The work around has been to change the Effective date..", what do you mean by "the prior day"?
      Thanks for using the LawsonGuru.com forums!
      John
      Louis Brockinton
      Basic Member
      Posts: 8
      Basic Member
        Specifically, on AP10, we have been clicking on the New Address link and changing the effective date to the day prior to what is on the AP10. So, if a vendor is created on 1/30/07 and we receive the "Address does not exist for AP vendor" message when trying to release a PO for this vendor on PO20, we go to AP10 and change the effective date of the address to the prior day (1/29/07). We thought that was a consistent work around, however, it's turning out to not be the case.
        John Henley
        Senior Member
        Posts: 3348
        Senior Member
          If it doesn't work, check the PO issue date; I think you need to add the vendor address as one day prior to the PO issue date rather than one day prior to the vendor address effective date.
          Thanks for using the LawsonGuru.com forums!
          John
          Louis Brockinton
          Basic Member
          Posts: 8
          Basic Member
            Yes. That's correct. In all the occurrences of this issue that's been the case. The effective date on AP10 is always changed to the the day prior to the PO date on PO20.
            What makes this case even stranger is that we searched our entire Lawson system for this message and get no returns. It's like the message isn't even a part of the message file.
            MaggyO
            New Member
            Posts: 1
            New Member
              Was there ever a fix found for this error?
              Lawsonnubcake
              Advanced Member
              Posts: 25
              Advanced Member

                13 years later and this issue arises for us. I too would like to know the resolve of this.

                UPDATE: After filing a ticket with Infor the resolve is that Infor stated to us they can't recreate the error and they don't know where it stems from. They offered a patch they stated works for 'some' clients. But we're not patching just to be patching. The anomoly has corrected itself because PO20 is running fine the next day for all our facilities.

                You are not authorized to post a reply.