FpML Issues Tracker
closed
Major
Have not tried
Examples/Test Cases
Admin
mgratacos
Summary
I noticed that some of the examples for terminations have a negative value in changeInNotionalAmount (see confirmation view/business-processes/confirmation) while other have a positive one (see execution-advice examples). Something is wrong.
What is the correct approach? I thought it was a positive number always. This is how this field was implemented in 4.x versions, even though in those versions it was called decreaseInNotionalAmount.
If it is always a positive number, the type should be changed to disallow negative values.
Marc
Notes:
h_mcallister
02/23/12 12:19 am
The ‘termination’ and ‘increase’ events share the type TradeNotionalChange, hence the requirement for ‘changeInNotionalAmount’ to be signed. The termination samples require a negative change amount in all cases, because by definition a termination results in a decrease of the notional amount (to zero, under a full termination).
* The corollary is that any examples for increase require a +ve change amount.
mgratacos
07/16/12 4:25 pm
Within “TradeNotionalChange”, changed “outstandingNotionalAmount” element’s type from “Money” to “NonNegativeMoney”. Rationale: To be consistent with earlier change for “changeInNotionalAmount”, which was a correction to resolve some confusion in the examples. Note: This is a Non-compatible change (errata would be issued for FpML 5.1 and 5.2 RECs)