Lanham PO Acknowledgment (EDI 855) Question

  • Lanham PO Acknowledgment (EDI 855) Question

    Posted by Lewis Rosenberg on May 7, 2020 at 4:58 pm
    • Lewis Rosenberg

      Member

      May 7, 2020 at 4:58 PM

      Is it possible to send a PO Acknowledgment (EDI 855) AFTER an order has been shipped and invoiced?

      Is it possible to prevent a sales order from being either released or shipped if a PO Acknowledgement hasĀ not been sent?

      ——————————
      Lewis Rosenberg
      IT Manager
      Mars Fishcare
      Chalfont PA
      http://www.apifishcare.com
      ————————————————————————
      BCUG/NAVUG All-Star
      BCUG/NAVUG Board of Advisors, Chairperson
      BCUG/NAVUG Programming Committee

      Twitter: @RosenbergL
      LinkedIn: https://www.linkedin.com/in/rosenbergl
      ————————————————————————

      NAVUG/D365BC-User Group Focus
      May 18-19, 2019
      Denver, Colorado
      ——————————

    • Charlotte Kinney

      Member

      May 8, 2020 at 11:06 AM

      Lanham EDI offers two different types of Advanced PO Acks (855s) based on licensing; Standard 855 and Advanced 855.Ā  By way of the question being asked, I am assuming this is the Advanced 855 setup using the “Navision Document” = E_ADVPOA.Ā  That being the case, it is possible to send the 855 after the sales order has been posted (Ship/Invoice) BUT as far as the data being present, that depends on how it was mapped.Ā  What I mean by this, is if the 855 mapping is pulling data from the Sales Header and Sales Lines, that data is no longer present and the E.D.I. Send Document would be created but have “Data Error” = TRUE since there is blank mandatory data and thereby not exported.Ā  So might want to revisit the mapping.Ā  Perhaps some of the mapping is pulling from Sales Header/Lines that may be pulled from Order Status Header/Lines instead.
      Another suggestion or tip, since the return of the 855 might be under deadline, is to automate the Adv 855 to be sent shortly after Sale Order creation.Ā  The 855 would reflect “IA” (item accepted) for all items for the 1st time it is sent (assuming this set as the “Default” E.D.I. Status Code).Ā  Then when the CSR has time to review the Adv PO Ack page at a later time, they may make edits the Status Codes and re-send a 2nd 855 when complete.Ā  If this option will work for Mars and their Trade Partners, the setup would be to enable the “Create Adv PO Ack on Receipt” = TRUE (this was probably already enabled) and “Auto Release Order Status” = TRUE on the E.D.I. Template page for the inbound 850 document.Ā  Then setup the EDI-enabled Job Queue to run the E.D.I. Job RoutineĀ SENDADVPOACK in a timely manner.
      Hope this helps you out Lewis!

      ——————————
      Charlotte Martinez
      Sr. EDI Specialist
      Lanham Associates
      ——————————
      ——————————————-

    • Wing Mak

      Member

      June 10, 2020 at 5:17 PM

      We face the same issue as BAK03, BAK04 & PO101 are not available in the Order Status Header/Line. I would like to know if we can enforce 855 sent before releasing orders.

      For the time being, I just had to remind order process personnel to send the 855 before posting the sales invoices.

      ——————————
      Wing Mak
      Director of IT
      City of Industry CA
      ——————————
      ——————————————-

    • Charlotte Kinney

      Member

      June 12, 2020 at 4:56 PM

      Hi Wing!
      Outside of automating the sending of the 855 upon Sales Order creation as described in my reply to Lewis, there is not functionality that ensures the Purchase Order Ack. has been sent prior to Sales Order Release.Ā  I have added this request to our “EDI Requested” list that the EDI product developer reviews when it’s time to work on future releases.Ā  In the meantime, perhaps this might be an option as well…

      From the 855, these are the definitions of the fields listed above with issue:
      BAK-03 = Customer PO #
      BAK-04 = Document Date
      PO1-01 = Assigned Line No.
      ?
      In the mapping of the 850, create the following Conditionals:
      ~BEG-03 (Customer PO #) additional conditional mapped to the “E.D.I. Receive Doc. Hdr. Info.” ‘Text_Field_1’
      ~BEG-05 (Document Date)Ā additional conditional mapped to the “E.D.I. Receive Doc. Hdr. Info.” ‘Date_Field_2’
      ~PO1-01 (Assigned Line No.)Ā additional conditional mapped to the “E.D.I. Receive Doc. Line Info.” ‘Text_Field_1’

      In the mapping of the 855, map the following Elements:
      ~BAK-03 (Customer PO #) mapped from the “E.D.I. Receive Doc. Hdr. Info.” ‘Text_Field_1’
      ~BAK-04 (Document Date) mapped from the “E.D.I. Receive Doc. Hdr. Info.” ‘Date_Field_2’
      ~PO1-01 (Assigned Line No.) mapped from the “E.D.I. Receive Doc. Line Info.” ‘Text_Field_1’

      Try that and see if it works for you.Ā  Let us know if you have any other questions.

      ——————————
      Charlotte Martinez
      Sr. EDI Specialist
      Lanham Associates
      ——————————
      ——————————————-

    • Lewis Rosenberg

      Member

      June 19, 2020 at 4:19 PM

      Thanks to Charlotte I now have my EDI Advanced PO Acknowledgements (EDI855) auto-creating and sending!

      ——————————
      Lewis Rosenberg
      IT Manager
      Mars Fishcare
      Chalfont PA
      http://www.apifishcare.com
      ————————————————————————
      BCUG/NAVUG All-Star
      BCUG/NAVUG Board of Advisors, Chairperson
      BCUG/NAVUG Programming Committee

      Twitter: @RosenbergL
      LinkedIn: https://www.linkedin.com/in/rosenbergl
      ————————————————————————

      NAVUG/D365BC-Community Summit: https://na.usergroupsummit.com/home
      October 6-9, 2020
      Nashville, TN
      ——————————
      ——————————————-

    Lewis Rosenberg replied 5 years, 4 months ago 1 Member · 0 Replies
  • 0 Replies

Sorry, there were no replies found.

The discussion ‘Lanham PO Acknowledgment (EDI 855) Question’ 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!