reda.041.001.01
The PartyActivityReport message is sent by the executing party to an instructing party containing information about changes on party reference data.
Scope and usage: It aims at informing about the changes occurred during a business date for party reference data.
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
%% PartyActivityAdviceV01 recursion level 0 with max 0
PartyActivityAdviceV01 *-- "0..1" MessageHeader1 : MessageHeader
PartyActivityAdviceV01 *-- "1..1" PartyStatement2 : PartyActivity
PartyActivityAdviceV01 *-- "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 |
PartyActivity building block
Activity report of changes occurred for a party defined in the system. Provides system date for all of the changes occurred for an entity. For comparison, see the ISO20022 official specification
classDiagram
direction tb
%% PartyStatement2 recursion level 0 with max 1
class PartyStatement2{
SystemDate IsoISODate
}
PartyStatement2 *-- "0..0" PartyReferenceDataChange2 : Change
%% PartyReferenceDataChange2 recursion level 1 with max 1
class PartyReferenceDataChange2{
OperationTimeStamp IsoISODateTime
}
PartyReferenceDataChange2 *-- "1..1" SystemPartyIdentification8 : PartyIdentification
PartyReferenceDataChange2 *-- "1..0" IUpdateLogPartyRecord1Choice : Record
PartyStatement2 members
| Member name | Description | Data Type / Multiplicity |
|---|---|---|
| SystemDate | Date for which the statement is valid. | IsoISODate - Required 1..1 |
| Change | Provides information on the actual change occurred to a party. | PartyReferenceDataChange2 - Unknown 0..0 |
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 PartyActivityAdviceV01 implementation follows a specific implementaiton pattern. First of all, PartyActivityAdviceV01 impleemnts IOuterRecord indicating it is the outermost logical part of the message definition. Like all message wrappers, PartyActivityAdviceV01Document implements IOuterDocument. Because PartyActivityAdviceV01 implements IOuterDocument, it is a suitable template parameter for IOuterDocument, and causes the internal ‘Message’ to be of type PartyActivityAdviceV01.
classDiagram
class IOuterRecord
PartyActivityAdviceV01 --|> IOuterRecord : Implements
PartyActivityAdviceV01Document --|> IOuterDocument~PartyActivityAdviceV01~ : Implements
class IOuterDocument~PartyActivityAdviceV01~ {
PartyActivityAdviceV01 Message
}
Document wrapper for serialization
The only real purpose PartyActivityAdviceV01Document serves is to cause the document to be serialized into the ‘urn:iso:std:iso:20022:tech:xsd:reda.041.001.01’ namespace. Therefore, it will probably be the usual practice to build the message and construct this wrapper at the last minute using PartyActivityAdviceV01.ToDocument() method. The returned PartyActivityAdviceV01Document value will serialize correctly according to ISO 20022 standards.
classDiagram
PartyActivityAdviceV01Document *-- PartyActivityAdviceV01 : 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:reda.041.001.01">
<PtyActvtyAdvc>
<MsgHdr>
<!-- MessageHeader inner content -->
</MsgHdr>
<PtyActvty>
<!-- PartyActivity inner content -->
</PtyActvty>
<SplmtryData>
<!-- SupplementaryData inner content -->
</SplmtryData>
</PtyActvtyAdvc>
</Document>
Data from ISO specification
This is the technical data from the specification document.
<messageDefinition
xmi:id="__JD_8ZeSEeen_cyMrluY4w"
name="PartyActivityAdviceV01"
definition="The PartyActivityReport message is sent by the executing party to an instructing party containing information about changes on party reference data.

Scope and usage:
It aims at informing about the changes occurred during a business date for party reference data."
registrationStatus="Registered"
messageSet="_Fl3iMBHREeqzEaNIFJIN-g"
xmlTag="PtyActvtyAdvc"
rootElement="Document"
xmlns:xmi="http://www.omg.org/XMI">
<messageBuildingBlock
xmi:id="_BZywcVhGEeih3fUfzR38Ig"
name="MessageHeader"
definition="Common business identification for the message."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="0"
xmlTag="MsgHdr"
complexType="_75DzkaMgEeCJ6YNENx4h-w_-613853819" />
<messageBuildingBlock
xmi:id="__JD_-ZeSEeen_cyMrluY4w"
name="PartyActivity"
definition="Activity report of changes occurred for a party defined in the system."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="1"
xmlTag="PtyActvty"
complexType="_7qW5tVhLEeih3fUfzR38Ig" />
<messageBuildingBlock
xmi:id="__JD_-5eSEeen_cyMrluY4w"
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="reda"
messageFunctionality="041"
flavour="001"
version="01" />
</messageDefinition>
ISO Building Blocks
The following items are used as building blocks to construct this message.