X12 816 Organizational Relationships

X12 Release 4010

This Draft Standard for Trial Use contains the format and establishes the data contents of the Organizational Relationships Transaction Set (816) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set can be used to transmit pertinent information about a parent organization, its members and the relationship of a member to another member, and/or to the parent organization. A parent organization could be an association, a multi-hospital system, a chain of retail stores, a holding company, etc.

This transaction set can be used to convey the identity and relationship of members to a parent organization; identify eligibility to purchase under the terms and conditions negotiated by a parent organization on behalf of its members; and to update application databases.

Delimiters

• ~ Segment
• * Element
• > Component

ISA Interchange Control Header

Required · Max use 1

To start and identify an interchange of zero or more functional groups and interchange-related control segments

ISA-01 · I01 · Authorization Information Qualifier · Required · Identifier (ID)

Code to identify the type of information in the Authorization Information

• 00: No Authorization Information Present (No Meaningful Information in I02)

ISA-02 · I02 · Authorization Information · Required · String (AN) · Min 10 Max 10

Information used for additional identification or authorization of the interchange sender or the data in the interchange; the type of information is set by the Authorization Information Qualifier (I01)

ISA-03 · I03 · Security Information Qualifier · Required · Identifier (ID)

Code to identify the type of information in the Security Information

• 00: No Security Information Present (No Meaningful Information in I04)

ISA-04 · I04 · Security Information · Required · String (AN) · Min 10 Max 10

This is used for identifying the security information about the interchange sender or the data in the interchange; the type of information is set by the Security Information Qualifier (I03)

ISA-05 · I05 · Interchange ID Qualifier · Required · Identifier (ID) · Min 2 Max 2

Qualifier to designate the system/method of code structure used to designate the sender or receiver ID element being qualified

Codes

• 01: Duns (Dun & Bradstreet)
• 02: SCAC (Standard Carrier Alpha Code)
• 03: FMC (Federal Maritime Commission)
• 04: IATA (International Air Transport Association)
• 08: UCC EDI Communications ID (Comm ID)
• 09: X.121 (CCITT)
• 10: Department of Defense (DoD) Activity Address Code
• 11: DEA (Drug Enforcement Administration)
• 12: Phone (Telephone Companies)
• 13: UCS Code (The UCS Code is a Code Used for UCS Transmissions; it includes the Area Code and Telephone Number of a Modem; it Does Not Include Punctuation, Blanks or Access Code)
• 14: Duns Plus Suffix
• 15: Petroleum Accountants Society of Canada Company Code
• 16: Duns Number With 4-Character Suffix
• 17: American Bankers Association (ABA) Transit Routing Number (Including Check Digit, 9 Digit)
• 18: Association of American Railroads (AAR) Standard Distribution Code
• 19: EDI Council of Australia (EDICA) Communications ID Number (COMM ID)
• 20: Health Industry Number (HIN)
• 21: Integrated Postsecondary Education Data System, or (IPEDS)
• 22: Federal Interagency Commission on Education, or FICE
• 23: National Center for Education Statistics Common Core of Data 12-Digit Number for Pre-K-Grade 12 Institutes, or NCES
• 24: The College Board's Admission Testing Program 4-Digit Code of Postsecondary Institutes, or ATP
• 25: American College Testing Program 4-Digit Code of Postsecondary Institutions, or ACT
• 26: Statistics of Canada List of Postsecondary Institutions
• 27: Carrier Identification Number as assigned by Health Care Financing Administration (HCFA)
• 28: Fiscal Intermediary Identification Number as assigned by Health Care Financing Administration (HCFA)
• 29: Medicare Provider and Supplier Identification Number as assigned by Health Care Financing Administration (HCFA)
• 30: U.S. Federal Tax Identification Number
• 31: Jurisdiction Identification Number Plus 4 as assigned by the International Association of Industrial Accident Boards and Commissions (IAIABC)
• 32: U.S. Federal Employer Identification Number (FEIN)
• 33: National Association of Insurance Commissioners Company Code (NAIC)
• 34: Medicaid Provider and Supplier Identification Number as assigned by individual State Medicaid Agencies in conjunction with Health Care Financing Administration (HCFA)
• 35: Statistics Canada Canadian College Student Information System Institution Codes
• 36: Statistics Canada University Student Information System Institution Codes
• 37: Society of Property Information Compilers and Analysts
• AM: Association Mexicana del Codigo de Producto (AMECOP) Communication ID
• NR: National Retail Merchants Association (NRMA) - Assigned
• SN: Standard Address Number
• ZZ: Mutually Defined

ISA-06 · I06 · Interchange Sender ID · Required · String (AN) · Min 15 Max 15

Identification code published by the sender for other parties to use as the receiver ID to route data to them; the sender always codes this value in the sender ID element

ISA-07 · I05 · Interchange ID Qualifier · Required · Identifier (ID) · Min 2 Max 2

Qualifier to designate the system/method of code structure used to designate the sender or receiver ID element being qualified

Codes

• 01: Duns (Dun & Bradstreet)
• 02: SCAC (Standard Carrier Alpha Code)
• 03: FMC (Federal Maritime Commission)
• 04: IATA (International Air Transport Association)
• 08: UCC EDI Communications ID (Comm ID)
• 09: X.121 (CCITT)
• 10: Department of Defense (DoD) Activity Address Code
• 11: DEA (Drug Enforcement Administration)
• 12: Phone (Telephone Companies)
• 13: UCS Code (The UCS Code is a Code Used for UCS Transmissions; it includes the Area Code and Telephone Number of a Modem; it Does Not Include Punctuation, Blanks or Access Code)
• 14: Duns Plus Suffix
• 15: Petroleum Accountants Society of Canada Company Code
• 16: Duns Number With 4-Character Suffix
• 17: American Bankers Association (ABA) Transit Routing Number (Including Check Digit, 9 Digit)
• 18: Association of American Railroads (AAR) Standard Distribution Code
• 19: EDI Council of Australia (EDICA) Communications ID Number (COMM ID)
• 20: Health Industry Number (HIN)
• 21: Integrated Postsecondary Education Data System, or (IPEDS)
• 22: Federal Interagency Commission on Education, or FICE
• 23: National Center for Education Statistics Common Core of Data 12-Digit Number for Pre-K-Grade 12 Institutes, or NCES
• 24: The College Board's Admission Testing Program 4-Digit Code of Postsecondary Institutes, or ATP
• 25: American College Testing Program 4-Digit Code of Postsecondary Institutions, or ACT
• 26: Statistics of Canada List of Postsecondary Institutions
• 27: Carrier Identification Number as assigned by Health Care Financing Administration (HCFA)
• 28: Fiscal Intermediary Identification Number as assigned by Health Care Financing Administration (HCFA)
• 29: Medicare Provider and Supplier Identification Number as assigned by Health Care Financing Administration (HCFA)
• 30: U.S. Federal Tax Identification Number
• 31: Jurisdiction Identification Number Plus 4 as assigned by the International Association of Industrial Accident Boards and Commissions (IAIABC)
• 32: U.S. Federal Employer Identification Number (FEIN)
• 33: National Association of Insurance Commissioners Company Code (NAIC)
• 34: Medicaid Provider and Supplier Identification Number as assigned by individual State Medicaid Agencies in conjunction with Health Care Financing Administration (HCFA)
• 35: Statistics Canada Canadian College Student Information System Institution Codes
• 36: Statistics Canada University Student Information System Institution Codes
• 37: Society of Property Information Compilers and Analysts
• AM: Association Mexicana del Codigo de Producto (AMECOP) Communication ID
• NR: National Retail Merchants Association (NRMA) - Assigned
• SN: Standard Address Number
• ZZ: Mutually Defined

