Replace allocation message

gideonabrams_x · August 25, 2005, 4:22pm

Imported from previous forum

gideonabrams_x · August 25, 2005, 4:22pm

What would be the correct response to the following situation:

A client sends an allocation AllocTransType=preliminary this is accepted and then we send back an AllocTransType=calculated.

That message is then rejected by client and then they wish to replace the initial allocation.

Would we send an unsolicited AllocTransType=Replace?
OR
an unsolicited AllocTransType=calculated?
OR
would the client send a new AllocTransType=preliminary with a new Allocation ID?

fplpo_x · August 26, 2005, 12:18pm

[ original email was from Leigh Thompson - leigh.thompson@rbos.com ]
I’m guessing you are using 4.2, as the fields below have been replaced in 4.4. It looks like you could get into problems with the AllocID, but the AllocReportID introduced in 4.4 might resolve this.

The scenario you’ve described is similar to fix-42-with_errata_20010501.doc Appendix K 2. Buyside-initiated with Misc Fee computation, to which I’ve added my 2p worth.

→ Allocation (AllocTransTyp=Preliminary, AllocID=1a)
← AllocationACK (AllocStatus=Received Not Yet Processed, AllocID=1a)
← Allocation (AllocTransTyp=Calculated, AllocID=1b, RefAllocID=1a)
→ AllocationACK (AllocStatus=Received Not Yet Processed, AllocID=1b)
→ AllocationACK (AllocStatus=Rejected, AllocID=1b, AllocRejCode=)
→ Allocation (AllocTransType=Replace,AllocID=2a, RefAllocID=1a,)
← AllocationACK (AllocStatus=Received Not Yet Processed, AllocID=2a)
← Allocation (AllocTransTyp=Calculated, AllocID=2b, RefAllocID=2a)
→ AllocationACK (AllocStatus=Received Not Yet Processed, AllocID=2b)
→ AllocationACK (AllocStatus=Accepted, AllocID=2b)

Also from the 4.2 spec

“Replacement allocation messages must contain all data for the replacement allocation. Calculated allocations should have a unique AllocID and use RefAllocID to specify the AllocID from the preliminary.”

I’m not 100% on this, can anyone else confirm?

regards

What would be the correct response to the following situation:

A client sends an allocation AllocTransType=preliminary this is accepted
and then we send back an AllocTransType=calculated.

That message is then rejected by client and then they wish to replace
the initial allocation.

Would we send an unsolicited AllocTransType=Replace? OR an unsolicited
AllocTransType=calculated? OR would the client send a new
AllocTransType=preliminary with a new Allocation ID?

gideonabrams_x · August 26, 2005, 2:28pm

Many thanks for your response, that clears up that scenario.

Following on from that, if we allocate incorrectly and then the client rejects the calculated message we send, what would be the appropriate response?

Would we send an unsolicited AllocTransType=Calculated with correct allocation?

OR

Would the client reject render the initial allocation invalid and as such a new allocation message is sent by the client

OR

Would we send an unsolicited AllocTransType=Replace with correct allocation?

I’m guessing you are using 4.2, as the fields below have been replaced
in 4.4. It looks like you could get into problems with the AllocID, but
the AllocReportID introduced in 4.4 might resolve this.

The scenario you’ve described is similar to fix-42-
with_errata_20010501.doc Appendix K 2. Buyside-initiated with Misc Fee
computation, to which I’ve added my 2p worth.

→ Allocation (AllocTransTyp=Preliminary, AllocID=1a) ← AllocationACK
(AllocStatus=Received Not Yet Processed, AllocID=1a) ← Allocation
(AllocTransTyp=Calculated, AllocID=1b, RefAllocID=1a) → AllocationACK
(AllocStatus=Received Not Yet Processed, AllocID=1b) → AllocationACK
(AllocStatus=Rejected, AllocID=1b, AllocRejCode=) → Allocation
(AllocTransType=Replace,AllocID=2a, RefAllocID=1a,) ← AllocationACK
(AllocStatus=Received Not Yet Processed, AllocID=2a) ← Allocation
(AllocTransTyp=Calculated, AllocID=2b, RefAllocID=2a) → AllocationACK
(AllocStatus=Received Not Yet Processed, AllocID=2b) → AllocationACK
(AllocStatus=Accepted, AllocID=2b)

