Question:
hi,
when you create a generic datasource, the system does everything itself, naming and so on. If you do it a second time the system recreates the same export datasource again. Is it possible to create a second export datasource from the same cube?
Gr,
M.
Answer:
I know I am not answering the question,
but I wonder why you would do so ?
If the aim is to use less components of the cube, then you should better do it in the infosource using the datasource.
Ch
Answer:
You cannot create a second export data source.
But you can use the existing one. Any reason against that?
Leandro
Answer:
CHC - Why? on user demand...
From one cube (actually it is an APO back up cube) users want to load data on a daily basis. We've got a IO called ZLOADTYPE, which has value "3" for daily load. Now users want to also have a monthly load with value "1" for ZLOADTYPE. If i extract the the two infosources from the same export datasource, I don't think it'is possible to code some abap in TR for ZLOADTYPE to assign value "1" or "3". I can't use the date as the monthly is not always loaded on the same day and when there is a monthly there is also a daily... I could use the name of the infopackage, but when somebody changes it the coding would be f***** up.
So that is why I'm wondering about creating a second datasource from the same cube...
But maybe there is a solution in the APO system, we are talking with the functional people now... I don't know a lot about backup cube, remote cubes, planning areas and so on. Apperently the same data is storred in different "cubes", so maybe I can use two different cubes, but with the same content (data synch???)
Gr,
M.
Answer:
If i extract the the two infosources from the same export datasource, I don't think it'is possible to code some abap in TR for ZLOADTYPE to assign value "1" or "3".
If I have the point correctly,
you can use one infosource for your daily extract, and put there ZLOADTYPE as a constant = 3,
and the other infosource for your monthly extract, putting ZLOADTYPE to 1 in this one ;
both using the same export datasource.
But I guess I didn't understood your problem correctly, because I think you would have been able to understand it on your own (I mean, from the experience you already demonstrated here)>
(I gave my input anyway, just in case)
Ch
Answer:
If i extract the the two infosources from the same export datasource, I don't think it'is possible to code some abap in TR for ZLOADTYPE to assign value "1" or "3".
You're right. You should put the abap code in the update rules.
You should not put abap code in the TR for an export data source anyways, because it's going to be lost if you change the source object.
Leandro
Answer:
CHC,
as far as I know you can link one datasource to exactly one infosource...correct?
to be more clear:
current situation :
Daily:
Exp. DS APO --> BW IS --> Cube
ZLOADTYPE = "3" (Cte in TR)
request:
Exp. DS APO --> BW IS --> Cube (daily)
| ZLOADTYPE = "3" (Cte in TR)
|
|_____> BW IS --> Cube (monthly)
ZLOADTYPE = "1" (Cte in TR??)
I thought I couldn't map the same DS to two different IS...
Problem with coding in TR or UR, so using a daily and a monthly IP for the same IS, is that once data has been extracted, the system is unable to see if it's a daily or monthly load...so I can't fill ZLOADTYPE correctly...
Users want to use ZLOADTYPE as an selection criteria in query to see daily planning or monthly planning figures and totals...
Answer:
Euhmmm, maybe i'm not seeing everything but :
can't you have the following : 1 DataSource > 1 InfoSource (both the generated ones) --> 2 Cubes and then fill ZLOADTYPE in the Update Rules?
You just have to:
* hardcode ZLOADTYPE = 3 in the UR to your 'daily' Cube and ZLOADTYPE = 1 in the UR to your 'monthly' Cube
* have 2 infopacakges (one for a daily load which you send only to your daily cube, one for the monthly load whihc you send only to your monthly cube)
Answer:
TFR,
this would do the trick...thanks.
FYI
I have a second DS in APO. Same data is found in a backup cube and in a planning area. One can create a exp DS from both. Restrictions : You can only extract data from backup cube when the job filling this cube has run (takes a couple of hours). This could lead to a BW loading during working hours (and we don't want that). From the planning area we can extract whenever we want.
So according to time schedule we will make a decision on which of both options to use.
anyway thanks a lot for input.
Gr,
M.
Answer:
Let me know if you go for "my" option, then i can send you my personal account number for billing purposes...
Answer:
Please ignore my last post. I think I will keep away from this site until I got some serious sleep.