856 - Advance shipment notice

This topic describes the Electronic Data Interchange (EDI) standards that Business Transaction Intelligence implements for document type 856, or advance shipment notice, which includes information about the shipment of a buyer's purchases, such as shipment contents and estimated delivery time.

Segment: BSN - Beginning segment for shipment notice

Loop

Level: Heading

Usage: Must use

Semantic notes:

  • BSN01 must be equal to 00.
  • BSN02 is the unique shipment ID.
  • BSN03 is the date on which a transaction is created.
  • BSN04 is the time at which a transaction is created.
Reference Element name Requirement Usage
BSN01 Transaction Set Purpose Code Mandatory Must use
BSN02 Shipment Identification Mandatory Must use
BSN03 Date Mandatory Must use
BSN04 Time Mandatory Must use

Segment: DTM - Date/time reference

Loop

Level: Heading

Usage: Optional - Used

Syntax note:

  • DTM02 is required if DTM01 is specified.

Semantic note:

  • If DTM01 is 011, DTM02 is the ship date, DTM03 is the ship time, and DTM04 is the time zone that is associated with the ship time.
Reference Element name Requirement Usage
DTM01 Date / Time Qualifier Mandatory Must use
DTM02 Date Optional Used
DTM03 Time Optional Used
DTM04 Time Code Optional Used

Segment: HL - Hierarchical level

Loop: HL

Level: Detail

Usage: Must use

Semantic notes:

  • HL01 is the unique number for each occurrence of the HL segment.
  • HL02 identifies the hierarchical ID number of the HL segment. If this field is specified, it is the parent HL instance of the current HL segment.
  • HL03 indicates the context of the series of segments that follow the current HL segment up to the next occurrence of an HL segment in the transaction. For example, shipment, order, item-level.
Reference Element name Requirement Usage
HL01 Hierarchical ID Number Mandatory Must use
HL02 Hierarchical Parent ID Number Optional Used
HL03 Hierarchical Level Code Mandatory Must use

Segment: LIN - Item identification

Loop: HL

Level: Detail

Usage: Optional - Used

Syntax notes:

  • If LIN02 is specified, LIN03 is required.
  • If LIN04 is specified, LIN05 is required.
  • If LIN06 is specified, LIN07 is required.
  • If LIN08 is specified, LIN09 is required.
  • If LIN10 is specified, LIN11 is required.
  • If LIN12 is specified, LIN13 is required.
  • If LIN14 is specified, LIN15 is required.
  • If LIN16 is specified, LIN17 is required.
  • If LIN18 is specified, LIN19 is required.
  • If LIN20 is specified, LIN21 is required.
  • If LIN22 is specified, LIN23 is required.
  • If LIN24 is specified, LIN25 is required.
  • If LIN26 is specified, LIN27 is required.
  • If LIN28 is specified, LIN29 is required.
  • If LIN30 is specified, LIN31 is required.

Semantic notes:

  • The first UPC qualifier that is found in this list is used. The following product/service ID qualifiers are UPC-related :
    • U2 - UPC/EAN shipping container code (1-2-5-5-1)
    • UA - UPC/EAN case code (2-5-5)
    • UD - UPC/EAN consumer package code (2-5-5)
    • UI - UPC consumer package code (1-5-5)
    • UK - GTIN (14 digits) - UPC/EAN shipping container code (1-2-5-5-1)
    • UP - UPC consumer package code (1-5-5-1)
    • UN - UPC/EAN Case Code Number (1-1-5-5)
  • Seller/supplier qualifiers are preferred over buyer qualifiers. The first seller/supplier qualifier that is found (MG-VP) in the list is used. If a seller/supplier qualifier is not found, the first found buyer qualifier is used. The following product number or ID-related product/service ID qualifiers are seller or buyer-related:
    • MG - the part number of the manufacturer
    • PI - the item code of the purchaser
    • SK - stock keeping unit
    • VC - the catalog number of the vendor (seller)
    • VN - the item number of the vendor (seller)
    • VP - the part number of the vendor (seller)
    • BP - the part number of the buyer
    • CB - the catalog number of the buyer
    • IN - the item number of the buyer
