P
(PeteCresswell)
I'm about to start writing a small-ish bond trading system.
Some years ago, I wrote a much trading system, but this one has a
new wrinkle: the securities master file/tables will reside
somewhere else. Call it "The Master Repository".
I will just be a consumer of The Master Repository - unable to
add/change/delete any information.
My system will mainly contain trades - each of which will refer
to a security in The Master Repository.
The chicken-and-egg conundrum comes when one of my guys has to
buy a bond that's not yet in The Master Repository.
As the last step in processing a "Buy" trade, we will generate a
trade ticket or a .CSV or whatever... that goes to the Fund
Accounting group - which duly sets up the security in question in
The Master Repository if it is not already there.
But meanwhile, I've got to create this temporary security - since
I have to link the trade to *something*.... or do I?
Anybody been here? Is there a commonly-accepted practice?
Some years ago, I wrote a much trading system, but this one has a
new wrinkle: the securities master file/tables will reside
somewhere else. Call it "The Master Repository".
I will just be a consumer of The Master Repository - unable to
add/change/delete any information.
My system will mainly contain trades - each of which will refer
to a security in The Master Repository.
The chicken-and-egg conundrum comes when one of my guys has to
buy a bond that's not yet in The Master Repository.
As the last step in processing a "Buy" trade, we will generate a
trade ticket or a .CSV or whatever... that goes to the Fund
Accounting group - which duly sets up the security in question in
The Master Repository if it is not already there.
But meanwhile, I've got to create this temporary security - since
I have to link the trade to *something*.... or do I?
Anybody been here? Is there a commonly-accepted practice?