UndertakingAmendmentResponseV01

tsrv.008.001.01

The UndertakingAmendmentResponse message is sent by the beneficiary to the party that issued the undertaking, either directly or via one or more advising parties, to indicate acceptance or rejection by the beneficiary of the amendment.

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
%% UndertakingAmendmentResponseV01 recursion level 0 with max 0
UndertakingAmendmentResponseV01 *-- "1..1" Amendment7 : UndertakingAmendmentResponseDetails
UndertakingAmendmentResponseV01 *-- "0..1" PartyAndSignature2 : DigitalSignature
  

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

UndertakingAmendmentResponseDetails building block

Details related to the proposed amendment response. Details of the amendment. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% Amendment7 recursion level 0 with max 1
class Amendment7{
    AmendmentStatus UndertakingStatus2Code
}
Amendment7 *-- "1..1" Amendment8 : AmendmentIdentification
%% Amendment8 recursion level 1 with max 1
class Amendment8{
    Identification IsoMax35Text
    SequenceNumber IsoMax4AlphaNumericText
    BeneficiaryReferenceNumber IsoMax35Text
}
Amendment8 *-- "1..1" PartyIdentification43 : Issuer
  

Amendment7 members

DigitalSignature building block

Digital signature of the response. Entity involved in an activity. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% PartyAndSignature2 recursion level 0 with max 1
PartyAndSignature2 *-- "1..1" PartyIdentification43 : Party
PartyAndSignature2 *-- "1..1" ProprietaryData3 : Signature
%% PartyIdentification43 recursion level 1 with max 1
class PartyIdentification43{
    Name IsoMax140Text
    CountryOfResidence CountryCode
}
PartyIdentification43 *-- "0..1" PostalAddress6 : PostalAddress
PartyIdentification43 *-- "0..1" IParty11Choice : Identification
PartyIdentification43 *-- "0..1" ContactDetails2 : ContactDetails
%% ProprietaryData3 recursion level 1 with max 1
ProprietaryData3 *-- "1..1" SkipProcessing : Any
  

PartyAndSignature2 members

Extensibility and generalization considerations

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

classDiagram
    class IOuterRecord
    UndertakingAmendmentResponseV01 --|> IOuterRecord : Implements
    UndertakingAmendmentResponseV01Document --|> IOuterDocument~UndertakingAmendmentResponseV01~ : Implements
    class IOuterDocument~UndertakingAmendmentResponseV01~ {
        UndertakingAmendmentResponseV01 Message
     }
  

Document wrapper for serialization

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

classDiagram
    UndertakingAmendmentResponseV01Document *-- UndertakingAmendmentResponseV01 : 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:tsrv.008.001.01">
    <UdrtkgAmdmntRspn>
        <UdrtkgAmdmntRspnDtls>
            <!-- UndertakingAmendmentResponseDetails inner content -->
        </UdrtkgAmdmntRspnDtls>
        <DgtlSgntr>
            <!-- DigitalSignature inner content -->
        </DgtlSgntr>
    </UdrtkgAmdmntRspn>
</Document>

Data from ISO specification

This is the technical data from the specification document.

<messageDefinition
  xmi:id="_9iGeInltEeG7BsjMvd1mEw_-1174691593"
  name="UndertakingAmendmentResponseV01"
  definition="The UndertakingAmendmentResponse message is sent by the beneficiary to the party that issued the undertaking, either directly or via one or more advising parties, to indicate acceptance or rejection by the beneficiary of the amendment."
  registrationStatus="Registered"
  messageSet="_SiMuI9n1EeGEPsbnW6ebrw"
  xmlTag="UdrtkgAmdmntRspn"
  rootElement="Document"
  xmlns:xmi="http://www.omg.org/XMI">
  <messageBuildingBlock
    xmi:id="_9iGeI3ltEeG7BsjMvd1mEw_1688211765"
    name="UndertakingAmendmentResponseDetails"
    definition="Details related to the proposed amendment response."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="UdrtkgAmdmntRspnDtls"
    complexType="_9_dIgXltEeG7BsjMvd1mEw_2073465972" />
  <messageBuildingBlock
    xmi:id="_9iGeJHltEeG7BsjMvd1mEw_-106555432"
    name="DigitalSignature"
    definition="Digital signature of the response."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="0"
    xmlTag="DgtlSgntr"
    complexType="_k4nFNZKuEeGnRMFvqYmPBQ" />
  <messageDefinitionIdentifier
    businessArea="tsrv"
    messageFunctionality="008"
    flavour="001"
    version="01" />
</messageDefinition>

ISO Building Blocks

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