ISA-08 · I07 · Interchange Receiver ID · Required · String (AN) · Min 15 Max 15

Identification code published by the receiver of the data; When sending, it is used by the sender as their sending ID, thus other parties sending to them will use this as a receiving ID to route data to them

ISA-09 · I08 · Interchange Date · Required · Date (DT) · YYMMDD format

Date of the interchange

ISA-10 · I09 · Interchange Time · Required · Time (TM) · HHMM format

Time of the interchange

ISA-11 · I10 · Interchange Control Standards Identifier · Required · Identifier (ID)

Code to identify the agency responsible for the control standard used by the message that is enclosed by the interchange header and trailer

• U: U.S. EDI Community of ASC X12, TDCC, and UCS

ISA-12 · I11 · Interchange Control Version Number · Required · Identifier (ID)

This version number covers the interchange control segments

• 00401: Draft Standards for Trial Use Approved for Publication by ASC X12 Procedures Review Board through October 1997

ISA-13 · I12 · Interchange Control Number · Required · Numeric (N0) · Min 9 Max 9

A control number assigned by the interchange sender

ISA-14 · I13 · Acknowledgment Requested · Required · Identifier (ID) · Min 1 Max 1

Code sent by the sender to request an interchange acknowledgment (TA1)

• 0: No Acknowledgment Requested
• 1: Interchange Acknowledgment Requested

ISA-15 · I14 · Usage Indicator · Required · Identifier (ID) · Min 1 Max 1

Code to indicate whether data enclosed by this interchange envelope is test, production or information

• I: Information
• P: Production Data
• T: Test Data

ISA-16 · I15 · Component Element Separator · Required · String (AN) · Min 1 Max 1

Type is not applicable; the component element separator is a delimiter and not a data element; this field provides the delimiter used to separate component data elements within a composite data structure; this value must be different than the data element separator and the segment terminator

• >: Component Element Separator

GS Functional Group Header

Required · Max use 1

To indicate the beginning of a functional group and to provide control information

GS-01 · 479 · Functional Identifier Code · Required · Identifier (ID)

Code identifying a group of application related transaction sets

• OR: Organizational Relationships (816)

GS-02 · 142 · Application Sender's Code · Required · String (AN) · Min 2 Max 15

Code identifying party sending transmission; codes agreed to by trading partners

GS-03 · 124 · Application Receiver's Code · Required · String (AN) · Min 2 Max 15

Code identifying party receiving transmission. Codes agreed to by trading partners

GS-04 · 373 · Date · Required · Date (DT) · CCYYMMDD format

Date expressed as CCYYMMDD

GS-05 · 337 · Time · Required · Time (TM) · HHMM, HHMMSS, HHMMSSD, or HHMMSSDD format

Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or HHMMSSD, or HHMMSSDD, where H = hours (00-23), M = minutes (00-59), S = integer seconds (00-59) and DD = decimal seconds; decimal seconds are expressed as follows: D = tenths (0-9) and DD = hundredths (00-99)

GS-06 · 28 · Group Control Number · Required · Numeric (N0) · Min 1 Max 9

Assigned number originated and maintained by the sender

GS-07 · 455 · Responsible Agency Code · Required · Identifier (ID) · Min 1 Max 2

Code used in conjunction with Data Element 480 to identify the issuer of the standard

• T: Transportation Data Coordinating Committee (TDCC)
• X: Accredited Standards Committee X12

GS-08 · 480 · Version / Release / Industry Identifier Code · Required · String (AN)

Code indicating the version, release, subrelease, and industry identifier of the EDI standard being used, including the GS and GE segments; if code in DE455 in GS segment is X, then in DE 480 positions 1-3 are the version number; positions 4-6 are the release and subrelease, level of the version; and positions 7-12 are the industry or trade association identifiers (optionally assigned by user); if code in DE455 in GS segment is T, then other formats are allowed

004010VICS

Heading

010 Heading > ST

ST Transaction Set Header

Required · Max use 1

To indicate the start of a transaction set and to assign a control number

ST-01 · 143 · Transaction Set Identifier Code · Required · Identifier (ID)

Code uniquely identifying a Transaction Set

• The transaction set identifier (ST01) used by the translation routines of the interchange partners to select the appropriate transaction set definition (e.g., 810 selects the Invoice Transaction Set).

• 816: Organizational Relationships

ST-02 · 329 · Transaction Set Control Number · Required · Numeric (N) · Min 4 Max 9

Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set

020 Heading > BHT

BHT Beginning of Hierarchical Transaction

Required · Max use 1

To define the business hierarchical structure of the transaction set and identify the business application purpose and reference data, i.e., number, date, and time

• BHT03 and BHT04 are mandatory.

Usage notes

The BHT02 field will only contain Change code 04 in a Location Address Structure (BHT01 = 0065).

BHT-01 · 1005 · Hierarchical Structure Code · Required · Identifier (ID)

Code indicating the hierarchical application structure of a transaction set that utilizes the HL segment to define the structure of the transaction set

• 0057: Supergroup, subgroup, member
• 0065: Company, Operating Unit

BHT-02 · 353 · Transaction Set Purpose Code · Required · Identifier (ID)

Code identifying purpose of transaction set

• 00: Original
• 04: Change

BHT-04 · 373 · Date · Required · Date (DT) · CCYYMMDD format

Date expressed as CCYYMMDD

• BHT04 is the date the transaction was created within the business application system.

N1 Loop Required Max 1

040 Heading > N1 Loop > N1

N1 Name

Required · Max use 1

To identify a party by type of organization, name, and code

• The N1 loop shall identify the transaction set issuer and optionally provide contact information if necessary.

Usage notes

At least one of N102 or N103 is required.

N1-01 · 98 · Entity Identifier Code · Required · Identifier (ID)

Code identifying an organizational entity, a physical location, property or an individual

• FR: Message From

N1-02 · 93 · Name · Required · String (AN) · Min 1 Max 60

Free-form name

Detail

HL Loop Company/Corporation Optional Max >1

Variants (all may be used)

HL Loop Supergroup

010 Detail > HL Loop Company/Corporation > HL

HL Hierarchical Level

Required · Max use 1

To identify dependencies among and the content of hierarchically related groups of data segments

HL-01 · 628 · Hierarchical ID Number · Required · String (AN) · Min 1 Max 12

A unique number assigned by the sender to identify a particular data segment in a hierarchical structure

• HL01 shall contain a unique alphanumeric number for each occurrence of the HL segment in the transaction set. For example, HL01 could be used to indicate the number of occurrences of the HL segment, in which case the value of HL01 would be "1" for the initial HL segment and would be incremented by one in each subsequent HL segment within the transaction.

HL-03 · 735 · Hierarchical Level Code · Required · Identifier (ID)

Code defining the characteristic of a level in a hierarchical structure

• HL03 indicates the context of the series of segments following the current HL segment up to the next occurrence of an HL segment in the transaction. For example, HL03 is used to indicate that subsequent segments in the HL loop form a logical grouping of data referring to shipment, order, or item-level information.

• 35: Company/Corporation

HL-04 · 736 · Hierarchical Child Code · Optional · Identifier (ID)

Code indicating if there are hierarchical child data segments subordinate to the level being described

• HL04 indicates whether or not there are subordinate (or child) HL segments related to the current HL segment.

• 0: No Subordinate HL Segment in This Hierarchical Structure.
• 1: Additional Subordinate HL Data Segment in This Hierarchical Structure.

N1 Loop Required Max 1

020 Detail > HL Loop Company/Corporation > N1 Loop > N1

N1 Name

Required · Max use 1

To identify a party by type of organization, name, and code

• N105, when used, defines the relationship of the entity designated in N102 or N104 to its parent organization.

