OS
From UG
(→HTS Feature) |
(→General and Preliminary) |
||
Line 40: | Line 40: | ||
== General and Preliminary == | == General and Preliminary == | ||
- | + | === General Ocean Status Admin === | |
Add UI Admin for: | Add UI Admin for: | ||
Line 62: | Line 62: | ||
* Access: restrict access (add line to access table) | * 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. | FTP protocol will be used on a transport level. | ||
Line 72: | Line 72: | ||
FTP credentials are defined in Admin. | FTP credentials are defined in Admin. | ||
- | + | ==== Message process ==== | |
One process will send/receive all messages accordingly to frequency defined in Admin. | One process will send/receive all messages accordingly to frequency defined in Admin. | ||
- | + | === HTS Feature === | |
- | + | ==== HTS field ==== | |
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | ==== | + | |
- | + | '''HTS''': | |
+ | * meaning: Harmonized System Code that is classifying commodity. Example: '''2907.11.0000''' is for Phenol (Hydroxybenzene) and its salts. More info: [[Ocean_Status_Misc#HTS]] | ||
+ | * format: | ||
+ | ** option 1: XXXX.XX, X represents number from 0 to 9 | ||
+ | ** option 2: XXXX.XX.XX, X represents number from 0 to 9 | ||
+ | * is an attribute of commodity table [[Commodity]] | ||
- | + | ==== HTS Functionality ==== | |
- | + | ||
- | + | ||
- | + | * for those CT records that correspond to Master that is used in EDI transmissions need additional column appear in CT Commodity table | |
- | * | + | * If [[#HTS Spreadsheet]] is present then as user enters SKU system should auto-suggest HTS based on link in spreadsheet between SKU and HTS |
- | + | ||
- | + | ||
- | + | * If [[#HTS Spreadsheet]] is not present then it is a free entry | |
- | + | ==== HTS Spreadsheet ==== | |
- | * | + | |
- | * upload | + | Under PO Issued By in ASN: |
+ | |||
+ | * Add option to upload separate xls that contains a list of SKUs and corresponding HTS | ||
+ | * Add option to upload "SKU to ASN Planner Map" with additional HTS column | ||
== All Message Types == | == All Message Types == |
Revision as of 20:41, 29 October 2013
Contents |
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:
- booking ocean with carrier
- sending Shipping Instructions to carrier
- 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.
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
HTS field
HTS:
- meaning: Harmonized System Code that is classifying commodity. Example: 2907.11.0000 is for Phenol (Hydroxybenzene) and its salts. More info: Ocean_Status_Misc#HTS
- format:
- option 1: XXXX.XX, X represents number from 0 to 9
- option 2: XXXX.XX.XX, X represents number from 0 to 9
- is an attribute of commodity table Commodity
HTS Functionality
- for those CT records that correspond to Master that is used in EDI transmissions need additional column appear in CT Commodity table
- If #HTS Spreadsheet is present then as user enters SKU system should auto-suggest HTS based on link in spreadsheet between SKU and HTS
- If #HTS Spreadsheet is not present then it is a free entry
HTS Spreadsheet
Under PO Issued By in ASN:
- Add option to upload separate xls that contains a list of SKUs and corresponding HTS
- Add option to upload "SKU to ASN Planner Map" with additional HTS column
All Message Types
This is a list of EDI messages being used here to exchange info between Jaguar and Steamshiline through VAN - see below.
Booking Request
See EDI 300
Booking Update and Cancellation
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 3: (Booking Update 300) JAG -> VAN -> CARRIER . day 3: (Booking Confirmation 301) JAG <- VAN <- CARRIER . day 10: (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