reda.005.001.03
Scope The InvestmentFundReportRequest message is sent by a report user, for example, a professional investor, investment fund distributor, market data provider, regulator or other interested party to the report provider, for example, a fund promoter, fund management company, transfer agent, or market data provider to request a report. The Investment Fund Report Request message can be used to request one or many fund reference data report messages. Usage If the InvestmentFundReportRequest message is used to request a fund reference data report then the request can specify the financial instrument for which the report is requested. Other appropriate parameters can also be included. It is also possible to indicate that the request is an open request, that is, there is no specific criteria for the report requested. For example, a request for a fund reference data report that is specified as “no criteria” means that the request is a request for a reference data report messages for all funds.
Message Construction
Every ISO20022 message has at the highest level what we call ‘building blocks’. Because the message is constructed as immutable records, the association is by composition. Below you can see the relationship between the message and its constituent building blocks: For comparison, see the ISO20022 official specification
classDiagram
direction LR
%% InvestmentFundReportRequestV03 recursion level 0 with max 0
InvestmentFundReportRequestV03 *-- "1..1" MessageIdentification1 : MessageIdentification
InvestmentFundReportRequestV03 *-- "0..1" AdditionalReference10 : PreviousReference
InvestmentFundReportRequestV03 *-- "0..1" AdditionalReference10 : RelatedReference
InvestmentFundReportRequestV03 *-- "1..1" IFundParameters4Choice : ReportRequest
Now, we will zero-in one-by-one on each of these building blocks.
MessageIdentification building block
Reference that uniquely identifies the message from a business application standpoint. Identifies a message by a unique identifier and the date and time when the message was created by the sender. For comparison, see the ISO20022 official specification
classDiagram
direction tb
%% MessageIdentification1 recursion level 0 with max 1
class MessageIdentification1{
Identification IsoMax35Text
CreationDateTime IsoISODateTime
}
MessageIdentification1 members
| Member name | Description | Data Type / Multiplicity |
|---|---|---|
| Identification | Identification of the message. | IsoMax35Text - Required 1..1 |
| CreationDateTime | Date of creation of the message. | IsoISODateTime - Required 1..1 |
PreviousReference building block
Reference to a linked message that was previously sent. Reference and reference issuer. For comparison, see the ISO20022 official specification
classDiagram
direction tb
%% AdditionalReference10 recursion level 0 with max 1
class AdditionalReference10{
Reference IsoMax35Text
MessageName IsoMax35Text
}
AdditionalReference10 *-- "0..1" PartyIdentification139 : ReferenceIssuer
%% PartyIdentification139 recursion level 1 with max 1
class PartyIdentification139{
LEI IsoLEIIdentifier
}
PartyIdentification139 *-- "1..1" IPartyIdentification125Choice : Party
AdditionalReference10 members
| Member name | Description | Data Type / Multiplicity |
|---|---|---|
| Reference | Reference issued by a party to identify an instruction, transaction or a message. | IsoMax35Text - Required 1..1 |
| ReferenceIssuer | Issuer of the reference. | PartyIdentification139 - Optional 0..1 |
| MessageName | Name of the message. | IsoMax35Text - Optional 0..1 |
RelatedReference building block
Reference to a linked message that was previously received. Reference and reference issuer. For comparison, see the ISO20022 official specification
classDiagram
direction tb
%% AdditionalReference10 recursion level 0 with max 1
class AdditionalReference10{
Reference IsoMax35Text
MessageName IsoMax35Text
}
AdditionalReference10 *-- "0..1" PartyIdentification139 : ReferenceIssuer
%% PartyIdentification139 recursion level 1 with max 1
class PartyIdentification139{
LEI IsoLEIIdentifier
}
PartyIdentification139 *-- "1..1" IPartyIdentification125Choice : Party
AdditionalReference10 members
| Member name | Description | Data Type / Multiplicity |
|---|---|---|
| Reference | Reference issued by a party to identify an instruction, transaction or a message. | IsoMax35Text - Required 1..1 |
| ReferenceIssuer | Issuer of the reference. | PartyIdentification139 - Optional 0..1 |
| MessageName | Name of the message. | IsoMax35Text - Optional 0..1 |
ReportRequest building block
Parameters for which the report is requested. Choice of fund parameters. For comparison, see the ISO20022 official specification
classDiagram direction tb %% IFundParameters4Choice recursion level 0 with max 1
FundParameters4Choice members
| Member name | Description | Data Type / Multiplicity |
|---|
Extensibility and generalization considerations
To facilitate generalized design patterns in the system, the InvestmentFundReportRequestV03 implementation follows a specific implementaiton pattern. First of all, InvestmentFundReportRequestV03 impleemnts IOuterRecord indicating it is the outermost logical part of the message definition. Like all message wrappers, InvestmentFundReportRequestV03Document implements IOuterDocument. Because InvestmentFundReportRequestV03 implements IOuterDocument, it is a suitable template parameter for IOuterDocument, and causes the internal ‘Message’ to be of type InvestmentFundReportRequestV03.
classDiagram
class IOuterRecord
InvestmentFundReportRequestV03 --|> IOuterRecord : Implements
InvestmentFundReportRequestV03Document --|> IOuterDocument~InvestmentFundReportRequestV03~ : Implements
class IOuterDocument~InvestmentFundReportRequestV03~ {
InvestmentFundReportRequestV03 Message
}
Document wrapper for serialization
The only real purpose InvestmentFundReportRequestV03Document serves is to cause the document to be serialized into the ‘urn:iso:std:iso:20022:tech:xsd:reda.005.001.03’ namespace. Therefore, it will probably be the usual practice to build the message and construct this wrapper at the last minute using InvestmentFundReportRequestV03.ToDocument() method. The returned InvestmentFundReportRequestV03Document value will serialize correctly according to ISO 20022 standards.
classDiagram
InvestmentFundReportRequestV03Document *-- InvestmentFundReportRequestV03 : Document
Sample of message format
This is an abbreviated version of what the message should look like.
<Document xmlns="urn:iso:std:iso:20022:tech:xsd:reda.005.001.03">
<InvstmtFndRptReq>
<MsgId>
<!-- MessageIdentification inner content -->
</MsgId>
<PrvsRef>
<!-- PreviousReference inner content -->
</PrvsRef>
<RltdRef>
<!-- RelatedReference inner content -->
</RltdRef>
<RptReq>
<!-- ReportRequest inner content -->
</RptReq>
</InvstmtFndRptReq>
</Document>
Data from ISO specification
This is the technical data from the specification document.
<messageDefinition
xmi:id="_qIk6YWolEeipaMTLlhaKMQ"
previousVersion="_Zsax2NEvEd-BzquC8wXy7w_-630681424"
name="InvestmentFundReportRequestV03"
definition="Scope
The InvestmentFundReportRequest message is sent by a report user, for example, a professional investor, investment fund distributor, market data provider, regulator or other interested party to the report provider, for example, a fund promoter, fund management company, transfer agent, or market data provider to request a report.
The Investment Fund Report Request message can be used to request one or many fund reference data report messages.
Usage
If the InvestmentFundReportRequest message is used to request a fund reference data report then the request can specify the financial instrument for which the report is requested. Other appropriate parameters can also be included. It is also possible to indicate that the request is an open request, that is, there is no specific criteria for the report requested. For example, a request for a fund reference data report that is specified as "no criteria" means that the request is a request for a reference data report messages for all funds."
registrationStatus="Registered"
messageSet="_hijK0WiLEeOuqdLlpUIWBw _qCumkAFwEeu2__1EbNXzuA"
xmlTag="InvstmtFndRptReq"
rootElement="Document"
xmlns:xmi="http://www.omg.org/XMI">
<messageBuildingBlock
xmi:id="_qIk6Y2olEeipaMTLlhaKMQ"
previousVersion="_Zsax2dEvEd-BzquC8wXy7w_-760876160"
name="MessageIdentification"
definition="Reference that uniquely identifies the message from a business application standpoint."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="1"
xmlTag="MsgId"
complexType="_Q7pG5Np-Ed-ak6NoX_4Aeg_-967008570" />
<messageBuildingBlock
xmi:id="_qIk6ZWolEeipaMTLlhaKMQ"
previousVersion="_Zsax2tEvEd-BzquC8wXy7w_62177576"
name="PreviousReference"
definition="Reference to a linked message that was previously sent."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="0"
xmlTag="PrvsRef"
complexType="_ZBypsWpTEeipaMTLlhaKMQ" />
<messageBuildingBlock
xmi:id="_qIk6Z2olEeipaMTLlhaKMQ"
previousVersion="_Zsax29EvEd-BzquC8wXy7w_1615234816"
name="RelatedReference"
definition="Reference to a linked message that was previously received."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="0"
xmlTag="RltdRef"
complexType="_ZBypsWpTEeipaMTLlhaKMQ" />
<messageBuildingBlock
xmi:id="_qIk6aWolEeipaMTLlhaKMQ"
previousVersion="_Zsax3NEvEd-BzquC8wXy7w_436796647"
name="ReportRequest"
definition="Parameters for which the report is requested."
registrationStatus="Provisionally Registered"
minOccurs="1"
xmlTag="RptReq"
complexType="_J-otAWomEeipaMTLlhaKMQ" />
<messageDefinitionIdentifier
businessArea="reda"
messageFunctionality="005"
flavour="001"
version="03" />
</messageDefinition>
ISO Building Blocks
The following items are used as building blocks to construct this message.