X12 163 Transportation Appointment Schedule Information (Inbound)
This Draft Standard for Trial Use contains the format and establishes the data contents of the Transportation Appointment Schedule Information Transaction Set (163) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used by transportation carriers and their trading partners to request and accept freight pick-up and delivery appointments.
- ~ Segment
- * Element
- > Component
- ^ Repetition
Interchange Control Header
To start and identify an interchange of zero or more functional groups and interchange-related control segments
Code identifying 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 identifying 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)
Code indicating 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
Code indicating 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
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
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
A control number assigned by the interchange sender
Code indicating sender's request for an interchange acknowledgment
- 0
- No Acknowledgment Requested
- 1
- Interchange Acknowledgment Requested
Code indicating 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
- AS
- Transportation Appointment Schedule Information (163)
Code identifying party sending transmission; codes agreed to by trading partners
Code identifying party receiving transmission; codes agreed to by trading partners
Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year
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 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
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
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) 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).
- 163
- Transportation Appointment Schedule Information
Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set
Beginning Segment for Appointment Schedule
To transmit identifying numbers and other basic data relating to the Appointment Schedule transaction set
Example Data: B13UniqueDociDSCAC~
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
- B1301 is the appointment pick-up or delivery request reference number. It is a number assigned by the party requesting the original appointment that uniquely identifies the request for a pick-up or delivery appointment. It is not a unique appointment number.
This needs to be a unique ID created by the requestor/originator of the
appointment request. This unique ID will be returned as the unique reference ID on subsequent responses (i. e. request for reschedules, granted appointments. appointment request rejections, Replacement to a rejected appointment request) related to this appointment process. It can be a BOL or a Carrier PRO/Load ID as long as it is unique and not used for any other appointment requests.
Standard Carrier Alpha Code
- B1302 is the Standard Carrier Alpha Code (SCAC) of the carrier who will be keeping the appointment.
This should contain the SCAC of the carrier requesting the appointment and ultimately responsible for the delivery of the shipment.
Set Purpose
To allow for positive identification of transaction set purpose
Example Data: B2A13AT~
Code identifying purpose of transaction set
- 01
- Cancellation
Should be used when attempting to cancel an already granted delivery appointment. This should only be done if the Load will no longer be delivering to Best Buy at any time in the future.
- 05
- Replace
Should be sent here when responding with full replacement of the originally transmitted appointment request, with the indicated corrections, in response to a rejection 163 from Best Buy for an initial request for an appointment.
- 13
- Request
Should always be sent here when requesting an appointment for the first time for a shipment where Best Buy is not paying the Freight.
- 18
- Reissue
Should be used here when requesting a reschedule of an already granted delivery appointment.
Special Services
To identify forms of unitization, liability issues, and special services
This segment should be used to indicate that you intend to exercise your right to drop trailers or request a live delivery appointment, if you are granted the ability by Best Buy at the facility indicated in the N1 segment in the 300 Loop.
Example Data: H6*******DT~
Specifies the location or type of pickup or delivery
- DT
- Drop Trailer
Should be used to indicate your intention to drop the trailer at the destination Best Buy facility that this appointment request is for.
- LD
- Live Delivery
Should be used if you are looking for a live delivery appointment at the destination Best Buy facility that this appointment request is for.
Equipment Details
To identify the equipment
This segment should contain the carrier's Trailer/Container ID of the shipment will be delivered for the appointment request being referenced.
Example Data: N7SCAC123467890~
Prefix or alphabetic part of an equipment unit's identifying number
- N701 is mandatory for rail transactions.
This element will be blank in most cases unless the alpha code is actually
visible on the trailer/container (This might also be the Carrier SCAC Code for the carrier responsible for the equipment) If present, this element should be return/mapped to the MS201 Element of the EDI 214 Shipment status message.
Sequencing or serial part of an equipment unit's identifying number (pure numeric form for equipment number is preferred)
The Trailer/Container ID in this element should be mapped/returned in the MS202 element of the 214 Shipment status message.
This Name Loop at the Header level will be used to define the carriers contact and email information or the appointment request being submitted. Best Buy is expecting only a single Name (Loop 100) Loop at the Header level with the contact information of the person/group responsible for requesting the delivery appointment.
Name
To identify a party by type of organization, name, and code
Example Data: N1CACarrier name~
Code identifying an organizational entity, a physical location, property or an individual
- CA
- Carrier
Free-form name
This element should contain the name of the carrier to whom the carrier
contact listed in the G61 is associated with.
Contact
To identify a person or office to whom communications should be directed
Example Data: G61A5Name of ContactEMNameofContact@carrier.com~
Code identifying the major duty or responsibility of the person or group named
This element is used to indicate that the contact information should be for the party that is requesting the appointment.
- A5
- Appointment Scheduler
Free-form name
This element should contain the name of the person or group associated with the carrier who is responsible for the appointment request.
Code identifying the type of communication number
- G6103 qualifies G6104.
This element is used to define the information in the G6104 element. Best Buy is expecting code "EM" for email and an email address post in the G6104 for the contact party.
- EM
- Electronic Mail
Complete communications number including country or area code when applicable
Best Buy is expecting an email address for the parties indicated in this
segment to be sent here.
The 300 (S5) Loop will be used to identify the destination location, provide the requested date and time the carrier would like the appointment for, and provide the shipment order detail information.
Best Buy allows for only a single destination/stop off point for each appointment request. Typically that should only entail a single 300 (S5) Loop.
If the carrier has freight that has come from multiple pickup points and is being delivered to a single Best Buy ship to location on a single trailer, using multiple S5 loops is allowed. This will provide the detail information breakdown for different BOL IDs coming from the different pickup locations. However the N1 segment, with the Best Buy location and the G62 segment for the date and time of the appointment request, must be repeated under each 300 (S5) loops .
Stop-off Details
To specify stop-off detail reference numbers and stop reason
Example Data: S51CU~
Identifying number for the specific stop and the sequence in which the stop is to be performed
This should be a sequential number, preferably starting off at 1.
Code specifying the reason for the stop
- CU
- Complete Unload
Name
To identify a party by type of organization, name, and code
Each occurrence of the Name segment will contain the Best Buy delivery location. It is expected that there is only a single iteration of this segment
Example Data: N1ST**94BBYLocID~
Code identifying an organizational entity, a physical location, property or an individual
- ST
- Ship To
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
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.
The N104 element should contain the Best Buy assigned Location ID that the Transportation Shipment Request is being submitted to receive a delivery appointment at.
Reference Identification
To transmit identifying information as specified by the Reference Identification Qualifier
An N9 segment is required on all EDI 163 Transportation Appointment messages where Best Buy is paying for the freight charges. For shipments where Best Buy has transmitted a 204 Load Tender there should be two iterations of the N9 segment.
The first iteration should contain the Best Buy TMS load ID (also known as CID (Unique Consignee ID) or SID (Unique Shipper ID) from VICS)) and the N901 must contain the "BN" qualifier, found in the B204 element, from
the Load Tender which should be mapped to the N902.
The second iteration should contain the Carriers PRO/Load/ID, for the Load this EDI 163 Transportation Request is being sent in for. The N902 should contain the Carriers PRO/Load ID and the N901 should contain the qualifier "CN". This is required to be sent for all EDI 163 Appointment Requests for freight where Best Buy is not paying the freight charges.
In addition, Best Buy expects the Bill of lading (N901 = "BM") and/or the Best Buy Dock Appointment ID (N901 = "AO"), if it is known, to be sent here.
Under special circumstances where the carrier is requesting a reschedule of an already existing appointment.(B2A01 code "18"). Best Buy is mandating that an additional N9 segment is sent with a Resubmission
Reason Code. The N901 should be populated with code "G7" and the N902 should contain a reason code provided below.
G7 Custom Code List when rescheduling an already existing appointment
AO - Weather
CR - Carrier Reschedule
VI - Vendor issue
BH - Transit Time
BO - Rail Delay
MA - missed appointment
Example Data:
Here is an N9 segment with Best Buy TMS Load ID
L11BN654321~
Here is an N9 segment with Carrier PRO/Load ID
L11CNCarrierPRO1~
Here is an N9 segment with Best Buy Dock Appointment ID
L11AO999999~
Here is an N9 segment with Bill of Lading ID
L11BMBOLID999999~
Here is an N9 segment with with Resubmission Reason code
L11G7CR~
Code qualifying the Reference Identification
If the N902 value is the Best Buy Load ID then the N901 should use the
qualifier "BN".
If the N902 value is the Bill of Lading ID then the N901 should use the qualifier "BM" .
If the N902 value is the Dock Appointment ID then the N901 should use the qualifier "AO".
If the N902 value is the Carrier PRO/Load ID then the N901 should use the qualifier "CN" .
If the N902 value is the Resubmission Reason Code from the custom list then the N901 should use the qualifier "G7" .
- AO
- Appointment Number
- BM
- Bill of Lading Number
- BN
- Booking Number
- CN
- Carrier's Reference Number (PRO/Invoice)
- G7
- Resubmission Reason Code
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
Date/Time
To specify pertinent dates and times
The G6201 qualifier "68" refers to the requested delivery date that the carrier is looking to deliver the freight on, in the G6202. The G6203 qualifier "Z" refers to the requested delivery time in the G6204, on the day transmitted in the G6202.
Example Data: G626820100520Z1200~
This date and Time is required on all EDI 163 Transportation Appointment Request types sent in by a carrier.
Code specifying type of date
- 68
- Requested Delivery Date
Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year
Code specifying the reported time
- Z
- Requested Delivery Time
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)
The values in the OID/350 Loop describe each individual order/shipment in the carrier shipment identified in the B1301 and/or N9 elements.
Each occurrence of this Loop should include one individual order/shipment that has been or will be loaded/unloaded at the stop off/freight point indicated in the N104 within 300 loop.
Order Identification Detail
To specify order identification detail
Example Data: OIDBestBuyPOCTN245L*18000~
Identifying number for Purchase Order assigned by the orderer/purchaser
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.
Code for packaging form of the lading quantity
This should 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 almost all cases the qualifier should be "CTN".
- CTN
- Carton
Numeric value of quantity
This is the actual numerical quantity of the Logistical shipping/handling units being moved on the shipment under the Reference ID indicated in the OID02.
Code specifying the weight unit
This should contain the qualifier that defines the type of weight units used for the logistical shipping/handling units 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.
- K
- Kilograms
- L
- Pounds
Numeric value of weight
This is the actual numerical weight for the logistical shipping/handling units being moved on the shipment under the Reference ID indicated in the OID02.
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
Appointment Request 1
B13*UniqueID1*SCAC~
B2A*13*AT~
H6*******DT~
N7*SCAC*TrailerID~
N1*CA*Carrier Name~
G61*A5*Name Of Contact*EM*name.contact@carriername.com~
S5*1*CU~
N1*ST**94*70~
N9*BM*Bill of Lading ID~
N9*CN*Carrier PRO/Load ID~
G62*68*20180426*Z*1400~
OID**ABCDEF**CTN*287*L*2000~
OID**FEDCBA**CTN*500~
OID**ZYXWVU**CTN*1200~
OID**999999**CTN*100*L*20000~
OID**PONID1**CTN*287~
SE*18*0001~
Appointment Request 2
B13*UniqueID1*SCAC~
B2A*18*AT~
H6*******DT~
N7*SCAC*TrailerID~
N1*CA*Carrier Name~
G61*A5*Name Of Contact*EM*name.contact@carriername.com~
S5*1*CU~
N1*ST**94*70~
N9*BM*Bill of Lading ID~
N9*CN*Carrier PRO/Load ID~
N9*G7*VI~
N9*AO*DOCKSCHEDID1~
G62*68*20180430*Z*1200~
OID**ABCDEF**CTN*287*L*2000~
OID**FEDCBA**CTN*500~
OID**ZYXWVU**CTN*1200~
OID**999999**CTN*100*L*20000~
OID**PONID1**CTN*287~
SE*20*0001~
Appointment Request 3
B13*UniqueID20*SCAC~
B2A*05*AT~
H6*******DT~
N7*SCAC*TrailerID~
N1*CA*Carrier Name~
G61*A5*Name Of Contact*EM*name.contact@carriername.com~
S5*1*CU~
N1*ST**94*70~
N9*BM*Bill of Lading ID30~
N9*CN*Carrier PRO/Load ID30~
G62*68*20180426*Z*1200~
OID**BADPO1**CTN*287*L*2000~
OID**MANBAT**CTN*500~
OID**DEDPOL**CTN*1200~
OID**999999**CTN*100*L*20000~
OID**PONID1**CTN*287~
SE*18*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.