Kraft Heinz
/
Motor Carrier Load Tender
  • Specification
  • EDI Inspector
Import guide into your account
Stedi maintains this guide based on public documentation from Kraft Heinz. Contact Kraft Heinz for official EDI specifications. To report any errors in this guide, please contact us.
Go to Stedi Network
Kraft Heinz logo

X12 204 Motor Carrier Load Tender

X12 Release 4010

This Draft Standard for Trial Use contains the format and establishes the data contents of the Motor Carrier Load Tender Transaction Set (204) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set can be used to allow shippers or other interested parties to offer (tender) a shipment to a full load (truckload) motor carrier including detailed scheduling, equipment requirements, commodities, and shipping instructions pertinent to a load tender. It is not to be used to provide a motor carrier with data relative to a Less-than-Truckload bill of lading, pick-up notification, or manifest.

Delimiters
  • ~ Segment
  • * Element
  • > Component
EDI sample
  • Sample
View the latest version of this implementation guide as an interactive webpage
https://www.stedi.com/app/guides/view/kraft-heinz/motor-carrier-load-tender/01GYW5M93YQGBRT5455MECN582
Powered by
Build 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
010
Transaction Set Header
Max use 1
Required
B2
020
Beginning Segment for Shipment Information Transaction
Max use 1
Required
B2A
030
Set Purpose
Max use 1
Required
L11
080
BOL of the previous leg of the Continuous Move
Max use 50
Optional
L11
080
Continuous Move Number
Max use 50
Optional
G62
090
Date/Time
Max use 1
Optional
AT5
110
Bill of Lading Handling Requirements
Max use 6
Optional
NTE
130
Note/Special Instruction
Max use 10
Optional
0100 Loop
detail
0300 Loop
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
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 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
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 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
Identifier (ID)
Min 2Max 2

Qualifier to designate 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
String (AN)
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
Identifier (ID)
Min 2Max 2

Qualifier to designate 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
String (AN)
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
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 9Max 9

A control number assigned by the interchange sender

ISA-14
I13
Acknowledgment Requested
Required
Identifier (ID)
Min 1Max 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 1Max 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 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
Identifier (ID)

Code identifying a group of application related transaction sets

SM
Motor Carrier Load Tender (204)
GS-02
142
Application Sender's Code
Required
String (AN)
Min 2Max 15

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

GS-03
124
Application Receiver's Code
Required
String (AN)
Min 2Max 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 1Max 9

Assigned number originated and maintained by the sender

GS-07
455
Responsible Agency Code
Required
Identifier (ID)
Min 1Max 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

004010
Draft Standards Approved for Publication by ASC X12 Procedures Review Board through October 1997

Heading

ST
010
Heading > ST

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
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).
204
Motor Carrier Load Tender
ST-02
329
Transaction Set Control Number
Required
Numeric (N)
Min 4Max 9

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

B2
020
Heading > B2

Beginning Segment for Shipment Information Transaction

RequiredMax use 1

To transmit basic data relating to shipment information

Example
B2-02
140
Standard Carrier Alpha Code
Required
Identifier (ID)
Min 2Max 4

Standard Carrier Alpha Code

  • B202 contains the Standard Carrier Alpha Code (SCAC) of the carrier that will receive the bill of lading.
  • B202 is mandatory for transaction set 204.
Usage notes

Carrier’s SCAC Code

B2-04
145
Shipment Identification Number
Optional
String (AN)
Min 1Max 30

Identification number assigned to the shipment by the shipper that uniquely identifies the shipment from origin to ultimate destination and is not subject to modification; (Does not contain blanks or special characters)

Usage notes

Bill of Lading Number (BOL). This identification number will be used for freight payment (sent to Kraft Heinz in the 210 segment).

This will be the SID – 10 digit Shipment number

B2-05
188
Weight Unit Code
Optional
Identifier (ID)

Code specifying the weight unit

L
Pounds
B2-06
146
Shipment Method of Payment
Required
Identifier (ID)

Code identifying payment terms for transportation charges

CC
Collect
PP
Prepaid (by Seller)
B2-07
147
Shipment Qualifier
Optional
Identifier (ID)

