Issue 2405:  Modify and specify the behavior of the insertExchangeRate interface                                                                                                                                    (currency-rtf)
Source:  (, )
Nature:  Revision
Severity: 
Summary: Summary: The behavior of the insertExchangeRate() interface should be modified.
 Since ExchangeRates will now have a window in time over which they are
 effective, the behavior needs to address what happens when an exchange rate
 is attempted to be inserted that overlaps (in time) an existing exchange
 rate. i.e. Suppose an exchange rate exists in the system for a certain rate
 type, source currency mnemonic, target currency mnemonic, and is effective
 from 12:00 15 July 1998 until 12:30 15 July 1998. Now suppose we attempt to
 insert an exchange rate for the same rate type, source/target currency
 mnemonics and is effective from 11:45 15 July 1998 until 12:15 15 July
 1998. How does the insertExchangeRate() interface react in this case, or in
 any other case where the exchange rate to be inserted has an effective
 window in time that in whole or in part overlaps existing exchange rate
 data?
 
 

Resolution: resolved by Currency 2 RTF
Revised Text: Resolution: Change text in spec. stating the new behavior of the insertExchangeRate operation to account for date-based exchange rates.	
Revised Text:  
Add to section 2.3.11 at the end of this paragraph:  "Adding an exchange rate will add the exchange rate to the ExchangeRateManager.  An exception will be raised if the exchange rate already exists in the manager": 
An exception will be thrown if the exchangeRate overlaps in time one or more exchange rates that already exist in the ExchangeRateManager for the given rate type and source and target currency mnemonics.    For example:  an exchange rate of rateType = "spot", source = "USD", target = "GBP", beginDateTime = 15 July 1997 12:15pm and endDateTime = 15 July 1997 12:45pm currently exists in the manager.  Now an exchange rate is inserted of rateType = "spot", source = "USD", target = "GBP", beginDateTime = 15 July 1997 12:30pm and endDateTime = 15 July 1997 1:00pm.  The insertExchangeRate will throw an exception as the exchangeRate to be inserted spans an ExchangeRate already in existence within the ExchangeRateManager

Actions taken:
January 11, 1999: received issue
May 4, 2000: closed issue
Discussion: 

End of Annotations:=====
Return-Path: <Robert_Mickley@CYBORG.COM>
From: Robert_Mickley@CYBORG.COM
X-Lotus-FromDomain: CYBORG@CYBORG_NET
To: issues@omg.org
cc: Robert_Mickley@CYBORG.COM, Amy_Griffis@CYBORG.COM
Date: Mon, 11 Jan 1999 21:28:52 -0700
Subject: Currency RTF Issues
Content-Disposition: inline



Today is the deadline for comments for the Currency RTF.  Below is an
itemized list of additions to that list.

===========================================================================


Issue Title:  Modify and specify the behavior of the
insertExchangeRate
interface of the ExchangeRateManager
Issue Type: Text Revision
Issue Description:
The behavior of the insertExchangeRate() interface should be modified.
Since ExchangeRates will now have a window in time over which they are
effective, the behavior needs to address what happens when an exchange
rate
is attempted to be inserted that overlaps (in time) an existing
exchange
rate. i.e. Suppose an exchange rate exists in the system for a certain
rate
type, source currency mnemonic, target currency mnemonic, and is
effective
from 12:00 15 July 1998 until 12:30 15 July 1998. Now suppose we
attempt to
insert an exchange rate for the same rate type, source/target currency
mnemonics and is effective from 11:45 15 July 1998 until 12:15 15 July
1998. How does the insertExchangeRate() interface react in this case,
or in
any other case where the exchange rate to be inserted has an effective
window in time that in whole or in part overlaps existing exchange
rate
data?