Dr Pepper Snapple(DPS) Group via Ryder EDI 204 Load Tender

Schema Reference

33 segments · X12 204 Motor Carrier Load Tender

ISA01 Authorization Information Qualifier

M ID 2-2

ISA02 Authorization Information

M AN 10-10

ISA03 Security Information Qualifier

M ID 2-2

ISA04 Security Information

M AN 10-10

ISA05 Interchange ID Qualifier

M ID 2-2

ISA06 Interchange Sender ID

M AN 15-15

ISA07 Interchange ID Qualifier

M ID 2-2

ISA08 Interchange Receiver ID

M AN 15-15

ISA09 Interchange Date

M DT 6-6

ISA10 Interchange Time

M TM 4-4

ISA11 Interchange Control Standards Identifier

M ID 1-1

ISA12 Interchange Control Version Number

M ID 5-5

ISA13 Interchange Control Number

M N0 9-9

ISA14 Acknowledgment Requested

M ID 1-1

ISA15 Usage Indicator

M ID 1-1

GS01 Functional Identifier Code

M ID 2-2

GS02 Application Sender's Code

M AN 2-15

GS03 Application Receiver's Code

M AN 2-15

GS04 Date

M DT 8-8

GS05 Time

M TM 4-8

GS06 Group Control Number

M N0 1-9

GS07 Responsible Agency Code

M ID 1-2

GS08 Version / Release / Industry Identifier Code

M AN 1-12

ST01 Transaction Set Identifier Code

M ID 3-3

ST02 Transaction Set Control Number

M AN 4-9

B202 Standard Carrier Alpha Code

O ID 2-4

B204 Shipment Identification Number

O AN 1-30

B205 Weight Unit Code

O ID 1-1

B206 Shipment Method of Payment

M ID 2-2

B207 Shipment Qualifier

O ID 1-1

B2A01 Transaction Set Purpose Code

M ID 2-2

B2A02 Application Type

O ID 2-2

L1101 Reference Identification

C AN 1-30

L1102 Reference Identification Qualifier

C ID 2-3

G6201 Date Qualifier

C ID 2-2

G6202 Date

C DT 8-8

G6203 Time Qualifier

C ID 1-2

G6204 Time

C TM 4-8

G6205 Time Code

O ID 2-2

AT501 Special Handling Code

C ID 2-3

AT502 Special Services Code

C ID 2-10

AT503 Special Handling Description

C AN 2-30

LH601 Name

O AN 1-60

LH602 Hazardous Certification Code

C ID 1-1

LH603 Hazardous Certification Declaration

C AN 1-25

LH604 Hazardous Certification Declaration

O AN 1-25

NTE02 Description

M AN 1-80

N1 Loop Repeat: 5

N101 Entity Identifier Code

M ID 2-3

N102 Name

C AN 1-60

N103 Identification Code Qualifier

C ID 1-2

N104 Identification Code

C AN 2-80

N301 Address Information

M AN 1-55

N302 Address Information

O AN 1-55

N401 City Name

O AN 2-30

N402 State or Province Code

O ID 2-2

N403 Postal Code

O ID 3-15

N404 Country Code

O ID 2-3

G6101 Contact Function Code

M ID 2-2

G6102 Name

M AN 1-60

G6103 Communication Number Qualifier

C ID 2-2

G6104 Communication Number

C AN 1-80

N7 Loop Repeat: 10

N701 Equipment Initial

O AN 1-4

N711 Equipment Description Code

O ID 2-2

N713 Temperature Control

O AN 3-6

N715 Equipment Length

O N0 4-5

N720 Height

O R 1-8

N721 Width

O R 1-8

S5 Loop Repeat: 999

S501 Stop Sequence Number

M N0 1-3

S502 Stop Reason Code

M ID 2-2

S503 Weight

C R 1-10

S504 Weight Unit Code

C ID 1-1

S505 Number of Units Shipped

C R 1-10

S506 Unit or Basis for Measurement Code

C ID 2-2

S507 Volume

C R 1-8

S508 Volume Unit Qualifier

C ID 1-1

L1101 Reference Identification

C AN 1-30

L1102 Reference Identification Qualifier

C ID 2-3

G6201 Date Qualifier

C ID 2-2

G6202 Date

C DT 8-8

G6203 Time Qualifier

C ID 1-2

G6204 Time

C TM 4-8

G6205 Time Code

O ID 2-2

PLD01 Quantity of Pallets Shipped

M N0 1-3

NTE02 Description

M AN 1-80

N1 Loop Repeat: 5

N101 Entity Identifier Code

M ID 2-3

