camt.104.001.01
Scope The ModifyMember message is sent by a member to the transaction administrator. It is used to create the profile of a member that the transaction administrator maintains. Usage Based on the criteria defined in the CreateLimit message, the transaction administrator will execute or reject the requested creation and respond with a Receipt message as a reply to the request.
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
%% CreateMemberV01 recursion level 0 with max 0
CreateMemberV01 *-- "1..1" MessageHeader1 : MessageHeader
CreateMemberV01 *-- "1..1" IMemberIdentification3Choice : MemberIdentification
CreateMemberV01 *-- "1..1" Member6 : ValueSet
CreateMemberV01 *-- "0..1" SupplementaryData1 : SupplementaryData
Now, we will zero-in one-by-one on each of these building blocks.
MessageHeader building block
Common business identification for the message. Set of characteristics, such as the identification or the creation date and time, specific to the message. For comparison, see the ISO20022 official specification
classDiagram
direction tb
%% MessageHeader1 recursion level 0 with max 1
class MessageHeader1{
MessageIdentification IsoMax35Text
CreationDateTime IsoISODateTime
}
MessageHeader1 members
| Member name | Description | Data Type / Multiplicity |
|---|---|---|
| MessageIdentification | Point to point reference, as assigned by the sender, to unambiguously identify the message. Usage: The sender has to make sure that MessageIdentification is unique for a pre-agreed period. | IsoMax35Text - Required 1..1 |
| CreationDateTime | Date and time at which the message was created. | IsoISODateTime - Optional 0..1 |
MemberIdentification building block
Unique and unambiguous identifier of a system member, as assigned by the system, or the system administrator. Set of elements used to identify a financial institution. For comparison, see the ISO20022 official specification
classDiagram direction tb %% IMemberIdentification3Choice recursion level 0 with max 1
MemberIdentification3Choice members
| Member name | Description | Data Type / Multiplicity |
|---|
ValueSet building block
New member values. Information about the members of a system. For comparison, see the ISO20022 official specification
classDiagram
direction tb
%% Member6 recursion level 0 with max 1
Member6 *-- "0..0" IMemberIdentification3Choice : MemberReturnAddress
Member6 *-- "0..0" ContactIdentificationAndAddress1 : ContactReference
Member6 *-- "0..1" CommunicationAddress8 : CommunicationAddress
%% IMemberIdentification3Choice recursion level 1 with max 1
%% ContactIdentificationAndAddress1 recursion level 1 with max 1
class ContactIdentificationAndAddress1{
Name IsoMax35Text
Role PaymentRole1Code
}
ContactIdentificationAndAddress1 *-- "1..1" CommunicationAddress8 : CommunicationAddress
%% CommunicationAddress8 recursion level 1 with max 1
class CommunicationAddress8{
PhoneNumber IsoPhoneNumber
FaxNumber IsoPhoneNumber
EmailAddress IsoMax256Text
}
CommunicationAddress8 *-- "1..1" ILongPostalAddress1Choice : PostalAddress
Member6 members
| Member name | Description | Data Type / Multiplicity |
|---|---|---|
| MemberReturnAddress | Physical/logical address belonging to a member, segregated from its main address that is used for normal operations. The fund return address is used to route messages that require specific attention/exception handling, for example, returns or rejects. | IMemberIdentification3Choice - Unknown 0..0 |
| ContactReference | Person to be contacted in a given organisation. | ContactIdentificationAndAddress1 - Unknown 0..0 |
| CommunicationAddress | Number, or virtual address, used for communication. | CommunicationAddress8 - Optional 0..1 |
SupplementaryData building block
Additional information that cannot be captured in the structured elements and/or any other specific block. Additional information that can not be captured in the structured fields and/or any other specific block. For comparison, see the ISO20022 official specification
classDiagram
direction tb
%% SupplementaryData1 recursion level 0 with max 1
class SupplementaryData1{
PlaceAndName IsoMax350Text
}
SupplementaryData1 *-- "1..1" IsoSupplementaryDataEnvelope1 : Envelope
%% IsoSupplementaryDataEnvelope1 recursion level 1 with max 1
SupplementaryData1 members
| Member name | Description | Data Type / Multiplicity |
|---|---|---|
| PlaceAndName | Unambiguous reference to the location where the supplementary data must be inserted in the message instance. In the case of XML, this is expressed by a valid XPath. | IsoMax350Text - Optional 0..1 |
| Envelope | Technical element wrapping the supplementary data. | IsoSupplementaryDataEnvelope1 - Required 1..1 |
Extensibility and generalization considerations
To facilitate generalized design patterns in the system, the CreateMemberV01 implementation follows a specific implementaiton pattern. First of all, CreateMemberV01 impleemnts IOuterRecord indicating it is the outermost logical part of the message definition. Like all message wrappers, CreateMemberV01Document implements IOuterDocument. Because CreateMemberV01 implements IOuterDocument, it is a suitable template parameter for IOuterDocument, and causes the internal ‘Message’ to be of type CreateMemberV01.
classDiagram
class IOuterRecord
CreateMemberV01 --|> IOuterRecord : Implements
CreateMemberV01Document --|> IOuterDocument~CreateMemberV01~ : Implements
class IOuterDocument~CreateMemberV01~ {
CreateMemberV01 Message
}
Document wrapper for serialization
The only real purpose CreateMemberV01Document serves is to cause the document to be serialized into the ‘urn:iso:std:iso:20022:tech:xsd:camt.104.001.01’ namespace. Therefore, it will probably be the usual practice to build the message and construct this wrapper at the last minute using CreateMemberV01.ToDocument() method. The returned CreateMemberV01Document value will serialize correctly according to ISO 20022 standards.
classDiagram
CreateMemberV01Document *-- CreateMemberV01 : 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:camt.104.001.01">
<CretMmb>
<MsgHdr>
<!-- MessageHeader inner content -->
</MsgHdr>
<MmbId>
<!-- MemberIdentification inner content -->
</MmbId>
<ValSet>
<!-- ValueSet inner content -->
</ValSet>
<SplmtryData>
<!-- SupplementaryData inner content -->
</SplmtryData>
</CretMmb>
</Document>
Data from ISO specification
This is the technical data from the specification document.
<messageDefinition
xmi:id="_P8togckHEem3UrxZgQhVAw"
name="CreateMemberV01"
definition="Scope
The ModifyMember message is sent by a member to the transaction administrator.
It is used to create the profile of a member that the transaction administrator maintains.
Usage
Based on the criteria defined in the CreateLimit message, the transaction administrator will execute or reject the requested creation and respond with a Receipt message as a reply to the request."
registrationStatus="Registered"
messageSet="_SZTDoxcNEeiyVv5j1vf1VQ"
xmlTag="CretMmb"
rootElement="Document"
xmlns:xmi="http://www.omg.org/XMI">
<messageBuildingBlock
xmi:id="_P8toickHEem3UrxZgQhVAw"
name="MessageHeader"
definition="Common business identification for the message."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="1"
xmlTag="MsgHdr"
complexType="_75DzkaMgEeCJ6YNENx4h-w_-613853819" />
<messageBuildingBlock
xmi:id="_P8toi8kHEem3UrxZgQhVAw"
name="MemberIdentification"
definition="Unique and unambiguous identifier of a system member, as assigned by the system, or the system administrator."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="1"
xmlTag="MmbId"
complexType="_h_8rhXSbEeiH1ZOt2UD8vQ" />
<messageBuildingBlock
xmi:id="_P8tojckHEem3UrxZgQhVAw"
name="ValueSet"
definition="New member values."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="1"
xmlTag="ValSet"
complexType="_W1ihMXSeEeiH1ZOt2UD8vQ" />
<messageBuildingBlock
xmi:id="_P8toj8kHEem3UrxZgQhVAw"
name="SupplementaryData"
definition="Additional information that cannot be captured in the structured elements and/or any other specific block."
registrationStatus="Provisionally Registered"
minOccurs="0"
xmlTag="SplmtryData"
complexType="_Qn0zC9p-Ed-ak6NoX_4Aeg_468227563" />
<messageDefinitionIdentifier
businessArea="camt"
messageFunctionality="104"
flavour="001"
version="01" />
</messageDefinition>
ISO Building Blocks
The following items are used as building blocks to construct this message.