OS

From UG

Revision as of 14:25, 29 October 2013 (edit) Alex (Talk | contribs) (→Reporting and Notifications) ← Older edit		Revision as of 14:31, 29 October 2013 (edit) (undo) Alex (Talk | contribs) (→Example 2) Newer edit →
Line 202:		Line 202:
	.		.
	day 35: (Shipment Status 315)        JAG <- VAN <- CARRIER		day 35: (Shipment Status 315)        JAG <- VAN <- CARRIER
-
-	===== Example 2 =====
-
-	[[File:300 and 301 exchange.png|700px]]
	== Reporting and Notifications ==		== Reporting and Notifications ==

---

Revision as of 14:31, 29 October 2013

Contents 1 Info 2 Definitions 3 Business Need 4 Business Analysis and Requirements 4.1 Current Biz Process 4.2 Phases 5 Solution 5.1 General and Preliminary 5.1.1 General Ocean Status Admin 5.1.2 Message Transport Level and Scheduled Process 5.1.2.1 Message Transport level 5.1.2.2 Message process 5.1.3 HTS Feature 5.1.3.1 HTS Automation 5.2 Steamshipline Admin 5.2.1 Account Bullet 5.2.2 Misc Constants 5.2.2.1 Jaguar Id In Cargosmart 5.2.2.2 PartyType codes in Cargosmart 5.3 Changes in Master Object and Master Profile 5.3.1 New Master Fields 5.3.2 Master Doc Tab 5.4 All Message Types 5.4.1 Booking Request 5.4.2 Booking Confirmation 5.4.3 Ocean Shipping Instructions 5.4.4 Shipment Status 5.4.5 Message Exchange Scenarios 5.4.5.1 Example 1 6 Reporting and Notifications 6.1 Master Comments Tab 6.2 Email Notifications 6.3 Reports 6.3.1 Option 1 6.3.2 Option 2 6.3.3 Option 3 6.4 Log

Info

Mantis parent: 4172

Mantis Category: Ocean Status

Wiki category: Category:Ocean Status - see all related wikis there

Definitions

• VAN - A Value-added Network (VAN) is a hosted service offering that acts as an intermediary between business partners sharing standards based or proprietary data. In the context of this project we use VAN as an intermediary between Jaguar and all carriers for message exchange.

• GLN - VAN owned by Descartes

• Descartes - EDI vendor

• Cargosmart - EDI vendor

Business Need

Core needs is to automate the following:

1. booking ocean with carrier
2. sending Shipping Instructions to carrier
3. receiving updates from carrier

Business Analysis and Requirements

Current Biz Process

Currently operators book with and get updates from ocean carriers manually. After that they manually update CT/Master record with the information they received.

Phases

Phase one will cover OOCL carrier only.

Solution

General and Preliminary

General Ocean Status Admin

Add UI Admin for:

• FTP credentials: url, uname, pwd
  • outbound and inbound
  • for test and prod envir

• Period (min)

• on/off switch for transmission/receiving each of four types of messages

• list of steamshiplines participating: On/Off switch

• email notification groups

• Location:
  • Admin > EDI > Ocean Status
  • move all EDIs to Admin > EDI (EUAN/Air Status, D2L, Trendset)

• Access: restrict access (add line to access table)

Message Transport Level and Scheduled Process

Message Transport level

FTP protocol will be used on a transport level.

Location of Inbound and Outbound folders TBD.

FTP credentials are defined in Admin.

Message process

One process will send/receive all messages accordingly to frequency defined in Admin.

HTS Feature

What:

• Add this field to commodity table (for each line): HTS Number

(commodity customs code). See http://www.foreign-trade.com/reference/hscode.htm

• This field should be presented and (be required only) for records that will be booked/processed through EDI
• For both ASN and CT records

How: (ideas):

• UI: combobox? tree?
• how to upload into system and how to maintain it there?
• for ASN recs entered by Shipper on Client

HTS Automation