Reference Element name Requirement Usage
LIN01 Assigned Identification Optional Not used
LIN02 Product/Service ID Qualifier Optional Used
LIN03 Product/Service ID Optional Must use
LIN04 Product/Service ID Qualifier Optional Used
LIN05 Product/Service ID Optional Used
LIN06 Product/Service ID Qualifier Optional Used
LIN07 Product/Service ID Optional Not used
LIN08 Product/Service ID Qualifier Optional Not used
LIN09 Product/Service ID Optional Used
LIN10 Product/Service ID Qualifier Optional Used
LIN11 Product/Service ID Optional Used
LIN12 Product/Service ID Qualifier Optional Used
LIN13 Product/Service ID Optional Used
LIN14 Product/Service ID Qualifier Optional Used
LIN15 Product/Service ID Optional Used
LIN16 Product/Service ID Qualifier Optional Used
LIN17 Product/Service ID Optional Used
LIN18 Product/Service ID Qualifier Optional Used
LIN19 Product/Service ID Optional Used
LIN20 Product/Service ID Qualifier Optional Used
LIN21 Product/Service ID Optional Used
LIN22 Product/Service ID Qualifier Optional Used
LIN23 Product/Service ID Optional Used
LIN24 Product/Service ID Qualifier Optional Used
LIN25 Product/Service ID Optional Used
LIN26 Product/Service ID Qualifier Optional Used
LIN27 Product/Service ID Optional Used
LIN28 Product/Service ID Qualifier Optional Used
LIN29 Product/Service ID Optional Used
LIN30 Product/Service ID Qualifier Optional Used
LIN31 Product/Service ID Optional Used

Segment: SN1 - Item detail (shipment)

Loop: HL

Level: Detail

Usage: Optional - Must use

Syntax note:

  • SN101 is required in order for the shipment line to link back to the purchase order line item.

Semantic note:

  • SN101 is the line number that matches the line number on the original purchase order.
Reference Element name Requirement Usage
SN101 Assigned Identification Optional Must use
SN102 Number of Units Shipped Mandatory Must use
SN103 Unit of Measure Mandatory Must use

Segment: SLN - Subline item detail

Loop: HL

Level: Detail

Usage: Optional - Used

Syntax notes:

  • If SLN09 is specified, SLN10 is required.
  • If SLN11 is specified, SLN12 is required.
  • If SLN13 is specified, SLN14 is required.
  • If SLN15 is specified, SLN16 is required.
  • If SLN17 is specified, SLN18 is required.
  • If SLN19 is specified, SLN20 is required.
  • If SLN21 is specified, SLN22 is required.
  • If SLN23 is specified, SLN24 is required.
  • If SLN25 is specified, SLN26 is required.
  • If SLN27 is specified, SLN28 is required.

Semantic notes:

  • The first UPC qualifier that is found in this list is used. The following product/service ID qualifiers are UPC-related :
    • U2 - UPC/EAN shipping container code (1-2-5-5-1)
    • UA - UPC/EAN case code (2-5-5)
    • UD - UPC/EAN consumer package code (2-5-5)
    • UI - UPC consumer package code (1-5-5)
    • UK - GTIN (14 digits) - UPC/EAN shipping container code (1-2-5-5-1)
    • UP - UPC consumer package code (1-5-5-1)
    • UN - UPC/EAN Case Code Number (1-1-5-5)
  • Seller/supplier qualifiers are preferred over buyer qualifiers. The first seller/supplier qualifier that is found (MG-VP) in the list is used. If a seller/supplier qualifier is not found, the first found buyer qualifier is used. The following product number or ID-related product/service ID qualifiers are seller or buyer-related:
    • MG - the part number of the manufacturer
    • PI - the item code of the purchaser
    • SK - stock keeping unit
    • VC - the catalog number of the vendor (seller)
    • VN - the item number of the vendor (seller)
    • VP - the part number of the vendor (seller)
    • BP - the part number of the buyer
    • CB - the catalog number of the buyer
    • IN - the item number of the buyer
