Request in Cube

I have requests in cube whihc is not showing up before 1st of may. Is there any setting in the cube which only shows the requests loaded for the month.Is there any way to find out the previous requests or also if who delted the requests.

if load is happening via PSA then by default the retension period will be 15 days, you cant retreive the data older than 1st May.
As far as recovery of deleted request is concerned, then we can do it in "Reconstruction" option available at mamage screen of the cube.
If you really want to get the historical data then check with the source system and so the full load for the desired peiord

Similar Messages

Data Request on Cube

Hi All
I'm new to IP.
I've created aggregation level on info cube then created a input ready query on the cube and I've saved the data on Cube.It's working fine but the data request on cube still stays with yellow.
What's the settings to be done to get yellow request to green.
Regards,
Charan.

For IP and BPS, the status remains yellow only.

Delete overlapping requests in Cube

Dear all,
I need delete the requests uploaded in the previous day when transferring new request into Cube,and the system is BW 7.0,but I use 3.5 data source and infoSource.
The issue is that when I

Tianli,
You can delete the overlapping request in the infocube.
In the infopackage -
> Data Targets -
> Automatic loading of similar/identical requests
You can set the parameter for deleting the overlapping request here.
If you are using process chains, there is a process type available
Load process and post processing-----> Delete overlapping request from infocube.
Can you post your question again as I see it is incomplete..
Sasi

Delete overlapping requests from cube not working in processchain.

In a process chain, 'deletion of overlapping requests from the cube ' step is used.
Before this step a DTP step runs with a full update to load the cube. This process chain is scheduled every day.
Issue is, the process chain failed at the DTP step and after correcting and repeating, the step got executed.
However, the next step after the DTP,'delete overlapping requests from the cube'
gets executed but without deleting the previous day's request.
In the step details a message that 'No request for deletion were found' can be seen.
Then next day when the DTPstep is executed without any problem the 'delete overlapping requests from cube' step is successful
and the previous requests from cube are deleted.
the deletion selections in the step ' delete overlapping request from infocube' is
Delete existing requests
Conditions:
only delete requests from same DTP
Selections
Same or more comprehensive
Because of this issue on a particular day because of the presence of 2 days requests the data is getting aggregated and shown as double in the reports.
Please help.

Hi Archana,
When you delete the bad request from target and before repeating your DTP in PC, make sure the bad request deleted from table RSBKREQUEST also.
If you find the same request in table, first delete the request from table and repeat the DTP in PC.
Now Delete overlapping step should work.
As this is not the permanent solution, please raise an OSS for SAP
Regards,
Venkatesh

Delete request in Cube - Urgent

Hello,
I am not able to delete the red request in Cube and the request in DSO were deleted.When i try delete the request, it'll be there in the cube.Please do let m,e know, what i have to do for this issue.
Thanks,
Madhu

Hi,
Are you loading data from ODS to CUBE?
If yes first delete the datamart symbol in ODS and then Change the request QMstatus to RED for CUBE and Delete it now.
NOTE:Assign pts if it helps.
Regards,
Arun.M.D

Deleting requests from Cube with code using infopackage with two targets

hi experts,
Working on BW 3.5.
I am creating a process chain to load from a table in a source system to two Infocubes.
In the start routines of the update rules depending on the date of load, if it is not the last day of month InfoCube A will be loaded with data and InfoCube B will have Datapackage deleted but a request will still load but will contain no data.
And vice versa if it is the last day of month.
In InfoCube A I only want to retain a rolling 15 days of data and have entered a "Delete Overlapping Request from Cube" step.
In the "Deletion-selections" of this step I have added a "Request Selection through Routine" and put in the following code;
del_date = sy-datum - 15.
loop at l_t_request_to_delete.
    if l_t_request_to_delete-timestamp+0(8) GT del_date.
      delete l_t_request_to_delete.
    endif.
endloop.
My question is, how can I ensure this delete code will only work for InfoCube A, as I only want the rollings 15 days of data in here, in Infocube B I want to store all the requests that are loaded here for the end of month.

Hi
Try in some sql browser with outer joins and you will see the problem.
select *
from (select nvl(leverklant.klant_code,'-1') fk_cube_abonnementen_kla_code,
     nvl(factuurklant.klant_code,'-1') fk_cube_abonnementen_kl2_code
     from ods_titsub
     left outer join dim_klant leverklant on (leverklant.klant_code = ods_titsub.cust)
     left outer join dim_klant factuurklant on (factuurklant.klant_code = ods_titsub.sta_cust)
     where (case substr(ods_titsub.isbn,1,8) when 'FBVISTAQ' then 'J' else 'N' end) = 'N'
     and ods_titsub.rec_sta <> 'X'
     and ods_titsub.curr_start >= to_date('01011999', 'DDMMYYYY')
     and ods_titsub.curr_start <= to_date('01022008', 'DDMMYYYY')
     and (leverklant.klant_sk is null or leverklant.klant_sk = leverklant.dimension_key)
     and (factuurklant.klant_sk is null or factuurklant.klant_sk = factuurklant.dimension_key)) a