Code defining relationship of this shipment with respect to other shipments given to the carrier at the same time

Usage notes

Based on the Load Class within SMS
I = Load class I
B = Load Class T (no stops)
F = Load Class T (with stops)

B
Bill of Lading for Individual Shipment

Single

F
Stop-off Shipment

Shipment contains stop–off(s)

I
Intermodal

Intermodal

L
LTL (less than truckload)
B2A
030
Heading > B2A

Set Purpose

RequiredMax use 1

To allow for positive identification of transaction set purpose

Example
B2A-01
353
Transaction Set Purpose Code
Required
Identifier (ID)

Code identifying purpose of transaction set

00
Original

Used when the load is tendered for the first time is used when the load is tendered again to the same carrier as the original tender. This can occur when the shipment is recalled and retendered for transmission problems.

01
Cancellation

Used when the shipment is recalled or cancelled

04
Change

Used when something on the order changes:
Ship/Delivery Dates
PO’s added or deleted
Stops added/deleted
CM created

L11
080
Heading > L11

BOL of the previous leg of the Continuous Move

OptionalMax use 50

To specify instructions in this business relationship or a reference number

Usage notes

This segment will be used when the Tender is part of a continuous
move

The PSI qualifier will be used to designate the previous leg of the
continuous move.

This segment will be used when the shipment being tendered is part of a continuous movement.

The first leg of a continuous movement will be tendered as a ‘normal’ shipment. When the second leg is tendered, the first leg will be updated. A 204 update will be sent and there will be an L11 segment with a CM qualifier. The Continuous movement number will be sent in the L1101.

When the second (or subsequent) leg of the continuous movement is tendered, there will be two occurrences of this segment.

The first will contain the continuous movement number and the CM qualifier. The second occurrence will contain the shipment number (BOL) of the previous leg with the PSI qualifier.

Example
Variants (all may be used)
L11Continuous Move Number
L11-01
127
Reference Identification
Optional
String (AN)
Min 1Max 30

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

Usage notes

This will be the BOL of the previous leg of the continuous move.

L11-02
128
Reference Identification Qualifier
Required
Identifier (ID)

Code qualifying the Reference Identification

PSI
BOL of the previous leg of the Continuous Move
L11
080
Heading > L11

Continuous Move Number

OptionalMax use 50

To specify instructions in this business relationship or a reference number

Usage notes

This segment will be used when the Tender is part of a continuous
move

The CM qualifier will be used to designate the continuous move
number.

This segment will be used when the shipment being tendered is part of a continuous movement.

The first leg of a continuous movement will be tendered as a ‘normal’ shipment. When the second leg is tendered, the first leg will be updated. A 204 update will be sent and there will be an L11 segment with a CM qualifier. The Continuous movement number will be sent in the L1101.

When the second (or subsequent) leg of the continuous movement is tendered, there will be two occurrences of this segment.

The first will contain the continuous movement number and the CM qualifier. The second occurrence will contain the shipment number (BOL) of the previous leg with the PSI qualifier.

Example
L11-01
127
Reference Identification
Optional
String (AN)
Min 1Max 30

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

Usage notes

This will be the Continuous Move Reference Number assigned by Kraft Heinz

L11-02
128
Reference Identification Qualifier
Required
Identifier (ID)

Code qualifying the Reference Identification

CM
Continuous Move Number
G62
090
Heading > G62

Date/Time

OptionalMax use 1

To specify pertinent dates and times

  • Segment G62 in header is used to convey the must-respond-by date and time when responding to a 204 transaction.
Usage notes

This segment is used to inform the carrier when they must respond to our offer. In other words, the 990 response is due back to LCC by the date and time provided in this segment. The Date & Time populated should be 2 hours after the tender time, and should be converted to local time for the carrier.

Example
If either Date Qualifier (G62-01) or Date (G62-02) is present, then the other is required
At least one of Date Qualifier (G62-01) or Time Qualifier (G62-03) is required
If either Time Qualifier (G62-03) or Time (G62-04) is present, then the other is required
G62-01
432
Date Qualifier
Optional
Identifier (ID)

