RoleAndBaselineRejectionV01

tsmt.050.001.01

Scope The RoleAndBaselineRejection message is sent by a secondary bank to the matching application if it rejects to join the transaction based on the baseline and the role that it is expected to play. Usage The RoleAndBaselineRejection message is sent in response to a message that is a direct request to join a transaction.

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
%% RoleAndBaselineRejectionV01 recursion level 0 with max 0
RoleAndBaselineRejectionV01 *-- "1..1" MessageIdentification1 : RejectionIdentification
RoleAndBaselineRejectionV01 *-- "1..1" MessageIdentification1 : RelatedMessageReference
RoleAndBaselineRejectionV01 *-- "1..1" SimpleIdentificationInformation : TransactionIdentification
RoleAndBaselineRejectionV01 *-- "0..1" Reason2 : RejectionReason
  

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

RejectionIdentification building block

Identifies the rejection 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

RelatedMessageReference building block

Reference to the message that contained the baseline and is rejected. 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

TransactionIdentification building block

Unique identification assigned by the matching application to the transaction. This identification is to be used in any communication between the parties. . Information related to an identification, eg, party identification or account identification. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% SimpleIdentificationInformation recursion level 0 with max 1
class SimpleIdentificationInformation{
    Identification IsoMax35Text
}
  

SimpleIdentificationInformation members

RejectionReason building block

Reason why the user cannot accept the request. Specifies the reason for an action. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% Reason2 recursion level 0 with max 1
class Reason2{
    Description IsoMax140Text
}
  

Reason2 members

Extensibility and generalization considerations

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

classDiagram
    class IOuterRecord
    RoleAndBaselineRejectionV01 --|> IOuterRecord : Implements
    RoleAndBaselineRejectionV01Document --|> IOuterDocument~RoleAndBaselineRejectionV01~ : Implements
    class IOuterDocument~RoleAndBaselineRejectionV01~ {
        RoleAndBaselineRejectionV01 Message
     }
  

Document wrapper for serialization

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

classDiagram
    RoleAndBaselineRejectionV01Document *-- RoleAndBaselineRejectionV01 : 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:tsmt.050.001.01">
    <RoleAndBaselnRjctn>
        <RjctnId>
            <!-- RejectionIdentification inner content -->
        </RjctnId>
        <RltdMsgRef>
            <!-- RelatedMessageReference inner content -->
        </RltdMsgRef>
        <TxId>
            <!-- TransactionIdentification inner content -->
        </TxId>
        <RjctnRsn>
            <!-- RejectionReason inner content -->
        </RjctnRsn>
    </RoleAndBaselnRjctn>
</Document>

Data from ISO specification

This is the technical data from the specification document.

<messageDefinition
  xmi:id="_uJ5PuNE8Ed-BzquC8wXy7w_1408620878"
  name="RoleAndBaselineRejectionV01"
  definition="Scope&#xD;&#xA;The RoleAndBaselineRejection message is sent by a secondary bank to the matching application if it rejects to join the transaction based on the baseline and the role that it is expected to play.&#xD;&#xA;Usage&#xD;&#xA;The RoleAndBaselineRejection message is sent in response to a message that is a direct request to join a transaction."
  registrationStatus="Registered"
  messageSet="_wRx2yk2rEeG_I4xRYCA_7g _1a374FXOEeOkkLyrDUP66g"
  xmlTag="RoleAndBaselnRjctn"
  rootElement="Document"
  xmlns:xmi="http://www.omg.org/XMI">
  <messageBuildingBlock
    xmi:id="_uJ5PudE8Ed-BzquC8wXy7w_1408620914"
    name="RejectionIdentification"
    definition="Identifies the rejection message."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="RjctnId"
    complexType="_Q7pG5Np-Ed-ak6NoX_4Aeg_-967008570" />
  <messageBuildingBlock
    xmi:id="_uJ5PutE8Ed-BzquC8wXy7w_-1800452718"
    name="RelatedMessageReference"
    definition="Reference to the message that contained the baseline and is rejected."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="RltdMsgRef"
    complexType="_Q7pG5Np-Ed-ak6NoX_4Aeg_-967008570" />
  <messageBuildingBlock
    xmi:id="_uKCZoNE8Ed-BzquC8wXy7w_1408620999"
    name="TransactionIdentification"
    definition="Unique identification assigned by the matching application to the transaction.&#xA;This identification is to be used in any communication between the parties.&#xA;."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="TxId"
    complexType="_P-ile9p-Ed-ak6NoX_4Aeg_745508310" />
  <messageBuildingBlock
    xmi:id="_uKCZodE8Ed-BzquC8wXy7w_1408621387"
    name="RejectionReason"
    definition="Reason why the user cannot accept the request."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="0"
    xmlTag="RjctnRsn"
    complexType="_RJ8oo9p-Ed-ak6NoX_4Aeg_949144780" />
  <messageDefinitionIdentifier
    businessArea="tsmt"
    messageFunctionality="050"
    flavour="001"
    version="01" />
</messageDefinition>

ISO Building Blocks

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