tsmt.007.001.02
Scope The AmendmentRejection message is sent by the party requested to accept or reject an amendment to the matching application. This message is used to reject an amendment request. Usage The AmendmentRejection message can be sent by the party requested to accept or reject an amendment to inform that it rejects the requested amendment. The message can be sent in response to a FullPushThroughReport and DeltaReport message conveying the details of a BaselineAmendmentRequest message. The acceptance of an amendment request can be achieved by sending an AmendmentAcceptance 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 %% AmendmentRejectionV02 recursion level 0 with max 0 AmendmentRejectionV02 *-- "1..1" MessageIdentification1 : RejectionIdentification AmendmentRejectionV02 *-- "1..1" SimpleIdentificationInformation : TransactionIdentification AmendmentRejectionV02 *-- "0..1" SimpleIdentificationInformation : SubmitterTransactionReference AmendmentRejectionV02 *-- "1..1" MessageIdentification1 : DeltaReportReference AmendmentRejectionV02 *-- "1..1" Count1 : RejectedAmendmentNumber AmendmentRejectionV02 *-- "1..1" IRejectionReason1Choice : 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 |
DeltaReportReference building block
Reference to the identification of the delta report that contained the amendment. 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 |
RejectedAmendmentNumber building block
Sequence number of the rejected baseline amendment. Specifies a sequence number or a total. For comparison, see the ISO20022 official specification
classDiagram direction tb %% Count1 recursion level 0 with max 1 class Count1{ Number IsoNumber }
Count1 members
Member name | Description | Data Type / Multiplicity |
---|---|---|
Number | Sequence or total number. | IsoNumber - Required 1..1 |
RejectionReason building block
Specifies the reaons for rejecting the amendment. Allows the sender of the rejection message to indicate only one rejection reason that applies to the entire rejected message. For comparison, see the ISO20022 official specification
classDiagram direction tb %% IRejectionReason1Choice recursion level 0 with max 1
RejectionReason1Choice members
Member name | Description | Data Type / Multiplicity |
---|
Extensibility and generalization considerations
To facilitate generalized design patterns in the system, the AmendmentRejectionV02 implementation follows a specific implementaiton pattern. First of all, AmendmentRejectionV02 impleemnts IOuterRecord indicating it is the outermost logical part of the message definition. Like all message wrappers, AmendmentRejectionV02Document implements IOuterDocument. Because AmendmentRejectionV02 implements IOuterDocument, it is a suitable template parameter for IOuterDocument, and causes the internal ‘Message’ to be of type AmendmentRejectionV02.
classDiagram class IOuterRecord AmendmentRejectionV02 --|> IOuterRecord : Implements AmendmentRejectionV02Document --|> IOuterDocument~AmendmentRejectionV02~ : Implements class IOuterDocument~AmendmentRejectionV02~ { AmendmentRejectionV02 Message }
Document wrapper for serialization
The only real purpose AmendmentRejectionV02Document serves is to cause the document to be serialized into the ‘urn:iso:std:iso:20022:tech:xsd:tsmt.007.001.02’ namespace. Therefore, it will probably be the usual practice to build the message and construct this wrapper at the last minute using AmendmentRejectionV02.ToDocument() method. The returned AmendmentRejectionV02Document value will serialize correctly according to ISO 20022 standards.
classDiagram AmendmentRejectionV02Document *-- AmendmentRejectionV02 : 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.007.001.02">
<AmdmntRjctn>
<RjctnId>
<!-- RejectionIdentification inner content -->
</RjctnId>
<TxId>
<!-- TransactionIdentification inner content -->
</TxId>
<SubmitrTxRef>
<!-- SubmitterTransactionReference inner content -->
</SubmitrTxRef>
<DltaRptRef>
<!-- DeltaReportReference inner content -->
</DltaRptRef>
<RjctdAmdmntNb>
<!-- RejectedAmendmentNumber inner content -->
</RjctdAmdmntNb>
<RjctnRsn>
<!-- RejectionReason inner content -->
</RjctnRsn>
</AmdmntRjctn>
</Document>
Data from ISO specification
This is the technical data from the specification document.
<messageDefinition
xmi:id="_krHoKNE8Ed-BzquC8wXy7w_-1775142973"
name="AmendmentRejectionV02"
definition="Scope
The AmendmentRejection message is sent by the party requested to accept or reject an amendment to the matching application.
This message is used to reject an amendment request.
Usage
The AmendmentRejection message can be sent by the party requested to accept or reject an amendment to inform that it rejects the requested amendment.
The message can be sent in response to a FullPushThroughReport and DeltaReport message conveying the details of a BaselineAmendmentRequest message.
The acceptance of an amendment request can be achieved by sending an AmendmentAcceptance message."
registrationStatus="Registered"
messageSet="_wRx2yk2rEeG_I4xRYCA_7g _1a374FXOEeOkkLyrDUP66g"
xmlTag="AmdmntRjctn"
rootElement="Document"
xmlns:xmi="http://www.omg.org/XMI">
<messageBuildingBlock
xmi:id="_krHoKdE8Ed-BzquC8wXy7w_-1775142819"
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="_krHoKtE8Ed-BzquC8wXy7w_-1775142850"
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="_krHoK9E8Ed-BzquC8wXy7w_-1775142970"
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="_krHoLNE8Ed-BzquC8wXy7w_-1775142881"
name="DeltaReportReference"
definition="Reference to the identification of the delta report that contained the amendment."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="1"
xmlTag="DltaRptRef"
complexType="_Q7pG5Np-Ed-ak6NoX_4Aeg_-967008570" />
<messageBuildingBlock
xmi:id="_krHoLdE8Ed-BzquC8wXy7w_-1775142942"
name="RejectedAmendmentNumber"
definition="Sequence number of the rejected baseline amendment."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="1"
xmlTag="RjctdAmdmntNb"
complexType="_RJDQxNp-Ed-ak6NoX_4Aeg_1838853440" />
<messageBuildingBlock
xmi:id="_krQyENE8Ed-BzquC8wXy7w_-1775142911"
name="RejectionReason"
definition="Specifies the reaons for rejecting the amendment."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="1"
xmlTag="RjctnRsn"
complexType="_RJ8ooNp-Ed-ak6NoX_4Aeg_891683676" />
<messageDefinitionIdentifier
businessArea="tsmt"
messageFunctionality="007"
flavour="001"
version="02" />
</messageDefinition>
ISO Building Blocks
The following items are used as building blocks to construct this message.