Code specifying type of date

64
Must Respond By
G62-02
373
Date
Optional
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD

G62-03
176
Time Qualifier
Optional
Identifier (ID)

Code specifying the reported time

1
Must Respond By
G62-04
337
Time
Optional
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)

Usage notes

Time expressed in 24-hour clock time as follows: HHMM

G62-05
623
Time Code
Optional
Identifier (ID)

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

LT
Local Time
AT5
110
Heading > AT5

Bill of Lading Handling Requirements

OptionalMax use 6

To identify Bill of Lading handling and service requirements

Usage notes

The AT5 segment is used to inform carriers that the shipment tender is a part of a loop. The carrier will need to invoice Kraft Heinz using a loop rate.

Example
Only one of Special Handling Code (AT5-01) or Special Handling Description (AT5-03) may be present
Only one of Special Services Code (AT5-02) or Special Handling Description (AT5-03) may be present
AT5-01
152
Special Handling Code
Optional
Identifier (ID)
Min 2Max 3

Code specifying special transportation handling instructions

Usage notes

Blank

AT5-02
560
Special Services Code
Optional
Identifier (ID)
Min 2Max 10

Code identifying the special service

Usage notes

Blank

AT5-03
153
Special Handling Description
Optional
String (AN)
Min 2Max 30

Free-form additional description of special handling instructions to appear on printed bill if special handling code is not adequate

Usage notes

Route Leg ID – contains ‘Route Template’, ‘Route Instance’, and the ‘Route Leg’ information

NTE
130
Heading > NTE

Note/Special Instruction

OptionalMax use 10

To transmit information in a free-form format, if necessary, for comment or special instruction

Usage notes

Up to 20 lines of additional data can be transmitted to the carriers. This data should include any comments that are sent to us via COD, or any standard comments that are associated with the stopoff. These could be directions to the facility or instructions about not using certain size equipment, etc.

Example
NTE-01
363
Note Reference Code
Optional
Identifier (ID)

Code identifying the functional area or purpose for which the note applies

ADD
Additional Information
NTE-02
352
Description
Required
String (AN)
Min 1Max 80

A free-form description to clarify the related data elements and their content

0100 Loop
OptionalMax >1
N1
140
Heading > 0100 Loop > N1

Name

RequiredMax use 1

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

  • Loop 0100 is used to convey name and address detail relative to bill-to, party controlling freight, or other shipment level name and address information. It is not used to convey ship from or ship to detail which should be handled within loop 0300 in table 2.
Usage notes

This segment will be populated with the information associated with the SHIPPER CODE on the shipment.
Ship-to Code and Ship-to Name. The internal customer number and qualifier will not be supplied when the shipment is a drop shipment.

Example
At least one of Name (N1-02) or Identification Code Qualifier (N1-03) is required
If either Identification Code Qualifier (N1-03) or Identification Code (N1-04) is present, then the other is required
N1-01
98
Entity Identifier Code
Required
Identifier (ID)

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

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

Free-form name

Usage notes

Name of Shipper (Kraft Heinz Foods Company)

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

Code assigned by Kraft Heinz

N1-04
67
Identification Code
Optional
String (AN)
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

Kraft Heinz internal customer number associated with Shipper

N2
150
Heading > 0100 Loop > N2

Additional Name Information

OptionalMax use 1

To specify additional names or those longer than 35 characters in length

Example
N2-01
93
Name
Required
String (AN)
Min 1Max 60

Free-form name

Usage notes

Additional shipper name information – if needed

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

Free-form name

Usage notes

Additional shipper name information – if needed

N3
160
Heading > 0100 Loop > N3

Address Information

OptionalMax use 2

To specify the location of the named party

Usage notes

This segment is populated with the address information in the ship-to record.

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

Address information

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

Address information

N4
170
Heading > 0100 Loop > N4

Geographic Location

OptionalMax use 1

To specify the geographic place of the named party

Usage notes

This segment contains the information relating to the ship-to record.

Example
N4-01
19
City Name
Optional
String (AN)
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

