Integration points for Rates DB

From UG

Revision as of 17:29, 11 October 2011 (edit) Alex (Talk | contribs) (→Core need and more) ← Older edit		Current revision as of 18:34, 12 October 2011 (edit) (undo) Alex (Talk | contribs)
Line 19:		Line 19:
	== Requirements and Design Ideas ==		== Requirements and Design Ideas ==
		+
		+
		+	== Solution ver 1 ==
		+
		+	TBD

---

Current revision as of 18:34, 12 October 2011

Contents 1 Info 2 Core need and more 3 Requirements and Design Ideas 4 Solution ver 1

[edit] Info

• 0003167: (proj: Rates DB) Define integration points between CT2 and Rates DB software

[edit] Core need and more

We need to integrate CT2 and external Rates DB software.

Main integration point is to send CT info to Rates DB and receive "rates data" (list of charges) for this move. At that point CT2 should populate CT2 database with this data on Save.

Of course there are many cases that needs to be considered (as usual). Examples:

• what happens if operator changes some CT fields (origin, commodity table, etc) after rates has been populated
• what if not all rates are available (origin trucking segment)?

Should we re-use existing "Estimated Charges Table"?

[edit] Requirements and Design Ideas

[edit] Solution ver 1

TBD