PortfolioTransferCancellationRequestV07

sese.014.001.07

Scope An instructing party, for example, a (new) plan manager (Transferee), sends the PortfolioTransferCancellationRequest message to the executing party, for example, a (old) plan manager (Transferor), to request the cancellation of a previously sent PortfolioTransferInstruction. Usage The PortfolioTransferCancellationRequest message is used to request the cancellation of an entire PortfolioTransferInstruction message, that is, all the product transfers that it contained. The cancellation request can be specified either by:

• quoting the transfer references of all the product transfers listed in the PortfolioTransferInstruction message, or,
• quoting the details of all the product transfers (this includes TransferReference) listed in PortfolioTransferInstruction message. The message identification of the PortfolioTransferInstruction may also be quoted in PreviousReference. It is also possible to request the cancellation of PortfolioTransferInstruction by just quoting its message identification in PreviousReference.

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
%% PortfolioTransferCancellationRequestV07 recursion level 0 with max 0
PortfolioTransferCancellationRequestV07 *-- "1..1" MessageIdentification1 : MessageReference
PortfolioTransferCancellationRequestV07 *-- "0..1" AdditionalReference6 : PoolReference
PortfolioTransferCancellationRequestV07 *-- "0..1" AdditionalReference6 : PreviousReference
PortfolioTransferCancellationRequestV07 *-- "0..1" AdditionalReference6 : RelatedReference
PortfolioTransferCancellationRequestV07 *-- "1..1" ICancellation11Choice : Cancellation
PortfolioTransferCancellationRequestV07 *-- "0..1" MarketPracticeVersion1 : MarketPracticeVersion
  

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

MessageReference building block

Identifies the message. 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

PoolReference building block

Collective reference identifying a set of messages. Reference to a related message or transaction. For comparison, see the ISO20022 official specification

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

AdditionalReference6 members

PreviousReference building block

Reference to a linked message that was previously sent. Reference to a related message or transaction. For comparison, see the ISO20022 official specification

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

AdditionalReference6 members

RelatedReference building block

Reference to a linked message that was previously received. Reference to a related message or transaction. For comparison, see the ISO20022 official specification

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

AdditionalReference6 members

Cancellation building block

Choice between cancellation by transfer details or reference. Choice between cancellation by transfer details or reference. For comparison, see the ISO20022 official specification

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

Cancellation11Choice members

MarketPracticeVersion building block

Identifies the market practice to which the message conforms. Identifies the implementation and version. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% MarketPracticeVersion1 recursion level 0 with max 1
class MarketPracticeVersion1{
    Name IsoMax35Text
    Date IsoISOYearMonth
    Number IsoMax35Text
}
  

MarketPracticeVersion1 members

Extensibility and generalization considerations

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

classDiagram
    class IOuterRecord
    PortfolioTransferCancellationRequestV07 --|> IOuterRecord : Implements
    PortfolioTransferCancellationRequestV07Document --|> IOuterDocument~PortfolioTransferCancellationRequestV07~ : Implements
    class IOuterDocument~PortfolioTransferCancellationRequestV07~ {
        PortfolioTransferCancellationRequestV07 Message
     }
  

Document wrapper for serialization

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

classDiagram
    PortfolioTransferCancellationRequestV07Document *-- PortfolioTransferCancellationRequestV07 : 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:sese.014.001.07">
    <PrtflTrfCxlReq>
        <MsgRef>
            <!-- MessageReference inner content -->
        </MsgRef>
        <PoolRef>
            <!-- PoolReference inner content -->
        </PoolRef>
        <PrvsRef>
            <!-- PreviousReference inner content -->
        </PrvsRef>
        <RltdRef>
            <!-- RelatedReference inner content -->
        </RltdRef>
        <Cxl>
            <!-- Cancellation inner content -->
        </Cxl>
        <MktPrctcVrsn>
            <!-- MarketPracticeVersion inner content -->
        </MktPrctcVrsn>
    </PrtflTrfCxlReq>
</Document>

Data from ISO specification

This is the technical data from the specification document.

