complexType "TradeCashflowsProposedMatch"

Namespace: | http://www.fpml.org/FpML-5/reporting
Content: | complex, 7 elements
Defined: | globally in fpml-reconciliation-5-3.xsd; see XML source
Used: | at 1 location

Content Model Diagram

XML Representation Summary
<...>
Content: | tradeCashflowsId?, (tradeIdentifyingItems?, adjustedPaymentDate?, payment*)?, matchId?, difference*, matchScore?
</...>

Content Model Elements (7):

  adjustedPaymentDate (defined in TradeCashflows.model group),
  difference (defined in ProposedMatch.model group),
  matchId (defined in ProposedMatch.model group),
  matchScore,
  payment (defined in TradeCashflows.model group),
  tradeCashflowsId (defined in IdAndTradeCashflows.model group),
  tradeIdentifyingItems (defined in TradeCashflows.model group)

All Direct / Indirect Based Elements (1):

  proposedMatch (in tradeCashflowsMatchResult)

Known Usage Locations

- As direct type of elements (1):
  proposedMatch (in tradeCashflowsMatchResult)

Annotation
"Other side's" cashflow that meets the minimimum matching criteria and is proposed as match to the cash flow that is being asserted.
XML Source (w/o annotations (1); see within schema source)

<xsd:complexType name="TradeCashflowsProposedMatch"> <xsd:sequence> <xsd:group ref="IdAndTradeCashflows.model"/> <xsd:group ref="ProposedMatch.model"/> </xsd:sequence> </xsd:complexType>

XML schema documentation generated with DocFlex/XML 1.8.6b2 using DocFlex/XML XSDDoc 2.5.1 template set. All content model diagrams generated by Altova XMLSpy via DocFlex/XML XMLSpy Integration.