• postpone for phase 2?
• remember link btw HTS and SKU as it gets entered so we can do "auto-suggest"?
• upload xls with link btw SKU and xls? (PO Issued By specific?)

Steamshipline Admin

Add new attributes to Steamshipline object - see below.

Account Bullet

Additional info related to #Contract Number.

This is lane (Country or Region) specific.

UI: Add to Admin > Carriers > Steamshiplines

Format: TBD

In Steamshipline Admin or Ocean Status Admin.

Misc Constants

Jaguar Id In Cargosmart

Office specific:

• Office // Id
• NY // BJINUS106971518
• LON // JAGUGB1610342265
• HK // JAGUHK1927007552

PartyType codes in Cargosmart

Code // Description
CA // Carrier 
SH // Shipper
CN // Consignee
FW // Forwarder
BR // Broker
NP // Notify Party
AP // Also Notify Party
BP // Booking Party

Changes in Master Object and Master Profile

New Master Fields

Add new attributes to Master Entity:

• Documentation Cut Off Date // Date+Time // Last possible date documentation can be sent.
  • Read only, M Det Tab

• CY open date // Date+Time // First possible date cargoes may be delivered to a ship or designated point.

• CY cutoff date // Date+Time // Last possible date cargoes may be delivered to a ship or designated point.
  • Read only, M Det Tab

• MBL Type // "original" or "express" // Defines what type of MBL is used. Takes one of two values: "original" or "express"
  • UI: add to Master Gen Tab below "2. Move type/MBL", default to "original"

• AES Number // AN, 15 digits // aka Internal Transaction Number (ITN), id received from Automated Export System. The ITN consists of the letters “AES” followed by the ITN: for example, “AES X20080930987654. See also http://en.wikipedia.org/wiki/Automated_Export_System

• Wood packing // "used" or "not used" // Any wooden packaging material is used or not, this is what we have to declare to the shipping line for every single booking to USA and Canada.

Master Doc Tab

• detect that given master is a subject to EDI transmission (carrier is on the EDI list)
• modify MBL template to accommodate EDI case (add new fields)
• on "generate report" send 304 Shipping Instructions and generate pdf, show confirmation
• Master Bill Of Lading

All Message Types

This is a list of EDI messages being used here to exchange info between Jaguar and Steamshiline through Descartes GLN - see below.

Booking Request

See EDI 300

Booking Confirmation

See EDI 301

Ocean Shipping Instructions

See EDI 304

Shipment Status

See EDI 315

Message Exchange Scenarios

Example 1

day 1: (Booking Request 300)          JAG -> VAN -> CARRIER
.
day 1:  (Booking Confirmation 301)    JAG <- VAN <- CARRIER 
.
day 4:  (Shipping Instructions 304)   JAG -> VAN -> CARRIER 
.
day 15: (Shipment Status 315)         JAG <- VAN <- CARRIER
.
day 35: (Shipment Status 315)         JAG <- VAN <- CARRIER

Reporting and Notifications

Master Comments Tab

Post all events/updates related to all messages here:

• Every time message was sent or received, content of the message, operator who initiated

Email Notifications

Notify group defined in Admin when these messages are received:

• Booking Conf 301
• Status 315

Reports

Option 1

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 Estimated day of Departure or port.

Add these filters to List Masters:

• MOT
• Master#Steamshipline
• Master#Origin Terminal Estimated Date
• more filters TBD

Add these output fields:

• 300 message Status: yet, sent
• 301 message Status: confirmed, rejected, conditionally accepted, pending
• 304 message Status: yet, sent
• 315 message status: there are 10-20 possible values, show the last received
• more fields TBD

Option 2

Dashboard for exceptions (rejected messages, etc).

Details TBD.

Option 3

Impending cargo cut off report/dashboard.

Impending documents cut off report/dashboard

Log

Log all related events.

Human initiated:

• send 300
• send 304

EDI initiated:

• received 301
• received various 315