N1-01 · 98 · Entity Identifier Code · Required · Identifier (ID)

Code identifying an organizational entity, a physical location, property or an individual

• CQ: Corporate Office

N1-02 · 93 · Name · Required · String (AN) · Min 1 Max 60

Free-form name

HL Loop Operating Unit Optional Max >1

Variants (all may be used)

HL Loop Subgroup

010 Detail > HL Loop Company/Corporation > HL Loop Operating Unit > HL

HL Hierarchical Level

Required · Max use 1

To identify dependencies among and the content of hierarchically related groups of data segments

HL-01 · 628 · Hierarchical ID Number · Required · String (AN) · Min 1 Max 12

A unique number assigned by the sender to identify a particular data segment in a hierarchical structure

• HL01 shall contain a unique alphanumeric number for each occurrence of the HL segment in the transaction set. For example, HL01 could be used to indicate the number of occurrences of the HL segment, in which case the value of HL01 would be "1" for the initial HL segment and would be incremented by one in each subsequent HL segment within the transaction.

HL-02 · 734 · Hierarchical Parent ID Number · Required · String (AN) · Min 1 Max 12

Identification number of the next higher hierarchical data segment that the data segment being described is subordinate to

• HL02 identifies the hierarchical ID number of the HL segment to which the current HL segment is subordinate.

HL-03 · 735 · Hierarchical Level Code · Required · Identifier (ID)

Code defining the characteristic of a level in a hierarchical structure

• HL03 indicates the context of the series of segments following the current HL segment up to the next occurrence of an HL segment in the transaction. For example, HL03 is used to indicate that subsequent segments in the HL loop form a logical grouping of data referring to shipment, order, or item-level information.

• 36: Operating Unit

HL-04 · 736 · Hierarchical Child Code · Optional · Identifier (ID)

Code indicating if there are hierarchical child data segments subordinate to the level being described

• HL04 indicates whether or not there are subordinate (or child) HL segments related to the current HL segment.

• 0: No Subordinate HL Segment in This Hierarchical Structure.
• 1: Additional Subordinate HL Data Segment in This Hierarchical Structure.

N1 Loop Place of Business Required Max >1

020 Detail > HL Loop Company/Corporation > HL Loop Operating Unit > N1 Loop Place of Business > N1

N1 Name

Required · Max use 1

To identify a party by type of organization, name, and code

• N105, when used, defines the relationship of the entity designated in N102 or N104 to its parent organization.

Usage notes

N102 and N106 will only be sent in a Location Address Structure (BHT01 = 0065).

If either Identification Code Qualifier (N1-03) or Identification Code (N1-04) is present, then the other is required

At least one of Name (N1-02) or Identification Code Qualifier (N1-03) is required

N1-01 · 98 · Entity Identifier Code · Required · Identifier (ID)

Code identifying an organizational entity, a physical location, property or an individual

• BU: Place of Business
• WH: Warehouse

N1-02 · 93 · Name · Optional · String (AN) · Min 1 Max 60

Free-form name

N1-03 · 66 · Identification Code Qualifier · Optional · Identifier (ID)

Code designating the system/method of code structure used for Identification Code (67)

• 93: Code assigned by the organization originating the transaction set

N1-04 · 67 · Identification Code · Optional · String (AN) · Min 2 Max 80

Code identifying a party or other code

• This segment, used alone, provides the most efficient method of providing organizational identification. To obtain this efficiency the "ID Code" (N104) must provide a key to the table maintained by the transaction processing party.

N1-06 · 98 · Entity Identifier Code · Optional · Identifier (ID)

Code identifying an organizational entity, a physical location, property or an individual

• CQ: Corporate Office
• SN: Store
• WH: Warehouse

040 Detail > HL Loop Company/Corporation > HL Loop Operating Unit > N1 Loop Place of Business > N3

N3 Address Information

Optional · Max use 2

To specify the location of the named party

Usage notes

This segment will only be sent in a Location Address Structure (BHT01 = 0065).

N3-01 · 166 · Address Information · Required · String (AN) · Min 1 Max 55

Address information

N3-02 · 166 · Address Information · Optional · String (AN) · Min 1 Max 55

Address information

050 Detail > HL Loop Company/Corporation > HL Loop Operating Unit > N1 Loop Place of Business > N4

N4 Geographic Location

Optional · Max use 1

To specify the geographic place of the named party

Usage notes

This segment will only be sent in a Location Address Structure (BHT01 = 0065).

N4-01 · 19 · City Name · Optional · String (AN) · Min 2 Max 30

Free-form text for city name

• A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.

N4-02 · 156 · State or Province Code · Optional · Identifier (ID) · Min 2 Max 2

Code (Standard State/Province) as defined by appropriate government agency

• N402 is required only if city name (N401) is in the U.S. or Canada.

N4-03 · 116 · Postal Code · Optional · Identifier (ID) · Min 3 Max 15

Code defining international postal zone code excluding punctuation and blanks (zip code for United States)

090 Detail > HL Loop Company/Corporation > HL Loop Operating Unit > N1 Loop Place of Business > DTM

DTM Date/Time Reference Closing Date

Optional · Max use 1

To specify pertinent dates and times

Variants (all may be used)

DTMDate/Time Reference EffectiveDTMDate/Time Reference Opening Date

DTM-01 · 374 · Date/Time Qualifier · Required · Identifier (ID)

Code specifying type of date or time, or both date and time

• 146: Closing Date

DTM-02 · 373 · Date · Required · Date (DT) · CCYYMMDD format

Date expressed as CCYYMMDD

090 Detail > HL Loop Company/Corporation > HL Loop Operating Unit > N1 Loop Place of Business > DTM

DTM Date/Time Reference Effective

Optional · Max use 1

To specify pertinent dates and times

Variants (all may be used)

DTMDate/Time Reference Closing DateDTMDate/Time Reference Opening Date

DTM-01 · 374 · Date/Time Qualifier · Required · Identifier (ID)

Code specifying type of date or time, or both date and time

• 007: Effective

DTM-02 · 373 · Date · Required · Date (DT) · CCYYMMDD format

Date expressed as CCYYMMDD

090 Detail > HL Loop Company/Corporation > HL Loop Operating Unit > N1 Loop Place of Business > DTM

DTM Date/Time Reference Opening Date

Optional · Max use 1

To specify pertinent dates and times

Variants (all may be used)

DTMDate/Time Reference Closing DateDTMDate/Time Reference Effective

DTM-01 · 374 · Date/Time Qualifier · Required · Identifier (ID)

Code specifying type of date or time, or both date and time

• 145: Opening Date

DTM-02 · 373 · Date · Required · Date (DT) · CCYYMMDD format

Date expressed as CCYYMMDD

100 Detail > HL Loop Company/Corporation > HL Loop Operating Unit > N1 Loop Place of Business > ASI

ASI Action or Status Indicator

Optional · Max use 1

To indicate the action to be taken with the information provided or the status of the entity described

ASI-01 · 306 · Action Code · Required · Identifier (ID)

Code indicating type of action

• 2: Change (Update)

ASI-02 · 875 · Maintenance Type Code · Required · Identifier (ID)

Code identifying the specific type of item maintenance

• 001: Change
• 002: Delete
• 021: Addition

HL Loop Member Optional Max >1

010 Detail > HL Loop Company/Corporation > HL Loop Operating Unit > HL Loop Member > HL

HL Hierarchical Level

Required · Max use 1

To identify dependencies among and the content of hierarchically related groups of data segments

HL-01 · 628 · Hierarchical ID Number · Required · String (AN) · Min 1 Max 12

A unique number assigned by the sender to identify a particular data segment in a hierarchical structure

