Workshop on ESA2010 transmission programme June 10-11, 2013 - Luxembourg

1. SDMX Implementation for National AccountsECB MUFA and GFS GuidelinesData flows and DataSet Identifiers Workshop on ESA2010 transmission programme June 10-11, 2013 - Luxembourg Zlatina Balabanova Lisbeth Yancis zlatina.balabanova@ecb.intlisbeth.yancis@ecb.int

2. Common DSDs

3. Example-ECB MUFA Guideline • Currently there are 13 dimensions • Using the new DSD the dimensions will be 18

4. Example-ECB GFS Guideline • Currently there are 8 dimensions • Using the new DSD the dimensions will be 18

5. SNA data exchange in ESCB context • Use of EXDI (ESCB data exchange infrastructure) • SDMX reporting format supported: • SDMX-EDI (Gesmes/TS) • SDMX-ML compact format version 2.0 • SDMX-ML structure specific version 2.1 • Starting date for the transition period: from September 2013 onwards • MUFA test transmission – November 2013 • Use of the test environment for the new SNA DSDs for the test transmissions and the production for the current SNA flows

6. Data flows • A data flow is characterised by: • a Data Structure Definition (DSD) • constraints = list of expected series keys / combination of valid codes in series key dimensions • providing and receiving institutions • a reporting deadline Data flows are equivalent to the Data Set Identifier in SDMX/EDI terminology

7. Compatibility: SDMX-EDI/SDMX-ML • SDMX-EDI and SDMX-ML data files must be easily convertible into each other • The data model underlying the pure data part of data files is the same for SDMX-EDI and SDMX-ML • Easy conversion between the two formats requires the same information model also to apply to the information contained in the header of the file • The mandatory pieces of information for SDMX-EDI and their counterparts in SDMX-ML, 2.1 in the example below, are highlighted in bold red

8. SDMX-EDI (Interchange level) UNB+UNOC:3+4F0+V12+120726:1510+IREF121557++GESMES/TS' ( sender, recipient, preparation time, IREF, message type and test string if relevant) (Message level) UNH+MREF000001+GESMES:2:1:E6' (MREF) BGM+74' (data message, a data structure message uses 73) NAD+Z02+ECB' (maintenance agency of key family) NAD+MR+V12' (recipient) NAD+MS+4F0' (sender) IDE+10+ECB_EXR1 EU EERs update (EXR)' DSI+ECB_EXR1' (Data Set Identifier) STS+3+7' (Update message, a Delete message uses value 6) DTM+Z02:1961010120111011:711(optional: (reporting begin and end period) IDE+5+ECB_EXR1' (key family) SDMX-ML 2.1 (Interchange level) <message:Header> <message:ID>IREF121557</message:ID>   <message:Test>false</message:Test>   <common:Name>ECB_EXR1 EU EERs update (EXR)</common:Name>   <message:Prepared>2013-02-21T10:37:00+01:00</message:Prepared>   <message:Sender id="4F0" />   <message:Receiver id="V12" /> <message:StructuredimensionAtObservation="TIME_PERIOD" structureID="ECB_BSI1" (key family) namespace="urn:sdmx:org.sdmx.infomodel.datastructure.DataStructure=ECB:ECB_BSI1(1.0):ObsLevelDim:TIME_PERIOD"> <common:Structure>   <Ref agencyID="ECB" id="ECB_EXR1" /> (key family)   </common:Structure>   </message:Structure>   <message:DataSetID>ECB_EXR1</message:DataSetID> (dsi)   <message:Extracted>2012-07-26T15:10:00+01:00</message:Extracted>   </message:Header> (Message level) <message:DataSetdata:action="Replace" data:structureRef="ECB_EXR1" (key family)data:dataScope="DataStructure" xsi:type="dsd:DataSetType">

9. SNA data flows • At this stage, some technical details still need to be further clarified and agreed between IOs in terms of: • Data flow definitions • from reporting institutions to IOs • between IOs • Data file content • Updates and Revisions data files (U&R) versus full refreshment • Transmission of attributes • Data transmissions to ECB using the new SDMX-NA DSD will take place from September 2014 onwards