X12 219 Logistics Service Request
This Draft Standard for Trial Use contains the format and establishes the data contents of the Logistics Service Request Transaction Set (219) for use within the context of an Electronic Data Interchange (EDI) environment. This set can be used by a shipper to transmit data to a logistics related organization to provide order detail relevant to upcoming transportation requirements.
- ~ Segment
- * Element
- > Component
- None included
Interchange Control Header
To start and identify an interchange of zero or more functional groups and interchange-related control segments
Code to identify the type of information in the Authorization Information
- 00
- No Authorization Information Present (No Meaningful Information in I02)
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)
Code to identify the type of information in the Security Information
- 00
- No Security Information Present (No Meaningful Information in I04)
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)
Qualifier to designate the system/method of code structure used to designate the sender or receiver ID element being qualified
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
Qualifier to designate the system/method of code structure used to designate the sender or receiver ID element being qualified
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
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
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
A control number assigned by the interchange sender
Code sent by the sender to request an interchange acknowledgment (TA1)
- 0
- No Acknowledgment Requested
- 1
- Interchange Acknowledgment Requested
Code to indicate whether data enclosed by this interchange envelope is test, production or information
- I
- Information
- P
- Production Data
- T
- Test Data
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
To indicate the beginning of a functional group and to provide control information
Code identifying a group of application related transaction sets
- AB
- Logistics Service Request (219)
Code identifying party sending transmission; codes agreed to by trading partners
Code identifying party receiving transmission. Codes agreed to by trading partners
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)
Assigned number originated and maintained by the sender
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
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
Transaction Set Header
To indicate the start of a transaction set and to assign a control number
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).
- 219
- Logistics Service Request
Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set
Beginning Segment for Logistics Services
To indicate the beginning of a logistics service transaction set
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.
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
- B901 is the logistics identification number.
Unique ID for this transaction (e.g. LSR ID) that can be used to check for duplicate submissions.
Code identifying purpose of transaction set
- 50
- Register
To provide such trading partner profile information as may be necessary to request registration as a trading partner in a system (e.g., be authorized to render quotes to the government)
Code identifying payment terms for transportation charges
- DE
- Per Contract
Destination with exceptions as agreed between buyer and seller
Service Request
To identify the specified logistics services requested
Code indicating the type of logistics service requested
- CT
- Contracted Services
Business Instructions and Reference Number
To specify instructions in this business relationship or a reference number
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
Code qualifying the Reference Identification
- BM
- Bill of Lading Number
If the Bill of Lading number that the consignor will use for the consignment is known in advance it can be communicated as part of the LSR
- CN
- Carrier's Reference Number (PRO/Invoice)
If authorized to pre-assign a carrier's Waybill or
PRO number - either from an allocated range or via an interactive service hosted by the shipping carrier - the pre-assigned ID can be communicated as part of the LSR.If not provided as part of the LSR, the shipping
carrier will issue an Id for the booking at the time it is registered in their system. - MCI
- Motor Carrier Identification Number
CommerceHub ID for the shipping carrier to whom the LSR is to be sent.
- ZC
- Connecting Carrier
Used to identify the SCAC for a connecting carrier (L11-01), and an optional trailer number (L11-03), for "dropoff" transfers.
- ZH
- Carrier Assigned Reference Number
Account number with the shipping carrier to whom the LSR is being sent for billing of freight charges.
A free-form description to clarify the related data elements and their content
Detail
Stop Off Details
To specify stop-off detail reference numbers and stop reason
- The 2000 Loop defines pickup or delivery information for an order.
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.
Identifying number for the specific stop and the sequence in which the stop is to be performed
Code specifying the reason for the stop
- AL
- Advance Loading
Carrier requested to hold a loaded trailer at carrier's facility or a place designated by the shipper for a brief period of time prior to delivery
- PL
- Part Load
- UL
- Unload
Date/Time
To specify pertinent dates and times
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
Code specifying type of date
- EP
- Earliest Pickup Date
Requested transfer date when a date window
needs to be conveyed as opposed to a specific
day. This element denotes the beginning of the
window and is used in conjunction with the "LP" qualified G62 which indicates the end of the window. If one of the "EP" or "LP" is present the
other is required. - LP
- Latest Pickup Date
Requested transfer date when a date window
needs to be conveyed as opposed to a specific
day. This element denotes the ending of the
window and is used in conjunction with the "EP" qualified G62 which indicates the start of the window. If one of the "EP" or "LP" is present the
other is required. - TR
- Transfer
Requested transfer date. This must be provided if the "EP" and "LP" qualified G62's are not.
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)
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
Name
To identify a party by type of organization, name, and code
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.
Code identifying an organizational entity, a physical location, property or an individual
- 45
- Drop-off Location
drop off contact / location
- CI
- Consignor
Consignor contact / address. This is the party in possession of the goods needing transport. This is optional in the LSR because the consigner
information can be obtained from the PO. - CN
- Consignee
Consignee contact / address. This is the party that will take possession of the goods when transport is complete. This is optional in the LSR because the consignee information will be stipulated on the PO.
- PW
- Pick Up Address
pick up contact / location
Code designating the system/method of code structure used for Identification Code (67)
- UL
- UCC/EAN Location Code
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.
Address Information
To specify the location of the named party
Geographic Location
To specify the geographic place of the named party
Free-form text for city name
- A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.
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.
Code defining international postal zone code excluding punctuation and blanks (zip code for United States)
Administrative Communications Contact
To identify a person or office to whom administrative communications should be directed
Code identifying the major duty or responsibility of the person or group named
- AG
- Agent
- FB
- Coordinator
Code identifying the type of communication number
- TE
- Telephone
Complete communications number including country or area code when applicable
Code identifying the type of communication number
- EM
- Electronic Mail
Complete communications number including country or area code when applicable
Assigned Number
To reference a line number in a transaction set
- The 2300 Loop provides details for tracking containers within an order.
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.
Number assigned for differentiation within a transaction set
Marks and Numbers
To indicate identifying marks and numbers for shipping containers
Use the MAN segment to identify the PO line number, quantity of product ordered, and SKUs
Code specifying the application or source of Marks and Numbers (87)
- MAN01/MAN02 and MAN04/MAN05 may be used to identify two different marks and numbers assigned to the same physical container.
- When MAN01 contains code "UC" (U.P.C. Shipping Container Code) and MAN05/MAN06 contain a range of ID numbers, MAN03 is not used. The reason for this is that the U.P.C. Shipping Container code is the same on every carton that is represented in the range in MAN05/MAN06.
- L
- Line Item Only
Marks and numbers used to identify a shipment or parts of a shipment
- When both MAN02 and MAN03 are used, MAN02 is the starting number of a sequential range and MAN03 is the ending number of that range.
PO Line number
Marks and numbers used to identify a shipment or parts of a shipment
- MAN03 and/or MAN06 are only used when sending a range(s) of ID numbers.
- When both MAN02/MAN03 and MAN05/MAN06 are used to send ranges of ID numbers, the integrity of the two ID numbers must be maintained.
Merchant sku
Code specifying the application or source of Marks and Numbers (87)
- ZZ
- Mutually Defined
Marks and numbers used to identify a shipment or parts of a shipment
- When both MAN05 and MAN06 are used, MAN05 is the starting number of a sequential range, and MAN06 is the ending number of that range.
Quantity ordered
Marks and numbers used to identify a shipment or parts of a shipment
Vendor sku
Buyer Identification
To specify instructions in this business relationship or a reference number
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
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
Code qualifying the Reference Identification
- YD
- Buyer Identification
Merchant ID
Purchase Order Number
To specify instructions in this business relationship or a reference number
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
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
Code qualifying the Reference Identification
- PO
- Purchase Order Number
PO number
Vendor ID Number
To specify instructions in this business relationship or a reference number
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
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
Code qualifying the Reference Identification
- VR
- Vendor ID Number
Vendor id. If not populated it is assumed to be the party submitting the LSR.
Summary
Total Weight and Charges
To specify the total shipment in terms of weight, volume, rates, charges, advances, and prepaid amounts applicable to one or more line items
The L3 segment is required by X12 but is not relevant for the LSR. Suppliers may populate the L3_01 with "0".
Transaction Set Trailer
To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)
Total number of segments included in a transaction set including ST and SE segments
Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set
Functional Group Trailer
To indicate the end of a functional group and to provide control information
Total number of transaction sets included in the functional group or interchange (transmission) group terminated by the trailer containing this data element
Assigned number originated and maintained by the sender
Interchange Control Trailer
To define the end of an interchange of zero or more functional groups and interchange-related control segments
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.