• HL01 shall contain a unique alphanumeric number for each occurrence of the HL segment in the transaction set. For example, HL01 could be used to indicate the number of occurrences of the HL segment, in which case the value of HL01 would be "1" for the initial HL segment and would be incremented by one in each subsequent HL segment within the transaction.

HL-02 · 734 · Hierarchical Parent ID Number · Required · String (AN) · Min 1 Max 12

Identification number of the next higher hierarchical data segment that the data segment being described is subordinate to

• HL02 identifies the hierarchical ID number of the HL segment to which the current HL segment is subordinate.

HL-03 · 735 · Hierarchical Level Code · Required · Identifier (ID)

Code defining the characteristic of a level in a hierarchical structure

• HL03 indicates the context of the series of segments following the current HL segment up to the next occurrence of an HL segment in the transaction. For example, HL03 is used to indicate that subsequent segments in the HL loop form a logical grouping of data referring to shipment, order, or item-level information.

• 26: Member

HL-04 · 736 · Hierarchical Child Code · Optional · Identifier (ID)

Code indicating if there are hierarchical child data segments subordinate to the level being described

• HL04 indicates whether or not there are subordinate (or child) HL segments related to the current HL segment.

• 0: No Subordinate HL Segment in This Hierarchical Structure.

N1 Loop Required Max >1

020 Detail > HL Loop Company/Corporation > HL Loop Operating Unit > HL Loop Member > N1 Loop > N1

N1 Name

Required · Max use 1

To identify a party by type of organization, name, and code

• N105, when used, defines the relationship of the entity designated in N102 or N104 to its parent organization.

If either Identification Code Qualifier (N1-03) or Identification Code (N1-04) is present, then the other is required

At least one of Name (N1-02) or Identification Code Qualifier (N1-03) is required

N1-01 · 98 · Entity Identifier Code · Required · Identifier (ID)

Code identifying an organizational entity, a physical location, property or an individual

• SN: Store

N1-02 · 93 · Name · Optional · String (AN) · Min 1 Max 60

Free-form name

N1-03 · 66 · Identification Code Qualifier · Optional · Identifier (ID) · Min 1 Max 2

Code designating the system/method of code structure used for Identification Code (67)

N1-04 · 67 · Identification Code · Optional · String (AN) · Min 2 Max 80

Code identifying a party or other code

• This segment, used alone, provides the most efficient method of providing organizational identification. To obtain this efficiency the "ID Code" (N104) must provide a key to the table maintained by the transaction processing party.

HL Loop Subgroup Optional Max >1

Variants (all may be used)

HL Loop Operating Unit

010 Detail > HL Loop Company/Corporation > HL Loop Subgroup > HL

HL Hierarchical Level

Required · Max use 1

To identify dependencies among and the content of hierarchically related groups of data segments

HL-01 · 628 · Hierarchical ID Number · Required · String (AN) · Min 1 Max 12

A unique number assigned by the sender to identify a particular data segment in a hierarchical structure

• HL01 shall contain a unique alphanumeric number for each occurrence of the HL segment in the transaction set. For example, HL01 could be used to indicate the number of occurrences of the HL segment, in which case the value of HL01 would be "1" for the initial HL segment and would be incremented by one in each subsequent HL segment within the transaction.

HL-02 · 734 · Hierarchical Parent ID Number · Required · String (AN) · Min 1 Max 12

Identification number of the next higher hierarchical data segment that the data segment being described is subordinate to

• HL02 identifies the hierarchical ID number of the HL segment to which the current HL segment is subordinate.

HL-03 · 735 · Hierarchical Level Code · Required · Identifier (ID)

Code defining the characteristic of a level in a hierarchical structure

• HL03 indicates the context of the series of segments following the current HL segment up to the next occurrence of an HL segment in the transaction. For example, HL03 is used to indicate that subsequent segments in the HL loop form a logical grouping of data referring to shipment, order, or item-level information.

• 25: Subgroup

HL-04 · 736 · Hierarchical Child Code · Optional · Identifier (ID)

Code indicating if there are hierarchical child data segments subordinate to the level being described

• HL04 indicates whether or not there are subordinate (or child) HL segments related to the current HL segment.

• 0: No Subordinate HL Segment in This Hierarchical Structure.
• 1: Additional Subordinate HL Data Segment in This Hierarchical Structure.

N1 Loop Place of Business Required Max >1

020 Detail > HL Loop Company/Corporation > HL Loop Subgroup > N1 Loop Place of Business > N1

N1 Name

Required · Max use 1

To identify a party by type of organization, name, and code

• N105, when used, defines the relationship of the entity designated in N102 or N104 to its parent organization.

Usage notes

N102 and N106 will only be sent in a Location Address Structure (BHT01 = 0065).

If either Identification Code Qualifier (N1-03) or Identification Code (N1-04) is present, then the other is required

At least one of Name (N1-02) or Identification Code Qualifier (N1-03) is required

N1-01 · 98 · Entity Identifier Code · Required · Identifier (ID)

Code identifying an organizational entity, a physical location, property or an individual

• BU: Place of Business
• WH: Warehouse

N1-02 · 93 · Name · Optional · String (AN) · Min 1 Max 60

Free-form name

N1-03 · 66 · Identification Code Qualifier · Optional · Identifier (ID)

Code designating the system/method of code structure used for Identification Code (67)

• 93: Code assigned by the organization originating the transaction set

N1-04 · 67 · Identification Code · Optional · String (AN) · Min 2 Max 80

Code identifying a party or other code

• This segment, used alone, provides the most efficient method of providing organizational identification. To obtain this efficiency the "ID Code" (N104) must provide a key to the table maintained by the transaction processing party.

N1-06 · 98 · Entity Identifier Code · Optional · Identifier (ID)

Code identifying an organizational entity, a physical location, property or an individual

• CQ: Corporate Office
• SN: Store
• WH: Warehouse

040 Detail > HL Loop Company/Corporation > HL Loop Subgroup > N1 Loop Place of Business > N3

N3 Address Information

Optional · Max use 2

To specify the location of the named party

Usage notes

This segment will only be sent in a Location Address Structure (BHT01 = 0065).

N3-01 · 166 · Address Information · Required · String (AN) · Min 1 Max 55

Address information

N3-02 · 166 · Address Information · Optional · String (AN) · Min 1 Max 55

Address information

050 Detail > HL Loop Company/Corporation > HL Loop Subgroup > N1 Loop Place of Business > N4

N4 Geographic Location

Optional · Max use 1

To specify the geographic place of the named party

Usage notes

This segment will only be sent in a Location Address Structure (BHT01 = 0065).

N4-01 · 19 · City Name · Optional · String (AN) · Min 2 Max 30

Free-form text for city name

• A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.

N4-02 · 156 · State or Province Code · Optional · Identifier (ID) · Min 2 Max 2

Code (Standard State/Province) as defined by appropriate government agency

• N402 is required only if city name (N401) is in the U.S. or Canada.

N4-03 · 116 · Postal Code · Optional · Identifier (ID) · Min 3 Max 15

Code defining international postal zone code excluding punctuation and blanks (zip code for United States)

090 Detail > HL Loop Company/Corporation > HL Loop Subgroup > N1 Loop Place of Business > DTM

DTM Date/Time Reference Closing Date

Optional · Max use 1

To specify pertinent dates and times

Variants (all may be used)

DTMDate/Time Reference EffectiveDTMDate/Time Reference Opening Date

DTM-01 · 374 · Date/Time Qualifier · Required · Identifier (ID)

Code specifying type of date or time, or both date and time

• 146: Closing Date

DTM-02 · 373 · Date · Required · Date (DT) · CCYYMMDD format

Date expressed as CCYYMMDD

090 Detail > HL Loop Company/Corporation > HL Loop Subgroup > N1 Loop Place of Business > DTM

