GLN (IC58/64) Upload

Rebecca,
I would recommend doing it in two steps. The first is to load the GLNs to the IC58 to create the entries and estabish the organizational structure. Once that is complete, then you can load to the appropriate IC64.x (depending on where you are connecting the GLNs within Lawson).

We do this pretty regularly and it works well. The one key is to make sure that you identify the GLN "type" in the IC64 load. It will allow you to load it as a "blank" type which can cause issues.

Just out of curiosity...
Q1. How many levels deep does your GLN heirarchy go?
Q2. To what level did you define your GLN? IC Loc? RQ Loc? Some other level?
Q3. Which supplier are you piloting with?

Good luck,
Red

Red,

Thanks for the information.


Q1. Our GLN has three levels. System, Hospital, Dock locations, but we are only using Hosital and Dock locations in Lawson. We have other entities that go up to the System that are outside our scope (other Hospitals, Physicians Groups, the University, etc) that use other systems for their purchasing.

Q2. We are defining our GLN to the IC Location that is sent through EDI in the NST field. The confusing thing for me is that we have internal delivery locations in the IC Location table also, but we are associating those through IC64 to the GLN for the dock locations where the items are shipped. Additionally, we use RQ locations for our med/surg distributor and office supply vendor to palletize orders by requesting location. We are not getting GLNs for internal locations unless they receive deliveries seperately from the dock. We have not run into any of those yet.

Q3. Cardinal, our primary med/surg distributor. We chose them mostly due their experience loading GLNs with Lawson users; although, it turns out it has all been with previous versions of Lawson (9.0.0 and earlier).

Rebecca