FpML Issues Tracker

788: ln-16 cannot compare two money types

August 29, 2008

closed

Minor

Always

Validation Rules

Admin

None

Summary

ln-16 tries to get the typed value of two elements with element only content. i.e. the elements contain other elements so you cannot compare them other than as sets, which is presumably not what is meant.

The rule today is: " ln-16 (Mandatory) Context: DrawdownNotice (complex type) [exists(facilityCommitmentPosition/priorAmount/shareAmount)] [same-currency((facilityCommitmentPosition/priorAmount/shareAmount,drawdownPayment/shareLoanContractAmount))] drawdownPayment/shareLoanContractAmount <= facilityCommitmentPosition/priorAmount/shareAmount. " The rule should be: " ln-16 (Mandatory) Context: DrawdownNotice (complex type) [exists(facilityCommitmentPosition/priorAmount/shareAmount)] [same-currency((facilityCommitmentPosition/priorAmount/shareAmount,drawdownPayment/shareLoanContractAmount))] drawdownPayment/shareLoanContractAmount/amount <= facilityCommitmentPosition/priorAmount/shareAmount/amount. "

Notes:

  • iyermakova

    12/11/08 8:04 pm

    The rule ln-16 has been corrected as proposed and submitted to trunk (4-5)

    • Leave an update

    You must be logged in to post an update.

    Report an Issue

    The FpML Issues Tracker is designed to facilitate public interaction in the standard.

    By registering you will be able to submit corrections and comments, generate reports, and view the complete issues archive for FpML.

    Report Issue