219 Logistics Service Request
One Kings Lane · X12 004010
One Kings Lane’s published 219 specification, rendered as an interactive guide. Expand any segment to see its elements, data types, lengths and accepted codes — then validate your own document against it below.
Specification
17 of 17 segments
HEADING
ST
Transaction Set Header ST
pos 010
Optional
max —
B9
Beginning Segment For Logistics Services B9
Used to identify a Logistic Service Request (LSR) in the supplier's Transportation Management System (TMS).
Several aspects of the rules for populating the 219 depend on how the consignment is to be transferred to the carrier to which this LSR is being sent.
An LSR is considered to be a "pickup" transfer if the carrier to whom the LSR is sent is responsible for the pickup of the consignment from the consignor's facility.
An LSR is considered to be a "dropoff" transfer if the carrier to whom the LSR is sent will receive the consignment at one of the terminals that it operates. With a "dropoff" LSR, the consignor is responsible for transporting the consignment from its facility to the carrier's terminal.
See the notes on the N1-01 qualifiers in the 2100 (N1) loop for an explanation of the coding used to stipulate "pickup" or "dropoff" transfer.
pos 020
Required
max —
B9A
Service Request B9A
pos 030
Required
max 7
L11
Business Instructions And Reference Number L11
pos 040
Required
max 99
DETAIL
2000 Looprequired
S5
Stop Off Details S5
The 219 is a 'stop' oriented document. Each instance of the detail level 2000 loop provides details about the logistic service that is being requested.
The 2000 loops are indexed by the numeric value of the Stop Sequence Number (S5-01) along with a Stop Reason Code (S5-02). A well-formed 219 LSR will have one or more 2000 loops, each with a specific purpose. The function of a 2000 loop is indicated with the following values in the S5 01/02 elements:
When S5 01/02 = . . .
0/AL - this (optional) 2000 loop provides the consignor information in the 2100 (N1) loop. This instance of the 2000 loop is not required because the Purchase Order being identified in the LSR (using the L11 segments of the 2300 loop) is stored in the CommerceHub system and already has this information. When the LSR is sent out to the designated carrier (i.e. the carrier identified in the "MCI" qualified L11) the consignor information will be taken from the Purchase Order and sent to the carrier as part of the LSR.
1/PL - this (required) 2000 loop provides the details (what, when, where) about the transfer of the consignment to the carrier that is receiving this LSR. This is where the transfer will be stipulated as either "pickup" or "dropoff".
3/UL - this (optional) 2000 loop provides the consignee information in the 2100 (N1) loop. This instance of the 2000 loop is not required because the Purchase Order being identified in the LSR (using the L11 segments of the 2300 loop) is stored in the CommerceHub system and already has this information. When the LSR is sent out to the designated carrier (i.e. the carrier identified in the "MCI" qualified L11) the consignee information will be taken from the Purchase Order and sent to the carrier as part of the LSR.
pos 010
Required
max —
G62
Date Time G62
The G62 segment is only used in the 2000 loop where the S5 01/02 value pair is 1/PL. It is used to schedule the transfer of the consignment to the carrier receiving the LSR.
In "pickup" transfers, the date/time values in the G62 should reflect the consignor's expectation as to when the transfer will take place at its facility.
In "dropoff" transfers, the date/time values in the G62 should reflect the consignor's expectation as to when the connecting (intermediary) carrier will transfer the consignment to the carrier receiving the LSR at the receiving carrier's terminal.
The expected time for the transfer is expressed using one or two G62 segments, qualified as follows:
TR - a single G62 to set the requested date for consignment transfer
or
EP - a G62 to set the beginning of acceptable window for consignment transfer
LP - a G62 to set the end of acceptable window for consignment transfer
pos 020
Required
max 2
2100 Looprequired
N1
Name N1
The optional "CI" qualified N1 loop is only valid in the the 2000 loop where the S5 01/02 value pair is 0/AL.
A "PW" or "45" qualified N1 loop must be present is the 2000 loop where the S5 01/02 value pair is 1/PL. This is what stipulates "pickup" or "dropoff" transfer.
The optional "CN" qualified N1 loop is only valid in the 2000 loop where the S5 01/02 value pair is 3/UL.
pos 050
Required
max —
N3
Address Information N3
pos 070
Required
max 2
N4
Geographic Location N4
pos 080
Required
max —
PER
Administrative Communications Contact PER
pos 090
Optional
max 3
2300 Looprequired
LX
Assigned Number LX
The 2300 loop is only used in the 2000 loop where the S5 01/02 value pair is 1/PL.
The 2300 loop is used to identify the lines of a Purchase Order for which the Logistic Service Request applies. The LX-01 values should begin at 1 and increment by one for each instance of the 2300 loop. The LX-01 values have no correlation to PO line numbers.
pos 200
Required
max —
MAN
Marks And Numbers MAN
Use the MAN segment to identify the PO line number, quantity of product ordered, and SKUs
pos 220
Required
max 10
L11
Buyer Identificationvariant 1 of 3
Use the L11 segments in this loop to identify the Purchase Order number,
a merchant that issued the PO, and the supplier to whom it was issued
pos 260
Required
max 10
L11
Purchase Order Numbervariant 2 of 3
Use the L11 segments in this loop to identify the Purchase Order number,
a merchant that issued the PO, and the supplier to whom it was issued
pos 260
Required
max 10
L11
Vendor ID Numbervariant 3 of 3
Use the L11 segments in this loop to identify the Purchase Order number,
a merchant that issued the PO, and the supplier to whom it was issued
pos 260
Required
max 10
SUMMARY
L3
Total Weight And Charges L3
The L3 segment is required by X12 but is not relevant for the LSR. Suppliers may populate the L3_01 with "0".
pos 010
Required
max —
SE
Transaction Set Trailer SE
pos 020
Optional
max —
Validate a 219
Paste or upload a document and check it against One Kings Lane’s published rules — segment order and repetition, required elements, field lengths, data types and accepted codes. Nothing is stored.
Go live on One Kings Lane’s 219 in days, not months
Weredi maps this guide to your ERP, runs the test cycle with One Kings Lane, and keeps the spec current as it changes.