EDI 300

From UG

Revision as of 05:34, 7 November 2013 (edit) Alex (Talk | contribs) (→FCL Business Process) ← Older edit		Revision as of 06:20, 7 November 2013 (edit) (undo) Alex (Talk | contribs) Newer edit →
Line 1:		Line 1:
	[[Category:Ocean Status]]		[[Category:Ocean Status]]
-	== Info ==	+	== Intro ==
	EDI 300 is a '''Booking Request''' message.		EDI 300 is a '''Booking Request''' message.
-	It is an outgoing Message: Jaguar sends this to Carrier.	+	It is an outgoing Message: Jaguar sends info to Carrier.
	The shipper or forwarder can use this transaction set to reserve cargo space.		The shipper or forwarder can use this transaction set to reserve cargo space.
Line 21:		Line 21:
	=== Basic booking request ===		=== Basic booking request ===
-	* From	+
-	* To	+	7.1 Rate/Reference Information
-	* When (dates)	+	7.2 Parties
-	* What (commodity)	+	7.3 Cargo
-	* Hazardous (y/n) -> if yes (haz description)	+	7.4 Routing
-	* How many containers / size / type	+	7.5 Container
		+	7.6 Trucking and Haulage
		+	7.7 Special Requirements
		+	7.8 Booking Remarks
		+
		+
		+	=== Message Flow ===
		+
		+	Below covers most scenarious except updates from carriers.
		+
		+	[[File:300 and 301 exchange.png|700px]]
		+
	== Business Process ==		== Business Process ==
Line 77:		Line 88:
	[[File:Sailing schedule.JPG]]		[[File:Sailing schedule.JPG]]
-
-	== Message Flow ==
-
-	Below covers most scenarious except updates from carriers.
-
-	[[File:300 and 301 exchange.png|700px]]
	== Master UI 1 ==		== Master UI 1 ==

---

Revision as of 06:20, 7 November 2013

Contents 1 Intro 1.1 Basic booking request 1.2 Message Flow 2 Business Process 3 Validations 4 Sailing Schedule 5 Master UI 1 6 Required Fields 6.1 Rate/Reference Information 6.2 Parties 6.3 Cargo 6.4 Routing 6.5 Container 6.6 Trucking and Haulage 6.7 Special Requirements 6.8 Booking Remarks 7 Old fields 7.1 Shipper 7.2 Forwarder 7.3 Consignee 7.4 Notify Party 7.5 Origin Terminal 7.6 Destination Terminal 7.7 Estimated Departure Date 7.8 Commodity 7.9 Hazardous Information 7.10 Maybe: Vessel Name / Voyage # 7.11 Maybe: Estimated Arrival Date 7.12 Door Pick Up Location 7.13 Door Delivery Location 7.14 Freight Prepaid / Freight Collect 7.15 Gross Weight 7.16 Service Mode (move type) 8 New Fields 8.1 Booking Remarks 8.2 RF Temperature 8.2.1 Reefer Indicator 8.3 Contract Number 8.4 AMS SCAC Code 8.5 Container Type ISO Code 9 See Also

Intro

EDI 300 is a Booking Request message.

It is an outgoing Message: Jaguar sends info 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.

Basic booking request

   7.1 Rate/Reference Information
   7.2 Parties
   7.3 Cargo
   7.4 Routing
   7.5 Container
   7.6 Trucking and Haulage
   7.7 Special Requirements
   7.8 Booking Remarks

Message Flow

Below covers most scenarious except updates from carriers.

Business Process

"Regular" FCL booking:

• 1/ Combine CTs into GRP and then into Master (currently not all operators are doing this at the moment of booking)

• 2/
  • Enter all required information such as containers, etc.
  • Pass all #Validations.

• 3/ Browse #Sailing Schedule to identify appropriate Vessel / Voyage (example: VANCOUVER EXPRESS / 029W)

• 4/ Enter Vessel / Voyage

• 5/ Send booking request by pressing a button in Master Context Menu. See #Master UI 1.

"Blind" booking: skip 3,4 above

"Phone" booking: at step 3 if there are no space then make a phone call. Then if space provided then complete it over the phone or proceed to 4,5

"Regular" LCL booking: TBD

Validations

EDI transmission assumes strict validations.

All required fields mast be marked as "required". See #Master UI 1.

On "Transmit" system should:

• validate all fields and present user with all required fields. See #Required fields
• validate that all contents are assigned to containers in all CTs under Master

Sailing Schedule

User needs access to this info in many cases before they make a booking.

Tech Note
---------
User accesses this through:
.
option A) A different free URL (example: https://www.e-usiship.com/party/sailingschedule/ss_expresslink.jsf?ANONYMOUS_BEHAVIOR=BUILD_UP&domainName=PARTY_DOMAIN&ENTRY_TYPE=USI&ENTRY=MCC&PREFER_LANGUAGE=en-US)
A1) on separate browser tab OR
A2) embedded into CT2 page
.
option B) CT2 module that connects through Web Service or alike(not free, example: CargoSmart's Sailing Schedule feature)

Master UI 1

Add Booking Request button to initiate 300 message.

Message will be scheduled and confirmation pop-up will be shown.

Required Fields

All below is provided for FCL/FCL traffic mode.

TBD what difference in case of other traffic mode if any.

• Traffic Mode:
  • FCL: constant "FCL/FCL"
  • other option: exists?

Rate/Reference Information

• #Contract Number

Parties

• #Shipper
• #Forwarder
• #Consignee

Cargo

• Outbound Traffic Mode
  • constant FCL: Full Container Load for FCL/FCL

• Inbound Traffic Mode
  • constant FCL: Full Container Load for FCL/FCL

• Cargo Nature
  • General / Reefer / Dangerous

• Cargo Descriptions
  • #Commodity

Routing

• Origin City
• Destination City
• #Vessel Name
• #Voyage Number

Container

For each size type:

• Quantity
• Size Type
• Cargo Weight (per container)
• Cargo Weight Unit (kg / lb)

Trucking and Haulage

Special Requirements

Booking Remarks

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

Old fields

Shipper

• map: Master Shipper
• required: Y
• EDI:
• Notes:

Forwarder

• map: Offices based on users login
• 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

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

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

See Also

• 300 CargoSmart