City of Shipper

N4-02
156
State or Province Code
Optional
Identifier (ID)
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

State or Province of Shipper

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

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

Usage notes

Postal / Zip code of shipper

N4-04
26
Country Code
Optional
Identifier (ID)
Min 2Max 3

Code identifying the country

Usage notes

Country of Shipper (USA)

G61
190
Heading > 0100 Loop > G61

Contact

OptionalMax use 3

To identify a person or office to whom communications should be directed

Usage notes

This segment will contain information relating to the load planner that actually tendered the shipment. The contact name will be the load planner’s name (found in the shipment audit record, x-refed to the userid).
The Communication number could be hard-coded to the 1888LOADCTR number. If at all possible if would be great to be able to map an extension number on the end.

Example
If either Communication Number Qualifier (G61-03) or Communication Number (G61-04) is present, then the other is required
G61-01
366
Contact Function Code
Required
Identifier (ID)

Code identifying the major duty or responsibility of the person or group named

SH
Shipper Contact
G61-02
93
Name
Required
String (AN)
Min 1Max 60

Free-form name

Usage notes

Contact Name

G61-03
365
Communication Number Qualifier
Optional
Identifier (ID)

Code identifying the type of communication number

  • G6103 qualifies G6104.
TE
Telephone
G61-04
364
Communication Number
Optional
String (AN)
Min 1Max 80

Complete communications number including country or area code when applicable

Usage notes

LCC Phone Number

0100 Loop end
0200 Loop
OptionalMax >1
N7
200
Heading > 0200 Loop > N7

Equipment Details

RequiredMax use 1

To identify the equipment

Usage notes

Information in this segment will come from the shipment record. Data element 40 – Equipment description code will be mapped as:

TF when equipment type starts with a VN
RT when equipment type starts with a RF
TI when equipment type starts with an IN
TA when equipment type starts with an HT

The equipment length field is from the last two digits of the equipment type at the shipment level.

Example
If either Weight (N7-03) or Weight Qualifier (N7-04) is present, then the other is required
If either Volume (N7-08) or Volume Unit Qualifier (N7-09) is present, then the other is required
N7-02
207
Equipment Number
Required
String (AN)
Min 1Max 10

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

Usage notes

Value Kraft Heinz will use 0 (zero)

N7-03
81
Weight
Optional
Decimal number (R)
Min 1Max 10

Numeric value of weight

Usage notes

Weight of Shipment

N7-04
187
Weight Qualifier
Optional
Identifier (ID)

Code defining the type of weight

G
Gross Weight
N7-08
183
Volume
Optional
Decimal number (R)
Min 1Max 8

Value of volumetric measure

Usage notes

Cubic Measure of shipment

N7-09
184
Volume Unit Qualifier
Optional
Identifier (ID)

Code identifying the volume unit

E
Cubic Feet
M
Cubic Meters (M3)

for Brazil only

N7-11
40
Equipment Description Code
Optional
Identifier (ID)

Code identifying type of equipment used for shipment

RT
Controlled Temperature Trailer (Reefer)
TA
Trailer, Heated/Insulated/Ventilated
TE
Trailer Easter (Brazil only)
TF
Trailer, Dry Freight
TI
Trailer, Insulated
N7-15
567
Equipment Length
Optional
Numeric (N0)
Min 4Max 5

Length (in feet and inches) of equipment ordered or used to transport shipment (The format is FFFII where FFF is feet and II is inches; the range for II is 00 through 11)

Usage notes

Length of equipment requested
4800 – 48’ trailer
5300 – 53’ trailer

0200 Loop end
Heading end

Detail

0300 Loop
RequiredMax >1
S5
010
Detail > 0300 Loop > S5

Stop Off Details

RequiredMax use 1

To specify stop-off detail reference numbers and stop reason

Usage notes

The S5 is the beginning of the stop-off loop. There will be at LEAST two occurrences of the S5 segment with each 204.
The weight, case count, and cube are populated from the stop off record. The stop reason code is straightforward and should be mapped accordingly. The stop sequence number will begin with 01 (for the original pickup) and 02 will designate the final unload.

