Skip to main content
All CollectionsX12 EDITransaction Sets200-299
X12 - 240 - Motor Carrier Package Status
X12 - 240 - Motor Carrier Package Status
Skylar Nguyen avatar
Written by Skylar Nguyen
Updated this week

Product: X12 EDI

Transaction: 240


240 - Motor Carrier Package Status

FUNCTIONAL GROUP=MZ

This X12 Transaction Set contains the format and establishes the data contents of the Motor Carrier Package Status Transaction Set (240) for use within the context of an Electronic Data Interchange (EDI) environment. This standard can be used to provide the status of a package, packages, or group of packages considered a shipment by a motor carrier.


SCHEMA


ST

Segment

Name

Position

ST

0100

BGN

Beginning Segment

0200

1000

2000

Segment

Name

Position

LX

Transaction Set Line Number

0100

2500

Segment

Name

Position

N1

0200

N2

0300

N3

0400

N4

0500

NM1

Individual or Organizational Name

0600

NTE

0700

2600

Segment

Name

Position

EFI

Electronic Format Identification

0800

BIN

Binary Data Segment

0900

2700

Segment

Name

Position

L11

Business Instructions and Reference Number

1000

MS2

Equipment or Container Owner and Type

1050

LS

Loop Header

1070

2710

Segment

Name

Position

MAN

1100

L11

Business Instructions and Reference Number

1150

AT7

Shipment Status Details

1200

CD3

Carton (Package) Detail

1300

NM1

Individual or Organizational Name

1350

Q7

Lading Exception Status

1400

LE

Loop Trailer

1420

2720

Segment

Name

Position

EFI

Electronic Format Identification

1440

BIN

Binary Data Segment

1460

SE

Segment

Name

Position

SE

Transaction Set Trailer

0100


COMMENTS


Notes

1/0300

This loop (1000) identifies the receiver(s) of the data.

2/0200

This loop (2500) provides the delivery address.

2/0700

The NTE is used to provide specific delivery information when a signature is not available.

2/0800

This loop (2600) provides the proof of delivery signature if captured upon delivery.

2/1000

This loop (2700) describes the package status.

rev 29/11/2024

Did this answer your question?