Best Buy
/
Transportation Appointment Schedule Information (Inbound)
  • Specification
  • EDI Inspector
Import guide into your account
Stedi maintains this guide based on public documentation from Best Buy. Contact Best Buy for official EDI specifications. To report any errors in this guide, please contact us.
Go to Stedi Network
Best Buy logo

X12 163 Transportation Appointment Schedule Information (Inbound)

X12 Release 4030

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.

Delimiters
  • ~ Segment
  • * Element
  • > Component
  • ^ Repetition
EDI samples
  • Appointment Request 1
View the latest version of this implementation guide as an interactive webpage
https://www.stedi.com/app/guides/view/best-buy/transportation-appointment-schedule-information-inbound/01GWA34PWASATS97AS9K0EC7BK
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
0100
Transaction Set Header
Max use 1
Required
B13
0200
Beginning Segment for Appointment Schedule
Max use 1
Required
B2A
0300
Set Purpose
Max use 1
Required
H6
0400
Special Services
Max use 5
Optional
N7
0500
Equipment Details
Max use 3
Optional
0100 Loop
0300 Loop
SE
2900
Transaction Set Trailer
Max use 1
Required
GE
-
Functional Group Trailer
Max use 1
Required
IEA
-
Interchange Control Trailer
Max use 1
Required
ISA

Interchange Control Header

RequiredMax use 1

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

Example
ISA-01
I01
Authorization Information Qualifier
Required
Identifier (ID)

Code identifying the type of information in the Authorization Information

00
No Authorization Information Present (No Meaningful Information in I02)
ISA-02
I02
Authorization Information
Required
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 identifying the type of information in the Security Information

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

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

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

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

Codes
ISA-08
I07
Interchange Receiver ID
Required
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
I65
Repetition Separator
Required
String (AN)
Min 1Max 1

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

^
Repetition Separator
ISA-12
I11
Interchange Control Version Number
Required
Identifier (ID)

Code specifying the version number of the interchange control segments

00403
Draft Standards for Trial Use Approved for Publication by ASC X12 Procedures Review Board through October 1999
ISA-13
I12
Interchange Control Number
Required
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 indicating sender's request for an interchange acknowledgment

0
No Acknowledgment Requested
1
Interchange Acknowledgment Requested
ISA-15
I14
Usage Indicator
Required
Identifier (ID)
Min 1Max 1

Code indicating whether data enclosed by this interchange envelope is test, production or information

I
Information
P
Production Data
T
Test Data
ISA-16
I15
Component Element Separator
Required
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

AS
Transportation Appointment Schedule Information (163)
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

Required
Date (DT)
CCYYMMDD format

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

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 identifying the issuer of the standard; this code is used in conjunction with Data Element 480

T
Transportation Data Coordinating Committee (TDCC)
X
Accredited Standards Committee X12
GS-08
480
Version / Release / Industry Identifier Code
Required
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

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

Heading

ST
0100
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) 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
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

B13
0200
Heading > B13

Beginning Segment for Appointment Schedule

RequiredMax use 1

To transmit identifying numbers and other basic data relating to the Appointment Schedule transaction set

Usage notes

Example Data: B13UniqueDociDSCAC~

Example
B13-01
127
Reference Identification
Required
String (AN)
Min 1Max 50

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.
Usage notes

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.

B13-02
140
Standard Carrier Alpha Code
Optional
Identifier (ID)
Min 2Max 4

Standard Carrier Alpha Code

  • B1302 is the Standard Carrier Alpha Code (SCAC) of the carrier who will be keeping the appointment.
Usage notes

This should contain the SCAC of the carrier requesting the appointment and ultimately responsible for the delivery of the shipment.

B2A
0300
Heading > B2A

Set Purpose

RequiredMax use 1

To allow for positive identification of transaction set purpose

Usage notes

Example Data: B2A13AT~

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

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.

B2A-02
346
Application Type
Optional
Identifier (ID)

Code identifying an application

AT
Appointment
H6
0400
Heading > H6

Special Services

OptionalMax use 5

To identify forms of unitization, liability issues, and special services

Usage notes

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~

Example
H6-07
108
Pick-up or Delivery Code
Optional
Identifier (ID)

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.

N7
0500
Heading > N7

Equipment Details

OptionalMax use 3

To identify the equipment

Usage notes

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~

Example
N7-01
206
Equipment Initial
Optional
String (AN)
Min 1Max 4

Prefix or alphabetic part of an equipment unit's identifying number

  • N701 is mandatory for rail transactions.