<messageDefinition
  xmi:id="_4S4okR8OEeWpZde3LQh6dg"
  nextVersions="_gblKUYZMEeemXK0UETsSiA"
  previousVersion="_-zqTYQgLEeSFYfyUKDXKaw"
  name="PortfolioTransferCancellationRequestV07"
  definition="Scope&#xD;&#xA;An instructing party, for example, a (new) plan manager (Transferee), sends the PortfolioTransferCancellationRequest message to the executing party, for example, a (old) plan manager (Transferor), to request the cancellation of a previously sent PortfolioTransferInstruction.&#xD;&#xA;Usage&#xD;&#xA;The PortfolioTransferCancellationRequest message is used to request the cancellation of an entire PortfolioTransferInstruction message, that is, all the product transfers that it contained. The cancellation request can be specified either by:&#xD;&#xA;- quoting the transfer references of all the product transfers listed in the PortfolioTransferInstruction message, or,&#xD;&#xA;- quoting the details of all the product transfers (this includes TransferReference) listed in PortfolioTransferInstruction message.&#xD;&#xA;The message identification of the PortfolioTransferInstruction may also be quoted in PreviousReference. It is also possible to request the cancellation of PortfolioTransferInstruction by just quoting its message identification in PreviousReference."
  registrationStatus="Registered"
  messageSet="_urpIICeJEeOCeO5e7islRQ"
  xmlTag="PrtflTrfCxlReq"
  rootElement="Document"
  xmlns:xmi="http://www.omg.org/XMI">
  <messageBuildingBlock
    xmi:id="_4S4okx8OEeWpZde3LQh6dg"
    nextVersions="_gblKU4ZMEeemXK0UETsSiA"
    previousVersion="_-zqTYwgLEeSFYfyUKDXKaw"
    name="MessageReference"
    definition="Identifies the message."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="MsgRef"
    complexType="_Q7pG5Np-Ed-ak6NoX_4Aeg_-967008570" />
  <messageBuildingBlock
    xmi:id="_4S4olR8OEeWpZde3LQh6dg"
    nextVersions="_gblKVYZMEeemXK0UETsSiA"
    previousVersion="_-zqTZQgLEeSFYfyUKDXKaw"
    name="PoolReference"
    definition="Collective reference identifying a set of messages."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="0"
    xmlTag="PoolRef"
    complexType="_JBe719edEeSA_uUacqhl1Q" />
  <messageBuildingBlock
    xmi:id="_4S4olx8OEeWpZde3LQh6dg"
    nextVersions="_gblKV4ZMEeemXK0UETsSiA"
    previousVersion="_-zqTZwgLEeSFYfyUKDXKaw"
    name="PreviousReference"
    definition="Reference to a linked message that was previously sent."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="0"
    xmlTag="PrvsRef"
    complexType="_JBe719edEeSA_uUacqhl1Q" />
  <messageBuildingBlock
    xmi:id="_4S4omR8OEeWpZde3LQh6dg"
    nextVersions="_gblKWYZMEeemXK0UETsSiA"
    previousVersion="_-zqTaQgLEeSFYfyUKDXKaw"
    name="RelatedReference"
    definition="Reference to a linked message that was previously received."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="0"
    xmlTag="RltdRef"
    complexType="_JBe719edEeSA_uUacqhl1Q" />
  <messageBuildingBlock
    xmi:id="_4S4omx8OEeWpZde3LQh6dg"
    previousVersion="_-zqTawgLEeSFYfyUKDXKaw"
    name="Cancellation"
    definition="Choice between cancellation by transfer details or reference."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="Cxl"
    complexType="_8SMzVSPvEeWQjryFgN2ITg" />
  <messageBuildingBlock
    xmi:id="_4S4onR8OEeWpZde3LQh6dg"
    nextVersions="_gblKXYZMEeemXK0UETsSiA"
    previousVersion="_-zqTbQgLEeSFYfyUKDXKaw"
    name="MarketPracticeVersion"
    definition="Identifies the market practice to which the message conforms."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="0"
    xmlTag="MktPrctcVrsn"
    complexType="_FaNY0RUVEeOIaq8KyCdIDQ" />
  <messageDefinitionIdentifier
    businessArea="sese"
    messageFunctionality="014"
    flavour="001"
    version="07" />
</messageDefinition>

ISO Building Blocks

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