OOCL 300

From UG

Revision as of 06:40, 15 November 2013 (edit) Alex (Talk | contribs) (→Booking Remarks) ← Older edit		Revision as of 06:49, 15 November 2013 (edit) (undo) Alex (Talk | contribs) Newer edit →
Line 1:		Line 1:
	[[Category: Ocean Status]]		[[Category: Ocean Status]]
-	== Data Elements ==	+	== Intro ==
-	Below is a list of all data elements to be sent through EDI.	+	This list is based on OOCL/Cargosmart requirements (phase one is OOCL only).
-	By default these fields are read only on '''Message Template'''.	+	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 12:		Line 16:
	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 ====		==== Booking Number ====
Line 156:		Line 168:
	Required: No (used in some cases)		Required: No (used in some cases)
-	== New Fields ==	+	== 301 Data Elements ==
-		+
-	=== 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'''.	+

---

Revision as of 06:49, 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.6 Container 2.7 Trucking and Haulage 2.8 Special Requirements 2.8.1 Export Declaration 2.8.2 Special Stowage 2.9 Booking Remarks 3 301 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

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

• • #Commodity

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
  • Master#Vessel_Name

• Voyage Number
  • Master#Voyage_Num

• Intended Date Range
  • sailing within X weeks from Date Y, details TBD

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

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

See EDI 300#Special Stowage

Booking Remarks

See EDI 300#Booking Remarks.

Required: No (used in some cases)

301 Data Elements