Best Buy
/
Motor Carrier Delivery Trailer Manifest
  • Specification
  • EDI Inspector
Import
Stedi maintains this guide based on public documentation from Best Buy. Contact Best Buy for official EDI specifications. To report any errors in this guide, please contact us.
Go to EDI Guide Catalog
Best Buy logo

X12 212 Motor Carrier Delivery Trailer Manifest

X12 Release 4030

This Draft Standard for Trial Use contains the format and establishes the data contents of the Motor Carrier Delivery Trailer Manifest Transaction Set (212) for use within the context of an Electronic Data Interchange (EDI) environment.
This transaction set can be used to allow motor carriers to provide consignees or other interested parties with the contents of a trailer, containing multiple shipments, that has been tendered for delivery. It is not to be used to provide the recipient with data relative to a full truckload shipment.

Delimiters
  • ~ Segment
  • * Element
  • > Component
  • ^ Repetition
EDI samples
    View the latest version of this implementation guide as an interactive webpage
    Powered by
    Build free EDI implementation guides at stedi.com
    Overview
    ISA
    -
    Interchange Control Header
    Max use 1
    Required
    GS
    -
    Functional Group Header
    Max use 1
    Required
    heading
    ST
    0100
    Transaction Set Header
    Max use 1
    Required
    ATA
    0200
    Beginning Segment for Motor Carrier Delivery Trailer Manifest
    Max use 1
    Required
    B2A
    0300
    Set Purpose
    Max use 1
    Required
    0100 Loop
    detail
    0200 Loop
    LX
    0100
    Assigned Number
    Max use 1
    Required
    L11
    0200
    Business Instructions and Reference Number
    Max use 10
    Required
    Ship From
    SE
    1500
    Transaction Set Trailer
    Max use 1
    Required
    GE
    -
    Functional Group Trailer
    Max use 1
    Required
    IEA
    -
    Interchange Control Trailer
    Max use 1
    Required
    ISA

    Interchange Control Header

    RequiredMax use 1

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

    Example
    ISA-01
    I01
    Authorization Information Qualifier
    Required

    Code identifying the type of information in the Authorization Information

    00
    No Authorization Information Present (No Meaningful Information in I02)
    ISA-02
    I02
    Authorization Information
    Required
    Min 10Max 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

    Code identifying the type of information in the Security Information

    00
    No Security Information Present (No Meaningful Information in I04)
    ISA-04
    I04
    Security Information
    Required
    Min 10Max 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
    Min 2Max 2

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

    Codes
    ISA-06
    I06
    Interchange Sender ID
    Required
    Min 15Max 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
    Min 2Max 2

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

    Codes
    ISA-08
    I07
    Interchange Receiver ID
    Required
    Min 15Max 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
    YYMMDD format

    Date of the interchange

    ISA-10
    I09
    Interchange Time
    Required
    HHMM format

    Time of the interchange

    ISA-11
    I65
    Repetition Separator
    Required
    Min 1Max 1

    Type is not applicable; the repetition separator is a delimiter and not a data element; this field provides the delimiter used to separate repeated occurrences of a simple data element or a composite data structure; this value must be different than the data element separator, component element separator, and the segment terminator

    ^
    Repetition Separator
    ISA-12
    I11
    Interchange Control Version Number
    Required

    Code specifying the version number of the interchange control segments

    00403
    Draft Standards for Trial Use Approved for Publication by ASC X12 Procedures Review Board through October 1999
    ISA-13
    I12
    Interchange Control Number
    Required
    Min 9Max 9

    A control number assigned by the interchange sender

    ISA-14
    I13
    Acknowledgment Requested
    Required
    Min 1Max 1

    Code indicating sender's request for an interchange acknowledgment

    0
    No Acknowledgment Requested
    1
    Interchange Acknowledgment Requested
    ISA-15
    I14
    Usage Indicator
    Required
    Min 1Max 1

    Code indicating 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
    Min 1Max 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

    Functional Group Header

    RequiredMax use 1

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

    Example
    GS-01
    479
    Functional Identifier Code
    Required

    Code identifying a group of application related transaction sets

    TM
    Motor Carrier Delivery Trailer Manifest (212)
    GS-02
    142
    Application Sender's Code
    Required
    Min 2Max 15

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

    GS-03
    124
    Application Receiver's Code
    Required
    Min 2Max 15

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

    GS-04
    373
    Date
    Required
    CCYYMMDD format

    Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year

    GS-05
    337
    Time
    Required
    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
    Min 1Max 9

    Assigned number originated and maintained by the sender

    GS-07
    455
    Responsible Agency Code
    Required
    Min 1Max 2

    Code identifying the issuer of the standard; this code is used in conjunction with Data Element 480

    T
    Transportation Data Coordinating Committee (TDCC)
    X
    Accredited Standards Committee X12
    GS-08
    480
    Version / Release / Industry Identifier Code
    Required

    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

    004030
    Draft Standards Approved for Publication by ASC X12 Procedures Review Board through October 1999

    Heading

    ST
    0100

    Transaction Set Header

    RequiredMax use 1

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

    Example
    ST-01
    143
    Transaction Set Identifier Code
    Required

    Code uniquely identifying a Transaction Set

    • The transaction set identifier (ST01) is used by the translation routines of the interchange partners to select the appropriate transaction set definition (e.g., 810 selects the Invoice Transaction Set).
    212
    Motor Carrier Delivery Trailer Manifest
    ST-02
    329
    Transaction Set Control Number
    Required
    Min 4Max 9

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

    ATA
    0200

    Beginning Segment for Motor Carrier Delivery Trailer Manifest

    RequiredMax use 1

    To transmit identifying numbers and other basic data relating to the Motor Carrier Delivery Trailer Manifest Transaction Set

    Usage notes

    Example Data: ATASCACManifestID*20100624~

    Example
    ATA-01
    140
    Standard Carrier Alpha Code
    Required
    Min 2Max 4

    Standard Carrier Alpha Code

    • ATA01 is the Standard Carrier Alpha Code (SCAC) of the carrier that is delivering the trailer.
    Usage notes

    This should contain the NMFTA registered SCAC code of the carrier who is ultimately responsible for the load and will be billing the customer for the shipment.

    ATA-02
    127
    Reference Identification
    Required
    Min 1Max 50

    Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier

    • ATA02 is the delivery trailer manifest number assigned by the carrier.
    Usage notes

    This element should contain the Delivery Trailer Manifest ID that has been assigned by the carrier.

    ATA-03
    373
    Date
    Required
    CCYYMMDD format

    Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year

    • ATA03 is the date that the delivery trailer manifest was created.
    Usage notes

    This element should contain the date the carrier created the manifest.

    B2A
    0300

    Set Purpose

    RequiredMax use 1

    To allow for positive identification of transaction set purpose

    Usage notes

    A Replace Manifest/05 that is current and complete, should be sent if freight is added or removed from the trailer after the original manifest has been transmitted to Best Buy. The original manifest ID must be used when the replace manifest is sent.

    A Manifest should be cancelled only if the trailer will no longer be arriving at Best Buy for any reason. The original Manifest ID must be transmitted in the document.

    Example Data: B2A*00~

    Example
    B2A-01
    353
    Transaction Set Purpose Code
    Required

    Code identifying purpose of transaction set

    00
    Original
    01
    Cancellation
    05
    Replace
    0100 Loop
    RequiredMax >1
    Usage notes

    This Loop should contain the information for the Best Buy location that the carrier is attempting to deliver the trailer to.

    N1
    0500

    Name

    RequiredMax use 1

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

    • Loop 0100 provides the location where the carrier will deliver the trailer.
    Usage notes

    This segment should contain the information for the Best Buy location that the carrier is attempting to deliver the trailer to.

    Example Data: N1STBest Buy RDC709470~

    Example
    N1-01
    98
    Entity Identifier Code
    Required

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

    Usage notes

    This element should always have the qualifier of "ST" used in it to indicate that this is a Ship To Location ID.

    ST
    Ship To
    N1-02
    93
    Name
    Optional
    Min 1Max 60

    Free-form name

    N1-03
    66
    Identification Code Qualifier
    Required

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

    94
    Code assigned by the organization that is the ultimate destination of the transaction set
    N1-04
    67
    Identification Code
    Required
    Min 2Max 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.
    Usage notes

    This element should contain the Unique Location ID that Best Buy has assigned to the location that the carrier is attempting to deliver the trailer to.

    0150 Loop
    RequiredMax >1
    Usage notes

    There should only be one iteration of the Shipment Status Details Loop/150. It should contain information about the entire delivery, including carrier and trailer information.

    AT7
    1200

    Shipment Status Details

    RequiredMax use 1

    To specify the status of a shipment, the reason for that status, the date and time of the status and the date and time of any appointments scheduled.

    • The AT7 segment provides the status of all of the shipments on the trailer.
    Usage notes

    This segment should contain the date and time that the items listed in the manifest are ready to be delivered.

    Example Data: AT7AVNS**201006241000*LT~

    Example
    AT7-01
    1650
    Shipment Status Code
    Required

    Code indicating the status of a shipment

    • If AT701 is present, AT705 is the date the status occurred. If AT703 is present, AT705 is a date related to an appointment.
    • If AT701 is present, AT706 is the time of the status. If AT703 is present, AT706 is the time of the appointment.
    Usage notes

    This status code should always be "AV" to indicate that the trailer is Available for Delivery.

    AV
    Available for Delivery
    AT7-02
    1651
    Shipment Status or Appointment Reason Code
    Required

    Code indicating the reason a shipment status or appointment reason was transmitted

    NS
    Normal Status
    AT7-05
    373
    Date
    Required
    CCYYMMDD format

    Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year

    Usage notes

    The date that the event indicated in the AT701 & AT702, occurred should be sent here.

    AT7-06
    337
    Time
    Required
    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)

    Usage notes

    The time that the event indicated in the AT701 & AT702 , occurred should be sent here.

    AT7-07
    623
    Time Code
    Required

    Code identifying the time. In accordance with International Standards Organization standard 8601, time can be specified by a + or - and an indication in hours in relation to Universal Time Coordinate (UTC) time; since + is a restricted character, + and - are substituted by P and M in the codes that follow

    • If AT707 is not present then AT706 represents local time of the status.
    Usage notes

    The time zone code that the event indicated in the AT701 & AT702, occurred should be sent here. Best Buy expects this to be "LT".

    LT
    Local Time
    0160 Loop
    RequiredMax >1
    Usage notes

    There should be only one iteration of the Equipment or Container and Type Loop/160. It should contain information about the trailer and seal numbers.

    MS2
    1500

    Equipment or Container Owner and Type

    RequiredMax use 1

    To specify the owner, the identification number assigned by that owner, and the type of equipment

    Usage notes

    Example Data: MS2SCAC9876544321*TL~

    Example
    MS2-01
    140
    Standard Carrier Alpha Code
    Required
    Min 2Max 4

    Standard Carrier Alpha Code

    Usage notes

    This field must contain the NMFTA registered SCAC of the carrier who is physically moving the shipment(s) and owns the trailer.

    MS2-02
    207
    Equipment Number
    Required
    Min 1Max 10

    Sequencing or serial part of an equipment unit's identifying number (pure numeric form for equipment number is preferred)

    Usage notes

    This field must contain the actual ID of the trailer or container that contains the shipment(s) that are being moved.

    MS2-03
    40
    Equipment Description Code
    Optional
    Min 2Max 2

    Code identifying type of equipment used for shipment

    • MS203 identifies the type for the equipment specified in MS202.
    Usage notes

    This field should contain the qualifier that best describes the physical trailer or container length and type attributes.

    M7
    1600

    Seal Numbers

    OptionalMax use 1

    To record seal numbers used and the organization that applied the seals

    Usage notes

    Any known seal number given to the carrier by the shipper should be listed here and the parties identified who applied the seal. If the seal is broken by another party such as Customs (DOT), the new seal ID should be sent on an update with "CM" qualifier (if it was Customs) sent in the M705.

    Example Data: M7Seal1***CM~

    Example
    M7-01
    225
    Seal Number
    Required
    Min 2Max 15

    Unique number on seal used to close a shipment

    M7-05
    98
    Entity Identifier Code
    Optional
    Min 2Max 3

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

    • M705 indicates the name of the organization which applied the seal(s).

    Detail

    0200 Loop
    RequiredMax >1
    Usage notes

    Each iteration of Loop 200 should contain information about a single LTL shipment that a single shipper is shipping to the Best Buy location identified in Loop 100, segment N1 of the header. The details of each individual order within the LTL shipment should be contained in Loop 210 and the details of the shipper of each order should be contained in Loop 220.

    LX
    0100

    Assigned Number

    RequiredMax use 1

    To reference a line number in a transaction set

    • Loop 0200 provides the specific details concerning all of the shipments included in the manifest. There will be one iteration of loop 0200 for each shipment contained in the manifest. The most common way to identify the shipments is by the PRO number assigned by the carrier.
    Usage notes

    Example Data: LX*1~

    Example
    LX-01
    554
    Assigned Number
    Required
    Min 1Max 6

    Number assigned for differentiation within a transaction set

    Usage notes

    This is the sequential number assigned for differentiation of each iteration of the LX/200 Loop. It should start with 1 and be incremented by 1 for each iteration.

    L11
    0200

    Business Instructions and Reference Number

    RequiredMax use 10

    To specify instructions in this business relationship or a reference number

    Usage notes

    There must be at least 2 iterations of the L11 segment in each LX loop. One must contain the Bill of lading and the other must contain the carrier PRO/Load/Tracking ID.

    In cases where Best Buy is paying for the freight charges a third iteration of the L11 must be present as well. This third iteration must contain the Best Buy TMS load ID/Carrier Move Number. (The Best Buy TMS Load ID may also be referred to as the CID (Unique Consignee ID) or SID (Unique Shipper ID) from VICS).

    Example Data:
    Typical L11 where Best Buy is not paying the freight charges for a particular shipment.
    L11BOLID12345BM~ - indicates the Bill of Lading ID
    L11CarrierPROID123CN~ - indicates the Carrier PRO/Load/Tracking ID

    Typical L11 where Best Buy is paying the freight charges for a particular shipment.
    L11BOLID54321BM~ - indicates the Bill of Lading ID
    L11CarrierPROID321CN~ indicates the Carrier PRO/Load/Tracking ID
    L111234567BN~ - indicates the Best Buy TMS Load/Carrier Move ID.

    Example
    If either Reference Identification (L11-01) or Reference Identification Qualifier (L11-02) is present, then the other is required
    L11-01
    127
    Reference Identification
    Required
    Min 1Max 50

    Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier

    Usage notes

    If the value in L1102 is "BN", the value to be entered in this L1101 element, can also be pulled from the 204 Load tender that Best Buy would have transmitted to the carrier. It is located in the B204 element of the 204.

    L11-02
    128
    Reference Identification Qualifier
    Optional

    Code qualifying the Reference Identification

    BM
    Bill of Lading Number

    This qualifier must be used to identify that the value sent in the L1101 is the Bill of lading ID.

    BN
    Booking Number

    This qualifier must be used to identify that the information in the L1101 element is the Best Buy TMS Load/Carrier Move ID (also known as CID (Unique Consignee ID) or SID (Unique Shipper ID) from VICS or should be noted on the BOL in a special instructions field.).

    This can also be pulled from the 204 Load tender that Best Buy would have transmitted to the carrier as well. It is located in the B204 element of the 204.

    CN
    Carrier's Reference Number (PRO/Invoice)

    This qualifier must be used to identify that the information in the L1101 element is the Carrier's PRO/Load/Tracking ID for the shipment.

    0210 Loop
    RequiredMax >1
    Usage notes

    The values in this OID Loop/210 describe each individual order/shipment included in the shipment identified in the current iteration of the LX /200 Loop.

    OID
    0800

    Order Identification Detail

    RequiredMax use 1

    To specify order identification detail

    Usage notes

    The OID segment will contain all reference numbers that drivers MUST HAVE in order to deliver the shipment to Best Buy.

    Example Data: OIDBestBuyPOCTN245L*18000~

    Example
    OID-02
    324
    Purchase Order Number
    Required
    Min 1Max 22

    Identifying number for Purchase Order assigned by the orderer/purchaser

    Usage notes

    This element should contain the Best Buy Purchase Order or similar reference number (Transfer ID, RTV (Return to Vendor Authorization number) #, etc) that has been assigned to all or some of the logistical shipping/handling units on the shipment. If a 204 Load Tender was received for this shipment from Best Buy the OID02 element from the 204 Load Tender should be mapped here.

    OID-04
    211
    Packaging Form Code
    Required

    Code for packaging form of the lading quantity

    Usage notes

    This must be the qualifier that defines the type of Logistical shipping/handling units that are being moved on the shipment under the Reference ID indicated in the OID02. In all cases the qualifier must be "CTN". If a 204 Load Tender was received for this shipment from Best
    Buy the OID04 element from the 204 Load Tender can be mapped here.

    CTN
    Carton
    OID-05
    380
    Quantity
    Required
    Min 1Max 15

    Numeric value of quantity

    Usage notes

    This is the actual numerical quantity of the Logistical shipping/handling units being moved on the Shipment. If Best Buy has provided a 204 Load Tender for this shipment then the OID05 from the 204 Load Tender should be mapped here.

    OID-06
    188
    Weight Unit Code
    Required

    Code specifying the weight unit

    Usage notes

    This should be the qualifier that defines the type of weight units used for the Logistical shipping/handling units that are being moved on the shipment under the Reference ID indicated in the OID02. In almost all cases the qualifier should be "L" for Pounds or "K" for kilograms. If Best Buy has provided a 204 Load Tender for this shipment then the OID06 from the 204 Load Tender should be mapped here.

    K
    Kilograms
    L
    Pounds
    OID-07
    81
    Weight
    Required
    Min 1Max 10

    Numeric value of weight

    Usage notes

    This is the actual numerical weight of the Logistical shipping/handling units being moved on the Shipment. If Best Buy has provided a 204 Load Tender for this shipment then the OID07 from the 204 Load Tender should be mapped here.

    0220 Ship From
    OptionalMax >1
    Usage notes

    The values in this Name loop/220 identify the shipper of the shipment identified in the current iteration of the LX loop/200. Since there can be only one shipper of a shipment, there must be only one iteration of this loop.

    Variants (all may be used)
    0220Shipper
    N1
    1000

    Name

    RequiredMax use 1

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

    • Loop 0220 shall only be used to provide the identification of the shipper if the carrier has not provided that information in a previous shipment status message.
    Usage notes

    This segment identifies the shipper of the shipment identified in the current iteration of the LX 200/loop.

    Example Data: N1SFShippers name93Shippers unique Loc ID~

    Example
    N1-01
    98
    Entity Identifier Code
    Required

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

    SF
    Ship From
    N1-02
    93
    Name
    Optional
    Min 1Max 60

    Free-form name

    N1-03
    66
    Identification Code Qualifier
    Required

    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
    Required
    Min 2Max 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.
    Usage notes

    If the shipping charges are being paid by Best Buy and a 204 Load Tender was received by the carrier for the shipment indicated within the 212 Carrier Delivery Trailer Manifest message, the N104 element should be filled with the ID from the N104 Element of the corresponding EDI 204 Load Tender for the appropriate type of location type indicated in the N101. Otherwise the N104 element should contain the identifier assigned by the facility/location shipping the product.

    N4
    1300

    Geographic Location

    RequiredMax use 1

    To specify the geographic place of the named party

    Usage notes

    This segment identifies the origin location of the shipment identified in the current iteration of the LX loop/200.

    Example Data: N4CityNameSt99999USA~

    Example
    N4-01
    19
    City Name
    Required
    Min 2Max 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.
    Usage notes

    This must be the name of the actual City that the location indicated in the N1 segment is located within/by.

    N4-02
    156
    State or Province Code
    Required
    Min 2Max 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.
    Usage notes

    This must be the code of the state or province that the location indicated in the N1 segment is located within/by.

    N4-03
    116
    Postal Code
    Optional
    Min 3Max 15

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

    Usage notes

    This must be the postal code for the location that is indicated in the N1 segment is located within.

    N4-04
    26
    Country Code
    Optional
    Min 2Max 3

    Code identifying the country

    Usage notes

    This must be the Country code for the location that is indicated in the N1 segment is located within.

    0220 Shipper
    RequiredMax >1
    Usage notes

    The values in this Name loop/220 identify the shipper of the shipment identified in the current iteration of the LX loop/200. Since there can be only one shipper of a shipment, there must be only one iteration of this loop.

    Variants (all may be used)
    0220Ship From
    N1
    1000

    Name

    RequiredMax use 1

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

    • Loop 0220 shall only be used to provide the identification of the shipper if the carrier has not provided that information in a previous shipment status message.
    Usage notes

    This segment identifies the shipper of the shipment identified in the current iteration of the LX 200/loop.

    Example
    N1-01
    98
    Entity Identifier Code
    Required

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

    SH
    Shipper
    N1-02
    93
    Name
    Optional
    Min 1Max 60

    Free-form name

    N1-03
    66
    Identification Code Qualifier
    Required

    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
    Required
    Min 2Max 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.
    Usage notes

    If the shipping charges are being paid by Best Buy and a 204 Load Tender was received by the carrier for the shipment indicated within the 212 Carrier Delivery Trailer Manifest message, the N104 element should be filled with the ID from the N104 Element of the corresponding EDI 204 Load Tender for the appropriate type of location type indicated in the N101. Otherwise the N104 element should contain the identifier assigned by the facility/location shipping the product.

    N4
    1300

    Geographic Location

    RequiredMax use 1

    To specify the geographic place of the named party

    Usage notes

    This segment identifies the origin location of the shipment identified in the current iteration of the LX loop/200.

    Example Data: N4CityNameSt99999USA~

    Example
    N4-01
    19
    City Name
    Required
    Min 2Max 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.
    Usage notes

    This must be the name of the actual City that the location indicated in the N1 segment is located within/by.

    N4-02
    156
    State or Province Code
    Required
    Min 2Max 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.
    Usage notes

    This must be the code of the state or province that the location indicated in the N1 segment is located within/by.

    N4-03
    116
    Postal Code
    Optional
    Min 3Max 15

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

    Usage notes

    This must be the postal code for the location that is indicated in the N1 segment is located within.

    N4-04
    26
    Country Code
    Optional
    Min 2Max 3

    Code identifying the country

    Usage notes

    This must be the Country code for the location that is indicated in the N1 segment is located within.

    SE
    1500

    Transaction Set Trailer

    RequiredMax 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)

    Example
    SE-01
    96
    Number of Included Segments
    Required
    Min 1Max 10

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

    SE-02
    329
    Transaction Set Control Number
    Required
    Min 4Max 9

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

    Functional Group Trailer

    RequiredMax use 1

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

    Example
    GE-01
    97
    Number of Transaction Sets Included
    Required
    Min 1Max 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
    Min 1Max 9

    Assigned number originated and maintained by the sender

    Interchange Control Trailer

    RequiredMax use 1

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

    Example
    IEA-01
    I16
    Number of Included Functional Groups
    Required
    Min 1Max 5

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

    IEA-02
    I12
    Interchange Control Number
    Required
    Min 9Max 9

    A control number assigned by the interchange sender

    EDI Samples

    212 Cancel Manifest

    ST*212*0001~
    ATA*SCAC*MANIFESTID1*20100902~
    B2A*01~
    N1*ST*BEST BUY RDC70*94*70~
    AT7*AV*NS***20100902*1525*LT~
    MS2*SCAC*9876544321*TL~
    M7*Seal1****CM~
    LX*1~
    L11*BOLID12345*BM~
    L11*CarrierPROID123*CN~
    OID**ABCDEF**CTN*245*L*3800~
    OID**LSEGAB**CTN*21*L*2162~
    N1*SH*Shippers name*93*Shipper-01~
    N4*Bellevue*WA*98004*US~
    LX*2~
    L11* CMV0000001*BM~
    L11*CarrierPROID321*CN~
    L11*CMV0000001*BN~
    OID**FEDCBA**CTN*120*L*10570~
    N1*SH*Widget Inc*93*WIDGE-01~
    N4*Los Angeles*CA*90001*US~
    LX*3~
    L11*76543210987654321*BM~
    L11*CarrierPROID789*CN~
    OID**EMPLEH**CTN*154*L*1253~
    OID**FEVAHI**CTN*336*L*2003~
    OID**YLLANI**CTN*14*L*210~
    OID**YMTSOL**CTN*56*L*3498~
    OID**YTINAS**CTN*34*L*4206~
    N1*SH*Arkham Mulysa Industries*93*Shipper-01~
    N4*New York*NY*10011*US~
    LX*4~
    L11* CMV0000020*BM~
    L11*CarrierPROID987*CN~
    L11*CMV0000020*BN~
    OID**AARRGH**CTN*5*L*1800~
    OID**MEWOOO**CTN*17*L*980~
    OID**WOLFIE**CTN*32*L*565~
    N1*SH*Johns Gizmo’s*93*BBYLoadATID-01~
    N4*Chicago*IL*60601*US~
    LX*5~
    L11*12345678901234567*BM~
    L11*CarrierPROID684*CN~
    OID**NAMTAB**CTN*24*L*1080~
    OID**SNIBOR**CTN*45*L*800~
    OID**SREKOJ**CTN*25*L*1000~
    N1*SH*Wayne Enterprises*93*WAYNE01~
    N4*New York*NY*10003*US~
    SE*49*0001~

    212 Original Manifest

    ST*212*0001~
    ATA*SCAC*MANIFESTID1*20100902~
    B2A*00~
    N1*ST*BEST BUY RDC70*94*70~
    AT7*AV*NS***20100902*1525*LT~
    MS2*SCAC*9876544321*TL~
    M7*Seal1****CM~
    LX*1~
    L11*BOLID12345*BM~
    L11*CarrierPROID123*CN~
    OID**ABCDEF**CTN*245*L*3800~
    N1*SH*Shippers name*93*Shipper-01~
    N4*Bellevue*WA*98004*US~
    LX*2~
    L11* CMV0000001*BM~
    L11*CarrierPROID321*CN~
    L11*CMV0000001*BN~
    OID**FEDCBA**CTN*120*L*10570~
    N1*SH*Widget Inc*93*WIDGE-01~
    N4*Los Angeles*CA*90001*US~
    LX*3~
    L11*76543210987654321*BM~
    L11*CarrierPROID789*CN~
    OID**EMPLEH**CTN*154*L*1253~
    OID**FEVAHI**CTN*336*L*2003~
    OID**YLLANI**CTN*14*L*210~
    OID**YMTSOL**CTN*56*L*3498~
    OID**YTINAS**CTN*34*L*4206~
    N1*SH*Arkham Mulysa Industries*93*Shipper-01~
    N4*New York*NY*10011*US~
    LX*4~
    L11* CMV0000020*BM~
    L11*CarrierPROID987*CN~
    L11*CMV0000020*BN~
    OID**AARRGH**CTN*5*L*1800~
    OID**MEWOOO**CTN*17*L*980~
    OID**WOLFIE**CTN*32*L*565~
    OID**BAGELS**CTN*21*L*2162~
    N1*SH*Johns Gizmo’s*93*BBYLoadATID-01~
    N4*Chicago*IL*60601*US~
    LX*5~
    L11*12345678901234567*BM~
    L11*CarrierPROID684*CN~
    OID**NAMTAB**CTN*24*L*1080~
    OID**SNIBOR**CTN*45*L*800~
    OID**SREKOJ**CTN*25*L*1000~
    N1*SH*Wayne Enterprises*93*WAYNE01~
    N4*New York*NY*10003*US~
    LX*6~
    L11*281-0000001*BM~
    L11*CarrierPROID264*CN~
    L11*CMV0000281*BN~
    OID**999999**CTN*15*L*120~
    N1*SH*Best Buy Richfield*93*281~
    N4*Richfield*MN*55423*US~
    SE*56*0001~

    212 Replacement Manifest

    ST*212*0001~
    ATA*SCAC*MANIFESTID1*20100902~
    B2A*05~
    N1*ST*BEST BUY RDC70*94*70~
    AT7*AV*NS***20100902*1525*LT~
    MS2*SCAC*9876544321*TL~
    M7*Seal1****CM~
    LX*1~
    L11*BOLID12345*BM~
    L11*CarrierPROID123*CN~
    OID**ABCDEF**CTN*245*L*3800~
    OID**LSEGAB**CTN*21*L*2162~
    N1*SH*Shippers name*93*Shipper-01~
    N4*Bellevue*WA*98004*US~
    LX*2~
    L11* CMV0000001*BM~
    L11*CarrierPROID321*CN~
    L11*CMV0000001*BN~
    OID**FEDCBA**CTN*120*L*10570~
    N1*SH*Widget Inc*93*WIDGE-01~
    N4*Los Angeles*CA*90001*US~
    LX*3~
    L11*76543210987654321*BM~
    L11*CarrierPROID789*CN~
    OID**EMPLEH**CTN*154*L*1253~
    OID**FEVAHI**CTN*336*L*2003~
    OID**YLLANI**CTN*14*L*210~
    OID**YMTSOL**CTN*56*L*3498~
    OID**YTINAS**CTN*34*L*4206~
    N1*SH*Arkham Mulysa Industries*93*Shipper-01~
    N4*New York*NY*10011*US~
    LX*4~
    L11* CMV0000020*BM~
    L11*CarrierPROID987*CN~
    L11*CMV0000020*BN~
    OID**AARRGH**CTN*5*L*1800~
    OID**MEWOOO**CTN*17*L*980~
    OID**WOLFIE**CTN*32*L*565~
    N1*SH*Johns Gizmo’s*93*BBYLoadATID-01~
    N4*Chicago*IL*60601*US~
    LX*5~
    L11*12345678901234567*BM~
    L11*CarrierPROID684*CN~
    OID**NAMTAB**CTN*24*L*1080~
    OID**SNIBOR**CTN*45*L*800~
    OID**SREKOJ**CTN*25*L*1000~
    N1*SH*Wayne Enterprises*93*WAYNE01~
    N4*New York*NY*10003*US~
    SE*49*0001~

    Stedi is a registered trademark of Stedi, Inc. All names, logos, and brands of third parties listed on this page are trademarks of their respective owners (including “X12”, which is a trademark of X12 Incorporated). Stedi, Inc. and its products and services are not endorsed by, sponsored by, or affiliated with these third parties. Use of these names, logos, and brands is for identification purposes only, and does not imply any such endorsement, sponsorship, or affiliation.