tsmt.033.001.03
Scope The StatusExtensionRequestRejection message is sent by the party requested to accept or reject a request to extend the status of a transaction to the matching application. This message is used to inform about the rejection of a request to extend the status of a transaction. Usage The StatusExtensionRequestRejection message can be sent by the party requested to accept or reject the request to extend the status of a transaction to inform that it rejects the request. The message can be sent in response to a StatusExtensionRequestNotification message. The acceptance of a request to extend the status of a transaction can be achieved by sending a StatusExtensionRequestAcceptance 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 %% StatusExtensionRequestRejectionV03 recursion level 0 with max 0 StatusExtensionRequestRejectionV03 *-- "1..1" MessageIdentification1 : RejectionIdentification StatusExtensionRequestRejectionV03 *-- "1..1" SimpleIdentificationInformation : TransactionIdentification StatusExtensionRequestRejectionV03 *-- "0..1" SimpleIdentificationInformation : SubmitterTransactionReference StatusExtensionRequestRejectionV03 *-- "1..1" TransactionStatus4 : StatusNotToBeExtended StatusExtensionRequestRejectionV03 *-- "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
Member name | Description | Data Type / Multiplicity |
---|---|---|
Identification | Identification of the message. | IsoMax35Text - Required 1..1 |
CreationDateTime | Date of creation of the message. | IsoISODateTime - Required 1..1 |
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
Member name | Description | Data Type / Multiplicity |
---|---|---|
Identification | Name or number assigned by an entity to enable recognition of that entity, eg, account identifier. | IsoMax35Text - Required 1..1 |
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
Member name | Description | Data Type / Multiplicity |
---|---|---|
Identification | Name or number assigned by an entity to enable recognition of that entity, eg, account identifier. | IsoMax35Text - Required 1..1 |
StatusNotToBeExtended building block
Identifies the status that the submitter does not want to be extended. Identifies the status of the transaction by means of a code. For comparison, see the ISO20022 official specification
classDiagram direction tb %% TransactionStatus4 recursion level 0 with max 1 class TransactionStatus4{ Status BaselineStatus3Code }
TransactionStatus4 members
Member name | Description | Data Type / Multiplicity |
---|---|---|
Status | Identifies the status of the transaction by means of a code. | BaselineStatus3Code - Required 1..1 |
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
Member name | Description | Data Type / Multiplicity |
---|---|---|
Description | Detailed description of the rejection. | IsoMax140Text - Required 1..1 |
Extensibility and generalization considerations
To facilitate generalized design patterns in the system, the StatusExtensionRequestRejectionV03 implementation follows a specific implementaiton pattern. First of all, StatusExtensionRequestRejectionV03 impleemnts IOuterRecord indicating it is the outermost logical part of the message definition. Like all message wrappers, StatusExtensionRequestRejectionV03Document implements IOuterDocument. Because StatusExtensionRequestRejectionV03 implements IOuterDocument, it is a suitable template parameter for IOuterDocument, and causes the internal ‘Message’ to be of type StatusExtensionRequestRejectionV03.
classDiagram class IOuterRecord StatusExtensionRequestRejectionV03 --|> IOuterRecord : Implements StatusExtensionRequestRejectionV03Document --|> IOuterDocument~StatusExtensionRequestRejectionV03~ : Implements class IOuterDocument~StatusExtensionRequestRejectionV03~ { StatusExtensionRequestRejectionV03 Message }
Document wrapper for serialization
The only real purpose StatusExtensionRequestRejectionV03Document serves is to cause the document to be serialized into the ‘urn:iso:std:iso:20022:tech:xsd:tsmt.033.001.03’ namespace. Therefore, it will probably be the usual practice to build the message and construct this wrapper at the last minute using StatusExtensionRequestRejectionV03.ToDocument() method. The returned StatusExtensionRequestRejectionV03Document value will serialize correctly according to ISO 20022 standards.
classDiagram StatusExtensionRequestRejectionV03Document *-- StatusExtensionRequestRejectionV03 : 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.033.001.03">
<StsXtnsnReqRjctn>
<RjctnId>
<!-- RejectionIdentification inner content -->
</RjctnId>
<TxId>
<!-- TransactionIdentification inner content -->
</TxId>
<SubmitrTxRef>
<!-- SubmitterTransactionReference inner content -->
</SubmitrTxRef>
<StsNotToBeXtnded>
<!-- StatusNotToBeExtended inner content -->
</StsNotToBeXtnded>
<RjctnRsn>
<!-- RejectionReason inner content -->
</RjctnRsn>
</StsXtnsnReqRjctn>
</Document>
Data from ISO specification
This is the technical data from the specification document.
<messageDefinition
xmi:id="_zwHRWNE8Ed-BzquC8wXy7w_1399062507"
name="StatusExtensionRequestRejectionV03"
definition="Scope
The StatusExtensionRequestRejection message is sent by the party requested to accept or reject a request to extend the status of a transaction to the matching application.
This message is used to inform about the rejection of a request to extend the status of a transaction.
Usage
The StatusExtensionRequestRejection message can be sent by the party requested to accept or reject the request to extend the status of a transaction to inform that it rejects the request.
The message can be sent in response to a StatusExtensionRequestNotification message.
The acceptance of a request to extend the status of a transaction can be achieved by sending a StatusExtensionRequestAcceptance message."
registrationStatus="Registered"
messageSet="_wRx2yk2rEeG_I4xRYCA_7g _1a374FXOEeOkkLyrDUP66g"
xmlTag="StsXtnsnReqRjctn"
rootElement="Document"
xmlns:xmi="http://www.omg.org/XMI">
<messageBuildingBlock
xmi:id="_zwHRWdE8Ed-BzquC8wXy7w_1399062518"
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="_zwHRWtE8Ed-BzquC8wXy7w_1399062539"
name="TransactionIdentification"
definition="Unique identification assigned by the matching application to the transaction.
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="_zwHRW9E8Ed-BzquC8wXy7w_1399062847"
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="_zwHRXNE8Ed-BzquC8wXy7w_1399062786"
name="StatusNotToBeExtended"
definition="Identifies the status that the submitter does not want to be extended."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="1"
xmlTag="StsNotToBeXtnded"
complexType="_RbFb-Np-Ed-ak6NoX_4Aeg_1598523783" />
<messageBuildingBlock
xmi:id="_zwHRXdE8Ed-BzquC8wXy7w_1399062817"
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="033"
flavour="001"
version="03" />
</messageDefinition>
ISO Building Blocks
The following items are used as building blocks to construct this message.