left outer join dim_klant b on
     b.klant_code = a.fk_cube_abonnementen_kla_code and
     b.dimension_key = b.klant_sk and b.klant_sk is not null
left outer join dim_klant c on
     c.klant_code = a.fk_cube_abonnementen_kl2_code and
     c.dimension_key = c.klant_sk and c.klant_sk is not null
Regards
Result will be like:
FACT_TABLE DIM1 NULL
FACT_TABLE NULL DIM2
but never like:
FACT_TABLE DIM1 DIM2
Message was edited by:
Armands

When do we compress the request in cube. ?

Hello all,
We have been live for a few months now. After how many days/weeks/months should we compress the request in cube. ?How often do we have to compress the data in the cube.
I know once compress than we cannot delete the data by request but we there is an issue and we need to delete data completely from the cube that is possible right ?
Thanks in advance

How often Compression needs to be done depends on the volume of data that is loaded everyday. Unless the volume of records loaded everyday is unusually high, doing compression once a week might be good enough.
Also you are right abt losing the ability to delete by request in the infocube after compressing the request. But we dont necessarily have to delete the whole cube incase of issues. There is always the option of doing 'SELECTIVE DELETION'.
Next, when doing the compression you have an option of mentioning the date range. Choose the option of compressing requests that are older than 4 days (arbitrary) to have a buffer for deleting the request incase of issues.
Hope this helps!

Request in cube is not avilable for reporting, how to trace this in chain?

Hello,
We have cube that gets the delta daily.
Some day, some body did full load and its failed.
Regular process chain delta load were sucessfull but they never turned reportable since the previous full load was failed.
Since we have not received any failure notification.
Is there way we can find if the request is not reportable to get notification>?
I have checked the avilable process types, it looks like we need to build custom process type.
Please advice.
Cheers
Angelo

Hi Angelo,
If the full update is run via a process chain then you can configure for that chain that if the load fails you get an email notification,
in the setup of the email notificaton you could make a reference to the target cube and then at least you know that if you don't fix this issue subsequent requests will not be available for reporting in the cube.
Best Regards,
Des

Identify ODS change log request from Cube update rules init routine

Hello all.
I need to use a logic in the Start routine of a cube, whcih change log request are move from an ODS when doing a delta.
Anyone knows if this is possible???
Thnaks and best regards,
Alofnso.

Hello Oscar.
Basically my requirement is to do a selective deletion of the cube, before I load the new data, but the selective deletion has to be done according to some fields of the data that is going to be load to the cube.
That´s why I need this.
Best Regards,
Alfonso.

Delete Overlapping Reqeust in DTP deletes more than one request from cube

Hi all,
I have selected the following options in delete overlapping request as we need only one request in the cube.
Delete existing requests
Only delete request frm same same DTP
Selections are
Same or More comprehensive
Scenario is:
DSO>DTP>Cube
I have set this delete overlapping request in the DTP (in a processchain).
Now at the time i added this step in Process chain, there were two requests in the Cube (both with the same DTP but first one was 2009 data and second was 2010 data)
Need was to delete only the latest request from the cube ie 2010 data.
As per my understanding, i assumed delete overlapping will delete only ONE request i.e. the latest one from the cube with 2010 data. But when i ran processchain, it deleted both the requests.
Is that the functionality or is there something I am missing? We need to retain 2009 data and overwrite 2010 data with the new request.
Suggestions please.

Hi,
I suspect that you have not set any DTP filter criteria. Is this the case?
Are these requests delta DTPs or full DTPs?
Have you read/applied these notes:
1155723 P18:DTP:PC: Deleting overlapping DTP requests in PC
1318438 P21:DTP:PC: Change of instance when DTP in PC repaired
1147766 P18:PC:DTP:Select only full DTPs for overlapping deletion
1336410 70SP22: Enhancements to CL_RSBK_DTP=>GET_ALL_BY_PROPERTY
Rgds,
Colum

Problem while deleting overlaping request from cube

Hi experts,
I have one process chain in which i have one step where i am executing one DTP to load one cube and in next step deleing overlapping requests from same cube.
i am getting error at that step "Error when deleting requests for comparison request DTPR_4CCDXZLK1OIGCVGGE1PP31Z3Y"
what could be reason?
plz help

Hello,
I guess you have not defined the overlapping variant properly.
Please goto the definition of the variant and check for the right DTP input.
Then at the bottom, select second option "Edit all Infocubes with Following Delete Selections"
Click on deletion selections -> select delete existing requests.
Also select if same datasource and source system. and importantly select the radio button as overlapping.
Then save the variant. and try to use it.
Regards,
Shashank

How to delete the previous request in Cube ?

