EDI 315

From UG

Revision as of 04:54, 8 November 2013 (edit) Alex (Talk | contribs) (→Old Fields) ← Older edit		Revision as of 05:26, 8 November 2013 (edit) (undo) Alex (Talk | contribs) (→Reporting and Notifications) Newer edit →
Line 52:		Line 52:
	=== Email Template ===		=== Email Template ===
	TBD		TBD
-
-	=== Reports ===
-	None?
	=== Log ===		=== Log ===
	Post updates?		Post updates?
		+
		+	=== Reports ===
		+
		+	None?

---

Revision as of 05:26, 8 November 2013

Contents 1 Info 1.1 Message Flow 2 Fields 2.1 Actual Departure Date 2.2 Actual Arrival Date 3 Reporting and Notifications 3.1 Master Comments Tab 3.2 Email Notifications 3.3 Email Template 3.4 Log 3.5 Reports

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

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:

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

Log

Post updates?

Reports

None?