Example
If either Weight (S5-03) or Weight Unit Code (S5-04) is present, then the other is required
If either Number of Units Shipped (S5-05) or Unit or Basis for Measurement Code (S5-06) is present, then the other is required
If either Volume (S5-07) or Volume Unit Qualifier (S5-08) is present, then the other is required
S5-01
165
Stop Sequence Number
Required
Numeric (N0)
Min 1Max 3

Identifying number for the specific stop and the sequence in which the stop is to be performed

Usage notes

Specific stop sequence number

S5-02
163
Stop Reason Code
Required
Identifier (ID)

Code specifying the reason for the stop

CL
Complete

complete shipment

CU
Complete Unload

complete unload (final stop)

LD
Load

complete load (last pickup)

PL
Part Load

part load (used when there are multiple pickup stops)

PU
Part Unload

part unload (used when there are multiple delivery stops)

S5-03
81
Weight
Optional
Decimal number (R)
Min 1Max 10

Numeric value of weight

Usage notes

Weight of Stop off

S5-04
188
Weight Unit Code
Optional
Identifier (ID)

Code specifying the weight unit

K
Kilograms
L
Pounds
S5-05
382
Number of Units Shipped
Optional
Decimal number (R)
Min 1Max 10

Numeric value of units shipped in manufacturer's shipping units for a line item or transaction set

Usage notes

Number of units (Cases) shipped

S5-06
355
Unit or Basis for Measurement Code
Optional
Identifier (ID)

Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken

CA
Case
S5-07
183
Volume
Optional
Decimal number (R)
Min 1Max 8

Value of volumetric measure

Usage notes

Volume of stop off

S5-08
184
Volume Unit Qualifier
Optional
Identifier (ID)

Code identifying the volume unit

E
Cubic Feet
M
Cubic Meters (M3)

for Brazil only

L11
020
Detail > 0300 Loop > L11

Business Instructions and Reference Number

OptionalMax use 50

To specify instructions in this business relationship or a reference number

Usage notes

