The NestedParties component block is identical to the Parties Block. It is used in other component blocks and repeating groups when nesting will take place resulting in multiple occurrences of the <Parties> block within a single FIX message.. Use of NestedParties under these conditions avoids multiple references to the <Parties> block within the same message which is not allowed in FIX tag/value syntax.
Added in protocol FIX.4.3
See in: FIX.4.4, FIX.5.0, FIX.5.0SP1, FIX.5.0SP2, FIX.5.0SP2 EP240.
| Field or Component | Name | Description | Is Required | Added | Is Deprecated |
|---|---|---|---|---|---|
| 539 | NoNestedPartyIDs | Repeating group below should contain unique combinations of NestedPartyID, NestedPartyIDSource, and NestedPartyRole | FIX.4.3 | ||
| 524 | NestedPartyID | Used to identify source of NestedPartyID. Required if NestedPartyIDSource is specified. Required if NoNestedPartyIDs > 0. | FIX.4.3 | ||
| 525 | NestedPartyIDSource | Used to identify class source of NestedPartyID value (e.g. BIC). Required if NestedPartyID is specified. Required if NoNestedPartyIDs > 0. | FIX.4.3 | ||
| 538 | NestedPartyRole | Identifies the type of NestedPartyID (e.g. Executing Broker). Required if NoNestedPartyIDs > 0. | FIX.4.3 | ||
| 545 | NestedPartySubID | Sub-identifier (e.g. Clearing Acct for NestedPartyID=Clearing Firm) if applicable | FIX.4.3 |
Used in messages
- Allocation (J)
- Cross Order Cancel/Replace Request (a.k.a. Cross Order Modification Request) (t)
- Execution Report (8)
- Multileg Order Cancel/Replace (a.k.a. Multileg Order Modification Request) (AC)
- New Order – Cross (s)
- Order List (E)
- New Order – Multileg (AB)
- Order Single (D)
- Order Cancel/Replace Request (G)
- Registration Instructions (o)