DTM Date/Time Reference Effective

Optional · Max use 1

To specify pertinent dates and times

Variants (all may be used)

DTMDate/Time Reference Closing DateDTMDate/Time Reference Opening Date

DTM-01 · 374 · Date/Time Qualifier · Required · Identifier (ID)

Code specifying type of date or time, or both date and time

• 007: Effective

DTM-02 · 373 · Date · Required · Date (DT) · CCYYMMDD format

Date expressed as CCYYMMDD

090 Detail > HL Loop Company/Corporation > HL Loop Subgroup > N1 Loop Place of Business > DTM

DTM Date/Time Reference Opening Date

Optional · Max use 1

To specify pertinent dates and times

Variants (all may be used)

DTMDate/Time Reference Closing DateDTMDate/Time Reference Effective

DTM-01 · 374 · Date/Time Qualifier · Required · Identifier (ID)

Code specifying type of date or time, or both date and time

• 145: Opening Date

DTM-02 · 373 · Date · Required · Date (DT) · CCYYMMDD format

Date expressed as CCYYMMDD

100 Detail > HL Loop Company/Corporation > HL Loop Subgroup > N1 Loop Place of Business > ASI

ASI Action or Status Indicator

Optional · Max use 1

To indicate the action to be taken with the information provided or the status of the entity described

ASI-01 · 306 · Action Code · Required · Identifier (ID)

Code indicating type of action

• 2: Change (Update)

ASI-02 · 875 · Maintenance Type Code · Required · Identifier (ID)

Code identifying the specific type of item maintenance

• 001: Change
• 002: Delete
• 021: Addition

HL Loop Member Optional Max >1

010 Detail > HL Loop Company/Corporation > HL Loop Subgroup > HL Loop Member > HL

HL Hierarchical Level

Required · Max use 1

To identify dependencies among and the content of hierarchically related groups of data segments

HL-01 · 628 · Hierarchical ID Number · Required · String (AN) · Min 1 Max 12

A unique number assigned by the sender to identify a particular data segment in a hierarchical structure

• HL01 shall contain a unique alphanumeric number for each occurrence of the HL segment in the transaction set. For example, HL01 could be used to indicate the number of occurrences of the HL segment, in which case the value of HL01 would be "1" for the initial HL segment and would be incremented by one in each subsequent HL segment within the transaction.

HL-02 · 734 · Hierarchical Parent ID Number · Required · String (AN) · Min 1 Max 12

Identification number of the next higher hierarchical data segment that the data segment being described is subordinate to

• HL02 identifies the hierarchical ID number of the HL segment to which the current HL segment is subordinate.

HL-03 · 735 · Hierarchical Level Code · Required · Identifier (ID)

Code defining the characteristic of a level in a hierarchical structure

• HL03 indicates the context of the series of segments following the current HL segment up to the next occurrence of an HL segment in the transaction. For example, HL03 is used to indicate that subsequent segments in the HL loop form a logical grouping of data referring to shipment, order, or item-level information.

• 26: Member

HL-04 · 736 · Hierarchical Child Code · Optional · Identifier (ID)

Code indicating if there are hierarchical child data segments subordinate to the level being described

• HL04 indicates whether or not there are subordinate (or child) HL segments related to the current HL segment.

• 0: No Subordinate HL Segment in This Hierarchical Structure.

N1 Loop Required Max >1

020 Detail > HL Loop Company/Corporation > HL Loop Subgroup > HL Loop Member > N1 Loop > N1

N1 Name

Required · Max use 1

To identify a party by type of organization, name, and code

• N105, when used, defines the relationship of the entity designated in N102 or N104 to its parent organization.

If either Identification Code Qualifier (N1-03) or Identification Code (N1-04) is present, then the other is required

At least one of Name (N1-02) or Identification Code Qualifier (N1-03) is required

N1-01 · 98 · Entity Identifier Code · Required · Identifier (ID)

Code identifying an organizational entity, a physical location, property or an individual

• SN: Store

N1-02 · 93 · Name · Optional · String (AN) · Min 1 Max 60

Free-form name

N1-03 · 66 · Identification Code Qualifier · Optional · Identifier (ID)

Code designating the system/method of code structure used for Identification Code (67)

• 93: Code assigned by the organization originating the transaction set

N1-04 · 67 · Identification Code · Optional · String (AN) · Min 2 Max 80

Code identifying a party or other code

• This segment, used alone, provides the most efficient method of providing organizational identification. To obtain this efficiency the "ID Code" (N104) must provide a key to the table maintained by the transaction processing party.

HL Loop Supergroup Optional Max >1

Variants (all may be used)

HL Loop Company/Corporation

010 Detail > HL Loop Supergroup > HL

HL Hierarchical Level

Required · Max use 1

To identify dependencies among and the content of hierarchically related groups of data segments

HL-01 · 628 · Hierarchical ID Number · Required · String (AN) · Min 1 Max 12

A unique number assigned by the sender to identify a particular data segment in a hierarchical structure

• HL01 shall contain a unique alphanumeric number for each occurrence of the HL segment in the transaction set. For example, HL01 could be used to indicate the number of occurrences of the HL segment, in which case the value of HL01 would be "1" for the initial HL segment and would be incremented by one in each subsequent HL segment within the transaction.

HL-03 · 735 · Hierarchical Level Code · Required · Identifier (ID)

Code defining the characteristic of a level in a hierarchical structure

• HL03 indicates the context of the series of segments following the current HL segment up to the next occurrence of an HL segment in the transaction. For example, HL03 is used to indicate that subsequent segments in the HL loop form a logical grouping of data referring to shipment, order, or item-level information.

• 24: Supergroup

HL-04 · 736 · Hierarchical Child Code · Optional · Identifier (ID)

Code indicating if there are hierarchical child data segments subordinate to the level being described

• HL04 indicates whether or not there are subordinate (or child) HL segments related to the current HL segment.

• 0: No Subordinate HL Segment in This Hierarchical Structure.
• 1: Additional Subordinate HL Data Segment in This Hierarchical Structure.

N1 Loop Required Max 1

020 Detail > HL Loop Supergroup > N1 Loop > N1

N1 Name

Required · Max use 1

To identify a party by type of organization, name, and code

• N105, when used, defines the relationship of the entity designated in N102 or N104 to its parent organization.

N1-01 · 98 · Entity Identifier Code · Required · Identifier (ID)

Code identifying an organizational entity, a physical location, property or an individual

• CQ: Corporate Office

N1-02 · 93 · Name · Required · String (AN) · Min 1 Max 60

Free-form name

HL Loop Operating Unit Optional Max >1

Variants (all may be used)

HL Loop Subgroup

010 Detail > HL Loop Supergroup > HL Loop Operating Unit > HL

HL Hierarchical Level

Required · Max use 1

To identify dependencies among and the content of hierarchically related groups of data segments

HL-01 · 628 · Hierarchical ID Number · Required · String (AN) · Min 1 Max 12

A unique number assigned by the sender to identify a particular data segment in a hierarchical structure

• HL01 shall contain a unique alphanumeric number for each occurrence of the HL segment in the transaction set. For example, HL01 could be used to indicate the number of occurrences of the HL segment, in which case the value of HL01 would be "1" for the initial HL segment and would be incremented by one in each subsequent HL segment within the transaction.

HL-02 · 734 · Hierarchical Parent ID Number · Required · String (AN) · Min 1 Max 12

Identification number of the next higher hierarchical data segment that the data segment being described is subordinate to

• HL02 identifies the hierarchical ID number of the HL segment to which the current HL segment is subordinate.

HL-03 · 735 · Hierarchical Level Code · Required · Identifier (ID)

