Open Forum

Expand all | Collapse all

Lanham EDI - Help needed using an EDI In field to capture and resend payment terms

Jump to Best Answer
  • 1.  Lanham EDI - Help needed using an EDI In field to capture and resend payment terms

    TOP CONTRIBUTOR
    Posted 6 days ago
    ​Hello Everyone,

    I'm working with Lanham EDI in #NAV2013R2 and I'm trying to capture the ITD12 (Payment Terms Description) from an inbound EDI 850 (PO) on an EDI In field and send it back on an EDI 855 (PO Acknowledgment).  I'll also have to do this with an EDI810 (invoice).

    Once a sales order is created, I can see the value received in the EDI In "Description" field that I mapped, but it does not get sent out on the EDI 855.

    Any ideas on what I am doing wrong?

    850 ITD12 Map:



    EDI IN- RECEIVE ELEMENTS:


    EDI855 - ITD Mapping:






    ------------------------------
    Lewis Rosenberg
    IT Manager
    Mars Fishcare
    Chalfont PA

    -----------------------------------------------

    BCUG/NAVUG All-Star
    BCUG/NAVUG Board of Advisors, Chairperson
    BCUG/NAVUG Programming Committee

    @RosenbergL
    https://www.linkedin.com/in/rosenbergl/
    ------------------------------


  • 2.  RE: Lanham EDI - Help needed using an EDI In field to capture and resend payment terms

    Posted 5 days ago

     

    Hi Lewis

     

    Do you see the EDI document number in the EDI FastTab of the NAV Order document (so it knows which EDI document has the associated EDI IN Description for that order)?

     

     

    Brad Hearn

    Liberty Grove Software

    Toronto






  • 3.  RE: Lanham EDI - Help needed using an EDI In field to capture and resend payment terms

    TOP CONTRIBUTOR
    Posted 5 days ago
    ​Hi Brad,  Thanks for responding.
    Is that the EDI tab of the sales order?

    Mine looks like this:



    ------------------------------
    Lewis Rosenberg
    IT Manager
    Mars Fishcare
    Chalfont PA

    -----------------------------------------------

    BCUG/NAVUG All-Star
    BCUG/NAVUG Board of Advisors, Chairperson
    BCUG/NAVUG Programming Committee

    @RosenbergL
    https://www.linkedin.com/in/rosenbergl/
    ------------------------------



  • 4.  RE: Lanham EDI - Help needed using an EDI In field to capture and resend payment terms
    Best Answer

    Posted 5 days ago
    ​Hi, Lewis. Do you have the EDI In - Description mapped anywhere else in the 850 document? If you are using that EDI In in another Segment and the 850 does not have data in that element, or the element is not being sent, it will blank out the previous EDI In data. You can also try mapping a second Conditional to the Navision-E.D.I. Receive Doc. Hdr. Info. table, to one of the Text Fields. This should hold the data if the EDI In is just being finicky.

    ------------------------------
    Ruthie Moshos
    EDI Specialist
    Western Computer
    Canyon Country CA
    ------------------------------



  • 5.  RE: Lanham EDI - Help needed using an EDI In field to capture and resend payment terms

    Posted 5 days ago
    Just a wild guess, but there are a lot of "Description" fields. Sometimes weird stuff happens.

    Have you tried naming the field something like "PTDescription"?  (Payment Term Description)

    Just throwing stuff at the wall......

    ------------------------------
    Ted Johnston
    IT Director
    Streicher's
    Minneapolis MN
    ------------------------------



  • 6.  RE: Lanham EDI - Help needed using an EDI In field to capture and resend payment terms

    TOP CONTRIBUTOR
    Posted 5 days ago
    ​Thanks @Ruthie Moshos and @Ted Johnston.  I will try creating a new EDI In field with a unique name and report back.


    ------------------------------
    Lewis Rosenberg
    IT Manager
    Mars Fishcare
    Chalfont PA

    -----------------------------------------------

    BCUG/NAVUG All-Star
    BCUG/NAVUG Board of Advisors, Chairperson
    BCUG/NAVUG Programming Committee

    @RosenbergL
    https://www.linkedin.com/in/rosenbergl/
    ------------------------------



  • 7.  RE: Lanham EDI - Help needed using an EDI In field to capture and resend payment terms

    TOP CONTRIBUTOR
    Posted 2 days ago
    ​Thanks @Ruthie Moshos and @Ted Johnston.  That was it!   I think from now on, I'll always create a new and unique EDI IN field for everything that requires it.
    ​​

    ------------------------------
    Lewis Rosenberg
    IT Manager
    Mars Fishcare
    Chalfont PA

    -----------------------------------------------

    BCUG/NAVUG All-Star
    BCUG/NAVUG Board of Advisors, Chairperson
    BCUG/NAVUG Programming Committee

    @RosenbergL
    https://www.linkedin.com/in/rosenbergl/
    ------------------------------



  • 8.  RE: Lanham EDI - Help needed using an EDI In field to capture and resend payment terms

    GOLD CONTRIBUTOR
    Posted 22 hours ago
    EDI IN are great for this, but Payment Terms you can also use General Cross-Ref and then on the outgoing Docs setup a Reverse Cross-Ref.

    Doing Payment terms this way allows you to Map what terms they send on the PO to the Sales Order, and if they are changed from what they sent the outgoing documents will reflect the changes.  It also makes it so the Payment Terms works if the Customer sends in a NON-EDI Order.

    ------------------------------
    Justin Falconer
    IT Manager
    Tender Corporation
    Littleton NH
    ------------------------------



  • 9.  RE: Lanham EDI - Help needed using an EDI In field to capture and resend payment terms

    Posted 2 days ago
    ​When ever I reference an EDI IN field on an out going document I try to select the corresponding EDI IN field. It seems like Lanham will create multiple fields.  Try selecting a different Description fld from your EDI IN Table.

    Another thought:
    I've experienced losing the connection to my EDI IN fields when manual changes have been made to the PO once its in Navision.  Is it possible this might be happening to your PO's?



    ------------------------------
    Louis Bustos
    Sr. Systems Analyst
    Cacique
    City of Industry CA
    ------------------------------