EDI 300

From UG

(Difference between revisions)
Jump to: navigation, search
(→Intro)
(→Intro)
Line 17: Line 17:
* '''Jaguar Booking Cancellation''' -  initiated by the customer. You can only send cancellations on confirmed, conditionally accepted or pending bookings.
* '''Jaguar Booking Cancellation''' -  initiated by the customer. You can only send cancellations on confirmed, conditionally accepted or pending bookings.
-
* '''Carrier Booking Update''' - booking amendment, initiated by the carrier. TBC
+
* '''Carrier Booking Update''' - booking amendment, initiated by the carrier. Supported by some carriers.
   
   
-
* '''Carrier Booking Cancellation''' -  initiated by the carrier. TBC
+
* '''Carrier Booking Cancellation''' -  initiated by the carrier.  
=== Message Flow ===
=== Message Flow ===

Revision as of 00:00, 10 November 2013


Contents

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
  • Jaguar 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
  • Jaguar Booking Cancellation - initiated by the customer. You can only send cancellations on confirmed, conditionally accepted or pending bookings.
  • Carrier Booking Update - booking amendment, initiated by the carrier. Supported by some carriers.
  • Carrier Booking Cancellation - initiated by the carrier.

Message Flow

Below covers most scenarious except updates from carriers.

Business Process

Full Master BP

  • 1/ Combine CTs into GRPs and then into Master (currently not all operators are doing this at the moment of booking)
  • 2/
    • Enter all required booking information such as containers, Vessel, Voyage, etc.
    • Pass all #Validations.
  • 3/ Send booking request by pressing a button in Master Context Menu. See #Master UI 1.

Empty Master BP

  • 1/ create empty master from Master template
  • steps 2,3 from #Regular BP

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

Transmit Menu

  • Add Buttons to initiate 300 messages:
    • New Booking
    • Update Booking
    • Cancel Booking
  • Messages will be sent instantly and confirmation pop-up will be shown.

New Booking

  • Once button is pressed system should:
    • validate required fields
    • show Booking Preview screen with all information that will be sent, missing required fields info and options to "Transmit" (disabled if not all mandatory fields are present) and "Go Back to Master Editor"
    • on "Transmit" send 300 message

Update Booking

TBA

Cancel Booking

TBA


Reporting and Notifications

Master Comments Tab

Post all events/updates related to all messages here:

  • Add record every time message was sent or received
  • Record content of the message, operator who initiated.

Email Notifications

997?

Email Template 


'''From''': cybertrax@jaguarfreight.com [cybertrax@jaguarfreight.com]
'''Sent''': <date>
'''To''': <user name>
'''Subject''': Rejected: <protocol number><message type><related master numbers>

Dear <user name>,

The following transmission was rejected:

<protocol number><message type><related master numbers>

This is automated message generated by Cybertrax 2 System.
  • <protocol number>: 300, 301, etc
  • <protocol name>: Booking Request, etc
  • <related master numbers>: Master numbers related to thi transmission. Example: M1234, M12414

Reports

997 Reporting

Optional for 300 (since we have 301 as a response).

Required for 304.

Dashboard similar to 997 dashboard in SI EDI (Data2Log).

Provides counter of Rejected messages.

Must be based off of #List Masters.

Log

Log all related events:

  • when Process started
  • when Process ended
  • 300 sent
  • 301 received
  • 304 sent
  • 315 received
  • any 997 received

Additional info to include into log event description:

  • related list of Master numbers
  • status for incoming messages (such as accepted/rejected)

Required Message Fields

  • Traffic Mode
    • FCL: constant "FCL/FCL"

Rate/Reference Information

Parties

  • Forwarder

Cargo

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


Routing

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

Container

For each size type:

  • Quantity
    • calculate from Master containers table

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

  • 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

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

Misc

Grouping inside Master

Add ability to group/ungroup selected CTs inside the Master.

Extend Master Templates

Following additional fields must be copied at the moment of creating a template from Master Clone.

Add column / filter of user who created them.

EDI Vendor Implementations

Retrieved from "https://wiki.jaguarfreight.com/EDI_300"
Personal tools