OOCL 300

From UG

Revision as of 00:20, 12 November 2013 (edit) Alex (Talk | contribs) (→Cargo) ← Older edit		Current revision as of 15:57, 15 November 2013 (edit) (undo) Alex (Talk | contribs) (→Cargo Nature)
(31 intermediate revisions not shown)
Line 1:		Line 1:
	[[Category: Ocean Status]]		[[Category: Ocean Status]]
-	== Data Elements ==	+	== 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 ===		=== Misc ===
Line 7:		Line 15:
	==== Traffic Mode ====		==== Traffic Mode ====
-	Constant = ''"FCL/FCL"''	+	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.
		+	* pull from [[Master#Booking Num]]
	=== Rate/Reference Information ===		=== Rate/Reference Information ===
Line 13:		Line 34:
	==== Contract Number ====		==== Contract Number ====
-	New field, see [[#Contract Number NEW]]	+	New field, see [[EDI 300#Contract Number]]
	=== Parties ===		=== Parties ===
Line 20:		Line 41:
	Name and Address for [[Master#Master_Shipper]].		Name and Address for [[Master#Master_Shipper]].
		+
	Send separately:		Send separately:
	* [[Address#Company Name]]		* [[Address#Company Name]]
Line 33:		Line 55:
	Name and Address for Jaguar Office to which operator who creates message belongs.		Name and Address for Jaguar Office to which operator who creates message belongs.
		+
	Send separately:		Send separately:
	* [[Address#Company Name]]		* [[Address#Company Name]]
Line 43:		Line 66:
	* [[Address#State]]		* [[Address#State]]
-	See also [[Offices]].	+	See also [[EDI 300#Jaguar Offices]].
-		+
-	Tech Note	+
-	----------	+
-	There is a problem.	+
-	Office addr is stored in one field tblOffice.Address	+
-	Need to re-factor DB to add separate fields that hold Zip, City, etc	+
-	and trigger to support existing field. Or other solution.	+
	==== Consignee ====		==== Consignee ====
	Name and Address for [[Master#Master_Consignee]].		Name and Address for [[Master#Master_Consignee]].
		+
	Send separately:		Send separately:
	* [[Address#Company Name]]		* [[Address#Company Name]]
Line 77:		Line 94:
	==== Cargo Nature ====		==== Cargo Nature ====
-	** ''General / Reefer / Dangerous''	+	* possible values: General / Reefer / Dangerous
-	** use [[Master#Hazardous]], details TBD	+
-	==== Cargo Descriptions ====	+	* if at least one container is a reefer (use [[EDI 300#Reefer Indicator]]) then Cargo Nature = Reefer
-	** [[#Commodity]]	+	* if Hazardous = Y then Cargo Nature = Hazardous
-	=== Routing ===	+	* else Cargo Nature = General
-	* '''Origin City'''	+	==== Cargo Descriptions ====
-	** for door/* moves: [[Master#Origin_Terminal]]	+
-	** for door/* moves: [[Master#Master_Pick-up]]	+
-	* '''Destination City'''	+	Pull from [[Master#Master Commodity Description]]
-	** for */port moves: [[Master#Destination_Terminal]]	+
-	** for */port moves: [[Master#Master_Delivery_Address]]	+
-	* '''Vessel Name'''	+	=== Routing ===
-	** [[Master#Vessel_Name]]	+
-	* '''Voyage Number'''	+	See [[EDI 300#Move type]]
-	** [[Master#Voyage_Num]]	+
-	* '''Intended Date Range'''	+	==== Origin City ====
-	** sailing within X weeks from Date Y, details TBD	+
-	=== Container ===	+	For Move type = "door to cy" or "door to door":
		+	* pull City from [[Master#Master_Pick-up]] address
-	For each size type:	+	For Move type = "cy to cy" or "cy to door":
		+	* pull City from [[Master#Origin_Terminal]] address
-	* '''Quantity'''	+	==== Destination City ====
-	** calculate from Master containers table	+
-	* '''Size Type'''	+	For Move type = "cy to door" or "door to door":
-	** see [[#Container Type ISO Code]]	+	* pull City from [[Master#Master Delivery Address]] address
-	* '''Cargo Weight'''	+	For Move type = "cy to cy" or "door to cy":
-	** see [[OS#Add Weight per container]]	+	* pull City from [[Master#Destination_Terminal]] address
-	* '''Cargo Weight Unit''' (kg / lb)	+	==== Vessel Name ====
-	** see [[OS#Add Weight per container]]	+
-	=== Trucking and Haulage ===	+	Pull from [[Master#Vessel_Name]]
-	* '''Door Pickup'''	+	==== Voyage Number ====
-	** options:  all 4 combinations of '''cy''' and '''door'''	+
-	** map to [[Master#Move_Type.2FMBL | Move Type/MBL ]] ''(Master Details tab. 2)''	+
-	*** cy = port	+
-	? do we need to add Appointment interface or always use "To be Advised"?	+	Pull from [[Master#Voyage_Num]]
-	* '''Empty Container Pickup Request'''	+	=== Container ===
-	** O	+
-	** do we need this?	+
-	=== Special Requirements ===	+	For each container:
-	* '''Export Declaration'''	+	* '''Size Type'''
-	** see [[#Export Declaration]]	+	** see [[EDI 300#Container Type ISO Code]]
-	* '''Special Stowage'''	+	* '''Cargo Weight'''
-	** see [[#Special Stowage]]	+	** see [[EDI 300#Container Weight]]
-	* '''Document Upload'''	+	* '''Cargo Weight Unit''' (kg / lb)
-	** O	+	** see [[EDI 300#Container Weight Unit]]
-	** no need?	+
-	=== Booking Remarks ===	+	=== Trucking and Haulage ===
-	* [[#Booking Remarks]]	+	==== Move type ====
-	** OOCL Example: If an item is over one ton, enter the Gross Weight per package	+
-	== New Fields ==	+	Pull from [[Master#Move Type/MBL]]
-	=== Export Declaration ===	+	=== Special Requirements ===
-	* options:	+	==== Export Declaration ====
-	** No Export Declaration	+
-	=== Special Stowage ===	+	Constant value = "No Export Declaration"
-	* options:	+	==== Special Stowage ====
-	** Stow below Deck	+
-	** Stow on Deck	+	See [[EDI 300#Special Stowage]]
-	** No Special Stowage	+
	=== Booking Remarks ===		=== Booking Remarks ===
-	* required: N (used in some cases)	+	See [[EDI 300#Booking Remarks]].
-	* AN // size TBD	+
-	* UI: textarea	+
-		+
-	=== 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"	+
		+	Required: No (used in some cases)
-	=== Contract Number NEW ===	+	=== Reefer Information ===
-	Contract number for contract between Jaguar and Steamshipline.	+	This section will be presented if [[#Cargo Nature]] = Reefer
-	UI: Add to Admin > Carriers > Steamshiplines	+	See [[EDI 300#Reefer Info]]
-	* OOCL	+	== 301 Data Elements ==
-	** Format: AN, 8 chars	+
-	** example: MT136710	+
-	=== AMS SCAC Code ===	+	=== Booking Number ===
-	* '''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'''.	+	* save into [[Master#Booking_Num ]]
-	=== Container Size Type ISO Code ===	+	=== Vessel Name ===
-	* '''map''': see below	+	* save into [[Master#Vessel_Name]]
-	* '''required''': Y	+
-	* '''EDI''':	+
-	* '''Notes''': cover all containers in the loop	+
		+	=== Voyage Number ===
-	Related to http://wiki.jaguarfreight.com/wiki/SI_EDI#SOW_18_Fix_Container_info	+	* save into [[Master#Voyage_Num ]]
-	In Admin > Transportation > Container Size/Type	+	=== Documentation Cut Off Date ===
-	* add field "ISO code", same format/validation	+	* '''Documentation Cut Off Date''' // Date+Time // Last possible date documentation can be sent.
-	* add Long Description field (100 char string)	+	** Read only, M Det Tab
-	NOTE:	+	* TBC!
-	D2L codes are based on ISO but not identical.	+
-	For example, open top type.	+
-	In ISO it is tagged as "UT" or U0, U1 or .... or U5.	+
-	In D2L classification it is "OT"	+
-	References:	+
-	ISO: http://en.wikipedia.org/wiki/ISO_6346	+
-	D2L: http://wiki.jaguarfreight.com/wiki/File:Container_Codes.xls	+
-	=== Est GW ===	+	=== CY open date ===
-	* "Est GW" checkbox	+	* '''CY open date''' // Date+Time // First possible date cargoes may be delivered to a ship or designated point.
-	** NOTE: "Use Estimated Weight for Booking Request instead of actual?"	+
-	** above master container table	+
-	=== Add Weight per container ===	+	* TBC!
-	* add extra column "GW" to cont table	+	=== CY Cutoff Date ===
-	** with dropdown with '''unit''' (kg/lb) in the header of column	+
-	* if Est GW is checked then show show textfield in each line (float, format same as GW in commod table) else show calculated read only from CTs	+	* save into [[EDI 300#CY Cutoff Date]]
-	** if CTs have mixed kg/lb then recalculate in '''unit''' above table	+

---

Current revision as of 15:57, 15 November 2013

Contents 1 Intro 2 300 Data Elements 2.1 Misc 2.1.1 Traffic Mode 2.1.2 AMS SCAC Code 2.1.3 Booking Number 2.2 Rate/Reference Information 2.2.1 Contract Number 2.3 Parties 2.3.1 Shipper 2.3.2 Forwarder 2.3.3 Consignee 2.4 Cargo 2.4.1 Outbound Traffic Mode 2.4.2 Inbound Traffic Mode 2.4.3 Cargo Nature 2.4.4 Cargo Descriptions 2.5 Routing 2.5.1 Origin City 2.5.2 Destination City 2.5.3 Vessel Name 2.5.4 Voyage Number 2.6 Container 2.7 Trucking and Haulage 2.7.1 Move type 2.8 Special Requirements 2.8.1 Export Declaration 2.8.2 Special Stowage 2.9 Booking Remarks 2.10 Reefer Information 3 301 Data Elements 3.1 Booking Number 3.2 Vessel Name 3.3 Voyage Number 3.4 Documentation Cut Off Date 3.5 CY open date 3.6 CY Cutoff Date

[edit] 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.

[edit] 300 Data Elements

Below is a list of all data elements to be sent through EDI.

[edit] Misc

[edit] Traffic Mode

Constant = "FCL/FCL".

[edit] 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.

[edit] Booking Number

• Available only for Bookings that were confirmed/rejected by carrier.
• pull from Master#Booking Num

[edit] Rate/Reference Information

[edit] Contract Number

New field, see EDI 300#Contract Number

[edit] Parties

[edit] 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

[edit] 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 EDI 300#Jaguar Offices.

[edit] 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

[edit] Cargo

[edit] Outbound Traffic Mode

constant = FCL

[edit] Inbound Traffic Mode

constant = FCL

[edit] Cargo Nature

• possible values: General / Reefer / Dangerous

• if at least one container is a reefer (use EDI 300#Reefer Indicator) then Cargo Nature = Reefer

• if Hazardous = Y then Cargo Nature = Hazardous

• else Cargo Nature = General

[edit] Cargo Descriptions

Pull from Master#Master Commodity Description

[edit] Routing

See EDI 300#Move type

[edit] Origin City

For Move type = "door to cy" or "door to door":

• pull City from Master#Master_Pick-up address

For Move type = "cy to cy" or "cy to door":

• pull City from Master#Origin_Terminal address

[edit] Destination City

For Move type = "cy to door" or "door to door":

• pull City from Master#Master Delivery Address address

For Move type = "cy to cy" or "door to cy":

• pull City from Master#Destination_Terminal address

[edit] Vessel Name

Pull from Master#Vessel_Name

[edit] Voyage Number

Pull from Master#Voyage_Num

[edit] Container

For each container:

• Size Type
  • see EDI 300#Container Type ISO Code

• Cargo Weight
  • see EDI 300#Container Weight

• Cargo Weight Unit (kg / lb)
  • see EDI 300#Container Weight Unit

[edit] Trucking and Haulage

[edit] Move type

Pull from Master#Move Type/MBL

[edit] Special Requirements

[edit] Export Declaration

Constant value = "No Export Declaration"

[edit] Special Stowage

See EDI 300#Special Stowage

[edit] Booking Remarks

See EDI 300#Booking Remarks.

Required: No (used in some cases)

[edit] Reefer Information

This section will be presented if #Cargo Nature = Reefer

See EDI 300#Reefer Info

[edit] 301 Data Elements

[edit] Booking Number

• save into Master#Booking_Num

[edit] Vessel Name

• save into Master#Vessel_Name

[edit] Voyage Number

• save into Master#Voyage_Num

[edit] Documentation Cut Off Date

• Documentation Cut Off Date // Date+Time // Last possible date documentation can be sent.
  • Read only, M Det Tab

• TBC!

[edit] CY open date

• CY open date // Date+Time // First possible date cargoes may be delivered to a ship or designated point.

• TBC!

[edit] CY Cutoff Date

• save into EDI 300#CY Cutoff Date