Map Use of GLN And GTIN in Order-to-Cash Transactions

The use of GLN in a transaction will occur in the N1 loop. The N1 loop is used to identify organizational entities associated with the transaction. The N1 loop can be repeated to add more than one entity, and/or more than one identifier per entity. The N1 loop is comprised of the following segments:

EDI GLN

As shown, the N103 field is a data qualifier that defines the type of identifier being used in the N104 field. The data qualifier for GLN is “UL.”

GLN

To replace Non-GS1 identifiers with GLN: for each N101 entity identifier code, populate N103 with “UL” and N104 with the GLN (replacing any other identifier that may have previously been used). To implement GLN alongside Non-GS1 identifiers: repeat the loop for each N101 entity identifier code, this time populating N103 with “UL” and N104 with the GLN to add the GLN to any other identifiers that are used for that entity.

The use of GTIN in a transaction will occur in segments where the Product/Service ID Qualifier (Code List 235) is used. For example, in 850 Purchase Order:

  • In the PO106 Code List 235 Product/Service ID Qualifier, where the UK qualifier = GTIN-14 1
  • In the PO106 Code list 235 Product/Service ID Qualifier, where the UP qualifier = GTIN-12
  • Use of the UK and UP qualifiers applies to all occurrences of data element 235 Product/Service ID Qualifier in the PO1 segment.

To learn more about EDI mapping and become a certified  EDI Professional please visit our course schedule page.

Leave a Reply

Your email address will not be published.

Post Navigation