FpML Issues Tracker

353: Trade version clashes

April 3, 2007

closed

Major

Always

Architecture

Admin

andrew

Summary

When a trade changes there is a new trade version. The same occurs for a contract. How do we prevent two different systems both processing a change and either creating different version numbers for the same change, or having the same version number for different changes?

Notes:

  • andrew

    05/30/07 9:50 am

    CUG messages are notifications of changes agreed upstream. If a trade version has changed that should be indicated by the content of the message which should contain the new trade version. The recipients should update themselves to reflect the version they are sent – they should not be creating new versions.

  • matthew

    05/30/07 11:09 am

    This is nothing to do with the SWIFT FpML CUG, those messages were merely an example. Consider the problem rather than why the example exists.

  • matthew

    05/31/07 2:14 pm

    The description that the AWG had was that the tradeId is versioned and not the trade. This needs to be made clear in the specification.

  • mgratacos

    06/07/07 9:03 am

    Documentation has been added to the schema for VersionedTradeId and VersionedContractId:



    Trade Id with Version Support





    The version of the trade id. The tradeId is versioned and not the trade.



    • 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