FpML Issues Tracker
closed
Minor
Always
Validation Rules
Admin
None
Summary
A new rule should be added to enforce disjoint Accounts.
The new rule is: " shared-19 (Mandatory) Context: AcceptQuote (complex type), AllocationAmended (complex type), AllocationCancelled (complex type), AllocationCreated (complex type), AmendmentConfirmed (complex type), CancelTradeCashflows (complex type), CancelTradeConfirmation (complex type), CancelTradeMatch (complex type), ConfirmationCancelled (complex type), ConfirmTrade (complex type), ContractCreated (complex type), ContractFullTermination (complex type), ContractFullTerminationCancelled (complex type), ContractIncreased (complex type), ContractIncreasedCancelled (complex type), ContractNovated (complex type), ContractNovatedCancelled (complex type), ContractPartialTermination (complex type), ContractPartialTerminationCancelled (complex type), ContractReferenceMessage (complex type), CreditEventNotification (complex type), DataDocument (complex type), DrawdownNotice (complex type), IncreaseConfirmed (complex type), InterestPaymentNotice (complex type), ModifyTradeConfirmation (complex type), ModifyTradeMatch (complex type), NovationMessage.model (group), OneOffFeeNotice (complex type), OnGoingFeeNotice (complex type), PositionReport (complex type), PositionsAcknowledged (complex type), PositionsAsserted (complex type), PositionsMatchResults (complex type), Quote (complex type), QuoteAcceptanceConfirmed (complex type), QuoteUpdated (complex type), RepaymentConfirmationNotice (complex type), RepaymentNotice (complex type), RequestAllocation (complex type), RequestAmendmentConfirmation (complex type), RequestIncreaseConfirmation (complex type), RequestPortfolio (complex type), RequestPositionReport (complex type), RequestQuote (complex type), RequestQuoteResponse (complex type), RequestTerminationConfirmation (complex type), RequestTradeConfirmation (complex type), RequestTradeMatch (complex type), RequestTradeStatus (complex type), RequestValuationReport (complex type), TerminationConfirmed (complex type), TradeAffirmation (complex type), TradeAffirmed (complex type), TradeAlleged (complex type), TradeAlreadyMatched (complex type), TradeAlreadySubmitted (complex type), TradeAmended (complex type), TradeAmendmentRequest (complex type), TradeAmendmentResponse (complex type), TradeCancelled (complex type), TradeCashflowsAsserted (complex type), TradeCashflowsMatchResult (complex type), TradeConfirmed (complex type), TradeCreated (complex type), TradeErrorResponse (complex type), TradeExecution (complex type), TradeExecutionCancelled (complex type), TradeExecutionModified (complex type), TradeIncreaseRequest (complex type), TradeIncreaseResponse (complex type), TradeMatched (complex type), TradeMismatched (complex type), TradeNotFound (complex type), TradeStatus (complex type), TradeTerminationRequest (complex type), TradeTerminationResponse (complex type), TradeUnmatched (complex type), ValuationReport (complex type)
Rule: Each party/account/accountId must be unique. The equivalence test for uniqueness tests the accountId content and accountIdScheme as strings. Additionally, where it exists each party/account/accountName must be unique. Comment: Each account must be disjoint. "
Notes:
matthewdr
06/03/08 1:44 pm
Agreed at VWG. Marc Gratacos to implement. The equivalence test will be represented as a function at Marc Gratacos’s request.
Agreed that Marc will raise this with the MTF.
lyteck
07/07/08 2:26 pm
fixed as proposed (using new specs format)
matthewdr
08/12/08 4:16 pm
Please see issue #717 as to why this was reopened.
lyteck
08/19/08 8:51 pm
fixed using format proposed in issue 722:
Added comment: Both an account’s name and account Id must be unique. The accountIdScheme is part of the accountId uniqueness check.
Updated rule definition: Each party/account/accountId must be unique. An account is identified by party/account/accountId or by party/account/accountName
matthewdr
08/20/08 9:27 am
Closing after review.