Amazon Direct Fulfillment Case Sensitive PO #

  • Amazon Direct Fulfillment Case Sensitive PO #

    Posted by Noreen Fujita-Sacco on November 21, 2022 at 2:28 pm
    • Noreen Fujita-Sacco

      Member

      November 21, 2022 at 2:28 PM

      We’re on NAV 2018 using Lanham EDI.

      Amazon DF requires a case sensitive Purchase Order #. I can bring in case sensitive Mixed and see it in the raw file but in the External Document No field on the Sales Order and any lists, the PO # is changed to Upper. I can try mapping an EDI In as case sensitive for outbound documents. However, we have PO # validation. I’ve manually tested entering a Sales Order with a different mixed case PO# and receive the duplicate PO alert. This would also cause an issue searching for a particular PO #.

      Does anyone know how that validation is affected for EDI? That is, will it validate against the incoming raw file’s Mixed value?

      Has anyone resolved the Mixed case PO # for search or manual entry?

      Thank you!
      ?????

      ——————————
      Noreen Fujita-Sacco
      Applications Coordinator
      Coghlan’s/Gear Aid
      Bellingham WA
      360-392-2703
      noreen.fujitasacco@gearaid.com
      ——————————

    • Margaret Mextorf

      Member

      November 22, 2022 at 12:01 PM

      Hi Noreen,

      Thank you for your question! As you said, using an EDI In on the inbound mapping for the PO # will preserve the case sensitive number and the same EDI In can be mapped on the outbound document. The External Document No. field is a code field which is why the value is stored as all upper case – with the duplicate PO check mapping tool in use, it would give you the duplicate error if the same letter/number combination is used as the PO # regardless of case. I have never seen Amazon do this, however, and it would be easy to check the PO #s against each other in the rare case that it happens. If you’d prefer to turn off the duplicate PO # check, remove the “Validation Type” field = “Purchase Order No.” on the External Document No. element mapping. I hope this helps!?????

      ——————————
      Margaret Mextorf
      EDI Support Specialist
      Lanham Associates/Lanham Services
      ——————————
      ——————————————-

    • Noreen Fujita-Sacco

      Member

      November 22, 2022 at 12:14 PM

      Thank you, Margaret.

      We wouldn’t want to turn off validation. It’s good to know you’ve never seen a duplicate, though.

      ——————————
      Noreen Fujita-Sacco
      Applications Coordinator
      Coghlan’s/Gear Aid
      Bellingham WA
      360-392-2703
      noreen.fujitasacco@gearaid.com
      ——————————
      ——————————————-

    • Ruthie Moshos

      Member

      November 22, 2022 at 1:40 PM

      Hi, Noreen-

      I agree with the EDI In as a second conditional, and you could also add a third conditional to map it to Nav-E.D.I Recieve Doc Hdr Info into one of the Text Fields. You can use this to map out of if you need to print case sensitive on a UCC label or another document.

      ——————————
      Ruthie Moshos
      EDI Specialist
      Western Computer
      santa clarita CA
      ——————————
      ——————————————-

    • Noreen Fujita-Sacco

      Member

      November 22, 2022 at 5:50 PM

      Thank you, Ruthie.

      Happy Thanksgiving!

      ——————————
      Noreen Fujita-Sacco
      Applications Coordinator
      Coghlan’s/Gear Aid
      Bellingham WA
      360-392-2703
      noreen.fujitasacco@gearaid.com
      ——————————
      ——————————————-

    Noreen Fujita-Sacco replied 1 year, 5 months ago 1 Member · 0 Replies
  • 0 Replies

Sorry, there were no replies found.

The discussion ‘Amazon Direct Fulfillment Case Sensitive PO #’ is closed to new replies.

Start of Discussion
0 of 0 replies June 2018
Now

Welcome to our new site!

Here you will find a wealth of information created for people  that are on a mission to redefine business models with cloud techinologies, AI, automation, low code / no code applications, data, security & more to compete in the Acceleration Economy!