OOCL 300
From UG
(→Misc) |
(→301 Data Elements) |
||
Line 169: | Line 169: | ||
== 301 Data Elements == | == 301 Data Elements == | ||
+ | |||
+ | |||
+ | === Booking Number === | ||
+ | |||
+ | * '''map''': [[Master#Booking_Num | Booking Num]] | ||
+ | * '''required''': Y | ||
+ | * '''EDI''': | ||
+ | * '''Notes''': | ||
+ | |||
+ | === Vessel Name === | ||
+ | |||
+ | * '''map''': [[Master#Vessel_Name | Vessel Name]] | ||
+ | * '''required''': Y | ||
+ | * '''EDI''': | ||
+ | * '''Notes''': | ||
+ | |||
+ | === Voyage Number === | ||
+ | |||
+ | * '''map''':[[Master#Voyage_Num | Voyage Num]] | ||
+ | * '''required''': Y | ||
+ | * '''EDI''': | ||
+ | * '''Notes''': | ||
+ | |||
+ | === Documentation Cut Off Date === | ||
+ | |||
+ | * '''Documentation Cut Off Date''' // Date+Time // Last possible date documentation can be sent. | ||
+ | ** Read only, M Det Tab | ||
+ | |||
+ | === CY open date === | ||
+ | |||
+ | * '''CY open date''' // Date+Time // First possible date cargoes may be delivered to a ship or designated point. | ||
+ | |||
+ | === CY cutoff date === | ||
+ | |||
+ | * '''CY cutoff date''' // Date+Time // Last possible date cargoes may be delivered to a ship or designated point. | ||
+ | ** Read only, M Det Tab |
Revision as of 09:00, 15 November 2013
Contents |
Intro
This list is based on OOCL/Cargosmart requirements (phase one is OOCL only).
We suppose that if we connect through other VANs/directly to other carriers we might have some but not very significant difference since X12 protocol for 300 is a standard.
300 Data Elements
Below is a list of all data elements to be sent through EDI.
Misc
Traffic Mode
Constant = "FCL/FCL".
AMS SCAC Code
Constant = "JAFR"
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.
Booking Number
Available only for Bookings that were confirmed/rejected by carrier.
Rate/Reference Information
Contract Number
New field, see #Contract Number NEW
Parties
Shipper
Name and Address for Master#Master_Shipper.
Send separately:
- Address#Company Name
- Address#Address 1
- Address#Address 2
- Address#Address 3
- Address#City
- Address#Zip
- Address#Country
- Address#State
Forwarder
Name and Address for Jaguar Office to which operator who creates message belongs.
Send separately:
- Address#Company Name
- Address#Address 1
- Address#Address 2
- Address#Address 3
- Address#City
- Address#Zip
- Address#Country
- Address#State
See also Offices.
Tech Note ---------- There is a problem. Office addr is stored in one field tblOffice.Address Need to re-factor DB table to add separate fields that hold Zip, City, etc and trigger to support existing field. Or other solution.
Consignee
Name and Address for Master#Master_Consignee.
Send separately:
- Address#Company Name
- Address#Address 1
- Address#Address 2
- Address#Address 3
- Address#City
- Address#Zip
- Address#Country
- Address#State
Cargo
Outbound Traffic Mode
constant = FCL
Inbound Traffic Mode
constant = FCL
Cargo Nature
- General / Reefer / Dangerous
- use Master#Hazardous, details TBD
Cargo Descriptions
Routing
- Origin City
- for door/* moves: Master#Origin_Terminal
- for door/* moves: Master#Master_Pick-up
- Destination City
- for */port moves: Master#Destination_Terminal
- for */port moves: Master#Master_Delivery_Address
- Vessel Name
- Voyage Number
- Intended Date Range
- sailing within X weeks from Date Y, details TBD
Container
For each container:
- Size Type
- Cargo Weight
- Cargo Weight Unit (kg / lb)
Trucking and Haulage
- Door Pickup
- options: all 4 combinations of cy and door
- map to Move Type/MBL (Master Details tab. 2)
- cy = port
? do we need to add Appointment interface or always use "To be Advised"?
- Empty Container Pickup Request
- O
- do we need this?
Special Requirements
Export Declaration
Constant value = "No Export Declaration"
Special Stowage
Booking Remarks
Required: No (used in some cases)
301 Data Elements
Booking Number
- map: Booking Num
- required: Y
- EDI:
- Notes:
Vessel Name
- map: Vessel Name
- required: Y
- EDI:
- Notes:
Voyage Number
- map: Voyage Num
- required: Y
- EDI:
- Notes:
Documentation Cut Off Date
- Documentation Cut Off Date // Date+Time // Last possible date documentation can be sent.
- Read only, M Det Tab
CY open date
- CY open date // Date+Time // First possible date cargoes may be delivered to a ship or designated point.
CY cutoff date
- CY cutoff date // Date+Time // Last possible date cargoes may be delivered to a ship or designated point.
- Read only, M Det Tab