Hi all, re: confirmations of repos : The samples that I have put together are based on the confirmation process that is outlined in the link below. http://www.fpml.org/spec/2006/tr-fpml-4-2-2006-09-28/html/fpml-4-2-intro.html#s3.3.3 I have also reused the samples data provided in the SMPG document (see page 6) so it should make it easy for everyone to better understand the mapping with ISO150022 messages and use a common reference. Request Trade Confirmation, from partyA (See attached file: RequestConfirmationFromPartyA.xml) The equivalent message, sent from partyB (See attached file: RequestConfirmationFromPartyB.xml) The 'matched' message sent by the confirmations provider : (See attached file: TradeMatchedMessage.xml) ConfirmTrade is actually the same content model as RequestTradeConfirmation, so I am not repeating it Here is an example of an Error messages. FpML has codified some reason codes - this one actually means that the product is not supported. This is what you would get in response if you were to try to submit a confirmation request to DTCC before they get a chance to implement the repo model... (See attached file: MessageRejected.xml) And for those who are interested, the entire set of operations that FpML supports in the context of Confirmations is available in the image document below; it follows a WSDL representation of the service and its operations. (See attached file: confirmationsOperations.JPG) Please have a look at those messages and prepare feedback and questions. See you all tomorrow for the WG meeting. -s This communication is for informational purposes only. It is not intended as an offer or solicitation for the purchase or sale of any financial instrument or as an official confirmation of any transaction. All market prices, data and other information are not warranted as to completeness or accuracy and are subject to change without notice. Any comments or statements made herein do not necessarily reflect those of JPMorgan Chase & Co., its subsidiaries and affiliates. This transmission may contain information that is privileged, confidential, legally privileged, and/or exempt from disclosure under applicable law. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or use of the information contained herein (including any reliance thereon) is STRICTLY PROHIBITED. Although this transmission and any attachments are believed to be free of any virus or other defect that might affect any computer system into which it is received and opened, it is the responsibility of the recipient to ensure that it is virus free and no responsibility is accepted by JPMorgan Chase & Co., its subsidiaries and affiliates, as applicable, for any loss or damage arising in any way from its use. If you received this transmission in error, please immediately contact the sender and destroy the material in its entirety, whether in electronic or hard copy format. Thank you.
Attachment:
RequestConfirmationFromPartyA.xml
Description: Binary data
Attachment:
RequestConfirmationFromPartyB.xml
Description: Binary data
Attachment:
TradeMatchedMessage.xml
Description: Binary data
Attachment:
MessageRejected.xml
Description: Binary data
Attachment:
confirmationsOperations.JPG
Description: JPEG image
