Component AllocAckGrp (ImplicitBlockRepeating)

Added in protocol FIX.4.4

See in: FIX.4.4, FIX.5.0SP1, FIX.5.0SP2, FIX.5.0SP2 EP240.

Field or Component Name Description Is Required Added Is Deprecated
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. FIX.4.4
79 AllocAccount Required if NoAllocs > 0. Must be first field in repeating group. FIX.4.4
661 AllocAcctIDSource FIX.4.4
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. FIX.4.4
1047 AllocPositionEffect FIX.4.4
467 IndividualAllocID FIX.4.4
776 IndividualAllocRejCode Required if NoAllocs > 0. FIX.4.4
BlockRepeating NestedParties FIX.4.4
161 AllocText Free format text field related to this AllocAccount (can be used here to hold text relating to the rejection of this AllocAccount) FIX.4.4
360 EncodedAllocTextLen Must be set if EncodedAllocText (361) field is specified and must immediately precede it. FIX.4.4
361 EncodedAllocText Encoded (non-ASCII characters) representation of the AllocText (161) field in the encoded format specified via the MessageEncoding (347) field. FIX.4.4
989 SecondaryIndividualAllocID Will allow the intermediary to specify an allocation ID generated by the system FIX.4.4
993 AllocCustomerCapacity Will allow for granular reporting of separate allocation detail within a single trade report or allocation message. FIX.4.4
992 IndividualAllocType Identifies whether the allocation is to be sub-allocated or allocated to a third party. FIX.4.4
80 AllocQty Quantity to be allocated to specific sub-account FIX.4.4