Import File Preparation for dspMonitor and dspCompose

Data Governance is paramount to a company's ongoing success in maintaining a high level of data quality in their ERP systems. Within the DSP toolset, there is a passive governance solution, dspMonitor, which reports on the data in an ERP system after it has already been added to the production system. The active governance solution, dspCompose, validates data prior to its load or update into the ERP system. And with the flexibility and power of the DSP toolset, these two applications can work in conjunction with each other providing a complete closed-loop remediation process that ensures the right data is delivered by the right person at the right time in the right format.

Combining dspMonitor data quality monitoring software with dspCompose remediation software has many advantages over traditional approaches. They provide for a low impact method of enforcement for data policies across existing systems, including those in the cloud, and require very little changes to underlying technologies and the processes that use them. They crowdsource the deep data and business expertise of people within the business – not just the IT staff - and automatically activate the right skills when quality issues arise and need to be corrected. All of this takes place while processes continue to execute – data monitoring attempts to locate poor quality data in systems before they impact business processes.

While there is no direct link between the two applications, it is relatively simple to create a request in dspCompose based on data from a dspMonitor report. An external request scenario may be used, but this article will highlight the technique of using an import view. 

1. At the template level, access the vertical view of the Data role and select Import Settings.
2. Click View Import Data Sources.
3. Select the database that will contain the import view. Click Allow.
4. Select the same database as the View Import Data Source ID Default.
5. Retrieve the fields used in the template that is registered in dspCompose. To do this, a manual request must first be created. Once that is done, then access the vertical view of the Data Role within the Request.
6. Click Generate Template File. This will automatically create an excel file containing all fields used in the template recording. These will be the technical field names and will be needed to reference when creating the import file.
7. Open SQL server and create a new view based on the report used in dspMonitor. Ideally, the report should already contain the fields used in the dspCompose Template. Add any that are not part of the report. Only select the fields used in the template recording.
8. Alias all field names to exactly match the technical field names, referencing the excel file generated in step 6.
9. If a D0110 field is used in the recording, add a column by hard coding a ('X') in the column and aliasing it as [RF02D-D0110]. This will ensure proper updating.
10. Save the file similar to the report name and add the suffix 'Import.' Without this suffix, the system will not recognize the view as an import view.
11. Back in the Vertical View of the Data role at the request level, select the data source ID allowed in step 3.
12. Select the view name. Add a where clause if necessary.
13. Click Import View Data.
14. Data is now ready for remediation in the request.

BackOffice Associates offers professional, instructor-led training in an interactive hands-on style. To view the latest schedule of classes currently offered, visit http://www.boaweb.com/company/product-training/