EDI 315
From UG
(Difference between revisions)
(→Reporting and Notifications) |
|||
| Line 40: | Line 40: | ||
=== Master Comments Tab === | === Master Comments Tab === | ||
| - | Post updates | + | |
| + | 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 === | === Email Notifications === | ||
Current revision as of 05:52, 8 November 2013
Contents |
[edit] Info
- EDI 315 is a Shipment Status message
- It is incoming message (sent by Carrier)
- This message is used to update Master record:
- Actual Departure Date
- Actual Arrival Date
Do we need any other updates?
[edit] Message Flow
[edit] Fields
[edit] Actual Departure Date
- map:
- Origin Terminal Actual Date if "Origin Terminal Actual Date" is NOT EMPTY
- Port Of Loading Actual Date if "Origin Terminal Actual Date" is EMPTY
- required: Y
- EDI:
- Notes:
[edit] Actual Arrival Date
- map:
- Destination Terminal Actual Date if "Destination Terminal Actual Date" is NOT EMPTY
- Port Of Discharge Actual Date if "Destination Terminal Actual Date" is EMPTY
- required: Y
- EDI:
- Notes:
[edit] Reporting and Notifications
[edit] 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.
[edit] Email Notifications
Per users important.
User who is monitoring this shipment must receive notification when fields are updated.
How to define this user? User who created record? Or add extra field "Updates monitored by"?
[edit] Email Template
TBD
[edit] Log
Post updates?
[edit] Reports
None?
