OOCL 300

From UG

Revision as of 00:20, 12 November 2013 (edit) Alex (Talk | contribs) (→Cargo) ← Older edit		Revision as of 21:46, 12 November 2013 (edit) (undo) Alex (Talk | contribs) (→Data Elements) Newer edit →
Line 2:		Line 2:
	== Data Elements ==		== Data Elements ==
		+
		+	Below is a list of all data elements to be sent through EDI.
		+
		+	By default these fields are read only on '''Message Template'''.
	=== Misc ===		=== Misc ===
Line 7:		Line 11:
	==== Traffic Mode ====		==== Traffic Mode ====
-	Constant = ''"FCL/FCL"''	+	Constant = ''"FCL/FCL"''.
		+
		+	==== Booking Number ====
		+
		+	Available only for Bookings that were confirmed/rejected by carrier.
	=== Rate/Reference Information ===		=== Rate/Reference Information ===
Line 20:		Line 28:
	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 42:
	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 49:		Line 59:
	There is a problem.		There is a problem.
	Office addr is stored in one field tblOffice.Address		Office addr is stored in one field tblOffice.Address
-	Need to re-factor DB to add separate fields that hold Zip, City, etc	+	Need to re-factor DB table to add separate fields that hold Zip, City, etc
	and trigger to support existing field. Or other solution.		and trigger to support existing field. Or other solution.
Line 55:		Line 65:
	Name and Address for [[Master#Master_Consignee]].		Name and Address for [[Master#Master_Consignee]].
		+
	Send separately:		Send separately:
	* [[Address#Company Name]]		* [[Address#Company Name]]

---

Revision as of 21:46, 12 November 2013

Contents 1 Data Elements 1.1 Misc 1.1.1 Traffic Mode 1.1.2 Booking Number 1.2 Rate/Reference Information 1.2.1 Contract Number 1.3 Parties 1.3.1 Shipper 1.3.2 Forwarder 1.3.3 Consignee 1.4 Cargo 1.4.1 Outbound Traffic Mode 1.4.2 Inbound Traffic Mode 1.4.3 Cargo Nature 1.4.4 Cargo Descriptions 1.5 Routing 1.6 Container 1.7 Trucking and Haulage 1.8 Special Requirements 1.9 Booking Remarks 2 New Fields 2.1 Export Declaration 2.2 Special Stowage 2.3 Booking Remarks 2.4 RF Temperature 2.4.1 Reefer Indicator 2.5 Contract Number NEW 2.6 AMS SCAC Code 2.7 Container Size Type ISO Code 2.8 Est GW 2.9 Add Weight per container

Data Elements

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

By default these fields are read only on Message Template.

Misc

Traffic Mode

Constant = "FCL/FCL".

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 size type:

• Quantity
  • calculate from Master containers table

• Size Type
  • see #Container Type ISO Code

• Cargo Weight
  • see OS#Add Weight per container

• Cargo Weight Unit (kg / lb)
  • see OS#Add Weight per container

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
  • see #Export Declaration

• Special Stowage
  • see #Special Stowage

• Document Upload
  • O
  • no need?

Booking Remarks

• #Booking Remarks
  • OOCL Example: If an item is over one ton, enter the Gross Weight per package

New Fields

Export Declaration

• options:
  • No Export Declaration

Special Stowage

• options:
  • Stow below Deck
  • Stow on Deck
  • No Special Stowage

Booking Remarks

• required: N (used in some cases)
• 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"

Contract Number NEW

Contract number for contract between Jaguar and Steamshipline.

UI: Add to Admin > Carriers > Steamshiplines

• OOCL
  • Format: AN, 8 chars
  • example: MT136710

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 Size 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

• add field "ISO code", same format/validation
• add Long Description field (100 char string)

NOTE:
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

• "Est GW" checkbox
  • NOTE: "Use Estimated Weight for Booking Request instead of actual?"
  • above master container table

Add Weight per container

• add extra column "GW" to cont table
  • 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
  • if CTs have mixed kg/lb then recalculate in unit above table