auth.039.001.01
The FinancialInstrumentReportingNonWorkingDayReport message is sent by the reporting entity to the competent authority to report on non-working days.
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 %% FinancialInstrumentReportingNonWorkingDayReportV01 recursion level 0 with max 0 FinancialInstrumentReportingNonWorkingDayReportV01 *-- "1..1" SecuritiesMarketReportHeader1 : ReportHeader FinancialInstrumentReportingNonWorkingDayReportV01 *-- "1..1" SecuritiesNonTradingDayReport1 : NonWorkingDay FinancialInstrumentReportingNonWorkingDayReportV01 *-- "0..1" SupplementaryData1 : SupplementaryData
Now, we will zero-in one-by-one on each of these building blocks.
ReportHeader building block
Header information related to the global report. Provides the securities market transaction report related header details. For comparison, see the ISO20022 official specification
classDiagram direction tb %% SecuritiesMarketReportHeader1 recursion level 0 with max 1 class SecuritiesMarketReportHeader1{ SubmissionDateTime IsoISODateTime } SecuritiesMarketReportHeader1 *-- "1..1" ITradingVenueIdentification1Choice : ReportingEntity SecuritiesMarketReportHeader1 *-- "1..1" IPeriod4Choice : ReportingPeriod %% ITradingVenueIdentification1Choice recursion level 1 with max 1 %% IPeriod4Choice recursion level 1 with max 1
SecuritiesMarketReportHeader1 members
Member name | Description | Data Type / Multiplicity |
---|---|---|
ReportingEntity | Identification of the venue which generates the report. | ITradingVenueIdentification1Choice - Required 1..1 |
ReportingPeriod | Date or date range the report relates to. | IPeriod4Choice - Required 1..1 |
SubmissionDateTime | Date and time of the report originally submitted by the reporting entity when the file is generated for submission to their reporting authority. | IsoISODateTime - Optional 0..1 |
NonWorkingDay building block
Provides details on the days a venue is not open. Details the non-working days of an entity. For comparison, see the ISO20022 official specification
classDiagram direction tb %% SecuritiesNonTradingDayReport1 recursion level 0 with max 1 SecuritiesNonTradingDayReport1 *-- "1..1" ITradingVenueIdentification1Choice : Identification SecuritiesNonTradingDayReport1 *-- "1..0" SecuritiesNonTradingDay1 : NonWorkingDay %% ITradingVenueIdentification1Choice recursion level 1 with max 1 %% SecuritiesNonTradingDay1 recursion level 1 with max 1 class SecuritiesNonTradingDay1{ TechnicalRecordIdentification IsoMax35Text Date IsoISODate Reason NonTradingDayReason1Code }
SecuritiesNonTradingDayReport1 members
Member name | Description | Data Type / Multiplicity |
---|---|---|
Identification | Identification of the specific venue this relates to - operating MIC, segment MIC, NCA | ITradingVenueIdentification1Choice - Required 1..1 |
NonWorkingDay | Provides the non working days of the identified venue. Details on why it is a non working day are also captured. | SecuritiesNonTradingDay1 - Unknown 1..0 |
SupplementaryData building block
Additional information that can not be captured in the structured fields 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 FinancialInstrumentReportingNonWorkingDayReportV01 implementation follows a specific implementaiton pattern. First of all, FinancialInstrumentReportingNonWorkingDayReportV01 impleemnts IOuterRecord indicating it is the outermost logical part of the message definition. Like all message wrappers, FinancialInstrumentReportingNonWorkingDayReportV01Document implements IOuterDocument. Because FinancialInstrumentReportingNonWorkingDayReportV01 implements IOuterDocument, it is a suitable template parameter for IOuterDocument, and causes the internal ‘Message’ to be of type FinancialInstrumentReportingNonWorkingDayReportV01.
classDiagram class IOuterRecord FinancialInstrumentReportingNonWorkingDayReportV01 --|> IOuterRecord : Implements FinancialInstrumentReportingNonWorkingDayReportV01Document --|> IOuterDocument~FinancialInstrumentReportingNonWorkingDayReportV01~ : Implements class IOuterDocument~FinancialInstrumentReportingNonWorkingDayReportV01~ { FinancialInstrumentReportingNonWorkingDayReportV01 Message }
Document wrapper for serialization
The only real purpose FinancialInstrumentReportingNonWorkingDayReportV01Document serves is to cause the document to be serialized into the ‘urn:iso:std:iso:20022:tech:xsd:auth.039.001.01’ namespace. Therefore, it will probably be the usual practice to build the message and construct this wrapper at the last minute using FinancialInstrumentReportingNonWorkingDayReportV01.ToDocument() method. The returned FinancialInstrumentReportingNonWorkingDayReportV01Document value will serialize correctly according to ISO 20022 standards.
classDiagram FinancialInstrumentReportingNonWorkingDayReportV01Document *-- FinancialInstrumentReportingNonWorkingDayReportV01 : 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:auth.039.001.01">
<FinInstrmRptgNonWorkgDayRpt>
<RptHdr>
<!-- ReportHeader inner content -->
</RptHdr>
<NonWorkgDay>
<!-- NonWorkingDay inner content -->
</NonWorkgDay>
<SplmtryData>
<!-- SupplementaryData inner content -->
</SplmtryData>
</FinInstrmRptgNonWorkgDayRpt>
</Document>
Data from ISO specification
This is the technical data from the specification document.
<messageDefinition
xmi:id="_4LUGIURNEee7JdgA9zPESA"
name="FinancialInstrumentReportingNonWorkingDayReportV01"
definition="The FinancialInstrumentReportingNonWorkingDayReport message is sent by the reporting entity to the competent authority to report on non-working days."
registrationStatus="Registered"
messageSet="_m18yAApTEeeand7dul6qJQ"
xmlTag="FinInstrmRptgNonWorkgDayRpt"
rootElement="Document"
xmlns:xmi="http://www.omg.org/XMI">
<messageBuildingBlock
xmi:id="_4LUGI0RNEee7JdgA9zPESA"
name="ReportHeader"
definition="Header information related to the global report."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="1"
xmlTag="RptHdr"
complexType="_Xt9fc8v5EeSxLrW9hropkQ" />
<messageBuildingBlock
xmi:id="_4LUGJURNEee7JdgA9zPESA"
name="NonWorkingDay"
definition="Provides details on the days a venue is not open."
registrationStatus="Provisionally Registered"
minOccurs="1"
xmlTag="NonWorkgDay"
complexType="_zms14Gw0EeWD9e8QDBgUOw" />
<messageBuildingBlock
xmi:id="_4LUGJ0RNEee7JdgA9zPESA"
name="SupplementaryData"
definition="Additional information that can not be captured in the structured fields and/or any other specific block."
registrationStatus="Provisionally Registered"
minOccurs="0"
xmlTag="SplmtryData"
complexType="_Qn0zC9p-Ed-ak6NoX_4Aeg_468227563" />
<messageDefinitionIdentifier
businessArea="auth"
messageFunctionality="039"
flavour="001"
version="01" />
</messageDefinition>
ISO Building Blocks
The following items are used as building blocks to construct this message.