StatusChangeRequestRejectionV02

tsmt.029.001.02

Scope The StatusChangeRequestRejection message is sent by the party requested to accept or reject the request of a change in the status of a transaction to the matching application. This message is used to inform about the rejection of a request to change the status of a transaction. Usage The StatusChangeRequestRejection message can be sent by the party requested to accept or reject a request to change the status of a transaction to inform that it rejects the request. The message can be sent in response to a StatusChangeRequestNotification message. The acceptance of a request to change the status of a transaction can be achieved by sending a StatusChangeRequestAcceptance message.

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
%% StatusChangeRequestRejectionV02 recursion level 0 with max 0
StatusChangeRequestRejectionV02 *-- "1..1" MessageIdentification1 : RejectionIdentification
StatusChangeRequestRejectionV02 *-- "1..1" SimpleIdentificationInformation : TransactionIdentification
StatusChangeRequestRejectionV02 *-- "0..1" SimpleIdentificationInformation : SubmitterTransactionReference
StatusChangeRequestRejectionV02 *-- "1..1" TransactionStatus3 : RejectedStatusChange
StatusChangeRequestRejectionV02 *-- "1..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

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

SubmitterTransactionReference building block

Reference to the transaction for the requesting financial institution. 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

RejectedStatusChange building block

Specifies the status rejected. Identifies the status of the transaction by means of a code. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% TransactionStatus3 recursion level 0 with max 1
class TransactionStatus3{
    Status BaselineStatus2Code
}
  

TransactionStatus3 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 StatusChangeRequestRejectionV02 implementation follows a specific implementaiton pattern. First of all, StatusChangeRequestRejectionV02 impleemnts IOuterRecord indicating it is the outermost logical part of the message definition. Like all message wrappers, StatusChangeRequestRejectionV02Document implements IOuterDocument. Because StatusChangeRequestRejectionV02 implements IOuterDocument, it is a suitable template parameter for IOuterDocument, and causes the internal ‘Message’ to be of type StatusChangeRequestRejectionV02.

classDiagram
    class IOuterRecord
    StatusChangeRequestRejectionV02 --|> IOuterRecord : Implements
    StatusChangeRequestRejectionV02Document --|> IOuterDocument~StatusChangeRequestRejectionV02~ : Implements
    class IOuterDocument~StatusChangeRequestRejectionV02~ {
        StatusChangeRequestRejectionV02 Message
     }
  

Document wrapper for serialization

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

classDiagram
    StatusChangeRequestRejectionV02Document *-- StatusChangeRequestRejectionV02 : 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.029.001.02">
    <StsChngReqRjctn>
        <RjctnId>
            <!-- RejectionIdentification inner content -->
        </RjctnId>
        <TxId>
            <!-- TransactionIdentification inner content -->
        </TxId>
        <SubmitrTxRef>
            <!-- SubmitterTransactionReference inner content -->
        </SubmitrTxRef>
        <RjctdStsChng>
            <!-- RejectedStatusChange inner content -->
        </RjctdStsChng>
        <RjctnRsn>
            <!-- RejectionReason inner content -->
        </RjctnRsn>
    </StsChngReqRjctn>
</Document>

Data from ISO specification

This is the technical data from the specification document.

<messageDefinition
  xmi:id="_xILlyNE8Ed-BzquC8wXy7w_-544947479"
  name="StatusChangeRequestRejectionV02"
  definition="Scope&#xD;&#xA;The StatusChangeRequestRejection message is sent by the party requested to accept or reject the request of a change in the status of a transaction to the matching application.&#xD;&#xA;This message is used to inform about the rejection of a request to change the status of a transaction.&#xD;&#xA;Usage&#xD;&#xA;The StatusChangeRequestRejection message can be sent by the party requested to accept or reject a request to change the status of a transaction to inform that it rejects the request.&#xD;&#xA;The message can be sent in response to a StatusChangeRequestNotification message.&#xD;&#xA;The acceptance of a request to change the status of a transaction can be achieved by sending a StatusChangeRequestAcceptance message."
  registrationStatus="Registered"
  messageSet="_wRx2yk2rEeG_I4xRYCA_7g _1a374FXOEeOkkLyrDUP66g"
  xmlTag="StsChngReqRjctn"
  rootElement="Document"
  xmlns:xmi="http://www.omg.org/XMI">
  <messageBuildingBlock
    xmi:id="_xIUvsNE8Ed-BzquC8wXy7w_-544947476"
    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="_xIUvsdE8Ed-BzquC8wXy7w_-544947355"
    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."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="TxId"
    complexType="_P-ile9p-Ed-ak6NoX_4Aeg_745508310" />
  <messageBuildingBlock
    xmi:id="_xIUvstE8Ed-BzquC8wXy7w_-544947447"
    name="SubmitterTransactionReference"
    definition="Reference to the transaction for the requesting financial institution."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="0"
    xmlTag="SubmitrTxRef"
    complexType="_P-ile9p-Ed-ak6NoX_4Aeg_745508310" />
  <messageBuildingBlock
    xmi:id="_xIUvs9E8Ed-BzquC8wXy7w_-544947416"
    name="RejectedStatusChange"
    definition="Specifies the status rejected."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="RjctdStsChng"
    complexType="_RKFyk9p-Ed-ak6NoX_4Aeg_-489445133" />
  <messageBuildingBlock
    xmi:id="_xIUvtNE8Ed-BzquC8wXy7w_-544947386"
    name="RejectionReason"
    definition="Reason why the user cannot accept the request."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="RjctnRsn"
    complexType="_RJ8oo9p-Ed-ak6NoX_4Aeg_949144780" />
  <messageDefinitionIdentifier
    businessArea="tsmt"
    messageFunctionality="029"
    flavour="001"
    version="02" />
</messageDefinition>

ISO Building Blocks

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