Usage notes

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.

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

The Trailer/Container ID in this element should be mapped/returned in the MS202 element of the 214 Shipment status message.

0100 Loop
RequiredMax >1
Usage notes

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.

N1
1000
Heading > 0100 Loop > N1

Name

RequiredMax use 1

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

Usage notes

Example Data: N1CACarrier name~

Example
N1-01
98
Entity Identifier Code
Required
Identifier (ID)

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

CA
Carrier
Required
String (AN)
Min 1Max 60

Free-form name

Usage notes

This element should contain the name of the carrier to whom the carrier
contact listed in the G61 is associated with.

G61
1500
Heading > 0100 Loop > G61

Contact

RequiredMax use 5

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

Usage notes

Example Data: G61A5Name of ContactEMNameofContact@carrier.com~

Example
G61-01
366
Contact Function Code
Required
Identifier (ID)

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

Usage notes

This element is used to indicate that the contact information should be for the party that is requesting the appointment.

A5
Appointment Scheduler
Required
String (AN)
Min 1Max 60

Free-form name

Usage notes

This element should contain the name of the person or group associated with the carrier who is responsible for the appointment request.

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

Code identifying the type of communication number

  • G6103 qualifies G6104.
Usage notes

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
G61-04
364
Communication Number
Required
String (AN)
Min 1Max 256

Complete communications number including country or area code when applicable

Usage notes

Best Buy is expecting an email address for the parties indicated in this
segment to be sent here.

0100 Loop end
0300 Loop
OptionalMax >1
Usage notes

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 .

S5
1900
Heading > 0300 Loop > S5

Stop-off Details

RequiredMax use 1

To specify stop-off detail reference numbers and stop reason

Usage notes

Example Data: S51CU~

Example
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

This should be a sequential number, preferably starting off at 1.

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

Code specifying the reason for the stop

CU
Complete Unload
N1
2000
Heading > 0300 Loop > N1

Name

OptionalMax use 1

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

Usage notes

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~

Example
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

ST
Ship To
N1-03
66
Identification Code Qualifier
Required
Identifier (ID)

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

94
Code assigned by the organization that is the ultimate destination of the transaction set
N1-04
67
Identification Code
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

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.

N9
2400
Heading > 0300 Loop > N9

Reference Identification

RequiredMax use 10

To transmit identifying information as specified by the Reference Identification Qualifier

Usage notes

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~

Example
N9-01
128
Reference Identification Qualifier
Required
Identifier (ID)

Code qualifying the Reference Identification

Usage notes

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
N9-02
127
Reference Identification
Optional
String (AN)
Min 1Max 50

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

G62
2600
Heading > 0300 Loop > G62

Date/Time

RequiredMax use 10

To specify pertinent dates and times

Usage notes

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.

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

Code specifying type of date

68
Requested Delivery Date
Optional
Date (DT)
CCYYMMDD format

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

G62-03
176
Time Qualifier
Required
Identifier (ID)

Code specifying the reported time

Z
Requested Delivery 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)

0350 Loop
OptionalMax >1
Usage notes

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.

OID
2700
Heading > 0300 Loop > 0350 Loop > OID

Order Identification Detail

RequiredMax use 1

To specify order identification detail

Usage notes

Example Data: OIDBestBuyPOCTN245L*18000~

Example
If either Packaging Form 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
OID-02
324
Purchase Order Number
Required
String (AN)
Min 1Max 22

Identifying number for Purchase Order assigned by the orderer/purchaser

Usage notes

This element should contain the Best Buy Purchase Order or similar reference number (Transfer ID, RTV (Return to Vendor Authorization number) etc) that has been assigned to all or some of the Logistical shipping/handling units on the shipment.

OID-04
211
Packaging Form Code
Required
Identifier (ID)

Code for packaging form of the lading quantity

Usage notes

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
OID-05
380
Quantity
Optional
Decimal number (R)
Min 1Max 15

Numeric value of quantity

Usage notes

This is the actual numerical quantity of the Logistical shipping/handling units being moved on the shipment under the Reference ID indicated in the OID02.

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

Code specifying the weight unit

Usage notes

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
OID-07
81
Weight
Optional
Decimal number (R)
Min 1Max 10

Numeric value of weight

Usage notes

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.

0350 Loop end
0300 Loop end
SE
2900
Heading > 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

Heading 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

Appointment Request 1

ST*163*0001~
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

ST*163*0001~
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

ST*163*0001~
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.