Code defining the characteristic of a level in a hierarchical structure

• HL03 indicates the context of the series of segments following the current HL segment up to the next occurrence of an HL segment in the transaction. For example, HL03 is used to indicate that subsequent segments in the HL loop form a logical grouping of data referring to shipment, order, or item-level information.

• 36: Operating Unit

HL-04 · 736 · Hierarchical Child Code · Optional · Identifier (ID)

Code indicating if there are hierarchical child data segments subordinate to the level being described

• HL04 indicates whether or not there are subordinate (or child) HL segments related to the current HL segment.

• 0: No Subordinate HL Segment in This Hierarchical Structure.
• 1: Additional Subordinate HL Data Segment in This Hierarchical Structure.

N1 Loop Place of Business Required Max >1

020 Detail > HL Loop Supergroup > HL Loop Operating Unit > N1 Loop Place of Business > N1

N1 Name

Required · Max use 1

To identify a party by type of organization, name, and code

• N105, when used, defines the relationship of the entity designated in N102 or N104 to its parent organization.

Usage notes

N102 and N106 will only be sent in a Location Address Structure (BHT01 = 0065).

If either Identification Code Qualifier (N1-03) or Identification Code (N1-04) is present, then the other is required

At least one of Name (N1-02) or Identification Code Qualifier (N1-03) is required

N1-01 · 98 · Entity Identifier Code · Required · Identifier (ID)

Code identifying an organizational entity, a physical location, property or an individual

• BU: Place of Business
• WH: Warehouse

N1-02 · 93 · Name · Optional · String (AN) · Min 1 Max 60

Free-form name

N1-03 · 66 · Identification Code Qualifier · Optional · Identifier (ID)

Code designating the system/method of code structure used for Identification Code (67)

• 93: Code assigned by the organization originating the transaction set

N1-04 · 67 · Identification Code · Optional · String (AN) · Min 2 Max 80

Code identifying a party or other code

• This segment, used alone, provides the most efficient method of providing organizational identification. To obtain this efficiency the "ID Code" (N104) must provide a key to the table maintained by the transaction processing party.

N1-06 · 98 · Entity Identifier Code · Optional · Identifier (ID)

Code identifying an organizational entity, a physical location, property or an individual

• CQ: Corporate Office
• SN: Store
• WH: Warehouse

040 Detail > HL Loop Supergroup > HL Loop Operating Unit > N1 Loop Place of Business > N3

N3 Address Information

Optional · Max use 2

To specify the location of the named party

Usage notes

This segment will only be sent in a Location Address Structure (BHT01 = 0065).

N3-01 · 166 · Address Information · Required · String (AN) · Min 1 Max 55

Address information

N3-02 · 166 · Address Information · Optional · String (AN) · Min 1 Max 55

Address information

050 Detail > HL Loop Supergroup > HL Loop Operating Unit > N1 Loop Place of Business > N4

N4 Geographic Location

Optional · Max use 1

To specify the geographic place of the named party

Usage notes

This segment will only be sent in a Location Address Structure (BHT01 = 0065).

N4-01 · 19 · City Name · Optional · String (AN) · Min 2 Max 30

Free-form text for city name

• A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.

N4-02 · 156 · State or Province Code · Optional · Identifier (ID) · Min 2 Max 2

Code (Standard State/Province) as defined by appropriate government agency

• N402 is required only if city name (N401) is in the U.S. or Canada.

N4-03 · 116 · Postal Code · Optional · Identifier (ID) · Min 3 Max 15

Code defining international postal zone code excluding punctuation and blanks (zip code for United States)

090 Detail > HL Loop Supergroup > HL Loop Operating Unit > N1 Loop Place of Business > DTM

DTM Date/Time Reference Closing Date

Optional · Max use 1

To specify pertinent dates and times

Variants (all may be used)

DTMDate/Time Reference EffectiveDTMDate/Time Reference Opening Date

DTM-01 · 374 · Date/Time Qualifier · Required · Identifier (ID)

Code specifying type of date or time, or both date and time

• 146: Closing Date

DTM-02 · 373 · Date · Required · Date (DT) · CCYYMMDD format

Date expressed as CCYYMMDD

090 Detail > HL Loop Supergroup > HL Loop Operating Unit > N1 Loop Place of Business > DTM

DTM Date/Time Reference Effective

Optional · Max use 1

To specify pertinent dates and times

Variants (all may be used)

DTMDate/Time Reference Closing DateDTMDate/Time Reference Opening Date

DTM-01 · 374 · Date/Time Qualifier · Required · Identifier (ID)

Code specifying type of date or time, or both date and time

• 007: Effective

DTM-02 · 373 · Date · Required · Date (DT) · CCYYMMDD format

Date expressed as CCYYMMDD

090 Detail > HL Loop Supergroup > HL Loop Operating Unit > N1 Loop Place of Business > DTM

DTM Date/Time Reference Opening Date

Optional · Max use 1

To specify pertinent dates and times

Variants (all may be used)

DTMDate/Time Reference Closing DateDTMDate/Time Reference Effective

DTM-01 · 374 · Date/Time Qualifier · Required · Identifier (ID)

Code specifying type of date or time, or both date and time

• 145: Opening Date

DTM-02 · 373 · Date · Required · Date (DT) · CCYYMMDD format

Date expressed as CCYYMMDD

100 Detail > HL Loop Supergroup > HL Loop Operating Unit > N1 Loop Place of Business > ASI

ASI Action or Status Indicator

Optional · Max use 1

To indicate the action to be taken with the information provided or the status of the entity described

ASI-01 · 306 · Action Code · Required · Identifier (ID)

Code indicating type of action

• 2: Change (Update)

ASI-02 · 875 · Maintenance Type Code · Required · Identifier (ID)

Code identifying the specific type of item maintenance

• 001: Change
• 002: Delete
• 021: Addition

HL Loop Member Optional Max >1

010 Detail > HL Loop Supergroup > HL Loop Operating Unit > HL Loop Member > HL

HL Hierarchical Level

Required · Max use 1

To identify dependencies among and the content of hierarchically related groups of data segments

HL-01 · 628 · Hierarchical ID Number · Required · String (AN) · Min 1 Max 12

A unique number assigned by the sender to identify a particular data segment in a hierarchical structure

• HL01 shall contain a unique alphanumeric number for each occurrence of the HL segment in the transaction set. For example, HL01 could be used to indicate the number of occurrences of the HL segment, in which case the value of HL01 would be "1" for the initial HL segment and would be incremented by one in each subsequent HL segment within the transaction.

HL-02 · 734 · Hierarchical Parent ID Number · Required · String (AN) · Min 1 Max 12

Identification number of the next higher hierarchical data segment that the data segment being described is subordinate to

• HL02 identifies the hierarchical ID number of the HL segment to which the current HL segment is subordinate.

HL-03 · 735 · Hierarchical Level Code · Required · Identifier (ID)

Code defining the characteristic of a level in a hierarchical structure

• HL03 indicates the context of the series of segments following the current HL segment up to the next occurrence of an HL segment in the transaction. For example, HL03 is used to indicate that subsequent segments in the HL loop form a logical grouping of data referring to shipment, order, or item-level information.

• 26: Member

HL-04 · 736 · Hierarchical Child Code · Optional · Identifier (ID)

Code indicating if there are hierarchical child data segments subordinate to the level being described

• HL04 indicates whether or not there are subordinate (or child) HL segments related to the current HL segment.

• 0: No Subordinate HL Segment in This Hierarchical Structure.

N1 Loop Required Max 1

020 Detail > HL Loop Supergroup > HL Loop Operating Unit > HL Loop Member > N1 Loop > N1

N1 Name

Required · Max use 1

To identify a party by type of organization, name, and code

