Lanham EDI General Cross Reference Shipping Agents / Services

  • Lanham EDI General Cross Reference Shipping Agents / Services

    Posted by Josh Kandiko on December 29, 2016 at 3:24 pm
    • Josh Kandiko

      Member

      December 29, 2016 at 3:24 PM

      We are trying to map a partner who sends in codes for the shipping agent / agent service in one value.  For instance, they would send in FGHM and we would like that to map to FedEx Ground Home Delivery and UGM would be mapped to US POSTAL Priority. 

      Using Lanham’s E-Ship, we have set up the General Cross Reference table with the values for Shipping Agent Code and E-Ship Agent Service. 

      We map the value to Sales Header – Ship Agent Code and that pulls in correctly.  But how would I map the same value to the Ship Agent Service?  If I put two lines with the same Segment / Element, only the last one gets mapped.

      Are there recipes somewhere on how to accomplish this seemingly common task?

      ——————————
      Josh Kandiko
      Saris Cycling Group
      Madison WI
      ——————————

    • Justin Falconer

      Member

      December 30, 2016 at 8:56 AM

      Can you use a Conditional and store the value in 2 different fields?  I have not tried this with shipping agents but it should work.

      Attached is a print screen of an element we store in more then one field using conditionals

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

    • Josh Kandiko

      Member

      December 30, 2016 at 9:15 AM

      6HAMF1bJRJqLXaWIkbF8_2016_12_30_08_14_03_Edit_General_Cross_References.pngbFa7ojdySHiAXfoOYfCT_2016_12_30_08_11_45_Edit_E.D.I._Conditionals.png

      Hi Justin,

      Thanks!  That put me on the right track.  Here’s a screenshot for anyone else facing this issue.

      ——————————
      Josh Kandiko
      Saris Cycling Group
      Madison WI
      ————————————————————————-

    • Tim Lecander

      Member

      December 30, 2016 at 9:31 AM

      Hi Josh,

      It seems you’re on the right path. I’ve done something similar for a client, where when GROUNDPOBOX is sent in FOB05, there’s a General Cross Reference entry to map this to Shipping Agent USPS, Service <whatever>. Then if the keyword GROUND is sent in FOB05, this is mapped to Shipping Agent UPS, Service GROUND, etc.

      The map for FOB05 does have the conditions like Justin mentioned, mapping to the Shipping Agent and E-Ship Service respectively. Admittingly the condition doesn’t look like it does anything if it weren’t for the underlying general cross reference.

      One key thing is the Cross Reference field on the General Cross References table needs to be set to “1”. This hooks into the logic to populate the fields you want. Other General Cross Reference Types are for Payment Terms, Shipment Methods, etc.

      ——————————
      Tim Lecander
      Developer
      ArcherPoint Inc.
      Decorah IA
      ————————————————————————-

    Josh Kandiko replied 7 years, 3 months ago 1 Member · 0 Replies
  • 0 Replies

Sorry, there were no replies found.

The discussion ‘Lanham EDI General Cross Reference Shipping Agents / Services’ 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!