GLN usage options

Options	Description
Both	Use the B usage indicator to use both vendor assigned account numbers and GLNs in the EDI transactions. With the B indicator, both the vendor assigned account numbers and GLNs are cross referenced and used in the translation. For outbound transactions (POs), if a GLN does not exist in the interface file, a GLN lookup is performed. If both account numbers and GLNs are used and available, then two N1 segments are created. One N1ST segment with the account number preceded by a 91 qualifier and an N1DA segment with the GLN preceded by a UL qualifier. `N1^ST^^91^1067A91067` `N1^DA^PO SHIP TO NAME 1067A IC02.1-X^UL^1234567890123` For inbound transactions (855, 810, etc.), if an N1 segment contains a 91 qualifier, an account number - CSF value cross reference look up is performed. If an N1 segment contains a UL qualifier and an Id hasn't already been found, then a GLN cross reference is performed.
Lookup	Use the L usage indicator to only use GLNs through data substitution cross references. With the L indicator, an attempt is made to cross reference identifiers with GLNs in the data substitution records. With the L indicator, only GLNs qualified with UL are created or processed. Vendor assigned account numbers are not created or processed. For outbound processing, the 850 transaction will only contain an N1ST segment with a UL qualifier. `N1^ST^PO SHIP TO NAME 1067A IC02.1-X^UL^1234567890123` For inbound processing, only N1 segments containing UL qualifier are used to look up Infor values. For example, an N1ST segment with a UL qualifier are used to lookup a ship to value using the GLN. This segment is not used because it does not contain a UL qualifier: `N1^ST^^91^1067A91067.` This segment is used because it does contain a UL qualifier: `N1^ST^PO SHIP TO NAME 1067A IC02.1-X^UL^1234567890123` The value "1234567890123" is used to lookup a EDI Data Substitutions record with a ship to.
Only	Use the O usage indicator to only use GLNs in transactions. With the O indicator, no cross referencing will be done. GLNs will be directly mapped between the interface files and the ASC X12 transactions. Only N1 segments with UL qualifiers are used.
None	There is a fourth option. Use an N to indicate not to use GLN's. This is useful if you have enabled GLN usage for all trading partners with an asterisk as described above and want to exclude specific trading partners.
Using GLNs with 9.0.1.4 Lawson Applications	As stated above, GLNs are available for use in the Lawson interface files. Customers meeting this requirement have the option to only use GLNs in ANSI X12 Transactions. The GLNs will need to be entered and associated with the Lawson identifiers in IC58.1 and be active. Also, the interface programs (e.g., MA531, MA540) need to have the GLN processing flag set to yes. For more information on GLN setup refer to the GTIN GLN Setup Guide available on the Lawson Knowledge base.

Both

Use the B usage indicator to use both vendor assigned account numbers and GLNs in the EDI transactions. With the B indicator, both the vendor assigned account numbers and GLNs are cross referenced and used in the translation.

For outbound transactions (POs), if a GLN does not exist in the interface file, a GLN lookup is performed. If both account numbers and GLNs are used and available, then two N1 segments are created. One N1ST segment with the account number preceded by a 91 qualifier and an N1DA segment with the GLN preceded by a UL qualifier.

N1^ST^^91^1067A91067

N1^DA^PO SHIP TO NAME 1067A IC02.1-X^UL^1234567890123

For inbound transactions (855, 810, etc.), if an N1 segment contains a 91 qualifier, an account number - CSF value cross reference look up is performed. If an N1 segment contains a UL qualifier and an Id hasn't already been found, then a GLN cross reference is performed.

Lookup

Use the L usage indicator to only use GLNs through data substitution cross references. With the L indicator, an attempt is made to cross reference identifiers with GLNs in the data substitution records. With the L indicator, only GLNs qualified with UL are created or processed. Vendor assigned account numbers are not created or processed.

For outbound processing, the 850 transaction will only contain an N1ST segment with a UL qualifier.

N1^ST^PO SHIP TO NAME 1067A IC02.1-X^UL^1234567890123

For inbound processing, only N1 segments containing UL qualifier are used to look up Infor values. For example, an N1ST segment with a UL qualifier are used to lookup a ship to value using the GLN.

This segment is not used because it does not contain a UL qualifier:

N1^ST^^91^1067A91067.

This segment is used because it does contain a UL qualifier:

N1^ST^PO SHIP TO NAME 1067A IC02.1-X^UL^1234567890123

The value "1234567890123" is used to lookup a EDI Data Substitutions record with a ship to.

Only

Use the O usage indicator to only use GLNs in transactions. With the O indicator, no cross referencing will be done. GLNs will be directly mapped between the interface files and the ASC X12 transactions. Only N1 segments with UL qualifiers are used.

None

There is a fourth option. Use an N to indicate not to use GLN's. This is useful if you have enabled GLN usage for all trading partners with an asterisk as described above and want to exclude specific trading partners.

Using GLNs with 9.0.1.4 Lawson Applications

As stated above, GLNs are available for use in the Lawson interface files. Customers meeting this requirement have the option to only use GLNs in ANSI X12 Transactions. The GLNs will need to be entered and associated with the Lawson identifiers in IC58.1 and be active. Also, the interface programs (e.g., MA531, MA540) need to have the GLN processing flag set to yes. For more information on GLN setup refer to the GTIN GLN Setup Guide available on the Lawson Knowledge base.