Page Comparison

...

This is the critical piece of time sensitive configuration. There are different options for managing the periods, but regardless of your preferred method, the configuration must follow these two rules:

1. Begin Date (220), which is the : effective date of the change, must

   1. Must be equal to an actual coupon date for

   underlying security changes; spread

   1. most changes

      1. Spread changes can occur on any date

   2. Must be less than/equal to Dated Date (1183) for the initial period

   3. If you are changing the underlying security and using an Adjusted day count basis such as ADJMBC (Modified Following - Adjusted), Begin Date must equal the adjusted coupon date

2. End Date (221) of one period must not overlap with Begin Date of the subsequent period
   

   Because Begin Date indicates the

   : set to one calendar day before effective date of the change,

   each End Date must be one calendar day prior to

   or leave null if there are no subsequent changes

   1. Must not overlap with Begin Date of the subsequent period

...

There is additional functionality for swaps in Issue Viewer V17 to simplify the manual workflow. The following fields become available after saving a swap with Time Sensitive = Yes, then reopening

...

it. They will not be available when setting Time Sensitive = Yes for the first time.

• Existing Effective Dates (7017): returns any time sensitive records that have been added and the associated data

• As Of Effective Date (4212): date a time sensitive change takes effects; this must be populated and is used as Begin Date when defining a time sensitive data change

Option 2: Managing Records Directly

...