N102 Name

C AN 1-60

N103 Identification Code Qualifier

C ID 1-2

N104 Identification Code

C AN 2-80

N201 Name

M AN 1-60

N202 Name

O AN 1-60

N301 Address Information

M AN 1-55

N302 Address Information

O AN 1-55

N401 City Name

O AN 2-30

N402 State or Province Code

O ID 2-2

N403 Postal Code

O ID 3-15

N404 Country Code

O ID 2-3

G6101 Contact Function Code

M ID 2-2

G6102 Name

M AN 1-60

G6103 Communication Number Qualifier

C ID 2-2

G6104 Communication Number

C AN 1-80

OID Loop Repeat: 999

OID01 Reference Identification

C AN 1-30

LAD01 Packaging Form Code

C ID 3-3

LAD02 Lading Quantity

C N0 1-7

LAD13 Lading Description

O AN 1-50

L5 Loop Repeat: 99

L502 Lading Description

O AN 1-50

L503 Commodity Code

C AN 1-30

L504 Commodity Code Qualifier

C ID 1-1

AT801 Weight Qualifier

C ID 1-2

AT802 Weight Unit Code

C ID 1-1

AT803 Weight

C R 1-10

AT804 Lading Quantity

O N0 1-7

AT805 Lading Quantity

O N0 1-7

AT806 Volume Unit Qualifier

C ID 1-1

AT807 Volume

C R 1-8

G61 Loop Repeat: 99

G6101 Contact Function Code

M ID 2-2

G6102 Name

M AN 1-60

G6103 Communication Number Qualifier

C ID 2-2

G6104 Communication Number

C AN 1-80

L1101 Reference Identification

C AN 1-30

L1102 Reference Identification Qualifier

C ID 2-3

L301 Weight

C R 1-10

L302 Weight Qualifier

C ID 1-2

L304 Rate/Value Qualifier

C ID 2-2

L305 Charge

O N2 1-12

L309 Volume

C R 1-8

L310 Volume Unit Qualifier

C ID 1-1

L311 Lading Quantity

O N0 1-7

L312 Weight Unit Code

O ID 1-1

L314 Declared Value

C N2 2-12

SE01 Number of Included Segments

M N0 1-10

SE02 Transaction Set Control Number

M AN 4-9

Dr Pepper Snapple(DPS) Group via Ryder EDI 204 FAQ

Common questions about 204 Motor Carrier Load Tender transactions with Dr Pepper Snapple(DPS) Group via Ryder.

How long does it take to set up Dr Pepper Snapple(DPS) Group via Ryder EDI with Stacksync?

Most suppliers are fully connected and processing live Dr Pepper Snapple(DPS) Group via Ryder EDI transactions within 3–5 business days. Stacksync's no-code setup means you don't need developers or EDI consultants — configure your field mappings through our visual interface, run a test cycle, and go live.

Do I need an existing VAN or AS2 connection to trade with Dr Pepper Snapple(DPS) Group via Ryder?

No. Stacksync handles the entire EDI transport layer. We connect directly to Dr Pepper Snapple(DPS) Group via Ryder's trading partner network through our certified connections. You don't need to manage a separate VAN subscription, AS2 certificates, or SFTP configurations.

How does Stacksync help with Dr Pepper Snapple(DPS) Group via Ryder compliance?

Stacksync improves compliance scores by eliminating manual processing delays. Purchase Orders sync to your system in real time, ASNs are generated automatically when you ship, and invoices are validated with three-way matching before submission. Real-time monitoring alerts you to issues before they become chargebacks.

What EDI document types does Stacksync support for Dr Pepper Snapple(DPS) Group via Ryder?

Stacksync supports all EDI document types required by Dr Pepper Snapple(DPS) Group via Ryder — including Purchase Orders (850), Invoices (810), ASNs (856), PO Acknowledgments (855), and more. Our platform handles the full lifecycle from order to payment automatically.

Can I connect Dr Pepper Snapple(DPS) Group via Ryder EDI to my existing ERP or WMS?

Yes. Stacksync integrates with any system that has a database or API — including SAP, Oracle, NetSuite, Microsoft Dynamics, and custom-built ERPs. Data flows bidirectionally between Dr Pepper Snapple(DPS) Group via Ryder's EDI network and your system in real time.

What happens when Dr Pepper Snapple(DPS) Group via Ryder updates their EDI specifications?

Stacksync monitors Dr Pepper Snapple(DPS) Group via Ryder's EDI spec changes and updates our mappings proactively. When a change affects your integration, we notify you and apply updates — so you stay compliant without scrambling to decode new implementation guides.