on 02-06-2008 11:27 AM
Hi,
We are using Infocube 0CCA_C11 with DS 0CO_OM_CCA_1. We use 0VTYPE (Value type) to differentiate between Planned and Actual costs.
What we want is to have a snapshot of that information. For example if the budget in the R/3 source system is changed (KP06), the users want to be able to see what the budget used to be before and after the change. Any ideas of how to implement such a solution?
thanks
In DS 0CO_OM_CCA_1 there is a field called VERSN which is mapped with 0VERSION and it should be save a snapshot (version 0 first snapshot, version 1 second snapshot...and so on).
Other idea for snapshot is to include a date in the load and to do queries based on that date as reference.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Oscar,
Thanks for that. The issue is that we've been using different versions and the accounting team wants to move away from that. They want to use a single version. That's why the snapshot is essential.
I think we could use a date for the load as you suggest. The problem is which date... Is there anything in the DS that I can use or do I need to enhance it?
My understanding is that planned data comes from datasource 0CO_OM_CCA_1, whereas actuals come from 0CO_OM_CCA_9 DS. We are using a full upload for 0CO_OM_CCA_1 and an initial with deltas for 0CO_OM_CCA_9.
The deltas and full upload will run once a month. That way there will be a snapshot of the data if we use the request ID. You say that I can use the request ID if I don't compress the cube. I'm not familiar with that functionality. Is compression of the cube recommended for performance reasons? And how exactly do you do, or in my case avoid to do a cube compression? Is it done automatically or is there a specific variant I need to add in the process chain?
thanks for your help
Michalis
I made some changes to the budget in R/3 (KP06) and then ran the full update infopackage for DS 0CO_OM_CCA_1, that contains the planned/budget data.
The system gives me a warning message and shows me the requests with overlap in the cube. Then the system deletes the old request and replaces it with the new one. If I need the request number for the snapshot, how do I keep the requests in the cube?
The compresion is recomended for performance, if you compress the cube, the request id is deleted. The request ID was an idea that you can use if you want. The compresion is done manually o programmed. But if deletion of requests happend is seems not compressions occurs.
The deletion of overlapped request, in your case, it seems to be done because of having only the last plannig version. The deletion of overlapped request is done at infopackege level in data targets tab. Each data target in that tab has a mark which indicates if the overlapped request are deleted based on conditions given. It can be deleted too in process chain with the corresponding process.
If you avoid deleting overlaped request for budget, you can use the month of loading as snapshot too.
Oscar,
That's been very helpful. I've removed the deletion flag in the infopackage but that's doing something I don't want. Obviously, if there are 100 records in the cube and I re-run the infopackage, it adds 100 more records and distorts the data.
So I've decided to create a copy of the Infocube, create a delta transformation between the two, limit 0VTYPE to 20 (planned) in the DTP and load data into the latter Infocube. Now I have my planned data in the second Infocube and they're distinguished by the request ID as you suggested.
However, the users would have to limit their query based on something that makes sense to them. Unlike the request ID, the loading date would be ideal, but I can't find it in the cube. How can I include it? What Infoobject should I be looking for?
Also, is the process I just described an efficient way of fulfilling the requirements?
thanks
Michalis
You can enhance your infocube with a Z infobject for saving a date for example and in update rules you can assign to it today date (system variable sy-datum) in routine.
You can also, instead of date char a calmonth char, derive the month and year from sy-datum and user will able to choose plannig of 01.2008 for example.
| User | Count |
|---|---|
| 3 | |
| 3 | |
| 2 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.