Beruflich Dokumente
Kultur Dokumente
Version Date
Number Author Version Date Description of Changes Distributed
References
The following references have been referred to or used as input while preparing this document:
Reference Description Location
Name
https://ishare.nielsen.com/teams/Port_Man2/ANSI/Pr
Project Plan Provides a baseline on
oject%20Management%20Documents/Nielsen%20Audi
the project
o%20[MCH-
Foundations]%20Convergence%20Plan.mpp
https://ishare.nielsen.com/teams/Port_Man2/ANSI/BP
Data Source Provides the input
Q%20Documentation/Forms/AllItems.aspx
details
Link to the data model \\nmrflpntldtg1\Projects\MediaContentHub\Audio.pd
Data Model
location m
Table of Contents
MCH will extract Design Weights Input data from UDP database and load the same into the MCH data
structure. In the Diary world, markets are closed out for each phase in a given quarterly survey before
the data can be reported. Markets are usually closed out in groups. As the markets are closed out,
county level Design Weight Input data is sourced from SMS and loaded into the UDP tables.
Following are the source UDP tables used for the Design Weight Input data. The Reference data related
for Group and Frame Components is loaded into MCH as one time only (OTO). Only Design Weight
Factors data is extracted by Foundations on a regular basis and will be loaded into the MCH.
Foundations will place the Design Weight Inputs data files into the MCH incoming directory. The MCH
directory is as follows for each environment:
Page 6 of 12
DWIS Inputs-MCH Technical Requirements Document
Each data extract file will have following format and data elements:
Example Record:
RPT_PERIOD_YEAR|LEGACY_QTR_CODE|ARBSU_ID|FRAME_CMPNT_ID| FRAME_COMPONENT_DESC
|GROUP_CMPNT_ID| GROUP_COMPONENT_DESC |DW_FACTOR
MCH extract process will be triggered by the Webservice call. The Design Weight Input data file,
at the county level, is available after each phase closeout of Diary markets for a given survey.
The load process will populate data to the MCH target table. Following load strategies will be
applied to different Design Weights data:
Page 7 of 12
DWIS Inputs-MCH Technical Requirements Document
1.1.2.1.1 WGHTNG_DSGN_GRP
The Design Weight Group reference data is loaded into the WGHTNG_DSGN_GRP table
as OTO. This data is not expected to change frequently.
During Design Weight Factors load, consider the distinct Group Component ID and
Group Description combination and check against the target MCH table. If a given
Group combination exists do nothing otherwise insert the new data into the target
table.
1.1.2.1.2 WGHTNG_DSGN_FRM
The Design Weight Frame reference data is loaded into the WGHTNG_DSGN_FRM table
as the extract is available. This data is not expected to change frequently.
During Design Weight Factors load, consider the distinct Frame Component ID and
Frame Description combination and check against the target MCH table. If a given
Frame combination exists do nothing otherwise insert the new data into the target
table.
1.1.2.1.3 WGHTNG_DSGN_FCTR
The Design Weight Factors data is loaded into the WGHTNG_DSGN_FCTR table as the
data extract is available for each closed out counties.
All newly inserted data will have:
o Same Insert and Update Date and timestamp for each record.
o The Load ID for inserted for each record.
o All records are flagged as Y.
For a given Reporting Year/Legacy Quarter Code/Sample Go ID context, if the Design
Weight Factors data within the extract already exists within the MCH then:
o The data is logically deleted by flagging each record as inactive N.
o Update timestamp value is updated
o The Load ID for reprocessing is inserted.
o Incoming new data will be inserted.
There will be no delete processing for Design Weight Group component reference data
within MCH.
There will be no delete processing for Design Weight Frame component reference data
within MCH.
During load process for Design Weight Factors data, if data already exists within the
MCH for a given Report Period Year/ Legacy QTR Code/ ARBSU ID context then the load
process would perform a logical delete of this data first and then insert the incoming
data.
Page 8 of 12
DWIS Inputs-MCH Technical Requirements Document
The target tables shall be populated successfully on load completion. The following actions shall be
performed on successful load:
Insert Job completion status into the audit table.
Archive the source data files to a specific directory as listed below:
o Dev: dayrheorad002: /odi/mchnas/dev/aud/<two digit country>/Archive/DWIS
o QA : dayrheorad003: /odi/mchnas/qa/aud/<two digit country>/Archive/DWIS
o UAT: dayrheorad003: /odi/mchnas/qa/aud/<two digit country>/Archive/DWIS
o Prod: : dayrhemchp008: /odi/mchnas/prod/aud/<two digit country>/Archive/DWIS
<two digit country>
us for USA
jp for Japan
If data loads fail or error out, system shall perform the following actions:
Rollback to the previous state and no partial data commits allowed
Insert failure status into the audit table
Move the Source Extract files to Error Directory for analysis
Send an email notification to support group.
The Error tables shall get updated and not the Final tables on load failures.
None.
Page 9 of 12
DWIS Inputs-MCH Technical Requirements Document
DWIS_MCH.vsd
The detailed technical requirements are provided in the Technical Requirements Spreadsheet (TRS)
below.
Arb_Nielsen
Convergence DWIS_Input_Loads - Mapping.xls
Page 10 of 12
DWIS Inputs-MCH Technical Requirements Document
2. Appendix
A. Definitions, Acronyms, and Abbreviations
The following acronyms and abbreviations have been used in this document: The general definitions
are provided in the SRP.
Definition/Acronym/ Description
Abbreviation
B. Assumptions
The assumptions are as follows:
Foundations will extract Frame and Group reference data based on LETS value.
Foundations will extract Frame component Factors data based on Close out parameter
value.
Foundations will provide MCH data values wherever possible.
C. Notes
None
Page 11 of 12
DWIS Inputs-MCH Technical Requirements Document
Page 12 of 12