AllocAckGrp/FIX.5.0+
From FIXwiki
Content of Component AllocAckGrp
| TagText | FieldName or ComponentName | Required | Description |
|---|---|---|---|
| 78 | NoAllocs | This repeating group is optionally used for messages with AllocStatus = 2 (account level reject), AllocStatus = 0 (accepted), to provide details of the individual accounts that were accepted or rejected. In the case of a reject, the reasons for the rejection should be specified. This group should not be populated where AllocStatus has any other value.
Indicates number of allocation groups to follow.
| |
| 79 | AllocAccount | Required if NoAllocs > 0. Must be first field in repeating group.
| |
| 661 | AllocAcctIDSource | ||
| 366 | AllocPrice | Used when performing "executed price" vs. "average price" allocations (e.g. Japan). AllocAccount plus AllocPrice form a unique Allocs entry. Used in lieu of AllocAvgPx.
| |
| 1047 | AllocPositionEffect | ||
| 467 | IndividualAllocID | ||
| 776 | IndividualAllocRejCode | Required if NoAllocs > 0.
| |
| NestedParties | |||
| 161 | AllocText | Free format text field related to this AllocAccount (can be used here to hold text relating to the rejection of this AllocAccount)
| |
| 360 | EncodedAllocTextLen | Must be set if EncodedAllocText field is specified and must immediately precede it.
| |
| 361 | EncodedAllocText | Encoded (non-ASCII characters) representation of the AllocText field in the encoded format specified via the MessageEncoding field.
| |
| 989 | SecondaryIndividualAllocID | Will allow the intermediary to specify an allocation ID generated by the system
| |
| 993 | AllocCustomerCapacity | Will allow for granular reporting of separate allocation detail within a single trade report or allocation message.
| |
| 992 | IndividualAllocType | Identifies whether the allocation is to be sub-allocated or allocated to a third party.
| |
| 80 | AllocQty | Quantity to be allocated to specific sub-account
|
Notes
Please post comments, clarifications, examples here. Click on the edit button on the right and away you go!
Don't forget to refer to the FPL Discussion Groups to back up anything you write. You will often find the authoritative statements on matters of FIX specification interpretation there. Links from FIXwiki pages to relevant discussions on the FPL site are very valuable.
For example if you were writing a clarification on how to specify the "quantity" of an order in FIX, you might add the following relevant link, http://www.fixprotocol.org/discuss/read/f5014573, to back up your points.
