[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

FpML-VALU changes to position model



All,

 

The Business Process Working Group is working on having an FpML representation for portfolio reconciliation. One of the tasks has been to review the current position representation defined by this group because we wanted to reuse the same representation for portfolio reconciliation. We have identified some potential changes to the Position type.

 

  • Position_current.jpg is the current position representation in 4.2 defined by this working group.
  • Positon_new.jpg is the new proposed position representation defined by the Business Process Working Group, which will be used for position reporting and portfolio reconciliation.

 

The changes include:

  • Removed containers scheduledDates and valuations since the architecture specification doesn’t recommend its use.
  • Made reportingRoles optional since for some portfolio reconciliation messages it’s not appropriate.
  • Added position identification elements: positionId, version.
  • Changed constituent content
    • Made choice structure optional for extensibility purposes.
    • Added positionVersionReference to reference the information of a submitted position.
    • Changed to a single partyTradeIdentifier block to reduce ambiguity.

 

Let me know your thoughts.

 

Best regards,

-Marc

Attachment: fpml-valuation-4-2.xsd
Description: fpml-valuation-4-2.xsd

Attachment: PositionReport_new.jpg
Description: PositionReport_new.jpg

Attachment: Position_new.jpg
Description: Position_new.jpg

Attachment: Position_current.jpg
Description: Position_current.jpg