Also from the 4.2 spec

“Replacement allocation messages must contain all data for the
replacement allocation. Calculated allocations should have a unique
AllocID and use RefAllocID to specify the AllocID from the preliminary.”

I’m not 100% on this, can anyone else confirm?

regards

What would be the correct response to the following situation:

A client sends an allocation AllocTransType=preliminary this is
accepted and then we send back an AllocTransType=calculated.

That message is then rejected by client and then they wish to replace
the initial allocation.

Would we send an unsolicited AllocTransType=Replace? OR an unsolicited
AllocTransType=calculated? OR would the client send a new
AllocTransType=preliminary with a new Allocation ID?

fplpo_x · August 26, 2005, 3:55pm

[ original email was from Leigh Thompson - leigh.thompson@rbos.com ]
My apologies, I am incorrect.

There is one line in 4.4 Vol5 (p23) which states, “A rejected Allocation Report must be resolved out-of-band.” so my previous response would be incorrect.

Many thanks for your response, that clears up that scenario.

Following on from that, if we allocate incorrectly and then the
client rejects the calculated message we send, what would be the
appropriate response?

Would we send an unsolicited AllocTransType=Calculated with correct
allocation?

OR

Would the client reject render the initial allocation invalid and as
such a new allocation message is sent by the client

OR

Would we send an unsolicited AllocTransType=Replace with correct
allocation?

I’m guessing you are using 4.2, as the fields below have been replaced
in 4.4. It looks like you could get into problems with the AllocID,
but the AllocReportID introduced in 4.4 might resolve this.

The scenario you’ve described is similar to fix-42-
with_errata_20010501.doc Appendix K 2. Buyside-initiated with Misc Fee
computation, to which I’ve added my 2p worth.

→ Allocation (AllocTransTyp=Preliminary, AllocID=1a) ← AllocationACK
(AllocStatus=Received Not Yet Processed, AllocID=1a) ← Allocation
(AllocTransTyp=Calculated, AllocID=1b, RefAllocID=1a) → AllocationACK
(AllocStatus=Received Not Yet Processed, AllocID=1b) → AllocationACK
(AllocStatus=Rejected, AllocID=1b, AllocRejCode=) → Allocation
(AllocTransType=Replace,AllocID=2a, RefAllocID=1a,) ← AllocationACK
(AllocStatus=Received Not Yet Processed, AllocID=2a) ← Allocation
(AllocTransTyp=Calculated, AllocID=2b, RefAllocID=2a) → AllocationACK
(AllocStatus=Received Not Yet Processed, AllocID=2b) → AllocationACK
(AllocStatus=Accepted, AllocID=2b)

Also from the 4.2 spec

“Replacement allocation messages must contain all data for the
replacement allocation. Calculated allocations should have a unique
AllocID and use RefAllocID to specify the AllocID from the
preliminary.”

I’m not 100% on this, can anyone else confirm?

regards

What would be the correct response to the following situation:

A client sends an allocation AllocTransType=preliminary this is
accepted and then we send back an AllocTransType=calculated.

That message is then rejected by client and then they wish to
replace the initial allocation.

Would we send an unsolicited AllocTransType=Replace? OR an
unsolicited AllocTransType=calculated? OR would the client send a
new AllocTransType=preliminary with a new Allocation ID?

Topic		Replies	Views
Replace allocation message 4.0/4.2 imported , allocations , xid_160832	1	10	September 9, 2005
Replaced allocations 4.0 / 4.2 imported , allocations , xid_160830	1	10	September 8, 2005
Which Tags are modifiable in a Replace Allocation Request imported , general-qa , xid_166379	2	13	July 15, 2003
Pre/Pos Allocation imported , allocations , xid_160881	2	12	November 13, 2003
Allocation Cancel/Replace Requests imported , allocations , xid_160813	2	14	September 17, 2004

Replace allocation message

Related topics