Reference Element name Requirement Usage
SLN01 Assigned Identification Mandatory Must use
SLN02 Assigned Identification Optional Used
SLN03 Relationship Code Mandatory Must use
SLN04 Quantity Optional Used
SLN05 Unit of Measure Optional Used
SLN06 Unit Price Optional Used
SLN07 Basis Of Unit Price Optional Not used
SLN08 Relationship Code Optional Not used
SLN09 Product/Service ID Qualifier Optional Used
SLN10 Product/Service ID Optional Used
SLN11 Product/Service ID Qualifier Optional Used
SLN12 Product/Service ID Optional Used
SLN13 Product/Service ID Qualifier Optional Used
SLN14 Product/Service ID Optional Used
SLN15 Product/Service ID Qualifier Optional Used
SLN16 Product/Service ID Optional Used
SLN17 Product/Service ID Qualifier Optional Used
SLN18 Product/Service ID Optional Used
SLN19 Product/Service ID Qualifier Optional Used
SLN20 Product/Service ID Optional Used
SLN21 Product/Service ID Qualifier Optional Used
SLN22 Product/Service ID Optional Used
SLN23 Product/Service ID Qualifier Optional Used
SLN24 Product/Service ID Optional Used
SLN25 Product/Service ID Qualifier Optional Used
SLN26 Product/Service ID Optional Used
SLN27 Product/Service ID Qualifier Optional Used
SLN28 Product/Service ID Optional Used

Segment: PRF - Purchase order reference

Loop: HL

Level: Detail

Usage: Optional - Must use

Syntax notes:

  • This segment is mandatory in order for the shipment to link to the original purchase order.
Reference Element name Requirement Usage
PRF01 Purchase Order Number Mandatory Must use

Segment: PID - Product / item description

Loop: HL

Level: Detail

Usage: Optional - Used

Semantic notes:

  • PID01 is set to Free Form (F).
  • PID05 is the description for the SN1 segment.
  • The first PID instance is used.
Reference Element name Requirement Usage
PID01 Item Description Type Mandatory Must use
PID02 Product/Process Characteristic Code Optional Not used
PID03 Agency Qualifier Code Optional Not used
PID04 Product Description Code Optional Not used
PID05 Description Optional Must use

Segment: REF - Reference identification

Loop: HL

Level: Detail

Usage: Optional - Must use

Syntax note:

  • If REF01 is set, REF02 is required.

Semantic note:

  • If REF01 is set to CN, REF02 is the pro/invoice number.
  • If REF01 is set to BM, REF02 is the bill of lading number.
  • If REF01 is set to MA, REF02 is the manifest number.
Reference Element name Requirement Usage
REF01 Reference Identification Qualifier Optional Used
REF02 Reference Identification Optional Used

Segment: N1 - Name

Loop: HL/N1

Level: Header

Usage: Optional

Syntax note:

  • This segment is only used if the N101 qualifier field is equal to Ship to (ST) or Bill to Party (BT).

Semantic notes:

  • If N101 is equal to ST, N102 is the name of the recipient.
  • If N101 is equal to BT, N102 is the name of the billing party.
Reference Element name Requirement Usage
N101 Entity Identifier Code Mandatory Must use
N102 Name Optional Used

Segment: N3 - Address information

Loop: N1

Level: Detail

Usage: Optional

Syntax notes:

  • This segment is only used if the N101 qualifier field is equal to ST or BT.

Semantic notes:

  • If N101 is equal to ST, N301 is the street address of the recipient.
  • If N101 is equal to BT, N301 is the street address of the billing party.
Reference Element name Requirement Usage
N301 Name Mandatory Must use

Segment: N4 - Geographic location

Loop: N1

Level: Detail

Usage: Optional

Syntax note:

  • This segment is only used if the N101 qualifier field is equal to ST or BT.

Semantic notes:

  • If N101 is equal to ST, N401 is the geographic location of the recipient.
  • If N101 is equal to BT, N401 is the geographic location of the billing party.
Reference Element name Requirement Usage
N401 City Name Optional Used
N402 State or Providence Code Optional Used
N403 Postal Code Optional Used
N404 Country Code Optional Used
N405 Location Qualifier Optional Used
N406 Location Identifier Optional Used

Segment: CTT - Transaction totals

Loop

Level: Summary

Usage: Optional - Used

Semantic notes:

  • CTT01 is equal to the number of HL segments in a transaction.
  • CTT02 specifies the number of items in the shipment. If CTT02 is missing, this number is calculated from all of the SN102 fields in the item level HL segments.
Reference Element name Requirement Usage
CTT01 Number of Line Items Mandatory Must use
CTT02 Hash Total Optional Used