StatusExtensionRequestV03

tsmt.035.001.03

Scope The StatusExtensionRequest message is sent by either party involved in a transaction to the matching application. This message is used to request the extension of the status of a transaction. Usage The StatusExtensionRequest message can be sent by either party involved in a transaction to the matching application to request the extension of the status of a transaction. The matching application will pass on the request by sending a StatusExtensionRequestNotification message to the counterparty which can accept or reject the status extension request by sending a StatusExtensionAcceptance or StatusExtensionRejection 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
%% StatusExtensionRequestV03 recursion level 0 with max 0
StatusExtensionRequestV03 *-- "1..1" MessageIdentification1 : RequestIdentification
StatusExtensionRequestV03 *-- "1..1" SimpleIdentificationInformation : TransactionIdentification
StatusExtensionRequestV03 *-- "0..1" SimpleIdentificationInformation : SubmitterTransactionReference
StatusExtensionRequestV03 *-- "1..1" TransactionStatus5 : StatusToBeExtended
  

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

RequestIdentification building block

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

StatusToBeExtended building block

Identifies the status of the transaction by means of a code. Identifies the future status of the transaction by means of a code and a period. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% TransactionStatus5 recursion level 0 with max 1
class TransactionStatus5{
    Status BaselineStatus3Code
    ChangeDateTime IsoISODateTime
    Description IsoMax140Text
}
  

TransactionStatus5 members

Extensibility and generalization considerations

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

classDiagram
    class IOuterRecord
    StatusExtensionRequestV03 --|> IOuterRecord : Implements
    StatusExtensionRequestV03Document --|> IOuterDocument~StatusExtensionRequestV03~ : Implements
    class IOuterDocument~StatusExtensionRequestV03~ {
        StatusExtensionRequestV03 Message
     }
  

Document wrapper for serialization

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

classDiagram
    StatusExtensionRequestV03Document *-- StatusExtensionRequestV03 : 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.035.001.03">
    <StsXtnsnReq>
        <ReqId>
            <!-- RequestIdentification inner content -->
        </ReqId>
        <TxId>
            <!-- TransactionIdentification inner content -->
        </TxId>
        <SubmitrTxRef>
            <!-- SubmitterTransactionReference inner content -->
        </SubmitrTxRef>
        <StsToBeXtnded>
            <!-- StatusToBeExtended inner content -->
        </StsToBeXtnded>
    </StsXtnsnReq>
</Document>

Data from ISO specification

This is the technical data from the specification document.

<messageDefinition
  xmi:id="_0MRo6NE8Ed-BzquC8wXy7w_2103710287"
  name="StatusExtensionRequestV03"
  definition="Scope&#xD;&#xA;The StatusExtensionRequest message is sent by either party involved in a transaction to the matching application.&#xD;&#xA;This message is used to request the extension of the status of a transaction.&#xD;&#xA;Usage&#xD;&#xA;The StatusExtensionRequest message can be sent by either party involved in a transaction to the matching application to request the extension of the status of a transaction.&#xD;&#xA;The matching application will pass on the request by sending a StatusExtensionRequestNotification message to the counterparty which can accept or reject the status extension request by sending a StatusExtensionAcceptance or StatusExtensionRejection message."
  registrationStatus="Registered"
  messageSet="_wRx2yk2rEeG_I4xRYCA_7g _1a374FXOEeOkkLyrDUP66g"
  xmlTag="StsXtnsnReq"
  rootElement="Document"
  xmlns:xmi="http://www.omg.org/XMI">
  <messageBuildingBlock
    xmi:id="_0MRo6dE8Ed-BzquC8wXy7w_2103710297"
    name="RequestIdentification"
    definition="Identifies the request message."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="ReqId"
    complexType="_Q7pG5Np-Ed-ak6NoX_4Aeg_-967008570" />
  <messageBuildingBlock
    xmi:id="_0MRo6tE8Ed-BzquC8wXy7w_2103710318"
    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="_0MRo69E8Ed-BzquC8wXy7w_2103710380"
    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="_0MRo7NE8Ed-BzquC8wXy7w_2103710350"
    name="StatusToBeExtended"
    definition="Identifies the status of the transaction by means of a code."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="StsToBeXtnded"
    complexType="_RbFb9Np-Ed-ak6NoX_4Aeg_-2036389843" />
  <messageDefinitionIdentifier
    businessArea="tsmt"
    messageFunctionality="035"
    flavour="001"
    version="03" />
</messageDefinition>

ISO Building Blocks

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