Message RequestForPositions Scenario base

SYNOPSIS: Request For Positions

ID MsgType Abbr Flow
73ANReqForPoss

Pedigree

Added EP Updated EP Deprecated EP
FIX.4.4

Responses

None

Members

RequestForPositions base members
ID Name Abbr Presence Description
1024StandardHeaderHdrrequiredSYNOPSIS: The standard FIX message header
ELABORATION:
710PosReqIDReqID required SYNOPSIS: Unique identifier for the position maintenance request as assigned by the submitter
724PosReqTypeReqTyp required SYNOPSIS: Unique identifier for the position maintenance request as assigned by the submitter
573MatchStatusMtchStat optional SYNOPSIS: The status of this trade with respect to matching or comparison
263SubscriptionRequestTypeSubReqTyp optional SYNOPSIS: Subscription Request Type
1012PartiesPtyrequiredSYNOPSIS: The Parties component block is used to identify and convey information on the entities both central and peripheral to the financial transaction represented by the FIX message containing the Parties Block. The Parties block allows many different types of entites to be expressed through use of the PartyRole field and identifies the source of the PartyID through the the PartyIDSource.
ELABORATION:
1AccountAcct required SYNOPSIS: Account mnemonic as agreed between buy and sell sides, e.g. broker and institution or investor/intermediary and fund manager.
660AcctIDSourceAcctIDSrc optional SYNOPSIS: Used to identify the source of the Account (1) code. This is especially useful if the account is a new account that the Respondent may not have setup yet in their system.
581AccountTypeAcctTyp required SYNOPSIS: Type of account associated with an order
1003InstrumentInstrmtoptionalSYNOPSIS: The Instrument component block contains all the fields commonly used to describe a security or instrument. Typically the data elements in this component block are considered the static data of a security, data that may be commonly found in a security master database. The Instrument component block can be used to describe any asset type supported by FIX.
ELABORATION:
15CurrencyCcy optional SYNOPSIS: Identifies currency used for price. Absence of this field is interpreted as the default for the security. It is recommended that systems provide the currency value whenever possible. See "Appendix 6-A: Valid Currency Codes" for information on obtaining valid values.
2019InstrmtLegGrpLegoptionalSYNOPSIS:
ELABORATION:
2066UndInstrmtGrpUndlyoptionalSYNOPSIS:
ELABORATION:
715ClearingBusinessDateBizDt required SYNOPSIS: The "Clearing Business Date" referred to by this maintenance request.
716SettlSessIDSetSesID optional SYNOPSIS: Identifies a specific settlement session
717SettlSessSubIDSetSubID optional SYNOPSIS: SubID value associated with SettlSessID (76)
2064TrdgSesGrpTrdSesoptionalSYNOPSIS:
ELABORATION:
60TransactTimeTxnTm required SYNOPSIS: Time of execution/order creation (expressed in UTC (Universal Time Coordinated, also known as "GMT")
725ResponseTransportTypeRspTransportTyp optional SYNOPSIS: Identifies how the response to the request should be transmitted
726ResponseDestinationRspDest optional SYNOPSIS: URI (Uniform Resource Identifier) for details) or other pre-arranged value. Used in conjunction with ResponseTransportType (725) value of Out-of-Band to identify the out-of-band destination. See "Appendix 6-B FIX Fields Based Upon Other Standards"
58TextTxt optional SYNOPSIS: Free format text string (Note: this field does not have a specified maximum length)
354EncodedTextLenEncTxtLen optional SYNOPSIS: Byte length of encoded (non-ASCII characters) EncodedText (355) field.
355EncodedTextEncTxt optional SYNOPSIS: Encoded (non-ASCII characters) representation of the Text (58) field in the encoded format specified via the MessageEncoding (347) field. If used, the ASCII (English) representation should also be specified in the Text field.
1025StandardTrailerTrlrrequiredSYNOPSIS: The standard FIX message trailer
ELABORATION: