EDI 300
From UG
(→Container Type ISO Code) |
(→Old fields) |
||
Line 18: | Line 18: | ||
only send cancellations on confirmed, conditionally accepted or pend | only send cancellations on confirmed, conditionally accepted or pend | ||
ing bookings. | ing bookings. | ||
+ | |||
+ | == Master Context Menu == | ||
+ | |||
+ | Add Booking Request button to initiate 300 message. | ||
+ | |||
+ | Message will be sent immediately and confirmation pop-up will be shown. | ||
+ | |||
== Old fields == | == Old fields == |
Revision as of 14:23, 29 October 2013
Info
EDI 300 is a Booking Request message.
It is an outgoing Message: Jaguar sends this to Carrier.
The shipper or forwarder can use this transaction set to reserve cargo space.
Types of 300 message:
- Initial Booking
- Booking Update - Booking amendment, initiated by the customer. You can only send amendments on confirmed, conditionally accepted or pending bookings. For rejected bookings a new initial booking needs to be sent
- Booking Cancellation - initiated by the customer. You can
only send cancellations on confirmed, conditionally accepted or pend ing bookings.
Master Context Menu
Add Booking Request button to initiate 300 message.
Message will be sent immediately and confirmation pop-up will be shown.
Old fields
Shipper
- map: Master Shipper
- required: Y
- EDI:
- Notes:
Consignee
- map: Master Consignee
- required: Y
- EDI:
- Notes:
Notify Party
- map: Master Notify
- required: Y
- EDI:
- Notes:
Origin Terminal
- map: Origin Terminal
- required: Y
- EDI:
- Notes:
Destination Terminal
- map: Destination Terminal
- required: Y
- EDI:
- Notes:
Estimated Departure Date
- map:
- Origin Terminal Estimated Date if "Origin Terminal Estimated Date" is NOT EMPTY
- Port Of Loading Estimated Date if "Origin Terminal Estimated Date" is EMPTY
- required: Y
- EDI:
- Notes: might be labeled something else, ready to ship date, or cargo delivery date, for example
Commodity
- map: Master Commodity Description
- required: Y
- EDI:
- Notes: cargo description
Hazardous Information
- map: Hazardous (Master General tab. 18)
- required: Y
- EDI:
- Notes: if any
Maybe: Vessel Name / Voyage #
- map: Vessel Name / Voyage Num
- required: Y
- EDI:
- Notes:
Maybe: Estimated Arrival Date
- map:
- Destination Terminal Estimated Date if "Destination Terminal Estimated Date" is NOT EMPTY
- Port Of Discharge Estimated Date if "Destination Terminal Estimated Date" is EMPTY
- required: Y
- EDI:
- Notes:
Door Pick Up Location
- map: Master Pick-up
- required: Y
- EDI:
- Notes:
Door Delivery Location
- map: Master Delivery Address
- required: Y
- EDI:
- Notes:
Freight Prepaid / Freight Collect
- map: Freight Prepaid Collect (Master Details tab. 1)
- required: Y
- EDI:
- Notes:
Gross Weight
- map: Total Gross KG(readonly) (Master General tab. 17)
- required: Y
- EDI:
- Notes:
Service Mode (move type)
- map: Move Type/MBL (Master Details tab. 2)
- required: Y
- EDI:
- Notes:
New Fields
RF Temperature
- RF Temperature // Format: 9999.99 // Temperature Requirement for RF containers.
- UI: add to container profile; textfield; default = TBD
- RF Temperature Unit // C (Celsius) or F(Farenheit) // Unit of measurement
- UI: add to container profile; dropdown ; default = TBD;
Above needs to be presented/validated only for RF type of containers - use #Reefer Indicator to distinguish.
Editable in container table in M only or in CT as well when CTs are under Master.
Reefer Indicator
Add "Reefer Indicator" attribute to container types. Values: "Y" or "No"
Contract Number
Contract number for contract between Jaguar and Steamshipline.
UI: Add to Admin > Carriers > Steamshiplines
Format: TBD
AMS SCAC Code
- AMS SCAC Code - SCAC/ACI Code. For USA trade, this is a code with normally 4 digits for AMS filing, we need this code to submit AMS filing and Jaguar is registered. Our AMS SCAC code is JAFR.
Container Type ISO Code
- map: see below
- required: Y
- EDI:
- Notes: cover all containers in the loop
Related to http://wiki.jaguarfreight.com/wiki/SI_EDI#SOW_18_Fix_Container_info
In Admin > Transportation > Container Size/Type
If D2L codes are same as ISO then:
- Rename "D2L codes" into "ISO code"
If D2L codes are NOT same as ISO then:
- add additional field "ISO code", same format/validation
In both cases add Long Description field (100 char string)