2782 rfd
From UG
(Difference between revisions)
(→Solution) |
(→System logs) |
||
Line 58: | Line 58: | ||
:* All update such as Actual arrival received. | :* All update such as Actual arrival received. | ||
:* All xmls received and sent ??? System can keep this log for x days define in admin. | :* All xmls received and sent ??? System can keep this log for x days define in admin. | ||
- |
Revision as of 17:50, 25 February 2011
Contents |
Glossary
- FSU-message - Freight Status Update message - Incoming message from Descartes to CT2
- Set up in XML format
- FSR-message - Freight Status Request message - Outgoing message to Descartes GLN
- Set up in XML format
- FSA-message - Freight Status Answer message - Incoming message from Descartes to CT2
- Set up in XML format
- FWB-message - Forwards way bill or MAWB details - Out going message to Descartes GLN
- See detail on CIMP-29thEdition2009_FWB.PDF from 2648
- Set Up in CargoImp format
Business Requirement
Solution
FSR functionality
- System should start/stop sending FSR messages automatically once certain condition are met
- parameters are defined in Admin
- For every date on this list: Departure, Trans-shipment, and Arrival.
- Start sending FSR X day(s) prior to Estimated date value. NOTE: in some cases system would have to start sending immediately after this date is set, for example: today is march 10 and oper set est date today and set it to march 11 and X is 2 days
- Stop sending FSR when actual date(s) is set.
- Descartes would forward back messages from the airline with certain updates. This specific info should update CT record.
- Type of update: DEP (Actual departure), ARR (Actual arrival), RCF or ARR (Actual arrival to trans-shipment airport.
FWB functionality
- Provide a transmit FWB button
- CT level on Exp Tab next to the "Master Bill of Lading#:" field.
- Condition: All required fields MUST be there, otherwise it is failed and pop-up error showing for missing information.
- Master level on Master detail Tab next to the "Master Bill of Lading#:" field.
- Condition: All required fields MUST be there, otherwise it is failed and pop-up error showing for missing information.
- Operator can have a choice whether they can transmit FWB from CT or Master level
- CT level on Exp Tab next to the "Master Bill of Lading#:" field.
Admin functionality
- Turn on/off FSR per airline
- FSR messsage frequency in X hour(s)
- Parameters for sending FSR
- Number of hours prior to Estimated dates to start sending FSR in advance
- Provide facility to manage ftp connection
- FTP server address
- Turning on/off
- FSR
- FWB
System logs
- Ideally log all events:
- Time date stamp for operator actions, FWB button, etc
- ALl system actions, message sent and received and etc
- All ftp error/fail messages
- All update such as Actual arrival received.
- All xmls received and sent ??? System can keep this log for x days define in admin.