DSA Quality Assurance (QA) / Testing Phase

From DataSelf Knowledge Base
Jump to navigation Jump to search

After a new DataSelf Analytics connector has been installed, one of the most important tasks is to be sure that your data and business rules are being correctly captured by the BI platform. You sure do NOT want to give end users access to dashboards and reports if the data is incorrect.


During the data quality assurance (QA) process, your team double-checks the information from your DataSelf system against your source system. They should match 100%. If they don’t, the DataSelf implementation team must be informed where the specific discrepancies are.


Be sure to include as many details as possible so the DataSelf deployment team will go straight to the issue (for instance, invoice number XYZ for product YZW on source system shows $1,000 and $500 in DSA). Note: you do NOT need to move forward with the QA from the same QA workbook since it’s possible that fixing one of the inconsistencies will fix them all (at least all associated to the incorrect business rule).


Procedure to do quality assurance - DSA v9

- Requirements:

  • Access to your DSA Web Server.
  • You should be a licensed DSA user with proper security credentials for the QA's project and workbooks.
  • Note: remember that the data on your DSA is not directly connected to your data source, but refreshed on a schedule basis.


- Procedure:

- Watch video: https://www.youtube.com/watch?v=-VfMbjDwoZA

- Or follow these steps:

  • Open a web browser and go to your DSA Web Server URL.
  • Log in.
  • Click "QA Quality Assurance" project.
  • Click a QA workbook. Ex: "QA SA Sales Analysis" or "QA AR Open Receivables".
  • Click the first view and follow the instructions posted on the "QA Procedure" section.
    • If you find inconsistencies, you do NOT need to move forward with the QA from the same QA workbook since it’s possible that fixing one of the inconsistencies will fix them all (at least all associated to the incorrect business rule).
  • After the test results from a view match 100% with your source system, go to the next view and follow the "QA Procedure".
    • To go to the next view: click the next tab right above the report's title, or click the QA workbook name and click the next view.
    • Repeat this step for all views on this QA workbook.
  • The QA phase for a given workbook is completed once the results from all its views match 100% with your source system reports.

Contact support@dataself.com for further assistance.

Procedure to do quality assurance - DSA v7 and v8

- Requirements:

  • DSA Desktop.
  • A DSA QA workbook (twb) for the data connector you want to test. Visit: DSA - How to Restore QA/Testing Workbooks
  • Knowing the basic DSA Desktop navigation techniques.
  • You should be a licensed DSA user with proper security credentials for the data connector you want to test.
  • Note: remember that the data on your DSA is not directly connected to your data source, but refreshed on a schedule basis.


- Procedure:

  • Open the QA workbook (twb).
  • You’ll find a few tabs at the bottom of DSA Desktop. Each tab will be associated to a dimension from the data panel.
  • For each tab, run the following procedure:
    • Open the tab.
    • You’ll view a query showing a reporting parameter on rows and a column for last year with a measure in descending order (for instance, last year’s sales by customer sorted in descending order by top sales).
    • Go to your source system (ex.: ERP and CRM) and run a report that shows the same data (ex.: last year’s sales by customer sorted in descending order by top sales).
    • Now compare the grand totals between DSA and your source system report. Do they match?
      • Yes. Great!
        • Move to the next tab and repeat the procedure.
        • All tabs covered? Great! QA for this connector is done!
      • No. Ok, odds are that you’ll find inconsistencies looking at larger amounts.
        • Pick the top line from both reports and see if they match.
        • If they match, go down the list until you find a line showing an inconsistency between the two reports.
        • Now you need to find one or two underlying transactions that are causing the inconsistency: Use the drill drown from year > quarter > month > date on DSA and look for equivalent reports from your source system. When you find one of two transactions that are not matching, stop QA and report this to your DSA deployment team and wait. Be sure to include as many details as possible so the DSA deployment team will go straight to the issue (for instance, invoice number XYZ on source system shows $1,000 and $500 in DSA). Note: you do not need move forward with the QA from the same data source since it’s possible that fixing one of the inconsistencies will fix them all (at least all associated to the incorrect business rule).

Contact support@dataself.com for further assistance.

Tips

Comparing SA sales by Salesperson

Note that:

  • The SA Sales report lists salesperson that is listed on the Invoice header, not the default Salesperson on the Customer masterlist (which is labeled Account Manager)
  • The SA Sales report is just for the line totals, and does not include Invoice Header amounts such as Freight, Sales Tax or Header Discount
  • The report is for actual line sales (and misc charges), which are not necessarily the same as commissionable sales

Then compare some particular invoices, by invoice number, in the ERP and in DataSelf for that salesperson.

  • Are the invoice numbers assigned to the same salesperson?
  • Or do the invoices show a different amount?

QA for specific ERP's

Sage 100 (MAS)

SO Sales Order

Use the "Sales Order Quote History" report to compare Booked values.

Sage Pro

Accounts Payable

Only the AP report "by Transaction Date" gives the total open AP.