IL qualifier – for internal order number (Kraft Heinz replenishment #) OR a PO qualifier – for the customer’s PO number

If the IL qualifier is used, the reference number will be the replenishment number (ROCET). If the PO qualifier is used, the reference number will be the customer’s Purchase Order Number. There will be multiple occurrences of this segment when there are multiple PO’s on a stop-off.

Example
Variants (all may be used)
L11Shipment stop-off identifier
L11-01
127
Reference Identification
Optional
String (AN)
Min 1Max 30

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

L11-02
128
Reference Identification Qualifier
Required
Identifier (ID)

Code qualifying the Reference Identification

IL
Internal Order Number

Used to identify Replenishment Orders

PO
Purchase Order Number

Purchase Order of Customer

L11
020
Detail > 0300 Loop > L11

Shipment stop-off identifier

RequiredMax use 50

To specify instructions in this business relationship or a reference number

Usage notes

This will be the reference number returned in the 214

The occurrence will include the shipment stop-off number (SID + 01 + stop), with the SI qualifier. The pickup stop will only have this reference. The delivery stops will have this qualifier and another occurrence of the L11.

Example
L11-01
127
Reference Identification
Optional
String (AN)
Min 1Max 30

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

L11-02
128
Reference Identification Qualifier
Required
Identifier (ID)

Code qualifying the Reference Identification

SI
Shipper's Identifying Number for Shipment (SID)
G62
030
Detail > 0300 Loop > G62

Date/Time

RequiredMax use 2

To specify pertinent dates and times

  • Use G62 segment either in loop 0300 or loop 0350, but not both.
Usage notes

The G62 segment is very dependent on the information passed to LCC on the order and to what stop it applies. There can be up to two occurrences of the G62 segment per stop-off. This is usually seen when a time range is provided to the carrier.

The pickup stop-offs (stop reason code LD or PL – see S502) will have the following:
G6201 will have a value of 10 or 69 (most times it will be 69, as Kraft Heinz is establishing the ship date.
The G6203 in the first occurrence of the G62 will contain an I. The second occurrence of the G62 will contain a K. The times entered in the G62 segments will relate to the dock hours if no specific time is specified.
If a specific time is specified (i.e. earliest & latest is the same), then the value of Y will be used and only one G62 will be sent.
Very rarely will pickup appointments be provided to the carriers.
If the order has a scheduled delivery appointment, it will be outlined in the standard comments.
Standard Comments are:
0002 _____A.M.-DEL. BEFORE - G6201 value = 70, G6203 value = L
0003 _____P.M.-DEL. BEFORE - G6201 value = 70, G6203 value = L
0004 _____A.M.-DEL. AFTER - G6201 value = 70, G6203 value = G
0005 _____P.M.-DEL. AFTER – G6201 value = 70, G6203 value = G
0006 _____A.M.-DEL TIME – G6201 value = 70, G6203 value = 3
0007 _____P.M.-DEL TIME – G6201 value = 70, G6203 value = 3
In many cases, the delivery date will be requested, with no assigned time. In this case, the G6201 value will be 69. The G6203 value will be:
Z if there is a specific time provided OR there will be two occurrences of the G62. The first G6203 will contain the value G and the second G6203 will contain the value L.

Example
If either Date Qualifier (G62-01) or Date (G62-02) is present, then the other is required
At least one of Date Qualifier (G62-01) or Time Qualifier (G62-03) is required
If either Time Qualifier (G62-03) or Time (G62-04) is present, then the other is required
G62-01
432
Date Qualifier
Optional
Identifier (ID)

Code specifying type of date

10
Requested Ship Date/Pick-up Date

Carrier MUST MAKE appointment

68
Requested Delivery Date

Carrier MUST MAKE appointment

69
Scheduled Pick-Up Date

Carrier MUST CONFIRM appointment

70
Scheduled Delivery Date

Carrier MUST CONFIRM appointment

G62-02
373
Date
Optional
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD

G62-03
176
Time Qualifier
Optional
Identifier (ID)

Code specifying the reported time

Usage notes

If pick up or delivery ‘windows’ are given:
G – Earliest Requested Delivery Time
I – Earliest Requested Pick up Time
K – Latest Requested Pick up Time
L – Latest Requested Delivery Time

2
Pickup Appointment Scheduled Time

Carrier MUST CONFIRM appointment time

3
Delivery Appointment Scheduled Time

Carrier MUST CONFIRM appointment time

G
Earliest Requested Deliver Time
I
Earliest Requested Pick Up Time
K
Latest Requested Pick Up Time
L
Latest Requested Delivery Time
Y
Requested Pick Up Time

Carrier MUST MAKE appointment

Z
Requested Delivery Time

Carrier MUST MAKE appointment

G62-04
337
Time
Optional
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)

Usage notes

Time expressed in 24-hour clock time as follows: HHMM

G62-05
623
Time Code
Optional
Identifier (ID)

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

LT
Local Time
NTE
065
Detail > 0300 Loop > NTE

Note/Special Instruction

RequiredMax use 20

To transmit information in a free-form format, if necessary, for comment or special instruction

Usage notes

Up to 20 lines of additional data can be transmitted to the carriers. This data should include any comments that are sent to us via COD, or any standard comments that are associated with the stop-off. These could be directions to the facility or instructions about not using certain size equipment, etc.

Example
NTE-01
363
Note Reference Code
Optional
Identifier (ID)

Code identifying the functional area or purpose for which the note applies

ADD
Additional Information
NTE-02
352
Description
Required
String (AN)
Min 1Max 80

A free-form description to clarify the related data elements and their content

Usage notes

A free-form description to clarify the related data elements and their content

0310 Loop
OptionalMax >1
N1
070
Detail > 0300 Loop > 0310 Loop > N1

Name

RequiredMax use 1

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

Usage notes

This segment is used to identify the stop-off details. There will be one occurrence of this segment for each S5. If the shipment is going to a ‘drop ship’ address, the drop ship information will be sent to the carrier in these segments. For the original pickup (stop 01, stop reason code LD) the N101 value will be SF. For subsequent pickup (if there are any, stop reason code PL) the N101 value will be PW. For intermediate stops (if there are any, stop reason code PU) the N101 value will be DA. For the final delivery (stop 02, stop reason code CU) the N101 value will be ST. The N102 will contain the name of the stop-off customer. The N104 will contain the customer number on the stop-off.

Example
At least one of Name (N1-02) or Identification Code Qualifier (N1-03) is required
If either Identification Code Qualifier (N1-03) or Identification Code (N1-04) is present, then the other is required
N1-01
98
Entity Identifier Code
Required
Identifier (ID)

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

CN
Consignee

used by SMS only

DA
Delivery Address

used by both SMS and Manugistics

PW
Pick Up Address
SF
Ship From
ST
Ship To

used by Manugistics only

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

Free-form name

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

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

N1-04
67
Identification Code
Optional
String (AN)
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.
N2
080
Detail > 0300 Loop > 0310 Loop > N2

Additional Name Information

OptionalMax use 1

To specify additional names or those longer than 35 characters in length

Usage notes

In general, we don’t usually use this. If there were a second line in the name, the information would go here.

Example
N2-01
93
Name
Required
String (AN)
Min 1Max 60

Free-form name

Usage notes

Name of Pick up or Delivery Location

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

Free-form name

Usage notes

Additional Name data

N3
090
Detail > 0300 Loop > 0310 Loop > N3

Address Information

OptionalMax use 2

To specify the location of the named party

Usage notes

Address information is shown here.

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

Address information

Usage notes

Address of pick up or delivery location

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

Address information

Usage notes

Additional Address information

N4
100
Detail > 0300 Loop > 0310 Loop > N4

Geographic Location

OptionalMax use 1

To specify the geographic place of the named party

Usage notes

This segment contains the information relating to the city/state of the stop-off. The information maps from the stop off data.

Example
N4-01
19
City Name
Optional
String (AN)
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

City Name of location

N4-02
156
State or Province Code
Optional
Identifier (ID)
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

State / Province of Location

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

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

Usage notes

Postal or Zip Code of location

N4-04
26
Country Code
Optional
Identifier (ID)

Code identifying the country

Usage notes

Code identifying the country of location

CA
Canada
US
United States of America (the)
G61
120
Detail > 0300 Loop > 0310 Loop > G61

Contact

OptionalMax use 3

To identify a person or office to whom communications should be directed

Usage notes

If there is a contact name & number associated with the stop off or customer number, it is sent in this segment. If the stop is a pickup stop the G6101 value will be SH, if the stop is a delivery stop the G6101 value is DC.

Example
If either Communication Number Qualifier (G61-03) or Communication Number (G61-04) is present, then the other is required
G61-01
366
Contact Function Code
Required
Identifier (ID)

Code identifying the major duty or responsibility of the person or group named

DC
Delivery Contact
SH
Shipper Contact
G61-02
93
Name
Required
String (AN)
Min 1Max 60

Free-form name

Usage notes

Contact Name

G61-03
365
Communication Number Qualifier
Optional
Identifier (ID)

Code identifying the type of communication number

  • G6103 qualifies G6104.
TE
Telephone
G61-04
364
Communication Number
Optional
String (AN)
Min 1Max 80

Complete communications number including country or area code when applicable

Usage notes

Telephone Number of contact Person

0310 Loop end
0350 Loop
OptionalMax >1
OID
150
Detail > 0300 Loop > 0350 Loop > OID

Order Identification Detail

RequiredMax use 1

To specify order identification detail

  • Use loop 0350 for conveying seller's order/invoice level detail or buyer's purchase order level detail. If not using order level detail, this loop should not be used.
Usage notes

This segment is used to provide the carrier with the case count, weight and cube of each order. It is used by larger customers when the delivery appointments are made. There will be one occurrence of this segment for each Purchase Order on the stop. This segment is associated with customer delivery stops only. The value in the OID02 should match the data sent in the L11 segment with a PO qualifier.

Example
If either Unit or Basis for Measurement Code (OID-04) or Quantity (OID-05) is present, then the other is required
If either Weight Unit Code (OID-06) or Weight (OID-07) is present, then the other is required
If either Volume Unit Qualifier (OID-08) or Volume (OID-09) is present, then the other is required
OID-02
324
Purchase Order Number
Optional
String (AN)
Min 1Max 22

Identifying number for Purchase Order assigned by the orderer/purchaser

OID-04
355
Unit or Basis for Measurement Code
Optional
Identifier (ID)

Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken

CA
Case
OID-05
380
Quantity
Optional
Decimal number (R)
Min 1Max 15

Numeric value of quantity

Usage notes

Number of cases ordered on given Purchase Order

OID-06
188
Weight Unit Code
Optional
Identifier (ID)

Code specifying the weight unit

K
Kilograms
L
Pounds
OID-07
81
Weight
Optional
Decimal number (R)
Min 1Max 10

Numeric value of weight

Usage notes

Weight (in pounds) associated with the given Purchase Order

OID-08
184
Volume Unit Qualifier
Optional
Identifier (ID)

Code identifying the volume unit

E
Cubic Feet
M
Cubic Meters (M3)

for Brazil only

OID-09
183
Volume
Optional
Decimal number (R)
Min 1Max 8

Value of volumetric measure

Usage notes

Volume (in cubic feet) associated with the given Purchase Order

0350 Loop end
0300 Loop end
Detail end

Summary

L3
010
Summary > L3

Total Weight and Charges

OptionalMax use 1

To specify the total shipment in terms of weight, volume, rates, charges, advances, and prepaid amounts applicable to one or more line items

Example
If either Volume (L3-09) or Volume Unit Qualifier (L3-10) is present, then the other is required
L3-01
81
Weight
Optional
Decimal number (R)
Min 1Max 10

Numeric value of weight

Usage notes

Weight of Shipment

L3-02
187
Weight Qualifier
Optional
Identifier (ID)

Code defining the type of weight

G
Gross Weight
L3-09
183
Volume
Optional
Decimal number (R)
Min 1Max 8

Value of volumetric measure

Usage notes

Total Volume of the Shipment (in cubic feet)

L3-10
184
Volume Unit Qualifier
Optional
Identifier (ID)

Code identifying the volume unit

E
Cubic Feet
M
Cubic Meters (M3)

for Brazil only

SE
020
Summary > SE

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
Numeric (N0)
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
Numeric (N)
Min 4Max 9

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

Summary end

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
Numeric (N0)
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
Numeric (N0)
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
Numeric (N0)
Min 1Max 5

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

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

A control number assigned by the interchange sender

EDI Samples

Sample

ST*204*22450~
B2**SCAC**2021601410*L*PP*B~
B2A*00~
G62*64*20160509*1*1247*LT~
N1*SH*Kraft Heinz Foods Company*93*569129~
N3*PO Box 982141~
N4*El Paso*TX*79998-2141*USA~
G61*SH*LOAD PLANNER*TE*Call Dispatch Office~
N7**0*300*G****51000*E**RT****5300~
S5*1*CL*30000*L*30000*CA*510*E~
L11*20216014100101*SI~
L11*3561004455*PO~
G62*10*20160516*I*0000*LT~
G62*10*20160516*K*2359*LT~
NTE*ADD*6~
N1*SF*GLANBIA FOODS INC*93*0002028601~
N3*236 WASHINGTON AVE S~
N4*TWIN FALLS*ID*83301*US~
G61*SH*LOAD PLANNER CONTACT*TE*Call Dispatch Office~
OID**3561004455**CA*30000*L*30000*E*510~
S5*2*CU*30000*L*30000*CA*510*E~
L11*20216014100102*SI~
L11*3561004455*PO~
G62*68*20160520*G*0000*LT~
G62*68*20160520*L*2359*LT~
NTE*ADD*6~
N1*ST*CEDAR GROVE*93*028787_0101~
N3*903 GROSSMAN STREET~
N4*SCHOFIELD*WI*54476-6103*US~
OID**3561004455**CA*30000*L*30000*E*510~
L3*30000*G*******51000*E~
SE*32*22450~

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.