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

Re: Important Update - Event Id



Title: RE: Important Update - Event Id

Every org and system may assign their own identifiers which map to those assigned by other participating orgs or systems.
Derek LaSalle
IB Architecture


 ----- Original Message -----
  From: "Katz, Ken" [Ken.Katz@xxxxxxxxx]
  Sent: 06/03/2008 01:57 PM AST
  To: <loanwg@xxxxxxxx>
  Subject: RE: Important Update - Event Id


I’m not sure why multiple vendors would have the same transaction.  What’s the scenario you’re concerned about?

 

It seems to me this should work along the lines of contractID, as you stated in an earlier email.  It should be driven by the Agent bank.

 

Regards,
Ken

 

Ken Katz

Global Product Manager

Misys
Solutions for Treasury & Capital Markets

1180 Avenue of Americas, 4TH Floor, New York, NY 10036, USA

T  +1 212 898 9596

F  +1 212 898 9510

E  Ken.Katz@xxxxxxxxx

www.misys.com

 


From: loanwg@xxxxxxxx [mailto:loanwg@xxxxxxxx] On Behalf Of Bhavik Katira
Sent: Tuesday, June 03, 2008 1:50 PM
To: loanwg@xxxxxxxx
Subject: RE: Important Update - Event Id

 

Ken, I guess the point here was not to identify multiple events but rather multiple references to the same event (by multiple vendors/participants).

 

From: loanwg@xxxxxxxx [mailto:loanwg@xxxxxxxx] On Behalf Of Katz, Ken
Sent: Tuesday, June 03, 2008 1:31 PM
To: loanwg@xxxxxxxx
Subject: RE: Important Update - Event Id

 

We would populate an event id with the internal transaction id.  This is unique for each business transaction (eg. drawdown, principal payment, fee payment, etc.).

 

I don’t see any reason for multiple event id’s, until we get to the more complex (group) transactions.  Then you would probably want an event id for the entire group and one for each transaction within the group.

 

Regards,
Ken

 

Ken Katz
Loan IQ Global Product Manager

Misys
Solutions for Treasury & Capital Markets

1180 Avenue of Americas, New York, NY 10036, USA

 

T  +1 212 898 9596

F  +1 212 898 9510

M +1 646 290 4611

ken.katz@xxxxxxxxx

 

www.misys.com

 


From: loanwg@xxxxxxxx [mailto:loanwg@xxxxxxxx] On Behalf Of Bhavik Katira
Sent: Tuesday, June 03, 2008 12:39 PM
To: loanwg@xxxxxxxx
Subject: RE: Important Update - Event Id

 

A follow up question to this is whether people think that we should have the ability to store multiple event id’s…?

I.e. different vendors may want to store their own id’s in the messages…

Any feedback on this from anyone…?

_____________________________________________
From: Bhavik Katira [mailto:bhavik.katira@xxxxxxxxx]
Sent: Tuesday, June 03, 2008 12:33 PM
To: 'loanwg@xxxxxxxx'
Subject: Important Update - Event Id

All,

It came to our attention that in previous discussions we spoke about introducing a business event id to all of our notices.

In the current design, there is a “message id” in the header section, which is unique for every single message sent out.

However, if for any reason there are multiple messages sent out all referring to the same business event then they should all have the same “event id”. This event id has been introduced at the Facility Notice and Loan Contract Notice levels. It is a required field and the sender of the message would populate the id based on their own scheme definition.

Please take a look at the attached and provide any feedback ASAP.

Note: The event id type used is inherited from an existing FpML structure.

Thanks,

BK

 << File: eventid.doc >>

 

"Misys" is the trade name for Misys plc (registered in England and Wales). Registration Number: 01360027. Registered office: Burleigh House, Chapel Oak, Salford Priors, Evesham WR11 8SP. For a list of Misys group operating companies please go to http://www.misys.com/html/about_us/group_operating_companies/. This email and any attachments have been scanned for known viruses using multiple scanners.

 

We believe that this email and any attachments are virus free, however the recipient must take full responsibility for virus checking. This email message is intended for the named recipient only. It may be privileged and/or confidential. If you are not the named recipient of this email please notify us immediately and do not copy it or use it for any purpose, nor disclose its contents to any other person. This email does not constitute the commencement of legal relations between you and Misys plc. Please refer to the executed contract between you and the relevant member of the Misysgroup for the identity of the contracting party with which you are dealing. 

   



"Misys" is the trade name for Misys plc (registered in England and Wales). Registration Number: 01360027.. Registered office: Burleigh House, Chapel Oak, Salford Priors, Evesham WR11 8SP. For a list of Misys group operating companies please go to http://www.misys.com/html/about_us/group_operating_companies/. This email and any attachments have been scanned for known viruses using multiple scanners.
 
We believe that this email and any attachments are virus free, however the recipient must take full responsibility for virus checking. This email message is intended for the named recipient only. It may be privileged and/or confidential. If you are not the named recipient of this email please notify us immediately and do not copy it or use it for any purpose, nor disclose its contents to any other person. This email does not constitute the commencement of legal relations between you and Misys plc. Please refer to the executed contract between you and the relevant member of the Misys group for the identity of the contracting party with which you are dealing. 

   


Generally, this communication is for informational purposes only and 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. In the event you are receiving the offering materials attached below related to your interest in hedge funds or private equity, this communication may be intended as an offer or solicitation for the purchase or sale of such fund(s). 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. Please refer to http://www.jpmorgan.com/pages/disclosures for disclosures relating to UK legal entities.