By far the most common support ticket received by 9Dots, and what are usually the easiest tickets to diagnose, are those that deal with seemingly incorrect data. Whether it be actual, budget, or forecasted data, it is a product of the same process:
Your ERP system -> our SQL database -> proCube Xchange cube -> proCube Submodule cube
The proCube xChange cubes house nothing but raw, actual data from SQL. There are no formulas, and the data housed in these cubes should be an accurate reflection of the data in your ERP system.
The proCube submodule cubes (FinRep, Compensation etc.) are the cubes that put the data from the Xchange cubes to work. Through various formulas and dependencies, the submodule cubes construct your forecasts for the final product to be published in reports.
If you ever come across data that seems incorrect, there are a few steps that you can follow to ensure it is an actual issue, versus a simple oversight.
If you are in a onePlan Excel report:
- In order to identify the cube the report is referencing, from anywhere within the report hold Control-U, and that will present the design page of the report.
- Be careful not to alter anything within the design page.
- FinRep <- X Ledger Balance or GL
- FTE & Headcount <- X FTE or FTE & Headcount Xchange
- Employee <- X Employee or Employee Xchange
- Compensation <- X Compensation or Compensation Xchange
- Revenue <- X Revenue or Revenue Xchange
There are certainly going to be data related issues that fall outside the realm of these directions, and those issues will require us to look at the appropriate formulas and dependencies, which we do not expect you to do. If you believe the data in question is a result of you or colleague’s work within the formulas or dependencies, it may fall under billable time for us to correct it. However if you have run through these validation steps and still believe it to be an issue with our system build, we will be glad to fix it.