EDI 315

From UG

(Difference between revisions)
Jump to: navigation, search
(Email Notifications)
Line 7: Line 7:
* It is incoming message (sent by Carrier)
* 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.
+
* This message is used to update Master record:
 +
** Actual Departure Date
 +
** Actual Arrival Date
 +
 
 +
Do we need any other updates?
=== Message Flow ===
=== Message Flow ===
Line 32: Line 36:
* '''EDI''':
* '''EDI''':
* '''Notes''':
* '''Notes''':
-
 
-
== New Fields ==
 
-
 
-
None.
 
== Reporting and Notifications ==
== Reporting and Notifications ==

Revision as of 04:53, 8 November 2013


Contents

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?

Message Flow

File:Message flow 315.JPG

Old Fields

Actual Departure Date

  • map:
  • required: Y
  • EDI:
  • Notes:

Actual Arrival Date

  • map:
  • required: Y
  • EDI:
  • Notes:

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?

Personal tools