• N105, when used, defines the relationship of the entity designated in N102 or N104 to its parent organization.

If either Identification Code Qualifier (N1-03) or Identification Code (N1-04) is present, then the other is required

At least one of Name (N1-02) or Identification Code Qualifier (N1-03) is required

N1-01 · 98 · Entity Identifier Code · Required · Identifier (ID)

Code identifying an organizational entity, a physical location, property or an individual

• SN: Store

N1-02 · 93 · Name · Optional · String (AN) · Min 1 Max 60

Free-form name

N1-03 · 66 · Identification Code Qualifier · Optional · Identifier (ID) · Min 1 Max 2

Code designating the system/method of code structure used for Identification Code (67)

N1-04 · 67 · Identification Code · Optional · String (AN) · Min 2 Max 80

Code identifying a party or other code

• This segment, used alone, provides the most efficient method of providing organizational identification. To obtain this efficiency the "ID Code" (N104) must provide a key to the table maintained by the transaction processing party.

HL Loop Subgroup Optional Max >1

Variants (all may be used)

HL Loop Operating Unit

010 Detail > HL Loop Supergroup > HL Loop Subgroup > HL

HL Hierarchical Level

Required · Max use 1

To identify dependencies among and the content of hierarchically related groups of data segments

HL-01 · 628 · Hierarchical ID Number · Required · String (AN) · Min 1 Max 12

A unique number assigned by the sender to identify a particular data segment in a hierarchical structure

• HL01 shall contain a unique alphanumeric number for each occurrence of the HL segment in the transaction set. For example, HL01 could be used to indicate the number of occurrences of the HL segment, in which case the value of HL01 would be "1" for the initial HL segment and would be incremented by one in each subsequent HL segment within the transaction.

HL-02 · 734 · Hierarchical Parent ID Number · Required · String (AN) · Min 1 Max 12

Identification number of the next higher hierarchical data segment that the data segment being described is subordinate to

• HL02 identifies the hierarchical ID number of the HL segment to which the current HL segment is subordinate.

HL-03 · 735 · Hierarchical Level Code · Required · Identifier (ID)

Code defining the characteristic of a level in a hierarchical structure

• HL03 indicates the context of the series of segments following the current HL segment up to the next occurrence of an HL segment in the transaction. For example, HL03 is used to indicate that subsequent segments in the HL loop form a logical grouping of data referring to shipment, order, or item-level information.

• 25: Subgroup

HL-04 · 736 · Hierarchical Child Code · Optional · Identifier (ID)

Code indicating if there are hierarchical child data segments subordinate to the level being described

• HL04 indicates whether or not there are subordinate (or child) HL segments related to the current HL segment.

• 0: No Subordinate HL Segment in This Hierarchical Structure.
• 1: Additional Subordinate HL Data Segment in This Hierarchical Structure.

N1 Loop Place of Business Required Max >1

020 Detail > HL Loop Supergroup > HL Loop Subgroup > N1 Loop Place of Business > N1

N1 Name

Required · Max use 1

To identify a party by type of organization, name, and code

• N105, when used, defines the relationship of the entity designated in N102 or N104 to its parent organization.

Usage notes

N102 and N106 will only be sent in a Location Address Structure (BHT01 = 0065).

If either Identification Code Qualifier (N1-03) or Identification Code (N1-04) is present, then the other is required

At least one of Name (N1-02) or Identification Code Qualifier (N1-03) is required

N1-01 · 98 · Entity Identifier Code · Required · Identifier (ID)

Code identifying an organizational entity, a physical location, property or an individual

• BU: Place of Business
• WH: Warehouse

N1-02 · 93 · Name · Optional · String (AN) · Min 1 Max 60

Free-form name

N1-03 · 66 · Identification Code Qualifier · Optional · Identifier (ID)

Code designating the system/method of code structure used for Identification Code (67)

• 93: Code assigned by the organization originating the transaction set

N1-04 · 67 · Identification Code · Optional · String (AN) · Min 2 Max 80

Code identifying a party or other code

• This segment, used alone, provides the most efficient method of providing organizational identification. To obtain this efficiency the "ID Code" (N104) must provide a key to the table maintained by the transaction processing party.

N1-06 · 98 · Entity Identifier Code · Optional · Identifier (ID)

Code identifying an organizational entity, a physical location, property or an individual

• CQ: Corporate Office
• SN: Store
• WH: Warehouse

040 Detail > HL Loop Supergroup > HL Loop Subgroup > N1 Loop Place of Business > N3

N3 Address Information

Optional · Max use 2

To specify the location of the named party

Usage notes

This segment will only be sent in a Location Address Structure (BHT01 = 0065).

N3-01 · 166 · Address Information · Required · String (AN) · Min 1 Max 55

Address information

N3-02 · 166 · Address Information · Optional · String (AN) · Min 1 Max 55

Address information

050 Detail > HL Loop Supergroup > HL Loop Subgroup > N1 Loop Place of Business > N4

N4 Geographic Location

Optional · Max use 1

To specify the geographic place of the named party

Usage notes

This segment will only be sent in a Location Address Structure (BHT01 = 0065).

N4-01 · 19 · City Name · Optional · String (AN) · Min 2 Max 30

Free-form text for city name

• A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.

N4-02 · 156 · State or Province Code · Optional · Identifier (ID) · Min 2 Max 2

Code (Standard State/Province) as defined by appropriate government agency

• N402 is required only if city name (N401) is in the U.S. or Canada.

N4-03 · 116 · Postal Code · Optional · Identifier (ID) · Min 3 Max 15

Code defining international postal zone code excluding punctuation and blanks (zip code for United States)

090 Detail > HL Loop Supergroup > HL Loop Subgroup > N1 Loop Place of Business > DTM

DTM Date/Time Reference Closing Date

Optional · Max use 1

To specify pertinent dates and times

Variants (all may be used)

DTMDate/Time Reference EffectiveDTMDate/Time Reference Opening Date

DTM-01 · 374 · Date/Time Qualifier · Required · Identifier (ID)

Code specifying type of date or time, or both date and time

• 146: Closing Date

DTM-02 · 373 · Date · Required · Date (DT) · CCYYMMDD format

Date expressed as CCYYMMDD

090 Detail > HL Loop Supergroup > HL Loop Subgroup > N1 Loop Place of Business > DTM

DTM Date/Time Reference Effective

Optional · Max use 1

To specify pertinent dates and times

Variants (all may be used)

DTMDate/Time Reference Closing DateDTMDate/Time Reference Opening Date

DTM-01 · 374 · Date/Time Qualifier · Required · Identifier (ID)

Code specifying type of date or time, or both date and time

• 007: Effective

DTM-02 · 373 · Date · Required · Date (DT) · CCYYMMDD format

Date expressed as CCYYMMDD

090 Detail > HL Loop Supergroup > HL Loop Subgroup > N1 Loop Place of Business > DTM

DTM Date/Time Reference Opening Date

Optional · Max use 1

To specify pertinent dates and times

Variants (all may be used)

DTMDate/Time Reference Closing DateDTMDate/Time Reference Effective

DTM-01 · 374 · Date/Time Qualifier · Required · Identifier (ID)

Code specifying type of date or time, or both date and time

• 145: Opening Date

DTM-02 · 373 · Date · Required · Date (DT) · CCYYMMDD format

Date expressed as CCYYMMDD

100 Detail > HL Loop Supergroup > HL Loop Subgroup > N1 Loop Place of Business > ASI

ASI Action or Status Indicator

Optional · Max use 1

To indicate the action to be taken with the information provided or the status of the entity described

ASI-01 · 306 · Action Code · Required · Identifier (ID)

Code indicating type of action

• 2: Change (Update)

