UndertakingNonExtensionRequestV01

tsrv.010.001.01

The UndertakingNonExtensionRequest message is sent by the party that requested issuance of the undertaking (applicant or obligor) to the party that issued the undertaking. It is used to request no further automatic extensions to the expiry of the referenced undertaking.

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
%% UndertakingNonExtensionRequestV01 recursion level 0 with max 0
UndertakingNonExtensionRequestV01 *-- "1..1" UndertakingNonExtensionRequest1 : UndertakingNonExtensionRequestDetails
UndertakingNonExtensionRequestV01 *-- "0..1" PartyAndSignature2 : DigitalSignature
  

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

UndertakingNonExtensionRequestDetails building block

Details of the non extension request. Details of the non extension request. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% UndertakingNonExtensionRequest1 recursion level 0 with max 1
UndertakingNonExtensionRequest1 *-- "1..1" PartyIdentification43 : RequestingParty
UndertakingNonExtensionRequest1 *-- "1..1" Undertaking9 : UndertakingIdentification
%% 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
%% Undertaking9 recursion level 1 with max 1
class Undertaking9{
    Identification IsoMax35Text
    ApplicantReferenceNumber IsoMax35Text
}
Undertaking9 *-- "1..1" PartyIdentification43 : Issuer
  

UndertakingNonExtensionRequest1 members

DigitalSignature building block

Digital signature of the request. 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 UndertakingNonExtensionRequestV01 implementation follows a specific implementaiton pattern. First of all, UndertakingNonExtensionRequestV01 impleemnts IOuterRecord indicating it is the outermost logical part of the message definition. Like all message wrappers, UndertakingNonExtensionRequestV01Document implements IOuterDocument. Because UndertakingNonExtensionRequestV01 implements IOuterDocument, it is a suitable template parameter for IOuterDocument, and causes the internal ‘Message’ to be of type UndertakingNonExtensionRequestV01.

classDiagram
    class IOuterRecord
    UndertakingNonExtensionRequestV01 --|> IOuterRecord : Implements
    UndertakingNonExtensionRequestV01Document --|> IOuterDocument~UndertakingNonExtensionRequestV01~ : Implements
    class IOuterDocument~UndertakingNonExtensionRequestV01~ {
        UndertakingNonExtensionRequestV01 Message
     }
  

Document wrapper for serialization

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

classDiagram
    UndertakingNonExtensionRequestV01Document *-- UndertakingNonExtensionRequestV01 : 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.010.001.01">
    <UdrtkgNonXtnsnReq>
        <UdrtkgNonXtnsnReqDtls>
            <!-- UndertakingNonExtensionRequestDetails inner content -->
        </UdrtkgNonXtnsnReqDtls>
        <DgtlSgntr>
            <!-- DigitalSignature inner content -->
        </DgtlSgntr>
    </UdrtkgNonXtnsnReq>
</Document>

Data from ISO specification

This is the technical data from the specification document.

<messageDefinition
  xmi:id="_9gmpVXltEeG7BsjMvd1mEw_634999527"
  name="UndertakingNonExtensionRequestV01"
  definition="The UndertakingNonExtensionRequest message is sent by the party that requested issuance of the undertaking (applicant or obligor) to the party that issued the undertaking. It is used to request no further automatic extensions to the expiry of the referenced undertaking."
  registrationStatus="Registered"
  messageSet="_SiMuI9n1EeGEPsbnW6ebrw"
  xmlTag="UdrtkgNonXtnsnReq"
  rootElement="Document"
  xmlns:xmi="http://www.omg.org/XMI">
  <messageBuildingBlock
    xmi:id="_9gmpVnltEeG7BsjMvd1mEw_1337678372"
    name="UndertakingNonExtensionRequestDetails"
    definition="Details of the non extension request."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="UdrtkgNonXtnsnReqDtls"
    complexType="_-D6xxnltEeG7BsjMvd1mEw_-1432358339" />
  <messageBuildingBlock
    xmi:id="_9gmpV3ltEeG7BsjMvd1mEw_-238052912"
    name="DigitalSignature"
    definition="Digital signature of the request."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="0"
    xmlTag="DgtlSgntr"
    complexType="_k4nFNZKuEeGnRMFvqYmPBQ" />
  <messageDefinitionIdentifier
    businessArea="tsrv"
    messageFunctionality="010"
    flavour="001"
    version="01" />
</messageDefinition>

ISO Building Blocks

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