Hi all,
Hope you can help me with this problem.
My client has an implementation of GP Analysis Cubes for GP 10.0. The version of cubes is 2005.
We have a problem whereby for some accounts open year transaction debits and credits in the GP DataWarehouse do not match the corresponding amounts in GP source table GL20000. The corresponding transaction amounts in GP source table GL20000 are correct.
In some instances and for some transactions not only the transaction amounts are wrong, sometimes even transaction dates are wrong in the GP DataWarehouse which is really worrying.
The nightly DW SSIS update runs with no problems.
I am very puzzled by this. Questions:
1. Has anyone experienced this problem ? Any idea under which circumstances this could happen ? (e.g. some stray late update of source tables or something)
2. Is there a way to force re-population of transactions in GPDataWarehouse for the offending company and table (for e.g. GLTransactions) ?
3. Can GPDataWarehouse table LastUpdated be used for forced re-population by somehow changing the LastRow and DateUpdated columns to force re-population as the data in the source table is correct ?
4. What would happen if I delete offending records in the GPDataWarehouse ? Would they be re-inserted from source tables presumably with correct values and dates ?
5. More generally, could some explain how the records insert/update in GPDataWarehouse via SSIS packages actualy work for GP Analysis Cubes? What is the logic for records insert/update ? I couldn't find any information on this important aspect nor can I inspect involved SSIS packages as they are password protected.
I really hope that someone can help me.
Many thanks.
Regards,
Davor
*This post is locked for comments