[ http://tools.oasis-open.org/issues/browse/OFFICE-2704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=22416#action_22416 ]
Robert Weir commented on OFFICE-2704:
--------------------------------------
I checked the published ISO/IEC 29500 text for ACCRINT. It defines this function as:
ACCRINT(issue, first_interest, settlement, rate, [par], frequency, [basis])
This is odd for three reasons:
1) An optional parameter (par) followed by a mandatory parameter (frequency)
2) No default value given for optional par
3) No mention of a calc_method parameter
I assume this is all wrong?
An equation is give in ISO/IEC 29500 for this function:
ACCRINT = par * (rate/frequency) * sum {i=1 to NC} (A_i/NL_i)
where A_i is "numberd of accrued days for the ith qyuasi-coupon period within odd period"
NL_i is "normal length in dayts of the ith quaiso-coupon period within odd period"
and NC is "number of quasi-coupon periods that fit in odd period".
but I have no independent conformation that this is correct. The fact that there is no mention of calc_method makes me think it is missing something.
> ACCRINT description is inconsistent
> -----------------------------------
>
> Key: OFFICE-2704
> URL: http://tools.oasis-open.org/issues/browse/OFFICE-2704
> Project: OASIS Open Document Format for Office Applications (OpenDocument) TC
> Issue Type: Bug
> Components: OpenFormula
> Affects Versions: ODF 1.2 CD 05
> Reporter: Andreas Guelzow
> Assignee: Robert Weir
> Fix For: ODF 1.2 CD 06
>
>
> The description of ACCRINT has several issues:
> 1) The constraint is given as: issue < first < settlement ; coupon > 0; par > 0. OOo and Excel clearly permit settlement<first and most examples on the web seem to be of that kind.
> 2) The short description of calc_method reads "A logical value that specifies how to treat the case where settlement>first." which seems to imply that there is a permitted case where settlement > first does not hold.
> 3) The formula given contains the undefined variables start-of-period and end-of-period. Especially in view of the statement "ACCRINT
> supports short, standard, and long coupon periods.", it is not clear what those values are.
> 4) If the constraint is changed, a formula for the settlement < first case is needed.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
