EDI 300

From UG

Contents 1 Intro 1.1 300 1.2 301 1.3 Message Flow 1.4 Limitations 2 Business Process 2.1 Actual Master BP 2.2 Estimated Master BP 3 EDI tab 3.1 Booking Request and Confirmation 3.2 Shipping Instructions 3.3 Status Updates 3.4 Events 3.5 Actions 3.5.1 300 Create 3.5.2 300 Update 3.5.3 300 Cancel 3.6 300 Message Form 3.6.1 Message Template Actions and Validations 3.6.2 Reefer 3.7 Message View 4 Data to Send 5 Reporting and Notifications 5.1 Master Comments Tab 5.2 Email Notifications 5.2.1 Email Template 5.3 Reports 5.3.1 Updated List Masters Report 5.3.2 Rejected Booking Dashboard 5.3.3 Impending Events Dashboard 5.4 Log 6 Misc 6.1 Changes to Carriers Admin 6.1.1 Contract Number 6.2 Changes to Container Size Type Admin 6.2.1 Container Size Type ISO Code 6.2.2 Reefer Indicator 6.3 Changes to Master Container Table 6.3.1 Container Weight 6.3.2 Container Weight Unit 6.3.3 Reefer Info 6.3.3.1 RF Temperature 6.3.3.2 RF Temperature Unit 6.4 New Master Fields for 300 6.4.1 Special Stowage 6.4.2 Booking Remarks 6.5 New Master Fields for reporting 6.5.1 Created On Date 6.5.2 Export Operator 6.6 Grouping inside Master 6.7 Extended Master Templates 6.8 Make Address Text fields read only 6.9 Tags for required fields 7 EDI Vendor Implementations 8 Wiki source files

Intro

300

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.

301

EDI 301 is a Booking Confirmation message.

This is incoming message sent by Carrier to Jaguar.

This message is used to confirm/reject/update the Booking Request.

Message Flow

Below is a typical flow. See also #Actions.

Limitations

We impose this limitation:

At any moment in time there could be only one Booking Request/Update 300 
and related Booking Response 301

Theoretically we could send multiple alternative booking requests to:

• different steamshiplines (to maximize chance of any booking)
• same steamshipline (say different dates)

but we are not going to support this now.

Business Process

Below is defined for New Booking.

Actual Master BP

When Master contains actual data.

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

• 2/
  • Enter all missing booking related information (if any)
  • Pass all validations.

• 3/ Send booking request from #EDI tab. Most data will come from Master fields.

Estimated Master BP

When Master contains estimated data.

• 1/ create empty master from Master template
• 2/ steps 2,3 from #Actual Master BP
  • some data will be estimated and some of it entered on EDI template (example: weight per container)

Note: User will wrap CTs inside the master with one or more groups later on (before EDI 301 is transmitted)

EDI tab

This tab is active only if:

Master#Steamshipline in given Master is on the list of 
active carriers in OS Admin (see OS#Steamshiplines) 
AND
Master#Master Mode of Transport = Full Container Load (AW) OR
                                      Full Container Load (MLB) 

NOTE:
-----
When Master MOT is set as FCL (AW or MLB) then CT/GRP could have MOT set as:
FCL (AW) or
FCL(MLB) or
Client Consol 

See mock up below.

Booking Request and Confirmation

Columns:

• ANSI# - 300 or 301 or 997

• Message type - Booking or Confirmation or Acknowledgement

• Date - date/time of update

• Event - see #Events

• By - Jag user name (First Name + Last Name) or CT2 or Carrier

• View Message - Link to human readable copy of a saved message

• XML - XML version of a message

Rows:

Each row corresponds to one update by operator or CT2 system or VAN/Carrier.

Actions:

• create - see #300 Create
• update - see #300 Update
• cancel - see #300 Cancel

Shipping Instructions

See EDI 304

Status Updates

See EDI 315

Events

Each event relates to 300 message and leads to a new status with the same name.

300:

• created (new) - 300 was initiated by Jag user, XML created by CT2 and waiting scheduled time to be transmitted to VAN/Carrier
• transmitted - 300 was posted into VAN/Carriers FTP folder, waiting to be read
• updated - Jag user initiates updates to existing 300
• cancelled - Jag user cancels existing 300

997:

• acknowledged - 300 has no errors (corresponds to 997 accepted) // set by VAN or carrier
• error - significant errors found in 300 (syntax, structure, validations, etc)(corresponds to 997 rejected) // set by VAN or carrier

301:

• conditionally accepted - (300 was set as conditionally accepted by carrier)
• pending - (300 was set as pending by carrier)
• rejected (300 was rejected by carrier)
• confirmed (300 was confirmed by carrier)
• updated (300 was updated by carrier)
• canceled (300 was canceled by carrier)

Actions

See actions available for each state:

General Rule
------------
You can only send cancellations on confirmed, 
conditionally accepted or pending bookings. 

300 Create

Template to create new 300 request.

See #300 Message Form

Action Type displayed as Create.

300 Update

Template to update 300 request.

Action Type displayed as Update.

See #300 Message Form

NOTE:
-----
System is not pulling data from last saved state of 300.
System pulls from Master/other entities as if it is a new 300.

300 Cancel

Present Confirmation pop-up:

Are you sure you want to cancel this Booking?
[OK]  [Cancel]

On OK:

• schedule cancellation message
• send e-mail to user who submitted with details of submission

On Cancel return user to Master Editor.

300 Message Form

Opens in pop-up.

Fields are defined in #OOCL 300.

All fields are read-only and are pulled from Master entity or other entities.

See mock up below.

Message Template Actions and Validations

If all required fields are present then show these buttons:

• Submit - submit message
• Cancel - return to Est Tab

If not all required fields are present then indicate what fields needs to be filed in and show this button:

• OK - return to Est Tab

Reefer

If Cargo Nature = Reefer then "Reefer info section will be added".

TBD

Message View

Is a read only version of #Message Template - without any action buttons.

Data to Send

• see OOCL 300

Reporting and Notifications

Master Comments Tab

Suggest not to duplicate here since we have log on EDI tab.

Email Notifications

Email all #Events to EDI 300#Export Operator.

Email Template

'''From''': cybertrax@jaguarfreight.com [cybertrax@jaguarfreight.com]
'''Sent''': <date>
'''To''': <user name>
'''Subject''': Rejected: <protocol number> <Event> <By> for <master number>

Dear <user name>,

Status has changed for <master number>:

<protocol number> was <Event> 

Updated by: <By>

This is automated message generated by Cybertrax 2 System.

<Event> and <By> as defined in #Booking Request and Confirmation.

Reports

Updated List Masters Report

At the core we need a report that lists Masters in the system.

Increment existing List Masters report to enable operator to look at EDI activity for desired group of Masters singled out by applying certain filters such as Steamshipline and Export Operator.

Add these filters to List Masters:

• MOT
• Master#Steamshipline
• EDI 300#Created On Date
• EDI 300#Export Operator

Add these output fields:

• EDI Status
  • map toEDI 300#Events

See mock up below.

Rejected Booking Dashboard

More details TBD once concept is approved.

Based on #List Masters Report

Level 1.

Level 2.

Impending Events Dashboard

• Impending cargo cut off report/dashboard.
• Impending documents cut off report/dashboard

See mock up below.

More details TBD once concept is approved.

Log

Log all #Events.

Misc

Changes to Carriers Admin

Contract Number

Contract number for contract between Jaguar and Steamshipline.

UI: Add to Admin > Carriers > Steamshiplines

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

Changes to Container Size Type Admin

Container Size Type ISO Code

In Admin > Transportation > Container Size/Type

• add field "ISO code", same format/validation as D2L codes
• 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: File:Container Codes.xls
SI_EDI#SOW_18_Fix_Container_info

Reefer Indicator

Add "Reefer Indicator" attribute to container types. Values: "Y" or "No"

Changes to Master Container Table

Container Weight

For every container table add columns/fields:

• weight
• unit

Also add selector to choose one of the following:

• actual weight
  • calculated weight based on commodity assignments to containers
  • weight field will be read-only

• estimated weight
  • in this case system will offer place to enter estimated weight required for EDI 300
  • this is for the case when no actual is available yet
  • store this into DB

• auto-populate max
  • in this case system will populate max weight for this type size of container
  • weight field will be read-only
  • default value

Container Weight Unit

Options:

• kg
• lb

Reefer Info

If at least one contained is reefer - see #Reefer Indicator - then present additional form.

More Details TBD.

RF Temperature

• Format: 9999.99 // Temperature Requirement for RF containers.
  • UI: add to container profile; textfield; default = TBD

RF Temperature Unit

• options: C (Celsius) or F(Farenheit) // Unit of measurement
  • UI: add to container profile; dropdown ; default = F;

New Master Fields for 300

Special Stowage

Add new Master field.

Possible values:

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

UI: radio group

Add to Master details bottom right - see mock up below.

Booking Remarks

• AN // size 1000 chars
• UI: textarea

UI: Master Det tab, See mock up below.

New Master Fields for reporting

Created On Date

• date Master was created
• similar to this field that we have for CT
• UI: read only
• DB: name it CreatedOnDate

Export Operator

• Operator who is responsible for this record on Export side
• default to user who created Master
• UI: Users Selector
• DB: name it ExportOperatorUserId

Grouping inside Master

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

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

TBD: ask opers/team leads if they cross share 
     or there is a benefit of cross sharing

Make Address Text fields read only

Make the following fields read-only on Masters profile:

Master#Master Shipper Text
Master#Master Consignee Text
Master#Master Notify Text
Master#Master Pick-up Text
Master#Master Delivery Text

Tags for required fields

EDI transmission assumes strict validations.

All required fields mast be marked as colored "*" (say orange).

Add note (in orange): "* Required fields for Booking Confirmation"

EDI Vendor Implementations

• CargoSmart: CSmart 300

Wiki source files

File:BR+SI+designs Nov13a.xls