3PL Integration

From UG

Revision as of 15:15, 9 March 2017 by Andrei (Talk | contribs)
Jump to: navigation, search


Contents

Info

parent: 4227

See Also

Reference

  • DISA serves as the Secretariat for ANSI ASC X12 and their X12 EDI and XML standards development process.

EDI documents

It is suggested to use the following EDI documents of X12 per Transport Mode:

  • Air
  • 104 - Air Shipment Information.
Transmits bill of lading and rating details about an air carrier shipment. This transaction set tells the air carrier 1) sender data, 2) shipment detail for multiple and single piece shipments, 3) consignee and third-party data, 4) detail and related charges for each shipment, and 5) shipment totals.
  • 110 - Air Freight Details and Invoice.
Gives a customer an air invoice for transportation and other charges pertaining to shipments. This includes: Original Invoices, Past Due Billings, Balance Due Bills and Revisions.
  • Trucking
  • 204 - Motor Carrier Load Tender.
Allows shippers or others to offer (tender) a shipment to a full load (truckload) motor carrier. It can include detailed scheduling, equipment requirements, commodities, and shipping instructions that are relevant to a load tender.
  • 210 - Motor Carrier Freight Details and Invoice.
Allows shippers or others that wish to contract with a motor carrier to provide a legal bill of lading for a shipment. It is not to be used to provide motor carriers with information about a load tender, pick-up manifest, or appointment scheduling.
  • 214 - Transportation Carrier Shipment Status Message.
Used by a transportation carrier to tell shippers, consignees, and their agents about the status of shipments; that is: dates, times, locations, route, identifying numbers, and conveyance.
  • 990 - Response to a Load Tender.
Provides general information relative to a specific shipment, or as a response to a Motor Carrier Load Tender Transaction Set (204) that was used as a load tender.
  • Ocean
  • 300 - Reservation (Booking Request) (Ocean).
A shipper or forwarder uses this to reserve space, containers and equipment for transport by ocean vessel.
  • 301 - Confirmation (Ocean).
Provides all the information an ocean carrier needs to confirm space, container, and equipment availability in response to the Reservation (Booking Request) (Ocean) Transaction Set (300); or to notify other parties such as terminal operators or other ocean carriers.
  • 303 - Booking Cancellation (Ocean).
Specifies all the information a shipper or forwarder requires to cancel a previous booking request.
  • 304 - Shipping Instructions.
Provides all the information needed to prepare and distribute a contact of carriage like an ocean bill of lading, sea waybill and other shipping documents. When transmitted to a freight forwarder or customs broker, it provides the shipping and financial information that the forwarder or customs broker requires in order to move cargo and provide the requested services.
  • 310 - Freight Receipt and Invoice (Ocean).
Provides ocean bill of lading information. It is transmitted by ocean carriers and can serve as the receipt for the shipment or as an invoice for freight. It can also take the place of a paper bill of lading; or can enable the shipper or forwarder to verify bill of lading information before an original is printed and released. Similarly, it can be used for information purposes (as a bill of lading copy), or to convey manifest information to a terminal operator.
  • 315 - Status Details (Ocean).
Provides the information required to report status or event details for specified shipments or containers. It can specify the details for one status or event associated with multiple shipments or containers, or for multiple statuses or events for one shipment or container.
  • Common docs
  • 997 - Functional Acknowledgment.
Used to define the control structures for a set of acknowledgments to indicate the results of the syntactical analysis of the electronically encoded documents. The encoded documents are the transaction sets, which are grouped in functional groups, used in defining transactions for business data interchange. Does not cover the semantic meaning of the information encoded in the transaction sets.

EDI documents flow

EDI projects

SOWs

Retrieved from "https://wiki.jaguarfreight.com/3PL_Integration"
Personal tools