AmendmentAcceptanceV02

tsmt.005.001.02

Scope The AmendmentAcceptance message is sent by the party requested to accept or reject an amendment to the matching application. The message is used to accept an amendment request. Usage The AmendmentAcceptance message can be sent by the party requested to accept or reject an amendment to inform that it accepts the requested amendment. The message can be sent in response to a FullPushThroughReport and DeltaReport message conveying the details of a BaselineAmendmentRequest message. The rejection of an amendment request can be achieved by sending an AmendmentRejection 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
%% AmendmentAcceptanceV02 recursion level 0 with max 0
AmendmentAcceptanceV02 *-- "1..1" MessageIdentification1 : AcceptanceIdentification
AmendmentAcceptanceV02 *-- "1..1" SimpleIdentificationInformation : TransactionIdentification
AmendmentAcceptanceV02 *-- "0..1" SimpleIdentificationInformation : SubmitterTransactionReference
AmendmentAcceptanceV02 *-- "1..1" MessageIdentification1 : DeltaReportReference
AmendmentAcceptanceV02 *-- "1..1" Count1 : AcceptedAmendmentNumber
  

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

AcceptanceIdentification building block

Identifies the acceptance 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 identification of 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

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

AcceptedAmendmentNumber building block

Sequence number of the accepted 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

Extensibility and generalization considerations

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

classDiagram
    class IOuterRecord
    AmendmentAcceptanceV02 --|> IOuterRecord : Implements
    AmendmentAcceptanceV02Document --|> IOuterDocument~AmendmentAcceptanceV02~ : Implements
    class IOuterDocument~AmendmentAcceptanceV02~ {
        AmendmentAcceptanceV02 Message
     }
  

Document wrapper for serialization

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

classDiagram
    AmendmentAcceptanceV02Document *-- AmendmentAcceptanceV02 : 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.005.001.02">
    <AmdmntAccptnc>
        <AccptncId>
            <!-- AcceptanceIdentification inner content -->
        </AccptncId>
        <TxId>
            <!-- TransactionIdentification inner content -->
        </TxId>
        <SubmitrTxRef>
            <!-- SubmitterTransactionReference inner content -->
        </SubmitrTxRef>
        <DltaRptRef>
            <!-- DeltaReportReference inner content -->
        </DltaRptRef>
        <AccptdAmdmntNb>
            <!-- AcceptedAmendmentNumber inner content -->
        </AccptdAmdmntNb>
    </AmdmntAccptnc>
</Document>

Data from ISO specification

This is the technical data from the specification document.

<messageDefinition
  xmi:id="_j0IVwtE8Ed-BzquC8wXy7w_1561210255"
  name="AmendmentAcceptanceV02"
  definition="Scope&#xD;&#xA;The AmendmentAcceptance message is sent by the party requested to accept or reject an amendment to the matching application.&#xD;&#xA;The message is used to accept an amendment request.&#xD;&#xA;Usage&#xD;&#xA;The AmendmentAcceptance message can be sent by the party requested to accept or reject an amendment to inform that it accepts the requested amendment.&#xD;&#xA;The message can be sent in response to a FullPushThroughReport and DeltaReport message conveying the details of a BaselineAmendmentRequest message.&#xD;&#xA;The rejection of an amendment request can be achieved by sending an AmendmentRejection message."
  registrationStatus="Registered"
  messageSet="_wRx2yk2rEeG_I4xRYCA_7g _1a374FXOEeOkkLyrDUP66g"
  xmlTag="AmdmntAccptnc"
  rootElement="Document"
  xmlns:xmi="http://www.omg.org/XMI">
  <messageBuildingBlock
    xmi:id="_j0IVw9E8Ed-BzquC8wXy7w_1561211944"
    name="AcceptanceIdentification"
    definition="Identifies the acceptance message."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="AccptncId"
    complexType="_Q7pG5Np-Ed-ak6NoX_4Aeg_-967008570" />
  <messageBuildingBlock
    xmi:id="_j0IVxNE8Ed-BzquC8wXy7w_1561211914"
    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="_j0IVxdE8Ed-BzquC8wXy7w_1561212005"
    name="SubmitterTransactionReference"
    definition="Reference to the identification of 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="_j0IVxtE8Ed-BzquC8wXy7w_1561211883"
    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="_j0IVx9E8Ed-BzquC8wXy7w_1561211975"
    name="AcceptedAmendmentNumber"
    definition="Sequence number of the accepted baseline amendment."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="AccptdAmdmntNb"
    complexType="_RJDQxNp-Ed-ak6NoX_4Aeg_1838853440" />
  <messageDefinitionIdentifier
    businessArea="tsmt"
    messageFunctionality="005"
    flavour="001"
    version="02" />
</messageDefinition>

ISO Building Blocks

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