ASI-02 · 875 · Maintenance Type Code · Required · Identifier (ID)

Code identifying the specific type of item maintenance

• 001: Change
• 002: Delete
• 021: Addition

HL Loop Member Optional Max >1

010 Detail > HL Loop Supergroup > HL Loop Subgroup > HL Loop Member > HL

HL Hierarchical Level

Required · Max use 1

To identify dependencies among and the content of hierarchically related groups of data segments

HL-01 · 628 · Hierarchical ID Number · Required · String (AN) · Min 1 Max 12

A unique number assigned by the sender to identify a particular data segment in a hierarchical structure

• HL01 shall contain a unique alphanumeric number for each occurrence of the HL segment in the transaction set. For example, HL01 could be used to indicate the number of occurrences of the HL segment, in which case the value of HL01 would be "1" for the initial HL segment and would be incremented by one in each subsequent HL segment within the transaction.

HL-02 · 734 · Hierarchical Parent ID Number · Required · String (AN) · Min 1 Max 12

Identification number of the next higher hierarchical data segment that the data segment being described is subordinate to

• HL02 identifies the hierarchical ID number of the HL segment to which the current HL segment is subordinate.

HL-03 · 735 · Hierarchical Level Code · Required · Identifier (ID)

Code defining the characteristic of a level in a hierarchical structure

• HL03 indicates the context of the series of segments following the current HL segment up to the next occurrence of an HL segment in the transaction. For example, HL03 is used to indicate that subsequent segments in the HL loop form a logical grouping of data referring to shipment, order, or item-level information.

• 26: Member

HL-04 · 736 · Hierarchical Child Code · Optional · Identifier (ID)

Code indicating if there are hierarchical child data segments subordinate to the level being described

• HL04 indicates whether or not there are subordinate (or child) HL segments related to the current HL segment.

• 0: No Subordinate HL Segment in This Hierarchical Structure.

N1 Loop Optional Max >1

020 Detail > HL Loop Supergroup > HL Loop Subgroup > HL Loop Member > N1 Loop > N1

N1 Name

Required · Max use 1

To identify a party by type of organization, name, and code

• N105, when used, defines the relationship of the entity designated in N102 or N104 to its parent organization.

If either Identification Code Qualifier (N1-03) or Identification Code (N1-04) is present, then the other is required

At least one of Name (N1-02) or Identification Code Qualifier (N1-03) is required

N1-01 · 98 · Entity Identifier Code · Required · Identifier (ID)

Code identifying an organizational entity, a physical location, property or an individual

• SN: Store

N1-02 · 93 · Name · Optional · String (AN) · Min 1 Max 60

Free-form name

N1-03 · 66 · Identification Code Qualifier · Optional · Identifier (ID)

Code designating the system/method of code structure used for Identification Code (67)

• 93: Code assigned by the organization originating the transaction set

N1-04 · 67 · Identification Code · Optional · String (AN) · Min 2 Max 80

Code identifying a party or other code

• This segment, used alone, provides the most efficient method of providing organizational identification. To obtain this efficiency the "ID Code" (N104) must provide a key to the table maintained by the transaction processing party.

110 Detail > SE

SE Transaction Set Trailer

Required · Max use 1

To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)

SE-01 · 96 · Number of Included Segments · Required · Numeric (N0) · Min 1 Max 10

Total number of segments included in a transaction set including ST and SE segments

SE-02 · 329 · Transaction Set Control Number · Required · Numeric (N) · Min 4 Max 9

Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set

GE Functional Group Trailer

Required · Max use 1

To indicate the end of a functional group and to provide control information

GE-01 · 97 · Number of Transaction Sets Included · Required · Numeric (N0) · Min 1 Max 6

Total number of transaction sets included in the functional group or interchange (transmission) group terminated by the trailer containing this data element

GE-02 · 28 · Group Control Number · Required · Numeric (N0) · Min 1 Max 9

Assigned number originated and maintained by the sender

IEA Interchange Control Trailer

Required · Max use 1

To define the end of an interchange of zero or more functional groups and interchange-related control segments

IEA-01 · I16 · Number of Included Functional Groups · Required · Numeric (N0) · Min 1 Max 5

A count of the number of functional groups included in an interchange

IEA-02 · I12 · Interchange Control Number · Required · Numeric (N0) · Min 9 Max 9

A control number assigned by the interchange sender

EDI Samples

Location Address Structure Example – Change file

ISA*00*          *00*.         *12*14147844480    *12*1111111111     *180719*1000*U*00401*600000001*0*P*>
GS*OR*14147844480*1111111111*20180719*1000*600000001*X*004010VICS
ST*816*000010001
BHT*0065*04**20180710
N1*FR*KOHLS DEPARTMENT STORE
HL*1**35
N1*CQ*KOHLS DEPARTMENT STORE
HL*2*1*36
N1*BU*GRAFTON*93*01199**SN
N3*1953 WISCONSIN AVE.
N4*GRAFTON*WI*53024
DTM*146*20180801
ASI*2*001
HL*3*1*36
N1*BU*RHINELANDER*93*01199**SN
N3*NWC OF US RTE. 8*(LINCOLN ST.) & DRISCOLL
N4*RHINELANDER*WI*54501
DTM*145*20180929
ASI*2*021
SE*18*000010001
GE*1*600000001
IEA*1*600000001

Location Address Structure Example – Original (Complete file)

ISA*00*.         *00*          *12*14147844480    *12*1111111111     *180719*1000*U*00401*600000001*0*P*>
GS*OR*14147844480*1111111111*20180719*1000*600000001*X*004010VICS
ST*816*000010001
BHT*0065*00**20180719
N1*FR*KOHLS DEPARTMENT STORE
HL*1**35
N1*CQ*KOHLS DEPARTMENT STORE
HL*2*1*36
N1*BU*MACOMB*93*00007**SN
N3*32100 BEACONSFIELD
N4*ROSEVILLE*MI*48066
HL*3*1*36
N1*BU*OAKLAND SQUARE*93*00008**SN
N3*500 JOHN R. ROAD
N4*TROY*MI*48083
HL*4*1*36
N1*BU*VALLEY RANCH*93*00410**SN
N3*1035 MARKET PLACE
N4*IRVING*TX*75063
DTM*146*20180922
HL*5*1*36
N1*BU*VALLEY RANCH*93*01233**SN
N3*RANCHVIEW DRIVE &*MACARTHUR BLVD.
N4*DALLAS*TX*75063
DTM*145*20180923
SE*24*000010001
GE*1*600000001
IEA*1*600000001

Location Relationship Structure Example – All Stores Associated to All DC’s

ISA*00*          *00*          *12*14147844480    *12*1111111111     *180719*1000*U*00401*600000001*0*P*>
GS*OR*14147844480*1111111111*20180719*1000*600000001*X*004010VICS
ST*816*000010001
BHT*0057*00**20180710
N1*FR*KOHLS DEPARTMENT STORE
HL*1**24
N1*CQ*KOHLS DEPARTMENT STORE
HL*2*1*25
N1*WH**93*00810
HL*3*2*26
N1*SN**93*00001
N1*SN**93*00002
N1*SN**93*00003
HL*4*1*25
N1*WH**93*00830
HL*5*4*26
N1*SN**93*00004
N1*SN**93*00005
N1*SN**93*00006
HL*6*1*25
N1*WH**93*00810
DTM*007*20180715
HL*7*6*26
N1*SN**93*00001
N1*SN**93*00002
N1*SN**93*00003
N1*SN**93*00004
HL*8*1*25
N1*WH**93*00830
DTM*007*20180715
HL*9*8*26
N1*SN**93*00005
N1*SN**93*00006
SE*32*000010001
GE*1*600000001
IEA*1*600000001