EDI 315
From UG
(Difference between revisions)
(→Info) |
(→Email Notifications) |
||
| Line 43: | Line 43: | ||
=== Email Notifications === | === Email Notifications === | ||
| + | |||
Per users important. | Per users important. | ||
User who is monitoring this shipment must receive notification when fields are updated. | 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"? | ||
=== Email Template === | === Email Template === | ||
Revision as of 04:52, 8 November 2013
Contents |
Info
- EDI 315 is a Shipment Status message
- It is incoming message (sent by Carrier)
- This message is used to report status or event details (cargo receipt, departure and arrival) for individual shipments.
Message Flow
Old Fields
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:
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:
New Fields
None.
Reporting and Notifications
Master Comments Tab
Post updates?
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"?
Email Template
TBD
Reports
None?
Log
Post updates?
