InvestmentFundReportRequestV02

reda.005.001.02

Scope A report user, for example, a professional investor, investment fund distributor, market data provider, regulator or other interested party sends the InvestmentFundReportRequest message to the report provider, for example, a fund promoter, fund management company, transfer agent, or market data provider to request a report. The InvestmentFundReportRequest message can be used to request one or many fund processing passport reports. Usage If the InvestmentFundReportRequest message is used to request a fund processing passport 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 processing passport report that is specified as “no criteria” means that the request is a request for all fund processing passports.

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
%% InvestmentFundReportRequestV02 recursion level 0 with max 0
InvestmentFundReportRequestV02 *-- "1..1" MessageIdentification1 : MessageIdentification
InvestmentFundReportRequestV02 *-- "0..1" AdditionalReference3 : PreviousReference
InvestmentFundReportRequestV02 *-- "0..1" AdditionalReference3 : RelatedReference
InvestmentFundReportRequestV02 *-- "1..1" IFundParameters3Choice : FundProcessingPassportReport
  

Now, we will zero-in one-by-one on each of these building blocks.

MessageIdentification building block

Reference that uniquely identifies a 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

PreviousReference building block

Reference to a linked message that was previously sent. References a related message or provides another reference, such as a pool reference, linking a set of messages. The party which issued the related reference may be the Sender of the referenced message or a party other than the Sender. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% AdditionalReference3 recursion level 0 with max 1
class AdditionalReference3{
    Reference IsoMax35Text
    MessageName IsoMax35Text
}
AdditionalReference3 *-- "0..1" IPartyIdentification2Choice : ReferenceIssuer
%% IPartyIdentification2Choice recursion level 1 with max 1
  

AdditionalReference3 members

RelatedReference building block

Reference to a linked message that was previously received. References a related message or provides another reference, such as a pool reference, linking a set of messages. The party which issued the related reference may be the Sender of the referenced message or a party other than the Sender. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% AdditionalReference3 recursion level 0 with max 1
class AdditionalReference3{
    Reference IsoMax35Text
    MessageName IsoMax35Text
}
AdditionalReference3 *-- "0..1" IPartyIdentification2Choice : ReferenceIssuer
%% IPartyIdentification2Choice recursion level 1 with max 1
  

AdditionalReference3 members

FundProcessingPassportReport building block

Parameters for which the fund processing passport report is requested. Choice of fund parameters. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% IFundParameters3Choice recursion level 0 with max 1
  

FundParameters3Choice members

Extensibility and generalization considerations

To facilitate generalized design patterns in the system, the InvestmentFundReportRequestV02 implementation follows a specific implementaiton pattern. First of all, InvestmentFundReportRequestV02 impleemnts IOuterRecord indicating it is the outermost logical part of the message definition. Like all message wrappers, InvestmentFundReportRequestV02Document implements IOuterDocument. Because InvestmentFundReportRequestV02 implements IOuterDocument, it is a suitable template parameter for IOuterDocument, and causes the internal ‘Message’ to be of type InvestmentFundReportRequestV02.

classDiagram
    class IOuterRecord
    InvestmentFundReportRequestV02 --|> IOuterRecord : Implements
    InvestmentFundReportRequestV02Document --|> IOuterDocument~InvestmentFundReportRequestV02~ : Implements
    class IOuterDocument~InvestmentFundReportRequestV02~ {
        InvestmentFundReportRequestV02 Message
     }
  

Document wrapper for serialization

The only real purpose InvestmentFundReportRequestV02Document serves is to cause the document to be serialized into the ‘urn:iso:std:iso:20022:tech:xsd:reda.005.001.02’ namespace. Therefore, it will probably be the usual practice to build the message and construct this wrapper at the last minute using InvestmentFundReportRequestV02.ToDocument() method. The returned InvestmentFundReportRequestV02Document value will serialize correctly according to ISO 20022 standards.

classDiagram
    InvestmentFundReportRequestV02Document *-- InvestmentFundReportRequestV02 : 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.02">
    <InvstmtFndRptReq>
        <MsgId>
            <!-- MessageIdentification inner content -->
        </MsgId>
        <PrvsRef>
            <!-- PreviousReference inner content -->
        </PrvsRef>
        <RltdRef>
            <!-- RelatedReference inner content -->
        </RltdRef>
        <FPPRpt>
            <!-- FundProcessingPassportReport inner content -->
        </FPPRpt>
    </InvstmtFndRptReq>
</Document>

Data from ISO specification

This is the technical data from the specification document.

<messageDefinition
  xmi:id="_Zsax2NEvEd-BzquC8wXy7w_-630681424"
  nextVersions="_qIk6YWolEeipaMTLlhaKMQ"
  name="InvestmentFundReportRequestV02"
  definition="Scope&#xD;&#xA;A report user, for example, a professional investor, investment fund distributor, market data provider, regulator or other interested party sends the InvestmentFundReportRequest message to the report provider, for example, a fund promoter, fund management company, transfer agent, or market data provider to request a report.&#xD;&#xA;The InvestmentFundReportRequest message can be used to request one or many fund processing passport reports.&#xD;&#xA;Usage&#xD;&#xA;If the InvestmentFundReportRequest message is used to request a fund processing passport 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 processing passport report that is specified as &quot;no criteria&quot; means that the request is a request for all fund processing passports."
  registrationStatus="Registered"
  messageSet="_wFQdsE2rEeG_I4xRYCA_7g"
  xmlTag="InvstmtFndRptReq"
  rootElement="Document"
  xmlns:xmi="http://www.omg.org/XMI">
  <messageBuildingBlock
    xmi:id="_Zsax2dEvEd-BzquC8wXy7w_-760876160"
    nextVersions="_qIk6Y2olEeipaMTLlhaKMQ"
    name="MessageIdentification"
    definition="Reference that uniquely identifies a message from a business application standpoint."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="MsgId"
    complexType="_Q7pG5Np-Ed-ak6NoX_4Aeg_-967008570" />
  <messageBuildingBlock
    xmi:id="_Zsax2tEvEd-BzquC8wXy7w_62177576"
    nextVersions="_qIk6ZWolEeipaMTLlhaKMQ"
    name="PreviousReference"
    definition="Reference to a linked message that was previously sent."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="0"
    xmlTag="PrvsRef"
    complexType="_Q6vvAdp-Ed-ak6NoX_4Aeg_2101402955" />
  <messageBuildingBlock
    xmi:id="_Zsax29EvEd-BzquC8wXy7w_1615234816"
    nextVersions="_qIk6Z2olEeipaMTLlhaKMQ"
    name="RelatedReference"
    definition="Reference to a linked message that was previously received."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="0"
    xmlTag="RltdRef"
    complexType="_Q6vvAdp-Ed-ak6NoX_4Aeg_2101402955" />
  <messageBuildingBlock
    xmi:id="_Zsax3NEvEd-BzquC8wXy7w_436796647"
    nextVersions="_qIk6aWolEeipaMTLlhaKMQ"
    name="FundProcessingPassportReport"
    definition="Parameters for which the fund processing passport report is requested."
    registrationStatus="Provisionally Registered"
    minOccurs="1"
    xmlTag="FPPRpt"
    complexType="_Q6l-ANp-Ed-ak6NoX_4Aeg_36568283" />
  <messageDefinitionIdentifier
    businessArea="reda"
    messageFunctionality="005"
    flavour="001"
    version="02" />
</messageDefinition>

ISO Building Blocks

The following items are used as building blocks to construct this message.