Inbound usage
This section provides examples of EDI GLN processing using these sample EDI segments:
N1^ST^^91^768593013
N1^DA^8801^UL^7601000939109
N1^BT^^UL^7601000939100
N1^VN^^UL^3333333333333
No GLN
For standard functionality using vendor assigned account numbers, we need these ED40 records:
| List Name | GS_I_COMPANY |
| Lawson Value | 1067 |
| External Value | 768593013 |
| List Name | GS_I_VENDOR |
| Lawson Value | 9 |
| External Value | 768593013 |
Without using GLNs, only an N1ST segment with a N103= "91" or "92" would be processed. The GLNs would not be used.
After translation, the Lawson interface file (for example, MA540CSV), would only contain:
| company | 1067 |
| vendor | 9 |
GLN Usage = B
If GLN usage is set to Both, both account number lookup and GLN lookup can occur.
| List Name | L1_I_USE_GLN |
| Lawson Value | GS |
| External Value | B |
After adding the L1_I_USE_GLN record with "B", and the L1_COMPANY_GLN and L1_VENDOR_GLN records above, the Lawson interface file (for example, MA540CSV), would contain this data:
| Company | 1067 |
| Vendor | 9 |
| company_gln | 7601000939100 |
| vendor_gln | 3333333333333 |
| shipto_gln | 7601000939109 |
GLN Usage = L
Changing the L1_I_USE_GLN record to "L" and adding the GLN records for COMPANY an VENDOR
| List Name | L1_I_USE_GLN |
| Lawson Value | GS |
| External Value | L |
| List Name | L1_COMPANY_GLN |
| Lawson Value | 1067 |
| External Value | 7601000939100 |
| List Name | L1_VENDOR_GLN |
| Lawson Value | 9 |
| External Value | 3333333333333 |
After translation, the Lawson interface file (for example, MA540CSV), would contain these values. Note that with USE_GLN set to "L", no GLNs are available, only the Lawson id values.
| company | 1067 |
| vendor | 9 |
GLN Usage = O
If GLN Usage is set to "O", only GLNs are directly mapped to the interface files. No account number or GLN lookup is performed to get the Lawson id values.
| company_gln | 7601000939100 |
| vendor_gln | 3333333333333 |
| shipto_gln | 7601000939109 |