Question:
Hi all,
There is a cube known as Contacts Cube.
Data will be loaded into the Contacts cube weekly. During a given month, contacts are classified into different categories. For example, a contact may be called a complaint, inquiry, or testimonial within a workstream. Throughout the month, the categorization of a contact may change, say, to a promotion and wouldn’t be included in the extract and loaded into the workstream. However, since the prior week’s load included it as a complaint, inquiry, or testimonial, it’s still reported in the Contacts Infocube and there isn’t a transaction record negating this contact. In which case, contacts are overstated.
There are several options that have been investigated:
• Delete the cube and reload it every month. However, the reload would contain 2 + current years which is an expensive process.
• Create two ODS (current month & finalized month) to load into one ODS. At the end of the month, delete the current month requests and load the contacts cube from the finalized month ODS.
• Load only monthly rather than weekly.
Please suggest if you have a better way to solve this issue.
Many Thanks!!
Isaac
Answer:
Is this soo tough ??
Answer:
I can offer this...
We have two scenarios at my organization that may be relavent to this discussion.
Open Sales Orders. This is a complete dump and re-load every night to essentially manage the status of Open or not. The volume is relatively small compared to your 2 years worth of history so dumping and re-loading is not an issue for us.
Contract Status. In this scenario a "recursive" InfoPackage reads data from the Contract Status ODS, evaluates the contract record and write back the current status.
The Contract Status scenario is probably the better of the two for you however our process is at the ODS level and not the cube although the data does eventually make it into a cube for reporting.
What I might suggest is have whatever "1st level" ODSs you will have, add a 2nd level for managing contract status, add a recusive process to update the status, and then send the delta to your Contracts cube.
Do you think that could work for you?
Answer:
Hi,
I appreciate ur response but could you be more ellaborate in your explanation?
Many Thanks!
Isaac
Answer:
I don´t know how difficult could be to include the "promotion contact" on the extract..
But if you do, and create an ODS as a first step and then fill the cube
from the ODS on a delta load, you will get what you want.
And you could filter the querys to exclue de promotion contacts.
It´s just another idea.
MMorales