EDI to CargoSmart
From UG
(Difference between revisions)
(Created page with 'Category:3PL Integration == Info == * ... == SOWs == === SOW 1 EDI to CargoSmart === <hr> '''mantis''': [http://mantis.jaguarfreight.com/mantis/view.php?id=4743 0004743]…') |
(→SOW 1 EDI to CargoSmart) |
||
| Line 10: | Line 10: | ||
<hr> | <hr> | ||
| - | '''mantis''': [http://mantis.jaguarfreight.com/mantis/view.php?id=4743 0004743] (''phase:'' | + | '''mantis''': [http://mantis.jaguarfreight.com/mantis/view.php?id=4743 0004743] (''phase:'' Dev, ''status:'' feedback) |
==== Core Requirements ==== | ==== Core Requirements ==== | ||
| - | * . | + | * Implement EDI to Cargosmart to send booking request and shipment instruction to receive status messages to update CT2. |
| + | |||
==== Solution ==== | ==== Solution ==== | ||
| - | * ... | + | * Add new date fields in CT2, per listed CT2 Fields Map for Cargosmart Events. |
| + | :* CT2 Fields Map for Cargosmart Events | ||
| + | * Create new "Ocean Transportation Events" tab for new fields, in CT and Master. | ||
| + | |||
| + | |||
| + | ==== Post-Implementation Notes ==== | ||
| + | |||
| + | * 2.39.0 | ||
| + | :* Implement EDI to Cargosmart to send booking request and shipment instruction to receive status messages to update CT2. | ||
| + | :* Create ability to add contract number per office for each steamshipline in admin. | ||
| + | * 2.39.1 | ||
| + | :* Implement EDI 300 and 304 messages to send “B.J. International, Inc. d/b/a Jaguar Freight Services” as hard coding master shipper information on EDI message | ||
| + | * 2.39.2 | ||
| + | :* N/A | ||
| + | * 2.39.3 | ||
| + | :* Provide ability to send EDI 300/304 from Master without shipments - remove validation | ||
| + | * 2.39.4 | ||
| + | :* Provided some more mapping info for LX loop. | ||
| + | * 2.39.5 | ||
| + | :* Provided some more required info to add validation for ports/terminals information. | ||
| + | * 2.39.6 | ||
| + | :* Provided some more mapping info for default weight value. | ||
| + | * 2.39.7 | ||
| + | :* Update a log for some updated vessel name info from 301. | ||
| + | |||
Revision as of 18:09, 27 April 2015
Contents |
Info
- ...
SOWs
SOW 1 EDI to CargoSmart
mantis: 0004743 (phase: Dev, status: feedback)
Core Requirements
- Implement EDI to Cargosmart to send booking request and shipment instruction to receive status messages to update CT2.
Solution
- Add new date fields in CT2, per listed CT2 Fields Map for Cargosmart Events.
- CT2 Fields Map for Cargosmart Events
- Create new "Ocean Transportation Events" tab for new fields, in CT and Master.
Post-Implementation Notes
- 2.39.0
- Implement EDI to Cargosmart to send booking request and shipment instruction to receive status messages to update CT2.
- Create ability to add contract number per office for each steamshipline in admin.
- 2.39.1
- Implement EDI 300 and 304 messages to send “B.J. International, Inc. d/b/a Jaguar Freight Services” as hard coding master shipper information on EDI message
- 2.39.2
- N/A
- 2.39.3
- Provide ability to send EDI 300/304 from Master without shipments - remove validation
- 2.39.4
- Provided some more mapping info for LX loop.
- 2.39.5
- Provided some more required info to add validation for ports/terminals information.
- 2.39.6
- Provided some more mapping info for default weight value.
- 2.39.7
- Update a log for some updated vessel name info from 301.
SOW 2: ...
mantis: ??? (phase: ???, status: ???)
Core Requirements
- ...
- ...
Solution