Hi All
I have 2 sources loaded to Cube..
Ex:
ODS A --> Cube 1
ODS B --> Cube 1
Today they 31.10.2011 for both in CUBE1
so it becomes...
ODS A --> Cube 1 --> 31.10.2011
ODS B --> Cube 1 --> 31.10.2011
tomorrow they load... CUBE 1 shld be..
ODS A --> Cube 1 > 31.10.2011--
DELETED
So finally my cube has only following requests..
ODS B --> Cube 1 --> 31.10.2011
ODS A --> Cube 1 --> 01.11.2011
ODS B --> Cube 1 --> 01.11.2011
ODS A request which is older than 1day must be deleted before loading the next day...
Can I use DELETE OVERLAPPING requests for this requirement? I am not too sure...what are the steps to be created..?
as I tried but it was not successful.
can anyone help me with IDEAS or steps??
thanks a lot

yes, you are right. You should use Delete overlapping request option.
If it is not working, please let us know what option did you select for overlapping request deletion, may be you missed something there because overlapping request deletion is the best fit for your requirement.
One thing you need to make sure that loads on both the days are done through PC only.
If you do a manual load on 31.10.2011 and then PC loads data on 01.11.11, overlapping request deletion step will not delete the request loaded manually on 31st but if loads are done throught PC only, there should not be a problem.
Regards,
Gaurav

Deleting Request from cube based on Selection Condition

HI All,
I have a scenario where i have three selection condition while i update from ODS to CUBE . I keep getting differnet versions of the file so the latest version should replace the old version , to do this i tired using the option
Delte Request from Info Cube after Update in the Data Tagets tab
And the Radio button Overlapping is checked . ( This is not working )
The three selection conditions in Info Pacake are
Reduest id from ODS : 11111
Cal Month                 : 20072
File Type                   : B
The selecion condition for the second Version in Info Pacake of the same file that should replace the first file in cube is
Reduest id from ODS : 22222 ( The request id is RID in the ODS for second file )
Cal Month                 : 20072
File Type                   : B
so can any one let me know how can i achvie this ........

Hi Abraham,
   You select the variable deletion conditions when you schedule the InfoPackage that is going to load the new data. On the Data Targets tab page in the Automatic Deletion of Similar/Same Requests from InfoCube column, you click on the pushbutton to go to the Deletion of Requests from the InfoCube After Update dialog box.
Here you determine under which conditions existing requests are deleted from the InfoCube:
·        You can include update modes, InfoSources, DataSources, and source systems for requests.
Example
Requests are deleted when the appropriate deletion conditions are met if existing requests and new ones were loaded from the same DataSource.
·        You can determine whether the selections for the new request need to be the same as or more comprehensive than the selections of the request that is to be deleted, or whether the selections for the new request need to completely or partially overlap the selections of the request that is to be deleted.
·        You can specify deletion restrictions according to date. This means that, when the deletion conditions are met, only those requests that were loaded within a specific time period are actually deleted.
Example
If you choose Data for the Request from the Last Seven Days, only those requests are deleted that have been loaded in the last seven days.
·        You can specify situations in which a request is not to be deleted, even if the appropriate deletion conditions are in place.
Example
If, under Exceptions, you choose the Today is the Last Day of a Month, existing requests are not deleted, if the new request is loaded on the last day of a month.
·        Another option for determining deletion conditions is creating a user routine for the InfoPackage and the InfoCube. In this routine you can exclude requests from a deletion process or include additional requests for deletion.
Check conditions again, it will work, if selection and data source is same.
Hope it Helps
Srini

How to delete perviously loaded request from cube

Hi All,
I am loading a standard cube from r3 w/o PSA through DTP.
1 ) how to delete data automatically from cube w/o using Process chains.( previously we have a facility in Infopackage to delete old loaded data ) .In BI7 how to delete the same automatically.
2) How to schedule the DTP to run on daily basis( w/o process chain ) .I am not able to schedule it via RSRDA ?
What might be the reason ?
Regards
KK

Chivukula,
I'm curious as to why you aren't using the process chains. There's now a "delete overlapping request" process type within rspc.
You are right thought, the DTP does not offer a facility to delete out the old loaded data. This feature is not in BI 7.0
As for scheduling a DTP to run daily, there's no way I know of to run it daily without rspc. Yes I understand that rspc could get very messy but just create a separate holding area, say DAILY DTPS and put your DTP's in there.
Cheers,
Pom

Delet request from cube

Hi,
I need your help,
i want to delete a request from a cube with the process "delete request in Infocube". But my problem is I want the deletion sections Is yesterday or today, only delete request from same DTP, New request will be loaded on (2 day of a month) BUT I dont want the selection restriction, because every day I want the last view (sy-datum - 1). I only want to save the last day of the month.
example
load from 31.08.2010
load from 30.09.2010
load from 01.10.2010 (deleted the day 02.10.2010)
load from 02.10.2010 (deleted the day 03.10.2010)
load from 03.10.2010 ...
any suggestion?
regards,
victoria

Hi,
Check the process "Delete overlapping requests from infocube".
Select radio button "Edit All infocubes with following delete selections" & press button Delete Selections > Delete existing requests>conditions : data sources are the same --> selections are : same or more comprehensive -->Request date is in the current month --> Exceptions : new request will be loaded on 1st day of the month (if it's running everyday including weekends)
--Akashdeep

Request in Cube

Similar Messages

Maybe you are looking for