3PL Integration
From UG
(Difference between revisions)
(→Info) |
(→Reference) |
||
| (22 intermediate revisions not shown) | |||
| Line 1: | Line 1: | ||
| - | [[Category: | + | [[Category:3PL Integration]] |
== Info == | == Info == | ||
| - | parent: 4227 | + | parent: [http://mantis.jaguarfreight.com/mantis/view.php?id=4227 4227] |
=== See Also === | === See Also === | ||
| Line 13: | Line 13: | ||
* [http://en.wikipedia.org/wiki/Electronic_data_interchange Electronic data interchange (EDI)] | * [http://en.wikipedia.org/wiki/Electronic_data_interchange Electronic data interchange (EDI)] | ||
| - | * http://en.wikipedia.org/wiki/XML_Schema_%28W3C%29 | + | * [http://en.wikipedia.org/wiki/XML_Schema_%28W3C%29 XML Schema (W3C)] |
* [http://en.wikipedia.org/wiki/ASC_X12 ANSI ASC X12 (X12)] - US EDI standard | * [http://en.wikipedia.org/wiki/ASC_X12 ANSI ASC X12 (X12)] - US EDI standard | ||
| - | * [http://en.wikipedia.org/wiki/X12_Document_List#Transportation X12 Document List for Transportation] | + | :* [http://en.wikipedia.org/wiki/X12_Document_List#Transportation X12 Document List for Transportation] |
| - | * [http://en.wikipedia.org/wiki/Data_Interchange_Standards_Association DISA | + | :* [http://www.1edisource.com/transaction-sets-x12 Complete List of X12 EDI T-Sets] |
| + | * [http://en.wikipedia.org/wiki/Data_Interchange_Standards_Association DISA - Data Interchange Standards Association] | ||
:* DISA serves as the Secretariat for ANSI ASC X12 and their X12 EDI and XML standards development process. | :* DISA serves as the Secretariat for ANSI ASC X12 and their X12 EDI and XML standards development process. | ||
| Line 23: | Line 24: | ||
It is suggested to use the following EDI documents of X12 per Transport Mode: | It is suggested to use the following EDI documents of X12 per Transport Mode: | ||
| - | * Air | + | * '''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. |
| - | * Trucking | + | :* '''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. |
| - | * Ocean | + | : 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. |
| - | * Common docs | + | * '''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 documents flow == | ||
| - | * ... | + | * [http://mantis.jaguarfreight.com/mantis/view.php?id=4528 0004528]: EDI documents flow |
| + | |||
| + | == EDI projects == | ||
| + | * [http://mantis.jaguarfreight.com/mantis/view.php?id=4558 0004558]: EDI: Integration Overton, FPA | ||
| + | * [http://mantis.jaguarfreight.com/mantis/view.php?id=4572 0004572]: EDI to DSV:France | ||
| + | * [http://mantis.jaguarfreight.com/mantis/view.php?id=4573 0004573]: [[EDI_to_Evergreen#SOW_1_EDI_to_Evergreen |EDI to Evergreen]] | ||
| + | * [http://mantis.jaguarfreight.com/mantis/view.php?id=4582 0004582]: [[EDI_to_BDP#SOW_1_EDI_to_BDP |EDI to BDP]] | ||
| + | * [http://mantis.jaguarfreight.com/mantis/view.php?id=4708 0004708]: [[EDI to OOCL#SOW_1_EDI to OOCL |EDI to OOCL]] | ||
| + | * [http://mantis.jaguarfreight.com/mantis/view.php?id=4742 0004742]: [[EDI to Schenker#SOW_1_EDI to Schenker |EDI to Schenker]] | ||
| + | * [http://mantis.jaguarfreight.com/mantis/view.php?id=4742 0004743]: [[EDI to CargoSmart#SOW_1_EDI to CargoSmart |EDI to CargoSmart]] | ||
| + | * [http://mantis.jaguarfreight.com/mantis/view.php?id=5035 0005035]: [[EDI to NYK#SOW_1_EDI to NYK |EDI to NYK]] | ||
| + | |||
| + | == SOWs == | ||
| + | * [http://mantis.jaguarfreight.com/mantis/view.php?id=4564 0004564]: [[ASN_20_ph3_%28part2%29#SOW_30_EDI:_211_file |EDI: 211 file]] | ||
| + | * [http://mantis.jaguarfreight.com/mantis/view.php?id=4595 0004595]: Incoming Data for "Bill To Party" on Est tab | ||
| + | * [http://mantis.jaguarfreight.com/mantis/view.php?id=4596 0004596]: [[3PL selection]] | ||
| + | * [http://mantis.jaguarfreight.com/mantis/view.php?id=4596 0004597]: [[EDI_to_Evergreen#SOW_2:_EDI_Carrier_Integration |EDI Carrier Integration]] | ||
| + | * [http://mantis.jaguarfreight.com/mantis/view.php?id=4729 0004729]: E-mails for 3PL | ||
Current revision as of 15:16, 9 March 2017
Contents |
[edit] Info
parent: 4227
[edit] See Also
[edit] Reference
- Electronic data interchange (EDI)
- XML Schema (W3C)
- ANSI ASC X12 (X12) - US EDI standard
- DISA serves as the Secretariat for ANSI ASC X12 and their X12 EDI and XML standards development process.
[edit] 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.
[edit] EDI documents flow
- 0004528: EDI documents flow
[edit] EDI projects
- 0004558: EDI: Integration Overton, FPA
- 0004572: EDI to DSV:France
- 0004573: EDI to Evergreen
- 0004582: EDI to BDP
- 0004708: EDI to OOCL
- 0004742: EDI to Schenker
- 0004743: EDI to CargoSmart
- 0005035: EDI to NYK
[edit] SOWs
- 0004564: EDI: 211 file
- 0004595: Incoming Data for "Bill To Party" on Est tab
- 0004596: 3PL selection
- 0004597: EDI Carrier Integration
- 0004729: E-mails for 3PL
